-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Platform: All, OS: All
We have 20 or so projects configured in Hudson. We use a combination of CVS
polling (each project polls CVS once every 5 min, although not all projects at
same time), and forced nightly build (around 3AM).
Since upgrading to 1.254 (from 1.233?) the timer isn't working well. It still
detects the change and queues a build, but the quiet time timer never counts
down. We have configured a quiet-time of 30 minutes, and it never decreases.
Ultimately, the nightly build will clear it out of the queue.
- duplicates
-
-
- Closed
-
[JENKINS-2530] quiet-time timer not working
jbennett2091
created issue -
jbennett2091
added a comment - This is still broken as of Hudson 1.279.
We use CVS and it is set to poll for activity every minute. It executes
commands like this:
cvs.exe -q -z3 -n update -PdC -D "Friday, January 30, 2009 2:17:13 PM UTC"
-n = "Do not execute anything that will change the disk." (i.e. it doesn't
actually update)
-D date = timestamp to update since.
Unfortunately, the date continues to be the date of the last build and doesn't
seem to change. The net effect is that when a change occurs, it spots the
change and drops the project into the queue. A minute later, it polls again,
sees the same change again, and resets the timer. The quiet timer never reaches
0 because it keeps seeing the same change over and over again (thus thinking it
has never become quiet).
Recommend either the "-n" flag be removed, or the "date" be the date of the last
CVS poll.
jbennett2091
added a comment - This is still broken as of Hudson 1.279.
We use CVS and it is set to poll for activity every minute. It executes
commands like this:
cvs.exe -q -z3 -n update -PdC -D "Friday, January 30, 2009 2:17:13 PM UTC"
-n = "Do not execute anything that will change the disk." (i.e. it doesn't
actually update)
-D date = timestamp to update since.
Unfortunately, the date continues to be the date of the last build and doesn't
seem to change. The net effect is that when a change occurs, it spots the
change and drops the project into the queue. A minute later, it polls again,
sees the same change again, and resets the timer. The quiet timer never reaches
0 because it keeps seeing the same change over and over again (thus thinking it
has never become quiet).
Recommend either the "-n" flag be removed, or the "date" be the date of the last
CVS poll. see my comments in issue #2180 for workaround
-
-
- This issue has been marked as a duplicate of 2180 ***
-
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link |
New:
This issue duplicates |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Jenkins IRC Bot
made changes -
| Component/s | New: core [ 15593 ] | |
| Component/s | Original: gui [ 15492 ] |
| Workflow | Original: JNJira [ 132603 ] | New: JNJira + In-Review [ 201535 ] |
Woops, I meant to say I was using Hudson 1.255 (not 1.254).