Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and Plans for Galileo Build

Hi Oisin,

Oisin Hurley wrote:
The new build is well documented at
Works well for headless -verifyOnly at least - I made a small
correction to the builder app name on the wiki page.
Glad to hear that you were able to run it. I guess this was on a Mac?

One thing to note - if you keep the <configs/> line in the file, it will default to processing a win32.win32.x86

Yes. The OS/WS/ARCH are all enums in the ecore 'Build' model and win32, win32, x86 happens to be the the default setting. I wouldn't be surprised if the editor actually senses that and hence, creates the empty <config/> element for that particular config.

When I do a full mirror build (which took 339 minutes) I get
a lot of whines about not being able to download some
artifacts, for example:

- mirroring artifact
Unable to unpack artifact
in repository file:/Users/ohurley/Projects/osstools/galileo/buckbuilder-tryout/build/mirror:
Problems downloading artifact:

I'm tempted to assume that this is a network transient
issue, rather than anything wrong with the particular
contributions or with the builder, since David and Thomas
have managed full builds.
A run using -logLevel DEBUG might tell you more about the cause of the error. I say might, because sometimes the information about the cause is simply gone and all that's left is the "Problems loading artifact:" exception. The p2 team is continuously improving the error propagation so we might see better output here in the near future.

I'd like to echo David's words of thanks to Rich and add my own
to Thomas for this build facility - good stuff guys!  Now, if we
could just create an Xtext editor based on the build model, we
wouldn't need to use XMI anymore ;)
Thank you kindly for you warm words :-)

- thomas

Back to the top