Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: m2release-plugin
-
Labels:None
-
Similar Issues:
Description
I am running a maven release on Jenkin using maven release plugin.
Below are the two issue I am facing
- After the successful release build, if I want to see the parameter from Jenkins page, it wont show the parameter used to trigger the particular release. From the left pane on Jenkins page, I am unable to see the parameter used.
- I wanted you do custom tag in git repository after the release. For that i have added a tag <tagFormatName> under the configuration tag in pom.xml. It is still not taking the custom tag and creating the default tag such as projectid-version with snapshot
Attachments
Activity
Thanks
For 2. I will try locally and see if I can replicate it
For 1., It used to work well with Jenkins 1.6.X, where I can see the build Parameter for the Maven release as well. The behavior started changing after I have upgraded to 2.X Jenkins version.
Now with Jenkins 2.x, its not showing the build parameters
Mahendra Singh
added a comment - Thanks
For 2. I will try locally and see if I can replicate it
For 1., It used to work well with Jenkins 1.6.X, where I can see the build Parameter for the Maven release as well. The behavior started changing after I have upgraded to 2.X Jenkins version.
Now with Jenkins 2.x, its not showing the build parameters 1. most likely -> JENKINS-35261 (caused by SECURITY-170) there is a PR you can build and test locally (but tests need to be disabled)
if I understood correctly, I am using m2plugin built out ofbelow git code:
https://github.com/jenkinsci/m2release-plugin
I am using 0.15.0-SNAPSHOt version of the plugin in my Jenkins (2.X).
Let me know if my understanding is in line with yours
Mahendra Singh
added a comment - if I understood correctly, I am using m2plugin built out ofbelow git code:
https://github.com/jenkinsci/m2release-plugin
I am using 0.15.0-SNAPSHOt version of the plugin in my Jenkins (2.X).
Let me know if my understanding is in line with yours I can trying building the PR in my local and see if that works well
Mahendra Singh
added a comment - I can trying building the PR in my local and see if that works well 
2. likely an issue with your pom as all Jenkins does is run the maven command you have told it to.
Take the command that Jenkins runs and use that locally see if it works. if it works locally please provide an example project replicating the issue.
1. is an RFE not a bug - the parameters are not Jenkins parameters.