Build issue: team.scm.acceptBeforeFetch not working?
![]()
In my build definition, I have the "Accept latest changes before loading" checked. If I make a change from a development workspace and deliver the change. Shouldn't I be able request a build against the default build workspace and have that change automatically accepted into the build workspace (and built)?
Using M5a, I make a change in my development workspace, deliver it and request a build (against the build workspace). The build fails because the change was not accepted into the build workspace. If I look at the pending changes on the build workspace, I see the incoming change waiting to be accepted. If I manually accept the change into the build workspace and request the build again from my development workspace, the build is successful. It seems the team.scm.acceptBeforeFetch isn't working. Is this a bug? Can someone please verify? |
7 answers
![]()
One thing to check is that your build workspace is correctly configured with the flow target of the stream you are delivering to. Open the workspace editor on the build workspace to verify.
Next, check the log file that was attached to the build result. A common error is that the owner of the build workspace is not the same as the user specified when the build engine (jbe) is run. Let me know if this helps. Jean-Michel Lemieux Source Control Team |
![]()
Also note that if your build workspace has multiple flow targets, it accepts changes from ALL flow targets. (this took me quite a while to figure out :-)
regards Daan. |
![]()
Jean-Michel,
I have confirmed that the build workspace and the development workspace have the same stream specified as the Flow Target. As I mentioned, delievering from the development workspace results in incoming pending changes on the build workspace, so I think this part is ok. Oringinally the build workspace had no owner specified. I corrected this by specifying the same user credentials used by the jbe. Additionally I confirmed that the build log shows the following:
This does not correct the error. The pending changes view still shows incoming changes after the build completes and the build fails because the file was not updated correctly in the build workspace prior to the build. Any other ideas? |
![]()
I should also mention that the stream specfied as the follow target is also a synchronized stream (syncs with ClearCase). I'm not sure if that is an issue.
|
![]()
I should also mention that the stream specfied as the follow target is also a synchronized stream (syncs with ClearCase). I'm not sure if that is an issue.
|
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Mar 25 '08, 4:43 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A ClearCase synchronized stream is just a regular Jazz stream that
happens to be updated by the ClearCase Connector, so that shouldn't have any effect on its behavior as a flow target for team.scm.acceptBeforeFetch. pravesh wrote: I should also mention that the stream specfied as the follow target is |
![]()
Your build log indicates the accept and fetch are working.
In the build result editor, Contribution Summary section, do you see a "Changes: Show Changes" link? If so, do you see your expected changes shown in the Change Explorer? You should see the changes that are included in the build. --- Ryan Manwiller Jazz Team Build "pravesh" <pravesh@us.ibm-dot-com.no-spam.invalid> wrote in message news:fsb3au$l2i$1@localhost.localdomain... In my build definition, I have the "Accept latest changes before |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.