-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: config-rotator-plugin
-
Labels:None
-
Similar Issues:
We use Jenkins version 1.502 and Config Rotator version 1.0.2.
If a job is configured:
and the baseline <baseline> has
promotion level TESTED then this job will not trig on new baselines of
that component with promotion level INITIAL. But if changing the promotion
level for baseline <baseline> then the
job trigger on new baselines.
So when searching for new baselines the promotion level for the current
baseline must not be used!
Code changed in jenkins
User: Christian Wolfgang
Path:
pom.xml
src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java
src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/NextBaseline.java
src/test/java/net/praqma/jenkins/configrotator/ClearCaseUCMBuilder.java
http://jenkins-ci.org/commit/config-rotator-plugin/8a4a016d14cf70cf241502a2d059b3de304885be
Log:
[fixed JENKINS-17229] Updated to baseline list