Recent we have faced issues with the Workflow-Listener JIRA plugin, which was developed using by Atlassian SDK, this plugin does link automatically created JIRA ticket in the BAMBOO’s comments section and also allows to trigger UAT/PROD deployment plan triggering form the JIRA using workflow status transitions. Required features are…
1)Automatic JIRA Ticket Linking: It automatically linked the newly created JIRA tickets within the relevant Bamboo build’s comments section. This ticket created for every new build happened in another BAMBOO’s build execution.
2)Deployment Triggering: It allowed for the triggering of UAT/PROD deployment plans directly from JIRA via workflow status transitions. But unfortunately, this Workflow-Listener stopped working due to latest JIRA upgradation to version 10.3.5, where there is no SD compatible version available in the Atlassian’s marketplace. Hence, please help us to find the way to achieve this functionality using nay readymade plugin or let us know how to achieve this? We have known about the JIRA webhooks, but it allows only to trigger BAMBOO plan, ,but how to achieve automatically created JIRA ticket linking in BAMBOO’s Comments section. This is caused PROD work delayed form long time, so please help us to find the best way to provide deployment our requirement.
Hi @DevendarGangapuram,
Please see this discussion thread New version of SDK coming? - #17 by richard.white which provides some information about how you can workaround this.
Cheers!
Mel
1 Like
Thank you so much, @mpaisley, let me check and try the work around and then get back you the updates here.
Hi,
Today, I am experiencing the error related to the “jira-stats” thread.
Understanding the Context:
The “jira-stats” thread is a scheduled job that runs periodically to collect and log performance data. The Invalid use of RequestCache error it generates is not a problem with the stats-gathering itself but with an underlying API call that is incorrectly being made outside a proper request context.
Error:
… jira-stats-0 ERROR [c.a.j.cache.request.RequestCacheRecorderImpl] Invalid use of RequestCache by thread: jira-stats.Incorrect usage of JIRA API. You can only create/use: RequestCacheImpl inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtil for details. This message will be logged once per thread. This ERROR should be fixed on the caller side (check the stack-trace or thread-name) as it is causing inconsistent data.
java.lang.Throwable
at com.atlassian.jira.cache.request.RequestCacheRecorderImpl.errorLogOOCThreadUsage(RequestCacheRecorderImpl.java:32)
at com.atlassian.jira.cache.request.RequestCacheRecorderImpl.recordRequestCacheOOCUsage(RequestCacheRecorderImpl.java:25)
at com.atlassian.jira.cache.request.RequestCacheImpl.get(RequestCacheImpl.java:46)
at com.atlassian.jira.config.feature.DefaultFeatureManager.isFlagEnabledByExternalActivator(DefaultFeatureManager.java:331)…
Please let me know how to get rid of this issue , which is causing from long time.
Thank you,
Dev G
Hi @mpaisley ,
I had tried applying the changes mentioned in the article, but no luck,
New version of SDK coming? - Atlassian Developer Tools - The Atlassian Developer Community.
Please share your thoughts/ideas on the above issue please.
Thanks,
Dev G
Apologies, @DevendarGangapuram but I haven’t worked on the Atlassian SDK team in over 6 years now, so I think your best bet would be to ask someone who commented on the thread i linked you to last year.