Fixed the issue of duplicate pipeline #239
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, when the buildconfig name is different then git repo name
then sync plugin is not able to find buildconfig by repo name while
syncing back to openshift after creating a buildconfig with strategy
JenkinsPipeline, and create a new buildconfig repo name, To fix this
issue, added a label of gitRepository name so it will first try to
find the BuildConfig with name of jenkins job, if that is not present
that is our case then it will also try to find the buildconfig having
label with the name of jenkins job and then if it is not present will
create a new BuildConfig #27
Declared constant variable for label key
Removed NPE and added comments in the code to always know the context behind this
cherry-pick of fabric8io#28 , as well as some space/tab issues
@openshift/sig-developer-experience @piyush1594 fyi/ptal