-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added support for bitbucket #34
base: master
Are you sure you want to change the base?
Conversation
|
||
def createMultibranchPipelineJob(project, gitPath, jte) { | ||
def buildNamespace = System.getenv("BUILD_NAMESPACE") ?: "labs-ci-cd" | ||
def buildNamespace = System.getenv("BUILD_NAMESPACE") ?: "ocp-ci-cd" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we keep this as labs-ci-cd
? 🙃
|
||
// Build Jenkins multibranch jobs | ||
multibranchPipelineJob(project) { | ||
branchSources { | ||
git { | ||
id("${project}") | ||
remote(gitPath) | ||
credentialsId("${buildNamespace}-${buildGitAuthSecret}") | ||
credentialsId("${credentialsId}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we need this. I think, instead of defining a new SSH_ACCESS_KEY variable, you can create a secret with ssh key in it (secret type kubernetes.io/ssh-auth
). It'd be the same as username/password secret. And you get to use BUILD_GIT_AUTH_SECRET
and doesn't have to change credentialsId
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@springdo tagging you to check if you have other suggestions
hey @rsachdeva-ma thanks for the PR! I put two comments there! I'll also try and see if I can verify that SSH key part :) |
Added support for bitbucket