how should we organize emergency fixing?
![]()
We defined a dedicated stream for emergency fixes, to which all developers of the team can make contributions if necessary.
This stream should be in sync with the production stream as well as the related build workspace. Without syncing the build workspace, too many items will be built. Sync of the stream is no problem as the developer is member of the team area owning the stream. Problem: the developer can't sync the build workspace as he is not the owner; the build user is. |
Accepted answer
![]()
Resolved by creating a script that performs the synchronization using the build user.
Ralph Schoon selected this answer as the correct answer
|
One other answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Oct 26 '15, 8:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Bernd,
1. You can set up a green stream scenario, where the build delivers the changes after a successful build. That way, you would always have a stream that is good. 2. If the build runs against the emergency stream, the build process loads the content of that stream during builds. So it is synchronized to the stream at the moment of the load. 2. Personal builds are the best way to run a build on the changes even before delivering, in this case the build is run on the repository workspace of the user. Comments Hi Ralph,
|
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.