|
Change by Dan Mastrian [25/Jun/07 06:19 PM]
|
| Field |
Original Value |
New Value |
|
Attachment
|
|
ccnet.config
[ 11120
]
|
|
Change by Dan Mastrian [25/Jun/07 06:21 PM]
|
|
Description
|
- Set up one project with a defaultlabeller.
- Make a second project with a projectTrigger that watches the first project.
- Make the second project's labeller be a stateFileLabeller referring to the first project.
- Force a build or two of the first project
- Notice that the second project, when it triggers, does NOT have the same label of the first project (which just completed successfully)...it has the label of the *previous* build of the first project.
CCNET 1.1.0.2498 was the last version I used...it did not have this behavior.
|
- Set up one project with a defaultlabeller.
- Make a second project with a projectTrigger that watches the first project.
- Make the second project's labeller be a stateFileLabeller referring to the first project.
- Force a build or two of the first project
- Notice that the second project, when it triggers, does NOT have the same label of the first project (which just completed successfully)...it has the label of the *previous* build of the first project.
CCNET 1.1.0.2498 was the last version I used...it did not have this behavior.
This makes splitting a build (using a stateFileLabeller referring to other projects) very difficult.
|
|
Change by Dan Mastrian [25/Jun/07 06:29 PM]
|
|
Description
|
- Set up one project with a defaultlabeller.
- Make a second project with a projectTrigger that watches the first project.
- Make the second project's labeller be a stateFileLabeller referring to the first project.
- Force a build or two of the first project
- Notice that the second project, when it triggers, does NOT have the same label of the first project (which just completed successfully)...it has the label of the *previous* build of the first project.
CCNET 1.1.0.2498 was the last version I used...it did not have this behavior.
This makes splitting a build (using a stateFileLabeller referring to other projects) very difficult.
|
- Set up one project with a defaultlabeller.
- Make a second project with a projectTrigger that watches the first project.
- Make the second project's labeller be a stateFileLabeller referring to the first project.
- Force a build or two of the first project
- Notice that the second project, when it triggers, does NOT have the same label of the first project (which just completed successfully)...it has the label of the *previous* build of the first project.
The issue appears to be that the LastSuccessfulIntegrationLabel element is not ever getting updated in Project1.state upon successful completion of the build (the Label element is, though), and the other project is looking at that element to determine its label.
CCNET 1.1.0.2498 was the last version I used; it did not have this behavior. This issue makes splitting a build (using a stateFileLabeller referring to other projects) very difficult, because the dependent projects constantly get the wrong labels.
|
|
Change by David Cameron [06/Sep/07 06:07 AM]
|
|
Link
|
|
This issue Relates to CCNET-948
[ CCNET-948
]
|
|
Change by David Cameron [06/Sep/07 06:12 AM]
|
|
Link
|
|
This issue Relates to CCNET-899
[ CCNET-899
]
|
|
Change by Ross Patterson [05/Dec/07 02:26 PM]
|
|
Assignee
|
|
Ross Patterson
[ rosspatterson
]
|
|
Change by Ross Patterson [05/Dec/07 02:31 PM]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Fix Version/s
|
|
Next
[ 10302
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
Change by Ruben Willems [25/Jul/10 12:48 PM]
|
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
Bug
Closed
Major
LastSuccessfulIntegrationLabel lags behind by one build, so dependent projects using stateFileLabeller are building with the wrong label
