You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2021. It is now read-only.
When deciding whether a job already exists on jenkins, or whether a new job needs to be created, the jenkins_pipeline_builder does a case-sensitive search; i.e. MyJob and MYJOB are considered to be different jobs. If the builder finds MYJOB on jenkins and it is processing MyJob, it will attempt to create a new item.
However, Jenkins will treat MyJob and MYJOB as a name collision, and the creation of MyJob will fail with JenkinsApi::Exceptions::JobAlreadyExists.
The builder should use the same case-insensitive comparison used by Jenkins to avoid this.
The text was updated successfully, but these errors were encountered:
When deciding whether a job already exists on jenkins, or whether a new job needs to be created, the jenkins_pipeline_builder does a case-sensitive search; i.e. MyJob and MYJOB are considered to be different jobs. If the builder finds MYJOB on jenkins and it is processing MyJob, it will attempt to create a new item.
However, Jenkins will treat MyJob and MYJOB as a name collision, and the creation of MyJob will fail with JenkinsApi::Exceptions::JobAlreadyExists.
The builder should use the same case-insensitive comparison used by Jenkins to avoid this.
The text was updated successfully, but these errors were encountered: