I am trying to create a build in Jenkins, from certain changesets made in TFS.
I want to be able to decide which changesets should go in the build and which should be excluded.
I saw an earlier question How do you build from a specific TFS 2008 Changeset in Jenkins? which provided the answer using labels. Haven't tried it yet. But the question is 3 yrs old and I wanted to know if anyone has found an answer.
Any help would be appreciated. If it is not possible in Jenkins, please suggest any other tool that provides such functionality.
Atlassian Bamboo with TFS Repository Plugin
provides a solution for you :)
https://bitbucket.org/stellaritysoftware/tfs-repository-plugin/wiki/Home#!34-build-from-a-label-or-a-revision
BTW I've been looking around the tfs-plugin and although the docs doesn't mention "specific checkout by changeSet" I think there is a good chance that setting the VERSION_SPEC variable to change-set value, might do the trick for you.
Related
Without switching over to Jenkins to do builds, is there (or will there be in the foreseeable future) a pipeline as code solution for TFS build?
EDIT: For clarity and future reference, I'm looking for a declarative method of defining a build, like appveyor or Travis or Jenkins do. Checkout the answer for the uservoice suggestion for this functionality.
There isn't any way to achieve this feature for now but we have already started working on this. Refer to this feature request on VSTS User Voice site for details: provide a way to version-control build definitions.
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.
After using SVN as a VCS (we're a small dev team), we found it too hard to work with, and we switched to perforce in April. We're really happy with it, and we want to take it one step further by adding a Continuous Integration Server so that our builds are more reliable.
We have a MSDN licence allowing us to have TFS if we want (as a CI server), but we don't want to change what's already in place.
BUT, TFS has no native interactions with perforce, and vice versa.
So my question is, does anyone know if it's actually possible?
I googled a bit, I found an answer posted in 2009 (using perforce with team foundation server) saying it's not. But maybe it has changed since then...I didn't find any plugin or anything else to help me, and I need your help here.
Thanks.
I don't think there is any direct way to migrate Perforce to TFS.
However if you have got MSDN subscription, you could evaluate TFS for ALM/Build/Deployment.
we use TFS as source control system.
When we check in, we provide a comment and relate to a work item.
We use TeamCity for automated builds.
Teamcity nicely shows us the ceck-in comments, but the test manager would like to see the Work Items related to the check-ins in the TeamCity build information.
Is this possible? How?
Kind regards,
Ugly Papa Ramone
There is a plugin avaialable from jet brains to do this.
http://teamcity.jetbrains.com/project.html;jsessionid=6B41F83740F0A6F1F6C3056661013EA8?projectId=project50&tab=projectOverview
James
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