What happens if a change set is delivered to a stream while that stream is fetching for a build?
Some of our components are quite large and users have expressed concern over what might happen if they deliver a change set while a build is in the process of fetching. I am hoping that the fetch creates a snapshot before it starts and knows that anything delivered after it starts should be excluded. Is that the case?
Thanks,
Alexa
Accepted answer
Hi Alexa,
There is an option in your build definition on the Jazz Source Control tab to accept the latest changes from the stream into your build workspace. If you select this (which is the typical behavior), a snapshot is created containing all the latest changes and the snapshot is used for the build. If you don't select this, whatever changes are already in your build workspace would be used for the build, and anything new delivered to the stream would have no impact. So, you're covered either way.
There is an option in your build definition on the Jazz Source Control tab to accept the latest changes from the stream into your build workspace. If you select this (which is the typical behavior), a snapshot is created containing all the latest changes and the snapshot is used for the build. If you don't select this, whatever changes are already in your build workspace would be used for the build, and anything new delivered to the stream would have no impact. So, you're covered either way.
Comments
3 other answers
If you are using the JBE, then let your worries be gone. The JBE creates a snapshot first and then populates the build workspace with the snapshot. So, at the time of the snapshot creation all delivered change sets would be included in the snapshot and thus the build. If the change set was delivered during the build process it would not be picked up by the JBE because it was not in the snapshot.
Hope this helps.
Once the build workspace has finished accepting changes from the stream, any deliveries to the stream will miss the build. The changes will have to wait until the next build.
If you're wondering about what happens when the workspace is accepting when someone delivers to the stream, the accept operation works off of a report to specify which changes will be accepted. It wouldn't know about the new changes while accepting.
I also believe the snapshot occurs after accepting changes. Someone else may correct me if I'm wrong.
If you're wondering about what happens when the workspace is accepting when someone delivers to the stream, the accept operation works off of a report to specify which changes will be accepted. It wouldn't know about the new changes while accepting.
I also believe the snapshot occurs after accepting changes. Someone else may correct me if I'm wrong.
I believe the build is based off of a snapshot.
To validate, one a build starts, you can view the change sets that were accepted into the build. See the following article for details
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?topic=%2Fcom.ibm.team.build.doc%2Ftopics%2Fc_understanding_build_spec_build_results.html&resultof%3D%2522%2562%2575%2569%256c%2564%2522%2520
To validate, one a build starts, you can view the change sets that were accepted into the build. See the following article for details
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?topic=%2Fcom.ibm.team.build.doc%2Ftopics%2Fc_understanding_build_spec_build_results.html&resultof%3D%2522%2562%2575%2569%256c%2564%2522%2520
