Re: Subversion Rev number - quick question
* Z. W.: Issue: For those files that User C checks in, we like to pick up the previous versions of those files, prior to User C's checkouts after the job B begins running and not pick up the files versions that User B checks in during the job B run. We like to know if there is anything needed to be done in SVN to make it work ? You can specify an explicit revision number when performing the checkouts. This way, you can ensure that they are consistent. Tags are mostly overkill for this, especially if you keep track of the revision number you used by other means.
Re: Subversion Rev number - quick question
Guten Tag Florian Weimer, am Dienstag, 1. Januar 2013 um 17:39 schrieben Sie: You can specify an explicit revision number when performing the checkouts. This way, you can ensure that they are consistent. But especially in a context of Jenkins and Co. this is not the default behavior and would require manual intervention all the day. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Subversion Rev number - quick question
Guten Tag Z W, am Montag, 31. Dezember 2012 um 20:48 schrieben Sie: Issue: For those files that User C checks in, we like to pick up the previous versions of those files, prior to User C's checkouts after the job B begins running and not pick up the files versions that User B checks in during the job B run. We like to know if there is anything needed to be done in SVN to make it work ? Besides tags I don't see any way directly in Subversion and form my opinion it is nothing which needs to or even can be addressed in Subversion as it's a special case depending on software builds of a company. What you could try is script your Jenkins jobs in a way where your first job of the chain saves a timestamp or revision number, depending on your repo layout, of what to checkout in subsequent jobs. For example Jenkins may checkout or update it working copies to head, as it does by default, but in the scripts you created to actually run the builds or whatever you do, you can update the working copies to a specific version or a version below a specific timestamp, a value, which the first job of the chain stored somewhere accessible for your other jobs. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Subversion Rev number - quick question
On Mon, Dec 31, 2012 at 1:48 PM, Z W mpc8...@gmail.com wrote: Hi All We are new to SVN. We are unsure where to configure in SVN, if needed, while using it with Jenkins/Hudson CI tool. We have a big chained job that runs for about an hour. Chained job meaning several jobs combined using downstream connections of jobs. We have the following problem, which is better explained in use case scenario: 3pm - User A checks in files into SVN directory X 315pm - Job B (has 4 subjobs) - and subjob 1 - checkouts files from SVN directory X, compiles and completes subjob run, then 320pm - subjob 2 - checksouts files from SVN directory Y and compiling 325pm - User C checks in files into SVN directory Z 335pm - subjob2 completes run and subjob 3 - checkouts files from SVN directory Z, compiles and completes subjob run, then 345pm - subjob4 checkouts files from SVN directory G, compiles and completes subjob run 4pm - subjob 4 completes run. Issue: For those files that User C checks in, we like to pick up the previous versions of those files, prior to User C's checkouts after the job B begins running and not pick up the files versions that User B checks in during the job B run. We like to know if there is anything needed to be done in SVN to make it work ? Thanks all for your contribution. If there is a way to pass information among the build jobs, pick up the revison number of the checkout for job B and specify it in peg revison format (path@rev) for the subsequent jobs. For something more human-readable you could also copy the project revision to a tag at the start of job B and do all the builds from the tag snapshot. The details of how to mesh that with jenkins would be a better question for the jenkins list. You might need to use parametrized builds with something external passing in the revision (easy to do with the rest interface) to kick it off instead of polling the svn repository for changes. -- Les Mikesell lesmikes...@gmail.com
Re: Subversion Rev number - quick question
On 12/31/2012 11:48 AM, Z W wrote: Hi All We are new to SVN. We are unsure where to configure in SVN, if needed, while using it with Jenkins/Hudson CI tool. We have a big chained job that runs for about an hour. Chained job meaning several jobs combined using downstream connections of jobs. We have the following problem, which is better explained in use case scenario: snip Issue: For those files that User C checks in, we like to pick up the previous versions of those files, prior to User C's checkouts after the job B begins running and not pick up the files versions that User B checks in during the job B run. We like to know if there is anything needed to be done in SVN to make it work ? Tags are cheap copies; make a tag at the start of the build process and have the build system use only the tag. -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com
