[JENKINS-28689] Make compatible with Workflow plugin#4
[JENKINS-28689] Make compatible with Workflow plugin#4stephenc merged 31 commits intojenkinsci:masterfrom
Conversation
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
There was a problem hiding this comment.
Extending ExternalResource and using a @Rule would be better style.
There was a problem hiding this comment.
(Though beware that I recall some problem with RestartableJenkinsRule not handling @Before/@After. Not sure if that also applies to extra @Rules.)
There was a problem hiding this comment.
@jglick I checked, does not work fine. I decided to remove it.
|
🐛 the |
…tephen's recommendations
|
@stephenc The Serial Version UIDs has been reviewed. I have to investigate how the JVM works in theses cases. |
There was a problem hiding this comment.
🐜 normally I would include a comment to explain that this was generated from the 1.7 version of the class and also include a @since 1.8 javadoc comment, e.g.
/**
* Ensure consistent serialization. Value generated from the 1.7 release.
* @since 1.8
*/
|
I've only 🐜s so here is my 🐝 (obviously I'd prefer if you fix the 🐜s but I am no longer blocking on the changes proposed) |
…UID was generated from 1.7
|
@stephenc I don' like 🐜 in my PRs ;) |
|
🐝 |
|
🐝 again. (One of the two comments about |
|
@reviewbybees done |
|
This pull request has completed our internal processes and we now respectfully request the maintainers of this repository to consider our proposal contained within this pull request for merging. |
|
As principal author of this plugin, and as the plugin was developed on CloudBees, Inc. time, I view this plugin's maintainers as including any CloudBees engineer. There seems to be some permissions problems on this repo at the present time, so I am merging this on behalf of @recena until he gets his permissions fixed. |
[JENKINS-28689] Make compatible with Workflow plugin
|
👎 for 31 unsquashed commits |
|
@KostyaSha Thanks for your feedback |
|
@recena i'm not against content, i'm against 31 commits for one feature. This is unreal headache for history. And it not even a refactoring... |
|
@KostyaSha as a maintainer, I prefer unsquashed commits in plugin repos that I am a maintainer of |
|
@KostyaSha In this case I considered that the commits were important. They are telling the path until the final solution. Anyway, thanks so much for your advice. |
|
Filed JENKINS-29810 for stronger restart behavior. |
There was a problem hiding this comment.
Isn't <optional>true</optional> missing here?
This is gonna make compulsory the installation of that part of the workflow plugin when using ssh-agent, right? For me, it does not sound totally right. Or I'm missing something?
I read the feature that requested that PR as: "if workflow is present, then contribute a step to it [but if absent, then just stay still]"
There was a problem hiding this comment.
@batmat they are adding hard dep to workflow-step-api in all plugins. Even credentials-binding. I got reply that they (CB) don't care :(
There was a problem hiding this comment.
No problem @recena see also the question on dev list that triggered this discussion just in case https://groups.google.com/forum/#!topic/jenkinsci-dev/K7pf_W8NgqA
Downstream of jenkinsci/pipeline-plugin#161
https://issues.jenkins-ci.org/browse/JENKINS-28689
SSHAgentStep,DescriptorImplandSSHAgentExecution