[
https://issues.jenkins-ci.org/browse/JENKINS-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161377#comment-161377
]
kutzi commented on JENKINS-13380:
---------------------------------
Actually, this works 'as designed' resp. works this way because of backwards
compatibility - although many people (including me) would say that this is a
bad design then.
See JENKINS-1241 for a longer discussion on this topic and especially for this
issue Dean's comment from 22/Nov/10 3:13 PM
> Changes on SCM during BuildWrapper.preCheckout are not checked out
> ------------------------------------------------------------------
>
> Key: JENKINS-13380
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13380
> Project: Jenkins
> Issue Type: Bug
> Components: core, subversion
> Environment: Windows 7 x64, Jenkins 1.456
> Reporter: Anne Stellingwerf
> Priority: Blocker
> Attachments: SleepBuildWrapper.java
>
>
> Changes that are made in SVN (possible other SCMs as well) AFTER start of the
> build but BEFORE end of BuildWrapper.preCheckout are not checked out.
> I created a BuildWrapper implementation that waits until several mirrored svn
> repositories are at the same revision. When the repos are in synch I want the
> SCM client in Jenkins to checkout the (then current) HEAD revision. Much to
> my surprise, the HEAD revision at the start of the build is checked out
> instead.
> Reproduction scenario:
> Configure a job with the attached SleepBuildWrapper.
> Trigger a new build.
> Within 20 seconds, commit a change to a svn repo attached to the job.
> Wait until the checkout is done.
> * Note that the revision you just committed is not in the checkout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
