-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-41591] Fix pipeline support using TransientActionFactory #55
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some breaking changes, but it should work well. Some integration tests would not hurt
I'm a user of this plugin (thanks, it's been really helpful!) and would love to see this update landed. Sorry I can't add more than my verbal support here. |
828fd8c
to
2c0da93
Compare
Rebased to master. |
I'm fine with this. I'll take en extra look this evening, and we'll see if can get it merged. |
Hmm.. Can you make the old action invisible (e.g. nulling the url/name/image) and allow the transient action factory to produce a superclass of the RebuildAction (TransientRebuildAction or similar) and allow that one to be visible instead? This way you could ensure only one action is visible, but don't have to write the boring migration stuff (or resave all the builds). |
Ping @Dohbedoh |
370af40
to
316c049
Compare
@GLundh Added a transient field to control this. |
@reviewbybees
Fix pipeline support, using a
TransientActionFactory<Job>
and aTransientActionFactory<Run>
.Note: Existing builds may have a duplicate "Build" link in the UI because of the non transient action added by previous version of the plugin. We could add a "migration" method although this will be fixed over time once new builds are being scheduled and old build discarded...