Re: Tag this Build - How to tag that build's workspace?
Ya I noticed that. I went ahead and downgraded my subversion to 1.7 so I no longer need it. On Tuesday, August 5, 2014 3:57:04 PM UTC-4, LesMikesell wrote: On Tue, Aug 5, 2014 at 10:22 AM, Eric ericlee...@gmail.com javascript: wrote: Is it safe to create a tag the following way so that I can do what I want? svn upgrade svn copy -m Creating a Tag https:/url/svn/test/HelloWorld/trunk@%PROMOTED_SVN_REVISION% https://url/svn/test/HelloWorld/tags/%Tst Tag% copy C:\Users\user\.jenkins\jobs\HelloWorld_Promote\builds\%PROMOTED_ID%\archive\Test\buildnum.txt C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test svn delete -m Deleting file before updating https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test svn copy -m Adding updated file to tag C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test Doing it this way, I can select a build and promote it using the promote build plugin. It first creates a tag at the builds revision. It then copies that builds artifacts to the workspace so it can then add it to the tag that was just created. If that 'svn upgrade' command actually changes the working copy to a different client level format than jenkins uses, the next build won't be able to update to the next revision. -- Les Mikesell lesmi...@gmail.com javascript: -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Tag this Build - How to tag that build's workspace?
Is it safe to create a tag the following way so that I can do what I want? svn upgrade svn copy -m Creating a Tag https:/url/svn/test/HelloWorld/trunk@%PROMOTED_SVN_REVISION% https://url/svn/test/HelloWorld/tags/%Tst Tag% copy C:\Users\user\.jenkins\jobs\HelloWorld_Promote\builds\%PROMOTED_ID%\archive\Test\buildnum.txt C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test svn delete -m Deleting file before updating https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test svn copy -m Adding updated file to tag C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test Doing it this way, I can select a build and promote it using the promote build plugin. It first creates a tag at the builds revision. It then copies that builds artifacts to the workspace so it can then add it to the tag that was just created. On Thursday, July 17, 2014 4:27:37 PM UTC-4, pcampbell wrote: You can only tag revisions of a file that have been committed to your scm. You would have to commit the change to the buildnum.txt file which would increment the revision number and tag that. Tagging does not make a copy of files from your workspace, it just makes a list of pointers within the scm to specific revisions of a file. If you haven't committed the change, there is no new revision to tag so you will get the last revision that was committed. On Thu, Jul 17, 2014 at 1:10 PM, Eric ericlee...@gmail.com javascript: wrote: 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 jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Tag this Build - How to tag that build's workspace?
On Tue, Aug 5, 2014 at 10:22 AM, Eric ericleesand...@gmail.com wrote: Is it safe to create a tag the following way so that I can do what I want? svn upgrade svn copy -m Creating a Tag https:/url/svn/test/HelloWorld/trunk@%PROMOTED_SVN_REVISION% https://url/svn/test/HelloWorld/tags/%Tst Tag% copy C:\Users\user\.jenkins\jobs\HelloWorld_Promote\builds\%PROMOTED_ID%\archive\Test\buildnum.txt C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test svn delete -m Deleting file before updating https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test svn copy -m Adding updated file to tag C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test Doing it this way, I can select a build and promote it using the promote build plugin. It first creates a tag at the builds revision. It then copies that builds artifacts to the workspace so it can then add it to the tag that was just created. If that 'svn upgrade' command actually changes the working copy to a different client level format than jenkins uses, the next build won't be able to update to the next revision. -- Les Mikesell lesmikes...@gmail.com -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Tag this Build - How to tag that build's workspace?
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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Tag this Build - How to tag that build's workspace?
You can only tag revisions of a file that have been committed to your scm. You would have to commit the change to the buildnum.txt file which would increment the revision number and tag that. Tagging does not make a copy of files from your workspace, it just makes a list of pointers within the scm to specific revisions of a file. If you haven't committed the change, there is no new revision to tag so you will get the last revision that was committed. On Thu, Jul 17, 2014 at 1:10 PM, Eric ericleesand...@gmail.com wrote: 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
