search

eclipse-modisco / org.eclipse.modisco

Eclipse Public License 2.0
0 stars 0 forks source link

Should MoDisco build monitor more than just plugins for changes? #60

Closed eclipse-modisco-bot closed 5 hours ago

eclipse-modisco-bot commented 5 hours ago

| --- | --- | | Bugzilla Link | 292553 | | Status | CLOSED WORKSFORME | | Importance | P3 normal | | Reported | Oct 16, 2009 12:43 EDT | | Modified | Sep 22, 2010 04:53 EDT | | Reporter | Nick Boldt |

Description

I notice in your nightly build you export http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/plugins/trunk so that Hudson can monitor it for changes and build reactively.

Then, for every build, you svn export the other files you need:

$SVN export svn://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/features/trunk $hudsonWorkspace/MoDiscoTree/features

$SVN export svn://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/plugins/trunk $hudsonWorkspace/MoDiscoTree/plugins

$SVN export svn://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/tests/trunk/ $hudsonWorkspace/MoDiscoTree/plugins --force\ $SVN export svn://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/tests/trunk/org.eclipse.gmt.modisco.tests.feature $hudsonWorkspace/MoDiscoTree/features/org.eclipse.gmt.modisco.tests.feature --force

You could also, if you wanted, simply set this path as your svn repo URL to monitor:

http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco

and then simply set this in EXTRAFLAGS:

-localSourceCheckoutDir /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/workspace/org.eclipse.gmt.modisco

The added bonus is that changes to features & tests would also trigger new nightly builds, not just changes to plugins.

eclipse-modisco-bot commented 5 hours ago

By Hugo Bruneliere on Oct 19, 2009 04:10

Hi Nick,

Thanks for the tip ;-)

Nicolas, do you think you could change this?

Regards,

Hugo

eclipse-modisco-bot commented 5 hours ago

By Nicolas Bros on Oct 19, 2009 10:22

I hesitated before choosing the svn URL to export, but I settled on "plugins/trunk" because I noticed that Hudson would pull the whole project SVN (with all the branches and tags) if I passed "http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco".

I checked again, and it still exports all branches and tags. It took 22 minutes just doing that, and there was only one branch (created by mistake, I just deleted it), and one tag.

eclipse-modisco-bot commented 5 hours ago

By Hugo Bruneliere on Oct 19, 2009 10:56

Hi Nicolas,

In that case, it is better to keep the current working solution (anyway, we can keep this in mind for later upgrades).

Regards,

Hugo

eclipse-modisco-bot commented 5 hours ago

By Nick Boldt on Oct 19, 2009 14:27

(In reply to comment #2)

I hesitated before choosing the svn URL to export, but I settled on "plugins/trunk" because I noticed that Hudson would pull the whole project SVN (with all the branches and tags) if I passed "http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco".

I checked again, and it still exports all branches and tags. It took 22 minutes just doing that, and there was only one branch (created by mistake, I just deleted it), and one tag.

If you reorg your SVN repo so it's

http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/trunk/\ http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/branches/\ http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/tags/

then you can simply export

http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/trunk/

You shouldn't have to do a full export each time. Hudson SHOULD be able to just do an svn up to fetch changes into the workspace, which shouldn't take more than seconds. There's a flag in the config for that iirc.

But to each their own. :)