Thanks for your response. I took a closer look at the situation.

It looks very similar to the situation described in the Metrics Plugin blog post, so that's what threw me off.

Neither Green Balls nor JQS Monitoring should be performing any extension list access this early. The former is explained in the blog post even.

Assigning this issue to the two plugins that both appear to contribute to the problem reported here.

I've added a InitMilestone check to the filter. Could you try this snapshot build and report back whether it fixes your issue?

Dear,

Thanks for your help.
We have taken into account the snapshot version enclosed to this ticket on our qualification environment and did not see any regression.
However, there is no big volume on this environment; we will be able to check this in production.

Could you please provide a final release for this plugin ?

Thanks

Dear,

Could you please provide an update on my previous comment ?

Could you please also tell if some changes are planned on the JQS Monitoring plugin ?

Best regards

We really need a MetaExtension extension point stephenconnolly. I fear that code in branch-api could hit the same problem you are apparently solving here but cannot use the same solution as it needs to run before EXTENSIONS_AUGMENTED at least according to the documentation of that milestone.

Code changed in jenkins
User: Asgeir Storesund Nilsen
Path:
src/main/java/hudson/plugins/greenballs/GreenBallFilter.java
http://jenkins-ci.org/commit/greenballs-plugin/0b35cac0ae518c14d1bcf0aa39dfcf694b6c09b5
Log:
Fix for JENKINS-28422

asgeirn Would you mind cutting a new release now that this issue is fixed?

Certainly. Can you confirm that this solves the issue?

Asgeir

Hopefully fixed in release 1.15.

I can't confirm that it really fixes the issue as I don't have a way to reproduce it easily. Will update the issue if that happens again.