Re: [jbosstools-dev] How to setup an eclipse update site for Fuse Eclipse tooling
On 05/31/2013 10:48 AM, Lars Heinemann wrote:
1. I set up a Jenkins job already
(https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/SOA-Team/view/Fuse_...)
and used the SwitchYard Eclipse Tools
job as template. So far all is fine and the project builds but I saw
that my update site repository zip file has a different naming than
for example SwitchYard Tools where it
is named like "site-assembly.zip". How can I change the name of the
created zip file?
site-assembly.zip is what you get when you use the deprecated
Tycho type
"eclipse-update-site". repository.zip is what you get when you use the
"eclipse-repository" packaging type. It's better to have repository.zip.
You should update your scripts and Switchyard stuff to use
"eclipse-repository" and repository.zip.
2. The SwitchYard Tools job is calling a shell script after the Maven
build is finished. You pull some script file from a remote location
and execute it locally at the Jenkins job.
This script seems to do the update site deployment or at least some
preparations (haven't fully examined the script) but it seems to be a
general script which is used for
more than one project. (btw. this script assumes that the update site
zip file is named like "site-assembly.zip" if I understood it correctly)
The question is now if I can also call that script in our Jenkins job.
Maybe somebody could explain a bit more detailed what exactly is done
by that script and to check with me
if that script can be used for Fuse Tools as well.
Do you really need this script?
If all you need is to publish the update
site, simply use a scp or a rsync command. Target destination would be
something like filemgmt.jboss.org:downloads_htdocs/fuse/...
Later, you can change your mind if you have a good reason to use this
specific script.
3. I saw that the SwitchYard Tools Jenkins job triggers another job
after it is finished.
(https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Tools-pub...)
I
would say that you don't need another job to publish. It's easier to
do it as part of you build job.
Later, you can change your mind if you have a good reason to have
another job.
HTH
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
Attachments:
- attachment.html (text/html — 3.6 KB)