Jx: support Gitlab and Bitbucket integration
Hi,
Jenkins looks very promising. I have watched Jenkins X works great with Github in the video demo. How about other (private and cloud) git repository like Gitlab and bitbucket ? Gitlab and Bitbucket is uniquitous so I think it would be great if Jenkins X support integrating with two both. Thanks.
Best Regards,
VietNC
vietwow
All 30 comments
Thanks for the issue.
It’s on our roadmap to support github enterprise, bitbucket & gitlab
http://jenkins-x.io/contribute/roadmap/
gitea is currently close.
jstrachan
on 20 Mar 2018
but gitea before gitlab ... why :(
tuananh
on 29 Mar 2018
@tuananh gitea small, lightweight, written in go and is very super easy to install on kubernetes.
Though we've started BitBucket and Gitlab integration if you fancy helping test it out?
jstrachan
on 29 Mar 2018
I would love to help testing out gitlab integration.
tuananh
on 30 Mar 2018
Here’s how to add a git server http://jenkins-x.io/developing/git/
It might be worth a try, then seeing if you can create a new repo via, say, ‘jx create spring’
jstrachan
on 30 Mar 2018
BTW GitHub Enterprise is working great. BitBucket Cloud is almost there apart from an issue with credentials when updating commit/PR build status:https://github.com/jenkins-x/jx/issues/665 and gitea is in a similar state - so we're making progress.
Hopefully someone can jump in and help on gitlab support too now all the multi-git provider gremlins are worked out
jstrachan
on 18 Apr 2018
I see #665 is now closed. Does that mean that Bitbucket Cloud is now working? Have any tests been done on Bitbucket on-prem?
nigelcharman
on 29 May 2018
@nigelcharman we think BitBucket Cloud is now working though there is still work to do on BitBucket Server
jstrachan
on 29 May 2018
Is there any doc or updates related to the bitbucket cloud integration with jenkins-X.
As I do "jx import" I don't see any option with bitbucket cloud but only github.
➜ vof_orch_proto git:(feature/cmt-103.0-pom-creation) ✗ jx import
✘ Sorry, your reply was invalid: "samyakr" is not a valid answer, please try again.
? Do you wish to use srout as the git user name: No
? git user name: samyakr
? GitHub user name: (samyakr)
Sam123ben
on 23 Jul 2018
@Sam123ben see https://jenkins-x.io/developing/git/
jstrachan
on 23 Jul 2018
Hello,
I know that Bitbucket Server integration is in-progress according the roadmap, but I have some feedback on the "create environment" feature. I'm not sure if it's ready for use with Bitbucket Server, but I am receiving an error when I try. Here are some relevant details with specific information redacted:
$ jx get git
Name Kind URL
servername bitbucketserver https://servername/bitbucket
$ jx create environment ci
? Label: Ci
? Namespace: jx-ci
? Domain: xx.xxx.xx.xx.nip.io
? Cluster URL:
? Promotion Strategy: Never
? We will now create a Git repository to store your ci environment, ok? : Yes
Using git provider servername at https://servername/bitbucket/
? Do you wish to use josiahp as the git user name? Yes
About to create repository environment-jx-ci on server https://servername/bitbucket/ with user josiahp
? Which organisation do you want to use? josiahp
? Enter the new repository name: environment-jx-ci
Creating repository josiahp/environment-jx-ci
Creating git repository josiahp/environment-jx-ci
error: Status: 404 , Body: <!DOCTYPE html><html lang="ja"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><title>指定のものが見つかりませんでした - Bitbucket</title><script>
The error in the 404 response is, predictably, "The specified page was not found."
If opening a separate ticket would be helpful then I would be happy to do that. If these kinds of reports are not helpful at this time then I would be equally happy to wait patiently for this integration.
josiahp
on 9 Aug 2018
The gitlab integration seems to be having trouble promoting to an environment from a private repo. Could this error be an indicator of an incorrect configuration or is this connector not complete yet?
_error:_
+ jx promote -b --all-auto --timeout 1h --version 0.0.8
Promoting app dippy-fork version 0.0.8 to namespace jx-staging
Created Pull Request: https://gitlab.com/gabeduke/environment-jx-staging/merge_requests/7
Failed to query the Pull Request last commit status for https://gitlab.com/gabeduke/environment-jx-staging/merge_requests/7 ref [ref] could not find a status for repository [rep] with ref [ref]
gabeduke
on 2 Sep 2018
I opened this issue related to this https://github.com/jenkinsci/gitlab-plugin/issues/827. The commit status is not automatically updated by the Gitlab plugin, it must be explicitly defined in the Jenkinsfile.
ccojocar
on 4 Sep 2018
My working example uses the following Jenkins file:
pipeline {
options {
disableConcurrentBuilds()
gitLabConnection('Gitlab')
}
agent {
label "jenkins-maven"
}
post {
failure {
updateGitlabCommitStatus name: 'state', state: 'failed'
}
success {
updateGitlabCommitStatus name: 'state', state: 'success'
}
}
environment {
DEPLOY_NAMESPACE = "jx-dev1"
}
stages {
stage('Validate Environment') {
steps {
container('maven') {
dir('env') {
sh 'jx step helm build'
}
}
}
}
stage('Update Environment') {
when {
branch 'master'
}
steps {
container('maven') {
dir('env') {
sh 'jx step helm apply'
}
}
}
}
}
}
You will also need to configure the GitLab connection in Jenkins.
benday280412
on 6 Sep 2018
@josiahp a separate ticket may help; I wonder if its related to the bitbucket server version you're using? do you get the same 404 when trying to create new projects (e.g. jx create spring / jx create quickstart)
jstrachan
on 6 Sep 2018
seems like this "catch all" ticket can be closed. there are plenty of specifics that exist for each of the providers.
https://github.com/jenkins-x/jx/issues?utf8=%E2%9C%93&q=is%3Aissue+bitbucket
https://github.com/jenkins-x/jx/issues?utf8=%E2%9C%93&q=is%3Aissue+gitlab
jtnord
on 27 Nov 2018
@jstrachan @wbrefvem Can we close this issue?
ccojocar
on 20 Feb 2019
@ccojocar I see on the link https://jenkins-x.io/contribute/roadmap/ looks like that it's still in-progress
vietwow
on 20 Feb 2019
@ccojocar Yeah, I think it might make sense. Bitbucket support is there (Cloud & Server), although I'm not so sure about Gitlab.
@vietwow I think it makes sense at this point to have an issue that tracks Gitlab support and then issues for individual bugs and feature requests that arise in Bitbucket Cloud and Bitbucket Server, since they're both basically done.
wbrefvem
on 20 Feb 2019
Can't make gitlab to work. Provisioning stucks on getting commit statuses from gitlab, but that code not even implemented in gitlab.go file. Webhooks work fine, merge request is created properly.
atomicleads
on 22 Feb 2019
@atomicleads Yeah, gitlab support is not quite there yet. We're always looking for contributors if you're interested. :)
wbrefvem
on 4 Mar 2019
Apologies that I haven't had time to contribute the Jira code I mentioned to @jstrachan that I'd try to take on.
briantopping
on 4 Mar 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
jenkins-x-bot
on 4 Jun 2019
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
jenkins-x-bot
on 5 Jul 2019
Quite happy to volunteer to help with GitLab testing if this helps speed things up (my Go skills are meagre at best, so can't promise anything regarding development). Jenkins-x is very much on the roadmap for my organisation, but github.com isn't an option for SCM.
TonyNoble
on 24 Jul 2019
Thanks for the issue.
It’s on our roadmap to support github enterprise, bitbucket & gitlab
http://jenkins-x.io/contribute/roadmap/gitea is currently close.
@jstrachan This page is 404 status, why?
blademainer
on 6 Jan 2020
@blademainer judging by the git log it looks like the roadmap/futures page might have been removed when the new docs site work was done in September 2019?
@dennisnewel might know more
connorads
on 6 Jan 2020
@blademainer the roadmap page hadn't been updated in quite a while when we updated the docs site, so it was deleted at that point. The plan was to replace it with an updated version, but we haven't gotten to that yet.
Bitbucket and GitLab is (experimentally) supported by the new Lighthouse component and we (as in CloudBees) will look to stabilize and productize Lighthouse in the coming months. The goal is to get Lighthouse to a point where we can offer official, commercial support for it; that involves a lot of testing which is why it'll take us a bit to get there :)
dennisnewel
on 6 Jan 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
jenkins-x-bot
on 12 Mar 2020
@jenkins-x-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
jenkins-x-bot
on 12 Mar 2020
Related issues
empath
·
3Comments
abayer
·
4Comments
ipv1337
·
3Comments
carlossg
·
4Comments
SmartassSkeleton
·
4Comments
Most helpful comment
Thanks for the issue.
It’s on our roadmap to support github enterprise, bitbucket & gitlab
http://jenkins-x.io/contribute/roadmap/
gitea is currently close.