Curently, Jenkins JIRA is polluting the comments in JIRA page, especially with matrix builds.
We had an issue with a couple of user comments and many hudson comments.
Every build, it records the changes.
Any idea to get rid of this issue?
Per Jenkins wiki, user has an option to turn updates on and off in Post-build Actions settings.
To turn off, make sure that there's no check mark set at "Updated relevant JIRA issues"
Related
On a jenkins instance we have the jira trigger plugin and it does not trigger some builds. I could not find a way to recreate the issue, so I would say it randomly happens.
I've enabled the advanced logs as per the documentation (https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting) , but, for the webhooks that are working and received I see the details with fields, change log and everything, while for the ones that do not work I see just the word: "Discarded", without any other details. Nobody is closing the builds or anything in Jenkins.
What could "discarded" mean?
Thank you!
I am new to jenkins and I have a Project named RetailcloudSolution_automation_cms2_prod but I just want to restrict this job by others doesnt do the build , but others can see , just shouldnt hit the Build for security issue and I want only three people to Build this job for now and also for the future use, Is there anyway I can do this for just this particular JOB...? Can i know the steps to do it..? It should not affect globally, I need restriction just for project based..
Thanks,
I strongly suggest you to use the Role Strategy Plugin in jenkins to manage the Users.
With this plugin you manage users based on projects
In other words you can make sure that project or job is not runnable by other users.
Refer this link for better understanding and plugin configuration.
https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin
I followed the next guide:
https://ecosystem.atlassian.net/wiki/display/FISH/JIRA+FishEye+Plugin+2.5.3+-+Perforce+Job+Integration
and successfully created a link between Perforce and JIRA.
I did manage to create a Perforce job on JIRA issue creation while selecting that option with the p4 job custom field.
What I cannot configure is a creation of a job automatically for each issue for a specific project as described in the next section:
Creating Jobs for ALL issues in a project
Another method of creating jobs (without the need to configure custom fields) is to set the Always create jobs for issues in this project flag in the project-level Perforce administration screen."
I can't find that flag for some reason.
Can anyone assist with screenshots or any other helpful information?
Eventually what I need to do is that for each issue that is created in JIRA a job should be created in Perforce.
Thanks in advance,
Max.
We want to create a defect/task in Jira automatically for a failed build in Bamboo. And need to assign this defect to the person who broke the build.
How to do these two things?
Thanks.
There is an open JIRA issue regarding this -- BAM-2537 -- watch it, vote for it - maybe they'll add it to the product.
The comments from Top 5 Reasons Creating JIRA Issues from Bamboo Makes Your Team Awesome-r also discuss what you're after.
Have a look at Atlassian CLI. There's already a good answer on StackOverflow.
Can Bamboo change status of tickets in JIRA
This is not "out of the box" solution, of course, and requires some additional work.
I have installed Jira and the subversion plugin (with success from what i can tell from the administration panel - subv. plugin installed).
I then add a repository that I have created on the file system, BUT i cannot see an option which will link/connect a new or existing project to a SVN repository. What i want to do is link a project with a repository so I can track commits made to the project (link commits with issues). After some searching i found that this is possible but I cannot figure a way to do it.
Do I need another plugin for that? I have tried googling for the last hours but I cannot find anything related.
regards,
The way SVN-Jira linking works by default is to simply put the issue identifier of the Jira issue in the comment when committing to the SVN repository.
It can be helpful to enable comment editing in the repository, if you have past commits or users who forget to add comments when committing.
Example commit comment:
Fixed problem with login. See issue MYJIRAPROJECT-26 in issue tracker.
There's a service in Jira which scans the SVN repository at regular intervals, and builds a cache of any SVN revisions where an issue identifier appears. Depending on the polling interval, it make take a few minutes for the commit to show up in Jira.
The polling time is controlled by the JIRA Service for the SVN plugin. See Admin, Services.
~Matt
you can enforce that future subversion commits require a jira issue reference for more reliable--than relying on your programmer's word ;)--jira-subversion integration
the jira commit acceptance plugin can be configured to block commits that don't include a valid (defined by subversion-jira project mapping and/or regular expression as appropriate to your situation) jira issue reference in the commit comment
reliable jira-subversion linkage availability allows handy stuff like:
Integration with issue trackers