Plugin functionality differs on remote agents Edited

I recently upgraded from bamboo 5.9 to 6.0 and ran into a strange problem with one of the (outdated) plugins.

Here is the plugin in question: https://bitbucket.org/dehringer/bamboo-newrelic-plugin/overview

Here is the stack trace: https://pastebin.com/hxBJt3NH

After much tinkering this is what I found:

- This only fails on remote agents (windows and linux). Local agents, the plugin works fine.

- Prior to the upgrade, the plugin had a similar, but funcational result. getNameForSentence() function on a TriggerReason object would return 'null' as a string, but not a null pointer. 

- getNameForSentence() function on a TriggerReason object returns a null pointer (obvious from the stack strace). However, getName() and getKey() work just fine

 - getNameForSentence() returns a string along the lines of "was <trigger type or reason> by <user name>".  

Given I can't see the source (that I know of), I don't know what other information/attributes/methods getNameForSentence() is trying to use, and failing just on the remote agents. If I had to guess, based on the result string, the user that triggered the event is unavailable to the remote agent.

1 answer

I recommend to report this issue in the add-on's public issue tracker at Bamboo New Relic Plugin - the add-on's author David Ehringer used to be fairly diligent in keeping his high quality add-ons up to date, but for a new release with breaking changes it can take a couple of weeks of course.

As for looking at the source, you already linked bitbucket.org/dehringer/bamboo-newrelic-plugin yourself, and the Bamboo source code is available for customers with an active maintenance status, see Do I get access to the source code? - you can download the source from the Licenses section on the my.atlassian.com page.

Steffen, there hasn't been a relase of this plugin in over a year. The issues tracker hasn't had any thing for several years. I've requested several times to have an update to this plugin over the last year. 

 

My issue, however, is not with the plugin maintainer, but with remote plugin's functionality being different. The information I provided is because I *already* have the plugin source. What I don't have is bamboo's source, which is where the problem lies.

I see, sorry to hear, and I've indeed misread the source code issue - I've updated my answer regarding access to the Bamboo source code.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,561 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you