It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: Nov 19 '07, 9:08 p.m.
question was seen: 5,143 times
last updated: Nov 19 '07, 9:08 p.m.

Related questions

Question about Builds using cmd-line

0
Tom Frauenhofer (1.3k●5●84●35) | asked Nov 19 '07, 9:08 p.m.
How does a cmd-line build get the source code to be built ??

I'm looking for the place where I tell Jazz that my command-line build
requires a certain stream/baseline.

Perhaps cmd-line build scripts must get their own source, so that begs
the question, how can a script or program ask the Jazz SCM to deliver
some source ??

Cheers

5 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ryan Manwiller (1.3k●1) | answered Nov 20 '07, 9:48 a.m.
JAZZ DEVELOPER
If you are using M3, you can apply the attached patch to get a "Jazz SCM"
page in the build definition editor (you'll need to create a new cmd line
build to see it).

This is fixed in M4.


Close Team Concert and replace the jar at
\jazz\client\eclipse\jazz\jtd\eclipse\plugins\com.ibm.team.build.common_0.5.0.I20071006-1336.jar


Be sure to add a -clean argument when you relaunch Team Concert. Otherwise,
the patch may not be recognized.


Once you put the new jar in place, you should then be able to create a
"Command line with Jazz SCM" build definition.
On the Jazz SCM page, select a workspace and fetch destination.
0
permanent link
Tom Frauenhofer (1.3k●5●84●35) | answered Nov 20 '07, 11:18 p.m.
Thanks Ryan

Yes, I'm using M3 so I'll give the patch a try

regards

Ryan Manwiller wrote:
If you are using M3, you can apply the attached patch to get a "Jazz
SCM" page in the build definition editor (you'll need to create a new
cmd line build to see it).

This is fixed in M4.


Close Team Concert and replace the jar at
\jazz\client\eclipse\jazz\jtd\eclipse\plugins\com.ibm.team.build.common_0.5.0.I20071006-1336.jar



Be sure to add a -clean argument when you relaunch Team Concert.
Otherwise, the patch may not be recognized.


Once you put the new jar in place, you should then be able to create a
"Command line with Jazz SCM" build definition.
On the Jazz SCM page, select a workspace and fetch destination.
0
permanent link
Tom Frauenhofer (1.3k●5●84●35) | answered Nov 21 '07, 8:08 a.m.
On closer inspection, I'm actually running 0.6M3a and my current jar
file looks like:

com.ibm.team.build.common_0.5.0.I20071012-2004.jar

So, I tried renaming the above, and dropping the attached replacement
into the same directory. Restarting RTC -clean didn't seem to offer any
new Build options.

Is there an 0.6M3a jar file ?




Ryan Manwiller wrote:
If you are using M3, you can apply the attached patch to get a "Jazz
SCM" page in the build definition editor (you'll need to create a new
cmd line build to see it).

This is fixed in M4.


Close Team Concert and replace the jar at
\jazz\client\eclipse\jazz\jtd\eclipse\plugins\com.ibm.team.build.common_0.5.0.I20071006-1336.jar



Be sure to add a -clean argument when you relaunch Team Concert.
Otherwise, the patch may not be recognized.


Once you put the new jar in place, you should then be able to create a
"Command line with Jazz SCM" build definition.
On the Jazz SCM page, select a workspace and fetch destination.
0
permanent link
Ryan Manwiller (1.3k●1) | answered Nov 26 '07, 10:38 a.m.
JAZZ DEVELOPER
The jar should work with M3a. As long as you renamed it so you are replacing
the existing jar and started the client with -clean, then you should see a
"Command line with Jazz SCM" option when you create a new build definition.
0
permanent link
Tom Frauenhofer (1.3k●5●84●35) | answered Nov 27 '07, 1:08 p.m.
OK, I get now ... I need to replace the existing jar

Thanks

Ryan Manwiller wrote:
The jar should work with M3a. As long as you renamed it so you are
replacing the existing jar and started the client with -clean, then you
should see a "Command line with Jazz SCM" option when you create a new
build definition.

Your answer

Register or to post 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.