-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
XP SP3
We have a build job that uses a dynamic view with Config Spec:
element * CHECKEDOUT
element -directory * /main/LATEST
element -file * 1T_READY
The view and bulld job process only source code labeled "1T_READY".
However when the job runs lshistory command (thus changes page) shows all the changed files since the last build job run regardless of their label.
This leads to show wrong JIRA reports related that job. Also when the build fails, even the user didn't label his code as 1T_READY gets an e-nmail message as his code broke the build.
Load rules in the configuration page did not have an option to include label type also. How can we manage to list changes only in build view?
Kind regards
Serkan ZENGIN
- is related to
-
JENKINS-9215 Detect changes by label generates excessive log
-
- Open
-
[JENKINS-7218] Base Clearcase : Tracking changes on a label
serk1979
created issue -
serk1979
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
serk1979
made changes -
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
serk1979
made changes -
| Description |
Original:
We have a build job that uses Config Spec: element * CHECKEDOUT element -directory * /main/LATEST element -file * 1T_READY The view and bulld job process only source code labeled "1T_READY". However when the job runs lshistory command (thus changes page) shows all the changed files since the last build job run regardless of their label. This leads to show wrong JIRA reports related that job. Also when the build fails, even the user didn't label his code as 1T_READY gets an e-nmail message as his code broke the build. Load rules in the configuration page did not have an option to include label type also. How can we manage to list changes only in build view? Kind regards Serkan ZENGIN |
New:
We have a build job that uses a dynamic view with Config Spec: element * CHECKEDOUT element -directory * /main/LATEST element -file * 1T_READY The view and bulld job process only source code labeled "1T_READY". However when the job runs lshistory command (thus changes page) shows all the changed files since the last build job run regardless of their label. This leads to show wrong JIRA reports related that job. Also when the build fails, even the user didn't label his code as 1T_READY gets an e-nmail message as his code broke the build. Load rules in the configuration page did not have an option to include label type also. How can we manage to list changes only in build view? Kind regards Serkan ZENGIN |
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
| Summary | Original: Changes Page shows file changes not defined in Config Spec | New: Base Clearcase : Tracking changes on a label |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | Original: Vincent Latombe [ vlatombe ] | New: Krzysztof Malinowski [ raspy ] |
| Fix Version/s | New: current [ 10162 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
serk1979
made changes -
| Status | Original: Resolved [ 5 ] | New: Verified [ 10000 ] |
| Status | Original: Verified [ 10000 ] | New: Closed [ 6 ] |
Jose Sa
made changes -
| Link | New: This issue is related to JENKINS-9215 [ JENKINS-9215 ] |