[JIRA] (JENKINS-37807) Add support of @Initializer(after = InitMilestone.COMPLETED)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev created an issue

Jenkins / JENKINS-37807 Add support of @Initializer(after = InitMilestone.COMPLETED) Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Aug/30 10:09 AM Priority: Minor Reporter: Oleg Nenashev It's a follow-up to JENKINS-37759. @Initializer(after = InitMilestone.COMPLETED) does not work properly now since COMPLETED switch is always the last task. We need a better solution for the task graph. Example: Artificial milestone "COMPLETED_HOOKS_PROCESSED", which does not actually modify Jenkins' initSlate field Handling of default definitions in @Initializer e.g. (after=COMPLETED) should make InitializerFinder to ignore the default before value Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-37807

Re: Add support of @Initializer(after = InitMilestone.COMPLETED) ItemListener.onLoaded can be used to run stuff just before Jenkins.<init> completes. Unfortunately I can find no listener for WebAppMain swapping in the completed Jenkins for the placeholder HudsonIsLoading.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-37807

Add support of @Initializer(after = InitMilestone.COMPLETED)

Change By: Jesse Glick Labels: api

Add Comment