Mark Waite commented on Bug JENKINS-26350

I am unable to duplicate this problem using the Jenkins long term support version, 1.580.2. I tried both a tag as selected by the git parameter plugin, and a tag as selected by a string parameter.

Can you confirm that you can duplicate the problem on the latest Jenkins long term support version? I may be using the wrong steps to duplicate the problem.

The steps I took:

  1. Create a new bare git repository (/var/lib/git/mwaite/bugs/JENKINS-26350.git)
  2. Clone that bare git repository and push some changes to it
  3. Create a tag and push the tag (I created master-tag-01)
  4. Define a freestyle project using that repository as a parameterized build with a Git parameter using a tag
  5. Run the job once so that the list of tags can be read
  6. Confirm the git parameter in the build shows the master-tag-01
  7. Add commits and a tag and push them to the bare repository
  8. Confirm the git parameter shows the new tag
  9. Confirm the build run with that new tag uses the expected SHA1
  10. Remove the Git parameter and replace it with a string parameter
  11. Run the job with that string parameter set to the name of the new tag
  12. Confirm the job uses that string parameter without error and without stack trace
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to