![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Praqma Support
|
|
Components:
|
config-rotator |
|
Created:
|
15/Mar/13 2:14 PM
|
|
Description:
|
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!
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jens Brejner
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
