Skip to content
This repository has been archived by the owner on May 10, 2021. It is now read-only.

Use case-insensitive comparison for jenkins job names #92

Open
slopes321 opened this issue Dec 29, 2015 · 1 comment
Open

Use case-insensitive comparison for jenkins job names #92

slopes321 opened this issue Dec 29, 2015 · 1 comment

Comments

@slopes321
Copy link
Contributor

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.

@AlexanderStohr
Copy link

sounds serious to me - subscribed...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants