What is the stream counterpart of "HEAD"?
I already have a build definition and build engine running. The build definition is configured to use the Jazz repository and will "Accept latest changes before loading". The build definition uses a workspace that has all the stream components and is only used by the auto-build user.
If I request a build, a snapshot get created. I was expecting that if new modifications get delivered to the stream then the succeeding builds should be able to accept those into the repository workspace and then load it in the build machine running the engine.
What I have observed so far is that the auto-build repository workspaces gets stuck on the last snapshot created so the new changes doesn't get accepted because technically the workspace is updated relative to the snapshot that it is configured in. I have to login and replace the components of the auto-build repository workspace with the latest in the stream.
Am I missing a configuration item? Maybe another track is how to automatically flow the created snapshot/baseline to the stream so that they will be synchronized and new delivered modifications can be seen in the auto-build workspace.
ciao!
If I request a build, a snapshot get created. I was expecting that if new modifications get delivered to the stream then the succeeding builds should be able to accept those into the repository workspace and then load it in the build machine running the engine.
What I have observed so far is that the auto-build repository workspaces gets stuck on the last snapshot created so the new changes doesn't get accepted because technically the workspace is updated relative to the snapshot that it is configured in. I have to login and replace the components of the auto-build repository workspace with the latest in the stream.
Am I missing a configuration item? Maybe another track is how to automatically flow the created snapshot/baseline to the stream so that they will be synchronized and new delivered modifications can be seen in the auto-build workspace.
ciao!
3 answers
This is odd because the build engine does exactly what you are requesting.
It will automatically accept in the latest changes when the "Accept latest
changes before loading" check box is enabled. If you click the workspace
link that is next to the workspace specified on the Jazz Source Control page
in the build definition editor for your build defintion...does it show any
flow targets assigned to it?
Don Weinand
Jazz Team Build
"ramfree17" <ramfree17> wrote in message
news:g94vhg$k98$1@localhost.localdomain...
It will automatically accept in the latest changes when the "Accept latest
changes before loading" check box is enabled. If you click the workspace
link that is next to the workspace specified on the Jazz Source Control page
in the build definition editor for your build defintion...does it show any
flow targets assigned to it?
Don Weinand
Jazz Team Build
"ramfree17" <ramfree17> wrote in message
news:g94vhg$k98$1@localhost.localdomain...
I already have a build definition and build engine running. The build
definition is configured to use the Jazz repository and will
"Accept latest changes before loading". The build
definition uses a workspace that has all the stream components and is
only used by the auto-build user.
If I request a build, a snapshot get created. I was expecting that if
new modifications get delivered to the stream then the succeeding
builds should be able to accept those into the repository workspace
and then load it in the build machine running the engine.
What I have observed so far is that the auto-build repository
workspaces gets stuck on the last snapshot created so the new changes
doesn't get accepted because technically the workspace is updated
relative to the snapshot that it is configured in. I have to login
and replace the components of the auto-build repository workspace
with the latest in the stream.
Am I missing a configuration item? Maybe another track is how to
automatically flow the created snapshot/baseline to the stream so
that they will be synchronized and new delivered modifications can be
seen in the auto-build workspace.
ciao!
Also...what's state of the "Delete directory before loading" checkbox on
the Jazz Source Control page for your definition?
Don Weinand
Jazz Team Build
"ramfree17" <ramfree17> wrote in message
news:g94vhg$k98$1@localhost.localdomain...
the Jazz Source Control page for your definition?
Don Weinand
Jazz Team Build
"ramfree17" <ramfree17> wrote in message
news:g94vhg$k98$1@localhost.localdomain...
I already have a build definition and build engine running. The build
definition is configured to use the Jazz repository and will
"Accept latest changes before loading". The build
definition uses a workspace that has all the stream components and is
only used by the auto-build user.
If I request a build, a snapshot get created. I was expecting that if
new modifications get delivered to the stream then the succeeding
builds should be able to accept those into the repository workspace
and then load it in the build machine running the engine.
What I have observed so far is that the auto-build repository
workspaces gets stuck on the last snapshot created so the new changes
doesn't get accepted because technically the workspace is updated
relative to the snapshot that it is configured in. I have to login
and replace the components of the auto-build repository workspace
with the latest in the stream.
Am I missing a configuration item? Maybe another track is how to
automatically flow the created snapshot/baseline to the stream so
that they will be synchronized and new delivered modifications can be
seen in the auto-build workspace.
ciao!
If you click the workspace
link that is next to the workspace specified on the Jazz Source Control page
in the build definition editor for your build defintion...does it show any
flow targets assigned to it?
thanks don, this hit the nail in the head. the flow targets of the auto-build workspace was empty. i don't know how it became that way but it seems to be working now so i am happy. :D
ciao!