[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [bpel-dev] Update sites and Builds


Actually, we are in version 0.8.0 (the Hudson job should be renamed).
OK for the promotion mechanism. But we have to do it manually, right? That's fine with me.
Yes, I think that should be done manually. It is just a copy on download.eclipse.org.
It always happen that someone has to perform something to do a release (could it be to run a new build with a flag, run a script...), here it is just a copy.

We have one job for Helios (bpel-0.5) and one for Juno (-juno). We must keep one job per platform to make sure it builds and works.
Eclipse Platform and the dependency you use guarantee that if you work with Indigo, it should be fine for Juno.
Maybe we could try to set up a mechanism to build on a Indigo platform and test on a 4.2.
For the moment, packing and signing is done with Maven, in the Juno build.
It could be done in any build, I don't think it will cause troubles.
What changes do you propose?
Which job will pack, sign and publish the snapshot update site?
bpel-0.8 would produce the repository, test it and publish it to 0.8.0/snapshot. All repositories (including snapshots) would be packed and signed).
If we want to test against several platforms, we could think about a job that would consume the published site and perform some tests.

What do you think about it?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets