Build related questions
Hi,
is following scenario OK:
1. I requested a build from our main stream
2. The build has been built successfully
3. Later on, I requested same build engine to create a build from my
repository workspace
This means the engine has fetched files from the stream; it is the local
copy; now it needs to check the local fetch towards the workspace - is this
OK?
Next question: the build definition/Jazz SCM page says I should create a
workspace for a stream - in fact, I have associated the build definition
with the stream. Is this OK?
Thanks,
Roman
is following scenario OK:
1. I requested a build from our main stream
2. The build has been built successfully
3. Later on, I requested same build engine to create a build from my
repository workspace
This means the engine has fetched files from the stream; it is the local
copy; now it needs to check the local fetch towards the workspace - is this
OK?
Next question: the build definition/Jazz SCM page says I should create a
workspace for a stream - in fact, I have associated the build definition
with the stream. Is this OK?
Thanks,
Roman
5 answers
You should probably not let two different workspace/stream be fetched to the
same location on the local file system (I'm not sure this will work in all
cases), unless you are "deleting before fetching" to clean the location.
In the build defintion, you should typically specify a workspace (not a
stream) because only then can the build system keep track the work items
that went into the build (it does this by analyzing what was accepted into
your build workspace from the main stream).
You should create a "build workspace" that flows from your main stream.
---
Ryan Manwiller
Jazz Team Build
same location on the local file system (I'm not sure this will work in all
cases), unless you are "deleting before fetching" to clean the location.
In the build defintion, you should typically specify a workspace (not a
stream) because only then can the build system keep track the work items
that went into the build (it does this by analyzing what was accepted into
your build workspace from the main stream).
You should create a "build workspace" that flows from your main stream.
---
Ryan Manwiller
Jazz Team Build
Why shall I create Build workspace?
Roman
"Ryan Manwiller" <ryanman@no-s-p-a-m.us.ibm.com> wrote in message
news:ft6apk$kdb$1@localhost.localdomain...
Roman
"Ryan Manwiller" <ryanman@no-s-p-a-m.us.ibm.com> wrote in message
news:ft6apk$kdb$1@localhost.localdomain...
You should probably not let two different workspace/stream be fetched to
the same location on the local file system (I'm not sure this will work in
all cases), unless you are "deleting before fetching" to clean the
location.
In the build defintion, you should typically specify a workspace (not a
stream) because only then can the build system keep track the work items
that went into the build (it does this by analyzing what was accepted into
your build workspace from the main stream).
You should create a "build workspace" that flows from your main stream.
---
Ryan Manwiller
Jazz Team Build
It is recommended to create a build workspace, instead of building directly
from your main stream. When you build directly from the main stream, we
cannot create baselines of the components and files used in the build, so
you have no way to re-create the files from the build later on.
By using a build workspace, you guarantee that the state of the workspace is
baselined before the build starts. You can then recreate the files used in
any build later on.
---
Ryan Manwiller
Jazz Team Build
from your main stream. When you build directly from the main stream, we
cannot create baselines of the components and files used in the build, so
you have no way to re-create the files from the build later on.
By using a build workspace, you guarantee that the state of the workspace is
baselined before the build starts. You can then recreate the files used in
any build later on.
---
Ryan Manwiller
Jazz Team Build
I see now. That is quite pity - I love SVN can reconstruct whatever state.
All you need to know is the revision number.
Anyway, I added Snapshot contribution and created a build from my private
workspace and a result still says: missing contribution (the snapshot
field).
What is missing?
Roman
"Ryan Manwiller" <ryanman@no-s-p-a-m.us.ibm.com> wrote in message
news:ftgall$8iv$1@localhost.localdomain...
All you need to know is the revision number.
Anyway, I added Snapshot contribution and created a build from my private
workspace and a result still says: missing contribution (the snapshot
field).
What is missing?
Roman
"Ryan Manwiller" <ryanman@no-s-p-a-m.us.ibm.com> wrote in message
news:ftgall$8iv$1@localhost.localdomain...
It is recommended to create a build workspace, instead of building
directly from your main stream. When you build directly from the main
stream, we cannot create baselines of the components and files used in the
build, so you have no way to re-create the files from the build later on.
By using a build workspace, you guarantee that the state of the workspace
is baselined before the build starts. You can then recreate the files used
in any build later on.
---
Ryan Manwiller
Jazz Team Build
I got it. When I created Build workspace and changed the build definition to
accept incoming changes I got the snapshot then.
Roman
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:fti1r8$m1$1@localhost.localdomain...
accept incoming changes I got the snapshot then.
Roman
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:fti1r8$m1$1@localhost.localdomain...
I see now. That is quite pity - I love SVN can reconstruct whatever state.
All you need to know is the revision number.
Anyway, I added Snapshot contribution and created a build from my private
workspace and a result still says: missing contribution (the snapshot
field).
What is missing?
Roman
"Ryan Manwiller" <ryanman@no-s-p-a-m.us.ibm.com> wrote in message
news:ftgall$8iv$1@localhost.localdomain...
It is recommended to create a build workspace, instead of building
directly from your main stream. When you build directly from the main
stream, we cannot create baselines of the components and files used in
the build, so you have no way to re-create the files from the build later
on.
By using a build workspace, you guarantee that the state of the workspace
is baselined before the build starts. You can then recreate the files
used in any build later on.
---
Ryan Manwiller
Jazz Team Build