Job Action that is initialized using SimpleBuildStep.LastBuildAction after Jenkins reboot

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Job Action that is initialized using SimpleBuildStep.LastBuildAction after Jenkins reboot

Tal Yanai
Hi,

I have a good working Project (Job) level Action that is being initialized by the build (yet an additional Action) as the latter implements SimpleBuildStep.LastBuildAction.

All works good after the pipeline steps are all done, and the build is over.  I see a link on the left menu (project), and as I clicked on it, there are some functions at the ProjectAction that are being called from within its corresponding index.jelly.

The only limitation is right after the Jenkins server restarts.  The link on the left sideline (produced by that ProjectAction) is still exist, although the Action was not yet initialized (as Jenkins was just restarted, and was yet to run even one build).    

Is there any best practice to avoid this bad UX?  Either eliminate the link from the sideline till the build runs post restart, or somehow initialize the Action even without running the build (once I click on the link).

Thanks,

Tal. 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2c55a596-6a4b-4649-b513-6488aefb2322%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Job Action that is initialized using SimpleBuildStep.LastBuildAction after Jenkins reboot

Jesse Glick-4
On Mon, Sep 9, 2019 at 7:32 AM Tal Yanai <[hidden email]> wrote:
> The only limitation is right after the Jenkins server restarts.  The link on the left sideline (produced by that ProjectAction) is still exist, although the Action was not yet initialized (as Jenkins was just restarted, and was yet to run even one build).

If reproducible, sounds like a bug. I cannot think of any reason why a
Jenkins restart should affect the behavior here; the list of builds is
of course retained.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3UUjErSQ6ENCZNAV6Fjt%3DwjcU4ZAn1d4ozebDpXcfdRg%40mail.gmail.com.