JenkinsUtilsTest fails with IllegalArgument Cloud must have a unique non-empty name (regression in 2.403)

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: docker-plugin
    • Environment:
      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.

            Assignee:
            Mark Waite
            Reporter:
            Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: