U++ forum: Welcome to the forum

Re: Automatic nightly builds reastored - and reason(s) why it was failing (unodgs, please read :) [message #30688 is a reply to message #30679]

Mon, 17 January 2011 11:20

dolik.rce
Messages: 1791
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

mirek wrote on Sun, 16 January 2011 23:29

I have noticed (quite late, apologies) that our nightly builds no google-code stopped at 12/31.

Now there probably were multiple issues (changed login, exceeded quota) but even after fixing all of these, process was failing.

The final reason was that TabBar package that is now part of ide.

The problem is that not all packages in uppsrc are exported to nightly builds - only those in uppsrc/packages (and uppsrc/packages1) are exported. With TabBar not being there, infrastructure had incomplete 'uppsrc' and failed to compiled theide.

So the moral of the story: If we add package to uppsrc, we must not forget to put it into uppsrc/packages Smile

Mirek

Hi Mirek,

I'm afraid that I should take part of the responsibility for not noticing earlier. The launchpad builds were failing as well Embarassed

Also I would like to say that I was not aware of this mechanism until today, even though I am pretty familiar with the build infrastructure.

Is there some special reason to limit uppsrce to certain packages? It is quite error prone I would say (e.g. RasterPlayer and XmlView are missing as of now...) Are you trying to save a bandwith or make the installer smaller? The first is not an issue if you use svn or just correctly set rsync. And the installer size won't change much if you add the three or four directories that are left out now.

I'd really recommend to reorganize it slightly, to use full copy to prevent failures like this in future and also to simplify the whole process.

Best regards,
Honza

PS: By "full copy" in the above paragraphs I mean only full copy of the five assemblies that are put in installer, no uppdev, uppbox etc.

Report message to a moderator