-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Follow-up to JENKINS-37759
From what I see in Jenkins plugins, there is no valid use-case when a test should proceed with a corrupted initialization graph.
- is related to
-
JENKINS-37759 Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic
-
- Resolved
-
[JENKINS-44453] JTH should ensure that Jenkins reaches the COMPLETED milestone in JenkinsRule
Description |
New:
Follow-up to |
Assignee | Original: Oliver Gondža [ olivergondza ] | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue is related to |
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Description |
Original:
Follow-up to |
New:
Follow-up to - From what I see in Jenkins plugins, there is no valid use-case when a test should proceed with a corrupted initialization graph. |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/org/jvnet/hudson/test/JenkinsRule.java
http://jenkins-ci.org/commit/jenkins-test-harness/fc7ef54f6aadfbf457e746847adbad0d4616dc56
Log:
[FIXED JENKINS-44453] - JenkinsRule should ensure that Jenkins reaches the COMPLETED milestone.
It should make issues like https://issues.jenkins-ci.org/browse/JENKINS-37759 much more explicit in funtional tests.
From what I see there is no valid use-case for proceeding with the test if the initialization fails.