Hello Alex, The revision come from the working copy (in the Job's workspace).
If you want to use the same job for building different content (tags, branches), is the safest way. Regards, 2015-11-16 15:24 GMT+01:00 Alex Kress <alex.kr...@gmail.com>: > Thanks Manuel, will try this. Does this mean that Jenkins stores the > revision of the last checkout separately somewhere in Workspace, which will > get deleted with this option? Or does this alternatively prevent it from > detecting the revision number of the previous checkout? > > On Monday, November 16, 2015 at 9:07:41 AM UTC-5, Manuel Jesús Recena Soto > wrote: >> >> Hello Alex, >> >> Try to use the option "Always checkout a fresh copy" in Check-out >> Strategy: >> "Delete everything first, then perform "svn checkout". While this >> takes time to execute, it ensures that the workspace is in the >> pristine state." from official documentation. >> >> Regards, >> >> 2015-11-16 14:59 GMT+01:00 Alex Kress <alex....@gmail.com>: >> > Hi, >> > >> > I was advised by Manuel Recena to post my question here, hoping you can >> > help >> > me with a problem I've been trying to resolve for quite sometime without >> > any >> > luck. >> > >> > I am using Genkins SVN plugin (thank you :) ) to run my CI. My jobs are >> > slightly unusual as I use the same job to run tests on multiple >> > branches. I >> > have the following branches: >> > >> > trunk >> > QA >> > unstable >> > >> > The job is parameterized to take in the path to the branch I want to >> > build. >> > As the job does many other things it was more efficient to do it this >> > way >> > rather than creating 3 separate jobs with a lot of logic duplication. >> > >> > The issue this is creating is that Jenkins is confused about what has >> > changed between runs. Most often is says that there were no changes. I >> > am >> > guessing it remembers the revision number of the last build, and if the >> > build on another branch has a lower revision number it says that nothing >> > changed. >> > >> > The job right now is triggered immediately after any change on any of >> > the >> > above branches. So in essence I need it to ignore the revision number >> > from >> > the previous build and just report the *last* change on the branch it is >> > currently looking at. Then, if there is failure, send the email to the >> > person making the last commit (which is the main problem for me right >> > now). >> > >> > Is there any way to make this happen? >> > >> > Thanks a lot! >> > >> > Alex >> > >> > -- >> > 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. >> > To view this discussion on the web visit >> > >> > https://groups.google.com/d/msgid/jenkinsci-users/3b96d223-0fda-4198-b5bd-fb4d2c61daf1%40googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Manuel Recena Soto >> * manuelrecena.com [/blog] >> * linkedin.com/in/recena > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/630f23ab-1a7a-4d3e-bb83-d504674229cc%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Manuel Recena Soto * manuelrecena.com [/blog] * linkedin.com/in/recena -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CABa-Uofa1iznBjYB2w9DdJvHnp4OHuyR_KgkgMV1AhJ8OsnhjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
