I'm trying to tag a build with "Tag this build" and use that build's workspace, not the workspace revision.
For instance, I set up Jenkins with my repository. Every time it does a build it creates a text file called buildnum.txt. The only thing in this text file is the current build number. So build #4 has 4 inside the text file, Build #16 has 16... etc. This buildnum.txt is packaged inside of a .war file. The reason for this, is so that I later know which build the war file came from. So If I go back to build #4 (and the latest build is #16) and tag it, I want, in the tags part of the repository, to have the war file with buildnum.txt that says "4" I believe the issue I'm having right now, is that I'm doing manual builds where the repository hasn't changed (right now just for testing). Therefore, the revision number is staying the same, but the buildnum.txt is changing. For instance, I just clicked "Build Now" and Build #364 succeeded. A .war file was created with buildnum.txt inside that says 364. The build says "Revision: 220 No changes" and when I click "Tag this Build" the Module URL says "https://name/svn/test/HelloWorld/trunk (rev.220)" If I click tag and go to the repository and under tags select the new tag I just created. The text file says "344" not "364" as I want. I'm assuming this is because the trunk hasn't changed at all since build 344, so it is using what was last changed. Is there a way to do this? I'm also open to better ideas. Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
