-
Bug
-
Resolution: Fixed
-
Minor
-
Docker plugin tests run with mvn -Djenkins.version=2.414 verify
The docker-plugin automated tests fail when run with Jenkins 2.414. They pass when run with Jenkins 2.401.3.
I suspect a change in the cloud naming interface will need changes to the tests. I don't have any report of an issue with the docker plugin, only that a few of the automated tests are failing.
The failing tests are:
- getCloudByNameOrThrowGivenForeignCloudNameThenThrows
- getCloudByNameOrThrowGivenUnknownNameThenThrows
- getCloudByNameOrThrowGivenNameThenReturnsCloud
I won't have time to investigate the failure for about a week. If someone else wants to investigate, they are welcome to do so.
- is caused by
-
JENKINS-70729 Rework clouds management into multiple pages
-
- Closed
-
- links to
[JENKINS-71825] JenkinsUtilsTest fails with IllegalArgument Cloud must have a unique non-empty name (regression in 2.403)
Summary | Original: Docker plugin unit tests fail on Jenkins 2.414 but pass on 2.401.3 | New: JenkinsUtilsTest fails with IllegalArgument Cloud must have a unique non-empty name |
Summary | Original: JenkinsUtilsTest fails with IllegalArgument Cloud must have a unique non-empty name | New: JenkinsUtilsTest fails with IllegalArgument Cloud must have a unique non-empty name (regression in 2.403) |
Labels | New: regression |
Link |
New:
This issue is caused by |
Assignee | Original: Nicolas De Loof [ ndeloof ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "PR 1010 that drops support of docker clouds with an empty name (Web Link)" [ 28923 ] |
Assignee | New: Mark Waite [ markewaite ] |