It's all about the answers!

Ask a question

Does Jazz have the notion of "released" builds?


Jeffrey Liu (111131) | asked Jul 17 '07, 5:12 p.m.
Hi,

Does Jazz have the notion of "released" builds (similar to how things work in Eclipse)? It seems to me once code is delivered, it will show up in the build. Meaning, a developer does not have to go through the process of "tagging" the code to make it available to the "released" build. The process of "tagging" the code allows us to have two types of builds:

1. Daily/Latest builds. This build fetches code has been delivered to the the server.

2. Released/Integration builds. This build fetches code that are delivered and tagged.

One of the reason for the two different types of builds is to allow us to discover integration problems in the daily builds before they make their way to the integration builds. Does Jazz support something similar?

Thanks,

Jeff

2 answers



permanent link
Jean-Michel Lemieux (2.5k11) | answered Jul 17 '07, 10:06 p.m.
JAZZ DEVELOPER
Hi Jeff,

Take a look at figure 8 in
https://jazz.net/learn/LearnItem.jsp?href=content/docs/source-control/streamdev/index.html.
In fact, it may be a useful read the whole document since it summarizes
how to use streams and repository workspace in Jazz do to what you are
asking.

In Jazz we don't tag things, instead you deliver the change-sets to the
streams you want them in. Integration builds are run from the
integration streams and daily builds are run from a particular teams
stream. If you want your changes in the integration build, deliver them
to that stream.

To summarize, the Jazz team works exactly as you describe. In addition,
we have builds which run from our own repository workspaces so that
developers can run builds before even delivering to their team ;)

Cheers,
Jean-Michel


jeffliu wrote:
Hi,

Does Jazz have the notion of "released" builds (similar to
how things work in Eclipse)? It seems to me once code is delivered,
it will show up in the build. Meaning, a developer does not have to
go through the process of "tagging" the code to make it
available to the "released" build. The process of
"tagging" the code allows us to have two types of builds:

1. Daily/Latest builds. This build fetches code has been delivered to
the the server.

2. Released/Integration builds. This build fetches code that are
delivered and tagged.

One of the reason for the two different types of builds is to allow us
to discover integration problems in the daily builds before they make
their way to the integration builds. Does Jazz support something
similar?

Thanks,

Jeff

permanent link
Christophe Cornu (47123) | answered Jul 17 '07, 11:11 p.m.
Jean-Michel's link works if you ignore the trailing dot.

https://jazz.net/learn/LearnItem.jsp?href=content/docs/source-control/streamdev/index.html

Chrix

Your answer


Register or to post your answer.