I have to configure our Bamboo server to work with Jira. My Objective is to trigger the Bamboo build from JIRA (when issue update) and Build status of Bamboo update into Jira with respective issue.
How can I do this?
You can just take a look into the official documentations; here the links:
Running a Bamboo Build when Releasing a Version
Viewing Bamboo activity in JIRA applications
Related
How can i integrate Jira and Gitlab and status will change on request!
Git commit -> ED-1511 #AutomationState Running
Jira ticket (ED-1511) - >> will change AutomationState on Running
I don't think that you can do this with the out of the box functionality of Jira and Gitlab.
From the structure of your commit message it looks like you are trying to use the smart commits functionality in Jira. Smart commits only allow you to perform three actions:
Log time
Comment on an issue
Transition an issue to a new workflow state
This is not something you can do with smart commits. In addition the current Jira Gitlab integration doesn't seem to support smart commits.
If you wanted to build this functionality you could probably build something yourself that:
Listens for Gitlab webhooks
On receipt of a Gitlab webhook calls the Jira REST api to modify the issue
If I understand your question correctly, the GitLab integration with JIRA described here should do what you want. I only recently set this up with our JIRA cloud instance and GitLab running in an AWS instance, and I haven't tried to integrate transitioning JIRA tickets from Git commit messages. However, the documentation seems to indicate that it is possible.
If there is the way to trigger Jenkins build via push to a specific branch on GitLab. At this moment I am using GitLab webhooks integration, to run a specific job? Now it starts after the push to any branch, but I need to start a job from push to the specific branch.
It's now possible since Gitlab 11.3 (https://about.gitlab.com/2018/09/22/gitlab-11-3-released/)
Does not appear to be possible currently by selecting a branch in the GitLab webhook. Feel free to watch progress on this new feature in the GitLab issue Filter web hooks by branch.
I did note in the issue comments the following that might help you configure things via Jenkins:
Jenkins GitLab plugin has an option to filter WebHooks by branch. Under Build Triggers --> Build when a change is pushed to GitLab --> Advanced...
I want to create a new Jira issue after everytime Jenkins jobs running no matter the result is passed or failed. But my setting was no effect in Jenkins. It only created a Jira issue for the first time, then, it only added a comment to the old JIRA issue after running job finished.
Here is my setting:
"JIRA: Create issue" in Jenkins
Only updated JIRA Comments in the old Jira issue
BTW: Other related functions are OK. Likeļ¼ triggered Jenkins job after Jira issue status changed or added comments to jira after running job.
Versions:
Jenkins ver. 2.32.2
JIRA plugin: 2.5
JIRA Integration for Jenkins: 3.1.3
Jira Issue Updater: 1.18
JIRA Pipeline Steps: 1.3.1
JiraTestResultReporter plugin 2.0.6
JIRA Trigger Plugin: 0.5.1
jira-ext Plugin:0.7
JIRA: 7.5.0
Thanks in advance!
I want to integrate Jenkins with JIRA Cloud.
I want Jenkins to start build job when i'm updating Issue Status in JIRA.
example: when the issue in jira is going from status IN PROGRESS to DEV COMPLETED, I want Jenkis to start a build.
regards, Maja
Usually the flow is a little bit different.
After you done with the development you should add JIRA ticket number in commit.
Then create pull request (if you use Git as VCS) and merge it to main branch.
Git server will trigger build on the Jenkins side (you should find Jenkins plugin for your case).
After build is done there Jenkins can send update status to Jira (via Jenkins JIRA plugin
There are some variations. For example you want to allow merge only when build on Jenkins was successful. In this case JIRA update should be performed by Git service.
Thank you for your fast response, but we got different situation than the given answer. I will try to explain clearly.
1. we got Jira on cloud that successfully communicate with Gitlab. (there is a build in jenkins after commit in Jira)
2. and we got one test Jenkins on our local machine
Jira is configured in Jenkins and we got all needed plugins in Jenkins.
Now we want, with every changed status on the issue in Jira (from IN PROGRESS to DEV COMPLETED), Jenkins to make an automatic build on the job.
Additionaly, Is there any Jenkins Plugin for Jira CLOUD that could help us?
At this time, there is no Jenkins plugin / add-on for JIRA cloud, even though it is in high demand. It is rumored there may be one coming out in November / December 2017 as a beta.
If you are using Bitbucket, I'd recommend checking out Pipelines. Or, take a look at Bamboo or TeamCity as these tools integrate directly with JIRA Software Cloud.
I've read the differences between Gitlab Community and Enterprise in this page: https://about.gitlab.com/features/
Based on that page I understand the integration with Jenkins is only available in the enterprise version. However, I've seen that using web hooks I can trigger builds in Jenkins when a push happens in Gitlab.
So my question is which is the difference between community and enterprise regarding the integration with jenkins?
On the merge request page, there is a state widget that shows the status of tests for that particular merge request, and on your project home page, there is test status badging. These two UI elements only show up if you enable a 'ci service' on the project. In community you can turn it on with Gitlab CI. In enterprise you can set it up to work with jenkins.
Based on that page I understand the integration with Jenkins is only
available in the enterprise version.
This is no longer true, the Jenkins GitLab Plugin (from a 3rd party) works to hook Jenkins into GitLab as a CI provider.
The wiki page has an example setup with lots of details you'll need to get it working.
This will give per-commit build/test status indicators in GitLab and also hook into the Merge Request system (both in the local repo and when merge requests come from forked repos).
You can also integrate GitLab with Jenkins using the Generic Webhook Trigger Plugin.
An example of integrating with that plugin, to perform static code analysis on merge requests, is available in the Violation Comments to GitLab Plugin wiki page.