Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Re: [Fwd: [Galileo] Failed for build 2009-07-30_12-45-59]

The Modeling build is deprecated. I won't be supporting it but if someone else wants to do so they're welcome. It's not an official project according to the Foundation but it wouldn't be hard to add more committers to /cvsroot/modeling/releng-common/ where all the magic happens - I can suggest a few people who'd be ideal candidates.

People wanting root access to modeling.eclipse.org can ask me and get it for little more than a song and proof they know what `sudo make me a sandwich` means. :)

---

As to the more immediate issue at hand...

If a project's maintenance updates break Galileo, then there's something very wrong w/ that update. Surely it should be a drop-in replacement for the x.y.0 bits that were shipped in June, along with an update to the appropriate .build file?

Note too that the bits ref'd by Galileo should be on the /releases/ or /stable/ site, and any new maintenance builds should be on the /interim/ site... so if you wanted to build without contributing to Galileo, that should be entirely doable too. That's how things worked for Ganymede, IIRC.

Nick

Dave Steinberg wrote:
Nick,

This sounds like it will be a significant problem in the not-too-distant future. During the last cycle, we were asked to refrain from pushing new builds to Galileo for days or weeks at a time.

Will we be able to find a solution for users of the old modeling build, or is the message here that everyone had better expect to get on Athena this time around?

Cheers,
Dave

--
Dave Steinberg
Rational Software - IBM Toronto Lab
mailto:davidms@xxxxxxxxxx


Inactive hide details for Nick Boldt ---08/03/2009 09:06:05 PM---Because we changed the way the Modeling update sites work duriNick Boldt ---08/03/2009 09:06:05 PM---Because we changed the way the Modeling update sites work during the


From:	
Nick Boldt <nickboldt@xxxxxxxxx>

To:	
David M Williams <david_williams@xxxxxxxxxx>

Cc:	
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Date:	
08/03/2009 09:06 PM

Subject:	
[cross-project-issues-dev] Re: [Fwd: [Galileo] Failed for build 2009-07-30_12-45-59]

------------------------------------------------------------------------



Because we changed the way the Modeling update sites work during the
Galileo cycle (only one build per type per branch per component is now
kept), I'd say yes, if you publish a new build to the existing shared
EMF update site, you must also share it w/ Galileo via a .build file
update.

--

Or, start using Athena [0], get a Hudson job [1], and you can publish
those new builds [2] to a new Teneo-only site which won't conflict w/
Galileo.

[0]http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Eclipse
[1]http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson
[2]http://wiki.eclipse.org/Common_Build_Infrastructure/Publishing

--

Nick


On Sat, Aug 1, 2009 at 2:30 AM, David M
Williams<david_williams@xxxxxxxxxx> wrote:
 > That's part of what should be maintained in a consistent state, somehow,
 > so that Galileo can always build successfully.
 >
 > What some people do is have one site that's relatively permeant, exactly
 > corresponding to their Galileo release, and then have another site for
 > their maintenance builds and repositories. And, then, only when Galileo
 > says "go" would you change the Galileo build files to point to your new
 > maintenance repositories. Hope that makes sense.
 >
 > But, you can work on improving that part of your process for the long
> term. It is about time to start Galileo maintenance builds anyway, so feel
 > free to update your Galileo .build files to be accurate for your
 > maintenance so Galileo can build clean once again.
 >
 > Let me know if I can help further.
 >
 > Thanks,
 >
 >
 >
 >
 >
 >
 > From:
 > Martin Taal <mtaal@xxxxxxxxx>
 > To:
 > David M Williams/Raleigh/IBM@IBMUS, Nick Boldt <nickboldt@xxxxxxxxx>
 > Date:
 > 08/01/2009 02:09 AM
 > Subject:
 > [Fwd: [Galileo] Failed for build 2009-07-30_12-45-59]
 >
 >
 >
 > Hi David,
 > The error below occurs because I have been publishing new maintenance
 > builds. I did not publish them to the galileo update site but these
 > maintenance build are published to the EMF update site. This means that
 > the previous build is removed from that site.xml. So therefore Galileo
 > can't find them anymore there.
 >
 > So maybe this means that I have to re-publish maintenance builds to
 > Galileo also?
 >
 > (Nick, let me know what you think here also).
 >
 > gr. Martin
 >
 > -------- Original Message --------
 > Subject:                 [Galileo] Failed for build 2009-07-30_12-45-59
 > Date:            Thu, 30 Jul 2009 12:46:43 -0400
 > From:            David Williams <david_williams@xxxxxxxxxx>
 > To:              EMF TENEO Build Team <mtaal@xxxxxxxxx>, EMF TENEO Build
 > Team
 > <stepper@xxxxxxxxxx>
 > CC:              David Williams <david_williams@xxxxxxxxxx>
 >
 >
 >
 > The following errors occured when building Galileo:
 >
 > Unable to find
> org.eclipse.emf.teneo.sdk.feature.group/1.1.1.v200907131202-42188FAGLgdKWIT4AQmYeJg_SEFC
 > in repository http://download.eclipse.org/modeling/emf/updates/interim/
 >
 > Unable to find
> org.eclipse.emf.teneo.eclipselink.sdk.feature.group/1.0.0.v200907131202-31184E44QYeJMQL9SeXgJZFWWGHN
 > in repository http://download.eclipse.org/modeling/emf/updates/interim/
 >
 > Check the log file for more information: https://$
> {env.HOSTNAME}.eclipse.org/hudson/view/Galileo/job/galileo.runBuckyBuild/643/console
 >
 >
 >
 >
 > --
 >
 > With Regards, Martin Taal
 >
 > Springsite/Elver.org
 > Office: Hardwareweg 4, 3821 BV Amersfoort
 > Postal: Nassaulaan 7, 3941 EC Doorn
 > The Netherlands
 > Cell: +31 (0)6 288 48 943
 > Tel: +31 (0)84 420 2397
 > Fax: +31 (0)84 225 9307
 > Mail: mtaal@xxxxxxxxxxxxxx - mtaal@xxxxxxxxx
 > Web: www.springsite.com - www.elver.org
 >
 >
 >
 >
 >



--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Dash Athena
http://nick.divbyzero.com
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



------------------------------------------------------------------------

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena


Back to the top