Were using TFS for Source control and Team City for CI.
I'd like to introduce YouTrack also to the mix.
What's the integration between the three of them like?
Eg Can I raise bugs in YouTrack against product backlog items (a "story") in TFS?
Cheers for any pearls of wisdom!!
In the integration environment you describe TFS would act just like a VCS, so no, you won't be able to raise bugs in YT against a story in TFS.
However, you will be able to modify state of a YT issue by simply mentioning it in a commit comment like #ISS-123 fixed. You'll be able to view commits related to an issue in YT.
In TC you will see which issues relate to a build.
Related
I'd like to know if it's possible (and how, if anyone has ever done it before) to have Mantis Bug Tracker "tickets" automatically imported/transformed into TFS work items.
We use mantis to keep track of development and TFS as a Repo. Every check-in made to TFS must be associated with one work item. Right now, these two systems are not integrated which causes, for example, that the ticket 100 is relative to the work item 497 without no way of knowing that one is relative to the other.
I've looked at TFS Integration Tools but was unable to install it for some reason at this time.
So, how can I have an automation process that "imports" Mantis tickets into TFS work items automatically? Is this even possible?
There is a plugin for source integration which supports Git, SVN and Mercurial (experimental).
https://github.com/mantisbt-plugins/source-integration
I am not aware that there is something similar avalaible for TFS, but it should be no big problem to implement TFS integration based on the framework which is offered by the plugin.
Does TFS support local commits?
In other words: Can I
modify the code,
make a local commit (without sharing these changes with others),
test my modifications and
if my changes didn't break anything, do a global commit (thereafter my changes are available to other developers)
in TFS 2012?
If it doesn't, are there any workarounds, which allow this functionality?
No it doesn't support this, however it does have a couple of alternatives you can use instead.
1) Branches - All developers work on their own branch then merge to trunk/main when they're happy with their changes.
2) Shelveset - developers shelve any change they don't want to commit yet. This lets you undo your change, or pass it to another developer on the team without losing the change or checking into the main branch
3) Gated Checkins + Unit/Automated tests. Any time a developer checks in, TFS Automatically shelves the changes and runs the tfs build + any associated tests (unit or automated). If everything succeeds then it is checked in. I don't believe this supports manual tests.
or a mix of all of the above.
TFS does not support this by itself.
However! Microsoft released Git integration with TFS. Brian Harry blogged about this: Announcing Git Integration with TFS a couple of weeks ago.
Using this setup you can use Git for your local commits and then commit it to Team Foundation Server.
Not for the on premise version of TFS (yet), but as of January 2013 Microsoft's hosted Team Foundation Service has Git support, which obviously supports local commits.
http://tfs.visualstudio.com/en-us/news/2013-jan-30.aspx#git%20support
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 am working with a small development shop that consists of a group of 5 developers and 1 QA person. We are using TFS and need to get more sophisticated on how we use this tool.
Currently the development team checks in their code each evening. A nightly build runs and pushes the output out on a network share. Our QA person uses this build for testing the next day. Sometimes the build off the trunk codebase has issues/bugs that hinder the QA process, and it hasn’t been a giant issue in the past, but we now want to get to a state where we have our QA person testing on a stable QA build.
So I believe we need to create a branch (call it QA), and the developers will continue to develop off the trunk, but the QA person will use builds created from code in the QA branch.
Seems simple enough, but we have started doing code reviews as well. So we have another desire in that only code that has been code reviewed can be promoted to the QA branch. Each developer works off a TFS item, and when they check in a changeset, they do it against a TFS item which creates a link between a checked in code file and a TFS item. Eventually the TFS item becomes complete and ready for code review. All code attached to the TFS item is reviewed. How can the versions of these files get promoted to the QA branch?
In the QA branch, if a bug is found, we want to fix it in the QA branch and have the changes migrated back to the trunk. I believe TFS has a way to automatically do this doesn’t it?
Long story short, we want to get to a build and CM environment that I believe is pretty standard, but we are unaware of how to make this happen with TFS. Given our situation above, can someone point out a book or website(s) that would address our specific needs? We would like to make this happen without having to get too deep in CM theory or TFS.
I very much appreciate any and all suggestions!
Thanks,
John
You might want to take a gander at the resources on CodePlex. There are different strategies laid out for how you might want to build your branching model.
Has anyone got any great ideas or experience around easily producing Branch Diagrams against TFS?
TFS 2008 does not include this functionality, so you'll have to resort to a plug-in/add-on. I haven't found any mature projects that produce branch or version diagrams, though many allow browsing of branch/version trees.
Team Foundation Sidekicks has a History Sidekick that includes version tree browsing
Vertigo plans to include version tree browsing for individual files, as well as branches, but is still in alpha.
Very similar questions already answered:
View TFS checkin history through merges?
TFS Branch/Merge meets History View
If you don't mind setting up a 2nd server just for playing with branch visualization, TFS 2010 Beta 1 is going to render by far the best diagrams.