-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Platform: All, OS: All
With my hudson.ramfelt.se server, i have several nodes contributed by different
persons and some of them are not properly setuped for releasing hudson plugins.
ie, they havent added the subversion credentials to the subversion cache (not
Hudson's svn credentials). To do that the user must run "svn -list
https://hudson..." (as discussed at http://wiki.hudson-
ci.org/display/JENKINS/Hosting+Plugins)
I have jobs that are being built by two nodes, but it is only one that I know
have done the "svn -list". Therefore I would like to specify what node I want
the release to be done on. Also, I would like to be certain that it will be
released by a specific user and not the user that is running the node.
[JENKINS-4500] Make it possible to select a node to do the release on
Note: code required in order to implement this may have been added in Jenins 1.416 (Plugins can now override where jobs are executed).
send a pull request: https://github.com/jenkinsci/m2release-plugin/pull/3
the pull request does not full follow the proposal of this issue, but if the user also installs the 'nodelabel-parameter-plugin' (https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin) he is able to configure it the way he wants it.
Code changed in jenkins
User: jtnord
Path:
.gitignore
src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java
src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly
http://jenkins-ci.org/commit/m2release-plugin/a1ddf1da50f48bb7eabee11871ea33e25948262e
Log:
Merge pull request #3 from imod/build-params
add support for build parameters in maven release
In addition to the normal release parameters, the 'normal' build parameters are shown and can be modified too before triggering a release build.
This fixes or supports the following currently open issues:
JENKINS-10127: M2 Release plugin ignores parameters from a parameterized buildJENKINS-4690: Be able to arbitrary paramterize m2 releasesJENKINS-4500: Make it possible to select a node to do the release on (together with the nodelabel-plugin)JENKINS-4958: add switch for -DdryRun=true
Compare: https://github.com/jenkinsci/m2release-plugin/compare/418a96c...a1ddf1d
I don't think it makes sense for a plugin to assume that releases needs to be
done on a different subset of nodes — I mean, it's not worth the price of an
additional text box, IMO.
Maybe Hudson could inject additional components into Maven execution, so that we
can supply credential from Hudson's records?