Ed,
El 16/08/2010 10:09, Ed Willink escribió:
Hi Adolfo
I'm a bit confused.
Obviously the hudson ocl buckminster jobs are for your work in progress.
But you say you're on to 3.1.0 and will do an integration build. This
implies that you will use
https://build.eclipse.org/hudson/job/cbi-mdt-ocl-3.0-integration/,
but
I wouldn't expect you to try an integration until an N-build was
working and there are no CVS changes to the old maps etc.
I understood from your email, that the N-build properly worked when you
restarted it by hand. I've not focused my attention to it so far...
I'll review the logs to see if I understand why it has been failing.
The integration build could be seen like a prior test to our stable
build. It will help me to configure the update sites and promotion
scripts without building and promoting the stable one
I don't want to commit anything to 3.0.1 until you've learnt how to do
the branch build. I know from experience that when struggling with an
obstinate problem, every distraction has to be investigated to try to
find the problem and I don't want to cause you extra distractions. I
also don't want to commit to 3.0.1 what has not beem tried on HEAD.
I was able to do a branch build since it finally got the releng project
and sources from the branch. The problem is that the build failed. I
think that I've discovered the cause (the same one I think that
provoked the integration build using HEAD it failed some minutes ago):
I only changed the source of the Eclipse 3.7M1. The only reason I
figure out this change may cause the build fail, is that I erroneously
picked the x86 version file, while we had been using the Power PC one.
Since the integration and stable builds I was trying last week are
based in map files, I don't think that making changes to our source
files may cause any problem. Anyway, I'm OK if you want to wait until
the build successfully finishes.
Am I right in thinking that the athena and buckminster builds can just
co-exist, so that code development builds can continue to use Athena,
while release eng builds can use Buckminster? If so we just let the
Athena builds evolve naturally from 3.0 to 3.1 until Buckminster is
ready to take over.
I'm not sure what's the difference between "code development builds"
and "releng eng builds", but about your last sentence, yes, that's my
idea, specially when Indigo M1 is today for us ;)
Cheers,
Adolfo.
Regards
Ed
On 16/08/2010 09:04, Adolfo Sánchez-Barbudo Herrera wrote:
Ed
El 16/08/2010 6:29, Ed Willink escribió:
Hi
Adolfo
I need to fix Bug 322675 at least, so I need to do an N-build.
The two most recent N-builds failed for stupid reasons, a rerun just
worked, so it appears that there are still intermittent issues on
Hudson, or our scripts. Beware, it is still the case that a fail is not
a fail until it is reproducible and repositories have been stable for
four hours.
Since https://build.eclipse.org/hudson/job/cbi-mdt-ocl-3.0/
seems to be
working again, I'll redesignate it as 3.1.0 and commit my Examples
fixes to HEAD and when you're ready we can commit them to the 3.0.1
branch.
I'm on 3.1.0 right now. Apart from establishing the new Eclipse 3.7M1
as our platform, I'll have to set the correspondent Indigo's M1
updatesite zips from EMF, UML, Xtext, etc. EMF doesn't have M1 build
yet...
... So:
1. I'll run an Integration build to see a green build with at least
Eclipse 3.7M1.
2. Look into the new update site we are going to use for Indigo.
3. Accurate the promotions scripts and promote an Integration build to
see that all works fine...
When our required dependencies have their builds, I'll do the same to
get the Stable build.
3.0.1 will go later. You can commit changes to the branch if you want
to, though.
Good luck.
I hope I have better luck than I had last week ;P
Cheers,
Adolfo.
Ed
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.851 / Virus Database: 271.1.1/3074 - Release Date: 08/15/10 19:35:00
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
