[closed] Setting up a build
Hello.
We are about to set up our first build in Jazz. The example ant build
file is working fine, but now we decided to really build something. :-)
Up to now, we always triggered a headless PDE build. The Eclipse PDE
build requires some maintenance effort; like keeping features and map
files in sync; build failure analysis occurs to be time consuming
especially when dependencies were set wrong or are not satisfied, ...
Now we wondered whether Jazz offers an alternative to the Eclipse PDE
build - for instance fetching the sources from SCM works via a seperate
build workspace instead of the ant fetch script generator. Is there a
way to trigger the compilation of plugins in an easier way or does the
build still rely on PDE build with disabled fetch phase?
Thanks and regards,
Stefan
We are about to set up our first build in Jazz. The example ant build
file is working fine, but now we decided to really build something. :-)
Up to now, we always triggered a headless PDE build. The Eclipse PDE
build requires some maintenance effort; like keeping features and map
files in sync; build failure analysis occurs to be time consuming
especially when dependencies were set wrong or are not satisfied, ...
Now we wondered whether Jazz offers an alternative to the Eclipse PDE
build - for instance fetching the sources from SCM works via a seperate
build workspace instead of the ant fetch script generator. Is there a
way to trigger the compilation of plugins in an easier way or does the
build still rely on PDE build with disabled fetch phase?
Thanks and regards,
Stefan
The question has been closed for the following reason: "The question is answered, right answer was accepted" by rschoon Feb 03 '18, 3:49 a.m.
4 answers
Hi Stefan,
Jazz offers the teamFetch task for fetching code from a Jazz workspace onto
the build machine. When using this task, you should disable PDE build's
fetch phase. I believe this is done by setting skipFetch=true in PDE build's
build.properties.
Jazz doesn't offer an alternative to PDE build for actually building
plugins.
Jazz itself is built using the teamFetch task and PDE build.
Ryan
Jazz offers the teamFetch task for fetching code from a Jazz workspace onto
the build machine. When using this task, you should disable PDE build's
fetch phase. I believe this is done by setting skipFetch=true in PDE build's
build.properties.
Jazz doesn't offer an alternative to PDE build for actually building
plugins.
Jazz itself is built using the teamFetch task and PDE build.
Ryan
Hello Ryan,
Yes, whereas it should be sufficient to have "skipFetch" set to whatever
value, as the "unless" condition only checks wheter a property is set or
not. :-) Took me some hours during my first times with and until I
realized that "skipFetch=false" didn't help :-D
Does the teamFetch order the sources in groups of "/plugins/*" and
"/features/*"? Or do I have to reorder them or reconfigure PDE build?
Regards,
Stefan
Jazz offers the teamFetch task for fetching code from a Jazz workspace onto
the build machine. When using this task, you should disable PDE build's
fetch phase. I believe this is done by setting skipFetch=true in PDE build's
build.properties.
Yes, whereas it should be sufficient to have "skipFetch" set to whatever
value, as the "unless" condition only checks wheter a property is set or
not. :-) Took me some hours during my first times with and until I
realized that "skipFetch=false" didn't help :-D
Does the teamFetch order the sources in groups of "/plugins/*" and
"/features/*"? Or do I have to reorder them or reconfigure PDE build?
Regards,
Stefan
Stefan,
No it's not going to order them by plugin, feature, etc. It's just fetching
the files and folders from SCM and writing them to the location you
specified in a way that matches the workspace you are fetching. It doesn't
try to interpret any kind of semantic meaning from the files...they are just
files and folders as far as that ant task is concerned.
Thanks,
Don
"Stefan Stern" <Stefan.Stern3@de.bosch.com> wrote in message
news:esi0j8$31f$1@localhost.localdomain...
No it's not going to order them by plugin, feature, etc. It's just fetching
the files and folders from SCM and writing them to the location you
specified in a way that matches the workspace you are fetching. It doesn't
try to interpret any kind of semantic meaning from the files...they are just
files and folders as far as that ant task is concerned.
Thanks,
Don
"Stefan Stern" <Stefan.Stern3@de.bosch.com> wrote in message
news:esi0j8$31f$1@localhost.localdomain...
Hello Ryan,
Jazz offers the teamFetch task for fetching code from a Jazz workspace
onto the build machine. When using this task, you should disable PDE
build's fetch phase. I believe this is done by setting skipFetch=true in
PDE build's build.properties.
Yes, whereas it should be sufficient to have "skipFetch" set to whatever
value, as the "unless" condition only checks wheter a property is set or
not. :-) Took me some hours during my first times with and until I
realized that "skipFetch=false" didn't help :-D
Does the teamFetch order the sources in groups of "/plugins/*" and
"/features/*"? Or do I have to reorder them or reconfigure PDE build?
Regards,
Stefan