Branch: refs/heads/quiet-period-exit-aware-checkout
Home: https://github.com/jenkinsci/cvs-plugin
Commit: dac1446221b6002149ba9670ba5ef038b6d89002
https://github.com/jenkinsci/cvs-plugin/commit/dac1446221b6002149ba9670ba5ef038b6d89002
Author: Stephen Connolly <stephen.alan.conno...@gmail.com>
Date: 2014-07-10 (Thu, 10 Jul 2014)
Changed paths:
M pom.xml
M src/main/java/hudson/scm/CVSSCM.java
A src/main/java/jenkins/scm/cvs/QuietPeriodCompleted.java
M src/main/resources/hudson/scm/CVSSCM/config.jelly
A src/main/resources/hudson/scm/CVSSCM/help-checkoutCurrentTimestamp.html
Log Message:
-----------
[ZD-19670] CloudBees customer reported that the quite period checkout
behaviour has anomolous logic that can result in failed builds
- This is likely where there is a delay between the build leaving the quiet
period and the build starting
- If there is a commit during that period of time then the build may checkout
an inconsistent state
- The solution is to use the time when the quiet period is completed as the
timestamp for the checkout
- Obviously people may prefer the original behaviour in some cases
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
