-
Bug
-
Resolution: Not A Defect
-
Major
I set up a parametrized job which correctly uses the git tag parameter to build a specified tag.
Then I set it up to trigger another job and passing that tag as parameter, with no success so far.
The triggered build of the second job receives and lists the parameter in the "Parameters" section, but doesn't use it at all and thus builds the default branch instead of the tag.
I tried multiple combinations of configurations both in the first and in the second job, with no success so far.
So I'm basically asking for a follow-up / hint / RTFM + link to the M
[JENKINS-15214] Triggered build correctly receives git tag parameter but doesn't use it at all
William Ghelfi
added a comment - Update:
There's a "parent" issue with the git parameter plugin.
Stay tuned while I check if this ticket is valid at all.
William Ghelfi
added a comment - Update:
There's a "parent" issue with the git parameter plugin.
Stay tuned while I check if this ticket is valid at all. William Ghelfi
added a comment - There's an issue with another plugin (see comments), thus this ticket is to be considered as "invalid" at the moment.
William Ghelfi
added a comment - There's an issue with another plugin (see comments), thus this ticket is to be considered as "invalid" at the moment. William Ghelfi
added a comment - invalid 
Update:
I just found out that the plugin worked only the very first time and only for the first job.
Now Jenkins is ignoring any configuration of the plugin I throw at it for new jobs, while even the first job got problems: it's stucked with the very first value of the tag parameter I configured the first time, and any attempt to change it in subsequent builds is ignored by Jenkins.
T_T
I'm going to delete all the jobs, uninstall the plugin, reinstall / recreate all and letting you know.