TFS, Jenkins and how to update work items with build numbers -


we using tfs , tfs build service. considering migrate build service jenkins came across issues. according this site, there things not work tfs , jenkins plugins. of them use lot:

  • associated change sets – team build automatically associates list of change sets included in build
  • associated work items – team build analysis relationships , associates work items build. indeed walks work item tree (parent) , maintains association in chain.

is still true? have scenario:

  • a developer checks in code fix bug or resolve user story. associating check in work item id.
  • his check in triggers build associate work item changeset. bugs, build update "integrated in build" field build number. use field know in witch version bug fixed.

is there way make jenkins behave , tfs build service does?

another option mix 2 using dummy builds on tfs side set records straight , kick-off jenkins' builds. hints how trigger jenkins builds remotely , pass parameters , “fake” tfs build.

this approach requires bit of effort has many advantages:

  • no big-bang, use jenkins opportunistically
  • can continue using existing builds
  • having build identifier in tfs allows overall monitoring , use test features

Comments

Popular posts from this blog

javascript - Karma not able to start PhantomJS on Windows - Error: spawn UNKNOWN -

Nuget pack csproj using nuspec -

c# - Display ASPX Popup control in RowDeleteing Event (ASPX Gridview) -