First build questions -- Build/Work item association
![]()
Hello,
I have gone through the tutorial, but in our production, I think we are missing something. Viewing the devs work items, change sets are attached -- check. The build is building the new changes -- check The stream has the latest releases -- check The target of the build is the correct stream -- check The build user and work space are correct -- check Users are running the build as build user -- check Users are accepting changes and delivering to stream -- check The build displays the work items -- missing I can't figure out why the builds do not display the work items...everything else checks out. They are associating changesets to work items...you can see it in the work items... |
Accepted answer
![]()
Ralph Schoon (62.3k●3●36●43)
| answered Dec 03 '14, 6:57 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Dec 03 '14, 6:58 a.m.
The work items that went into the build depend on a snapshot being created after the build. This only works if the build is not a private build. Because the build system does not have the permission to create a snapshot on the personal repository workspace of a user.
Make sure there is a dedicated repository workspace owned by the build user selected in the build definition. The links between the work item and the changesets are actually created by the developers that is the information used during the compare. Mahari Hill selected this answer as the correct answer
Comments That was it, they were doing a personal build as the build user... :-\
Just to clarify one point: it's not that we can't create a snapshot for a personal build, we just don't currently since it's not seen to have a benefit in this case.
Also note that developer workspaces need to be visible to the build user, so it can load them, but build requests are normally submitted by the dev user (or scheduled), not the build user.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The Build user does not have the permission to alter the personal repository workspace. And the build runs in the build users context not the owners.
|