Bamboo and bitbucket are two pieces from the same vendor and there should be no problem integrating those two with each other, but I have a weird situation.
Here is what i get when trying to add bitbucket repo to my Bamboo.
See attached screenshot.
I'm pretty sure my repo is public and I use correct bitbucket user account name.
Thanks in advance.
I have installed BAMBOO to AWS using Java script provided by Atlassian
At the end it gave me a web UI links as on following screenshot .
It worked, however some functionality was blocked by XSRF (that is not enabled by default in Atlassian products).
Works fine when I use native Bamboo URL (HTTP and port 8085) instead on HTTPS.
Be careful with that... I just wasted about 2 days trying to fix something that didn't have to be fixed at all.
Have you linked your Bitbucket repo to Bamboo server. If not see this https://confluence.atlassian.com/bamboo/linking-to-another-application-360677713.html
May be this can help.
Related
I am using the GitHub pull request builder plugin in Jenkins to make pull requests on GitHub automatically trigger Jenkins jobs.
I am using GitHub Enterprise and when I try to get the values of environment vars ghprbActualCommitAuthor and ghprbActualCommitAuthorMail, I get incorrect values:
ghprbActualCommitAuthor : GitHub Enterprise
ghprbActualCommitAuthorEmail : noreply#github.***.com
Please help, thanks!
This behavior is seen in GitHub Enterprise when users commit changes directly using the web UI or they have not set their email addresses.
According to GHE support:
This is by design, since the commit is actually done by the GitHub Enterprise instance. This is because we do not impersonate users when creating commits.
You can fix this by ensuring that users make commits only through the Git clients using their own SSH credentials or Personal Access Tokens.
I can't find a way to trigger builds on jenkins when a gitlab merge request get accepted.
Here is my job configuration :
jenkins version : Jenkins ver. 2.107.3
gitlab version : 11.2.3
My webhook configuration on gitlab :
I tried, to select push events and accepted MR events on jenkins side, it works but for each push !
I want to know if this is the only way to get that works (push + accepted MR events).
Logically i just have to select accepted Mr only, but i get nothing, it doesn't seems to work that way.
I checked jenkins issues and find this one, i don't know if this is the same issue ? https://github.com/jenkinsci/gitlab-plugin/issues/636
Can you help me please, any ideas ?
Thank you.
you have to double check because i have same scenario and it's working fine
I dont find any solution so far using the plugin alone, and as I read this plugin is not directly developed by gitlab, my combo solution so far is:
to have a freestyle job, with configured webhook, where I can choose the MR events I need (Opened/Accepted/Closed) and retrieve all gitlab variables like gitlabMergeRequestState
from this job call another job defined via a fully elaborated pipeline, passing that gitlab variables, where all needed details can be handled via gitlab API.
I'm trying to link Gitlab commit messages to JIRA, that is, if a user commits such as:
PROJECT-ID: Some commit message
Then through the Gitlab UI, it links these commit messages to JIRA.
The only way I can seem to do this at the moment takes control of issue tracking itself from Gitlab and links the "Issue" user interface button in Gitlab back to JIRA.
I'd like to still manage and raise issues in Gitlab, but just have Gitlab link any formatted commit messages to JIRA.
I'm using the community addtion
Unless you set GitLab to use JIRA as your issue tracker, you can't make it link formatted commit messages to JIRA automatically.
You can do this only if you set JIRA to be your issue tracker in GitLab. You can find information about doing that here: http://doc.gitlab.com/ee/integration/jira.html
UPDATE: As Peter said, this functionality is only available using GitLab's Enterprise Edition.
UPDATE: As jalanb stated in the comment below, this functionality is now available in the community edition as well.
There is also the lesstif/gitlab-jira-integration open source solution, that I haven't tried yet myself. It is only a few commits, but I myself considered this approach so it must be sound ;-)
I'm a little confused though. You write you want to use Jira and "I'd like to still manage and raise issues in Gitlab, but just have Gitlab link any formatted commit messages to JIRA." I'm not sure you can get the supertight integration you're looking for. Or maybe I misunderstand.
I am new to bitbucket and cloudbees. Is anyone aware of the ways to connect them. Any detailed documentation about integrating them with complete details of output. Please help I am stuck with this for 3 days. Thanks in advance for your help.
I just released bitbucket jenkins plugin to address this use-case, as bitbucket "jenkins" hook is really poor and offer minimal service. Let me know your account ID if you want me to install it, and configure a "POST" hook on your repo with URL https://.ci.cloudbees.com/bitbucket-hook (no need for credentials)
I also updated http://wiki.cloudbees.com/bin/view/DEV/Bitbucket to reflect this new option.
We have several repositories on BitBucket. For every repository we
have the issue tracker enabled. For our progress reports I would like
to be able to see all issues from all related repositories in one
overview.
Is this possible and how can it be done?
Thanks,
Paul
Bitbucket has an API. You could quickly put together a script (or webpage using JSONP) calling:
https://api.bitbucket.org/1.0/repositories/USERNAME/REPOSITORY/issues/
for each repository? (Replacing USERNAME and REPOSITORY with appropriate values)
For something more advanced you could query the USER, get all their repositories, then iterate.
I needed the same thing today so I made the following python script available here on github.
The two API call URLs you need are
https://bitbucket.org/api/1.0/user/repositories/
https://bitbucket.org/api/1.0/repositories/{owner}/{slug}/issues/
You'll have to authenticate with your BitBucket credentials which I did using the python requests library:
response = requests.get(url, auth=HTTPBasicAuth(_USERNAME, _PASSWORD))