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 <[email protected] <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 > [email protected] <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 [email protected]. For more options, visit https://groups.google.com/d/optout.
