Automatically Trigger a Build on Code Delivery
![](http://jazz.net/_images/myphoto/a408c118b57ef745f293aff9800ab3bd.jpg)
2 answers
![](http://jazz.net/_images/myphoto/a408c118b57ef745f293aff9800ab3bd.jpg)
Although ideally, you'd request a personal build *before* you delivered
to the stream ... if the code has already been delivered to the stream,
you might as well let it be picked up by the continuous build on that
stream.
Cheers,
Geoff
On 3/18/2011 11:38 AM, xophe wrote:
to the stream ... if the code has already been delivered to the stream,
you might as well let it be picked up by the continuous build on that
stream.
Cheers,
Geoff
On 3/18/2011 11:38 AM, xophe wrote:
xophewrote:
What would be the easiest way to automatically trigger a 'Request
Personal Build' when Delivering Code to a Stream ?
cf. OSLC Workshop and Jazz
Extensions Workshop and the
Labs
where this Follow-up action is developed: "When a
Story is changed to the
Implemented state, the projects integration build will be
run"
Comments
![](http://jazz.net/_images/myphoto/f57199c599264a4bb3727ecda32b753f.jpg)
I know this is an old post and initially I thought this had my answer but now that I look closer, it seems it's not as straightforward as that. Question being: how do you set up Build Forge continuous integration on a stream? I.e., if one did want to auto-initiate a build after a delivery (which seems like a pretty typical use case), how would they do it?
![](http://jazz.net/_images/myphoto/f57199c599264a4bb3727ecda32b753f.jpg)
Nevermind, I think this article has what I need.
![](http://jazz.net/_images/myphoto/a408c118b57ef745f293aff9800ab3bd.jpg)
What would be the easiest way to automatically trigger a 'Request Personal Build' when Delivering Code to a Stream ?
cf. OSLC Workshop and Jazz Extensions Workshop and the Labs where this Follow-up action is developed: "
Implemented state, the projects integration build will be run