Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Linux (Ubuntu), Windows (all platforms)
Description
Hi,
Long time (Hudson) user, first-time reporter.
Hudson ver: 1.347
OS: Linux vbuild05 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux
CVS: Concurrent Versions System (CVS) 1.12.13 (client/server)
Here is the issue.
Console Output:
"
...
P src/NBBuilderRun.cpp
P inc/SyCLib.h
P src/SyCLib.cpp
$ no changes detected
...
"
However, CVS Polling Log shows:
"
...
Done. Took 2 min 47 sec
Changes found
"
As we can see, Hudson is fetching cvs checkouts, but reporting that there are no changes. At the same time, it doesn't update the 'changelog.xml' file in the 'builds' dir.
changelog.xml contents:
$ more changelog.xml
<changelog/>
If you need any other info, please let me know. This is a blocker for us. I hope somebody would kindly look into it.
Thanks so much!
Attachments
Issue Links
- depends on
-
JENKINS-49 self-contained cvs client libs
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
URL | http://issues.hudson-ci.org/browse/HUDSON-49?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab | |
Environment | Linux (Ubuntu) | Linux (Ubuntu), Windows (all platforms) |
Link |
This issue is blocking |
Link |
This issue depends on |
Link |
This issue is blocking |
Assignee | Michael Clarke [ mc1arke ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Workflow | JNJira [ 135836 ] | JNJira + In-Review [ 187056 ] |
I'm still seeing this issue as well on my Jenkins CI server (currently at Jenkins ver. 1.400). The core bug usually presents itself in the following order:
A CVS polling operation completes and detects changes triggering a build of a job.
The build runs, performs a cvs update of files that have changed but when the build job finishes the jenkins job specific UI reports no changes in the changelog.
I see this bug was reported over a year ago but noticed that zero activity has occured on it so I decided to vote it up one.
On a secondary note, it looks like progress is already underway on integrating in a self-contained cvs client library. It seems like that issue could be considered a blocker for this fix as it significantly would alter the way the cvs plugin interacts with the system....