[BUILD] deliver snapshots to stream
Currently we have a stream, lets call it 'trunk'.
We then have a workspace 'trunk-build' which is used by our jazz build
engine to perform builds (as per the instructions suggest it should be
setup).
Currently snapshots are automatically created in the 'trunk-build'
(e.g., trunk-20090101-0900) workspace by the build engine whenever it
creates a build.
a) is there a way to have these snapshots automatically delivered to the
stream?
b) (even better) is there a way to have just the successfully built
snapshots automatically delivered to the stream?
We then have a workspace 'trunk-build' which is used by our jazz build
engine to perform builds (as per the instructions suggest it should be
setup).
Currently snapshots are automatically created in the 'trunk-build'
(e.g., trunk-20090101-0900) workspace by the build engine whenever it
creates a build.
a) is there a way to have these snapshots automatically delivered to the
stream?
b) (even better) is there a way to have just the successfully built
snapshots automatically delivered to the stream?
2 answers
On 02/03/09 16:54, Dominic Evans wrote:
Surprised no responses to this yet, hasn't anyone else wanted to do this?
I guess I could achieve it by calling out to the scm executable and
delivering from trunk-build to trunk, but presumed there was a better
'standard' way of doing this.
Currently we have a stream, lets call it 'trunk'.
We then have a workspace 'trunk-build' which is used by our jazz build
engine to perform builds (as per the instructions suggest it should be
setup).
Currently snapshots are automatically created in the 'trunk-build'
(e.g., trunk-20090101-0900) workspace by the build engine whenever it
creates a build.
a) is there a way to have these snapshots automatically delivered to the
stream?
b) (even better) is there a way to have just the successfully built
snapshots automatically delivered to the stream?
Surprised no responses to this yet, hasn't anyone else wanted to do this?
I guess I could achieve it by calling out to the scm executable and
delivering from trunk-build to trunk, but presumed there was a better
'standard' way of doing this.