Build server script for autoproj-based installs

Build server script for autoproj-based installs

On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
> Here it is
>
> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-server
>
> I hope the usage message is self-explanatory. If in doubt, ask !
>
> Sylvain

I had to modify this script for my hudson build. Now for some reason, I get
this error:

+ ruby autoproj_bootstrap git /home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master/buildconf
branch=master
autodetecting the operating system
autoproj: installing a proper Ruby environment (this can take a long time)
autoproj: installing autoproj and its dependencies (this can take a long time)
installing/updating RubyGems dependencies: autobuild, rdoc
Enclosing class/module 'mUtilrb' for class WeakRef not known
Enclosing class/module 'cWeakRef' for class RefError not known
Enclosing class/module 'mUtilrb' for class WeakRef not known
Enclosing class/module 'cWeakRef' for class RefError not known
installing/updating RubyGems dependencies: autoproj
autodetecting the operating system
checking out autoproj main configuration
Access method to gitorious (git, http or ssh)
Use 'ssh' only if you have a gitorious account and have commit rights
on the Orocos projects. Otherwise, we advise you to use 'git' [git]
/home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master/orocos-
toolchain/autoproj/init.rb:66: end of file reached
 in /home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master/orocos-
toolchain/autoproj/init.rb:66
ERROR: failed to run autoproj bootstrap git,
/home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master/buildconf,
branch=master

I have no idea where this comes from, the init.rb file looks fine to me...
ideas?

I also had to remove the comitting of the config.yml file since autoproj refused
to merge the upstream master branch with that local commit. I just removed the
git add/commit for config.yml.

Peter

Build server script for autoproj-based installs

On 12/16/2010 01:54 PM, Peter Soetens wrote:
> On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
>> Here it is
>>
>> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-server
>>
>> I hope the usage message is self-explanatory. If in doubt, ask !
>>
>> Sylvain
>
> I had to modify this script for my hudson build. Now for some reason, I get
> this error:
Can you send me the diff ?

> I also had to remove the comitting of the config.yml file since autoproj refused
> to merge the upstream master branch with that local commit. I just removed the
> git add/commit for config.yml.
This is weird. autoproj does not have to merge anything
* either you run it as "bootstrap" and everything is deleted, so no
merge
* or you run it as "incremental" and *you* have to run it manually the
first time to get the configuration and then autoproj should not ask
questions

Build server script for autoproj-based installs

On Thursday 16 December 2010 14:40:00 Sylvain Joyeux wrote:
> On 12/16/2010 01:54 PM, Peter Soetens wrote:
> > On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
> >> Here it is
> >>
> >> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-serv
> >> er
> >>
> >> I hope the usage message is self-explanatory. If in doubt, ask !
> >>
> >> Sylvain
> >
> > I had to modify this script for my hudson build. Now for some reason, I
> > get
>
> > this error:
> Can you send me the diff ?

I've included the full script, since it's a big hack. I just found out the
init.rb error is being reported by *hudson* because we get a prompt for 'git'.

We got the prompt because I removed the git add/commit of the config file (see
below). So I added the config.yml file to the git buildconf repository again.

>
> > I also had to remove the comitting of the config.yml file since autoproj
> > refused to merge the upstream master branch with that local commit. I
> > just removed the git add/commit for config.yml.
>
> This is weird. autoproj does not have to merge anything
> * either you run it as "bootstrap" and everything is deleted, so no
> merge
> * or you run it as "incremental" and *you* have to run it manually the
> first time to get the configuration and then autoproj should not ask
> questions

I don't understand yet how it could have happened then, but I probably forgot
to erase the 'dev' directory (because I renamed it to orocos-toolchain). An
example config.yml file that contains the minimum of what must be in there would
have helped though.

I'm still running it, but I think it's fixed now...

Peter

Build server script for autoproj-based installs

On 12/16/2010 03:07 PM, Peter Soetens wrote:
> I don't understand yet how it could have happened then, but I probably forgot
> to erase the 'dev' directory (because I renamed it to orocos-toolchain). An
> example config.yml file that contains the minimum of what must be in there would
> have helped though.
The process for me is:
* bootstrap and configure once manually
* copy the resulting config.yml and use it for following builds.

> I'm still running it, but I think it's fixed now...
OK

Build server script for autoproj-based installs

On Thursday 16 December 2010 15:10:01 Sylvain Joyeux wrote:
> On 12/16/2010 03:07 PM, Peter Soetens wrote:
> > I don't understand yet how it could have happened then, but I probably
> > forgot to erase the 'dev' directory (because I renamed it to
> > orocos-toolchain). An example config.yml file that contains the minimum
> > of what must be in there would have helped though.
>
> The process for me is:
> * bootstrap and configure once manually
> * copy the resulting config.yml and use it for following builds.
>
> > I'm still running it, but I think it's fixed now...
>
> OK

It isn't :-) master branch works fine. When you change on top
'branch=toolchain-2.2' in the script I've sent, you'll have this error:

...
autoproj bootstrap successfully finished

To further use autoproj and the installed software, you
must add the following line at the bottom of your .bashrc:
source /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
toolchain/env.sh

WARNING: autoproj will not work until your restart all
your consoles, or run the following in them:
$ source /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
toolchain/env.sh

To import and build the packages, you can now run
autoproj update
autoproj build

The resulting software is installed in
/home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
toolchain/install

+ . ./env.sh
+ export RUBYOPT=-rubygems
+ export GEM_HOME=/home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/orocos-toolchain/.gems
+ export PATH=/home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/orocos-toolchain/.gems/bin:/home/kaltan/src/git/orocos-
toolchain/orogen/bin:/opt/orocos/bin:/home/kaltan/src/git/orocos-
toolchain/.gems/bin:/opt/ros/cturtle/ros/bin:/usr/lib/ccache:/home/kaltan/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
+ autoproj full-build
Access method to gitorious (git, http or ssh): git
autodetecting the operating system
looking for RubyGems updates
updating autoproj main configuration
checking out branch master for autoproj_main_configuration
Build failed: autoproj_main_configuration: failed in import phase
'git checkout -b master FETCH_HEAD' returned status 1
see /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
toolchain/install/log/autoproj_main_configuration-import.log for details
last 10 lines are:

From /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/buildconf
* branch master -> FETCH_HEAD
Thu Dec 16 15:16:22 +0100 2010: running
git update-ref -m updated by autobuild refs/remotes/autobuild/master
cf10a8154670f0a2598201f24e587c9ad633de3c

Thu Dec 16 15:16:22 +0100 2010: running
git checkout -b master FETCH_HEAD

error: You have local changes to 'config.yml'; cannot switch branches.

It tries to check out the master branch, while we're working on toolchain-2.2.
Did you test your script using a branch other than 'master' ?

Peter

Build server script for autoproj-based installs

On 12/16/2010 03:19 PM, Peter Soetens wrote:
> On Thursday 16 December 2010 15:10:01 Sylvain Joyeux wrote:
>> On 12/16/2010 03:07 PM, Peter Soetens wrote:
>>> I don't understand yet how it could have happened then, but I probably
>>> forgot to erase the 'dev' directory (because I renamed it to
>>> orocos-toolchain). An example config.yml file that contains the minimum
>>> of what must be in there would have helped though.
>>
>> The process for me is:
>> * bootstrap and configure once manually
>> * copy the resulting config.yml and use it for following builds.
>>
>>> I'm still running it, but I think it's fixed now...
>>
>> OK
>
> It isn't :-) master branch works fine. When you change on top
> 'branch=toolchain-2.2' in the script I've sent, you'll have this error:
>
> ...
> autoproj bootstrap successfully finished
>
> To further use autoproj and the installed software, you
> must add the following line at the bottom of your .bashrc:
> source /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> toolchain/env.sh
>
> WARNING: autoproj will not work until your restart all
> your consoles, or run the following in them:
> $ source /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> toolchain/env.sh
>
> To import and build the packages, you can now run
> autoproj update
> autoproj build
>
> The resulting software is installed in
> /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> toolchain/install
>
> + . ./env.sh
> + export RUBYOPT=-rubygems
> + export GEM_HOME=/home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/orocos-toolchain/.gems
> + export PATH=/home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/orocos-toolchain/.gems/bin:/home/kaltan/src/git/orocos-
> toolchain/orogen/bin:/opt/orocos/bin:/home/kaltan/src/git/orocos-
> toolchain/.gems/bin:/opt/ros/cturtle/ros/bin:/usr/lib/ccache:/home/kaltan/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + autoproj full-build
> Access method to gitorious (git, http or ssh): git
> autodetecting the operating system
> looking for RubyGems updates
> updating autoproj main configuration
> checking out branch master for autoproj_main_configuration
> Build failed: autoproj_main_configuration: failed in import phase
> 'git checkout -b master FETCH_HEAD' returned status 1
> see /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> toolchain/install/log/autoproj_main_configuration-import.log for details
> last 10 lines are:
>
>
> From /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/buildconf
> * branch master -> FETCH_HEAD
> Thu Dec 16 15:16:22 +0100 2010: running
> git update-ref -m updated by autobuild refs/remotes/autobuild/master
> cf10a8154670f0a2598201f24e587c9ad633de3c
>
> Thu Dec 16 15:16:22 +0100 2010: running
> git checkout -b master FETCH_HEAD
>
> error: You have local changes to 'config.yml'; cannot switch branches.
>
> It tries to check out the master branch, while we're working on toolchain-2.2.
> Did you test your script using a branch other than 'master' ?
The script does not take a branch name, and my guess is that there is
therefore a mixup between the "git clone"/ add config.yml and the
bootstrap line.

You must:

* in the "adding config.yml part", make sure you add it to the right
branch
* when bootstrapping, make sure you give the right branch to bootstrap

Sylvain

Build server script for autoproj-based installs

On Thursday 16 December 2010 15:30:15 Sylvain Joyeux wrote:
> On 12/16/2010 03:19 PM, Peter Soetens wrote:
> > On Thursday 16 December 2010 15:10:01 Sylvain Joyeux wrote:
> >> On 12/16/2010 03:07 PM, Peter Soetens wrote:
> >>> I don't understand yet how it could have happened then, but I probably
> >>> forgot to erase the 'dev' directory (because I renamed it to
> >>> orocos-toolchain). An example config.yml file that contains the minimum
> >>> of what must be in there would have helped though.
> >>
> >> The process for me is:
> >> * bootstrap and configure once manually
> >> * copy the resulting config.yml and use it for following builds.
> >>>
> >>> I'm still running it, but I think it's fixed now...
> >>
> >> OK
> >
> > It isn't :-) master branch works fine. When you change on top
> > 'branch=toolchain-2.2' in the script I've sent, you'll have this error:
> >
> > ...
> > autoproj bootstrap successfully finished
> >
> > To further use autoproj and the installed software, you
> >
> > must add the following line at the bottom of your .bashrc:
> > source
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> >
> > toolchain/env.sh
> >
> > WARNING: autoproj will not work until your restart all
> >
> > your consoles, or run the following in them:
> > $ source
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> >
> > toolchain/env.sh
> >
> > To import and build the packages, you can now run
> >
> > autoproj update
> > autoproj build
> >
> > The resulting software is installed in
> >
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> >
> > toolchain/install
> >
> > + . ./env.sh
> > + export RUBYOPT=-rubygems
> > + export GEM_HOME=/home/kaltan/vbox/hudson/jobs/bootstrap-
> > toolchain/workspace/orocos-toolchain/.gems
> > + export PATH=/home/kaltan/vbox/hudson/jobs/bootstrap-
> > toolchain/workspace/orocos-toolchain/.gems/bin:/home/kaltan/src/git/oroco
> > s- toolchain/orogen/bin:/opt/orocos/bin:/home/kaltan/src/git/orocos-
> > toolchain/.gems/bin:/opt/ros/cturtle/ros/bin:/usr/lib/ccache:/home/kalta
> > n/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
> > sbin:/bin:/usr/games + autoproj full-build
> >
> > Access method to gitorious (git, http or ssh): git
> > autodetecting the operating system
> > looking for RubyGems updates
> > updating autoproj main configuration
> > checking out branch master for autoproj_main_configuration
> >
> > Build failed: autoproj_main_configuration: failed in import phase
> >
> > 'git checkout -b master FETCH_HEAD' returned status 1
> > see
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/orocos-
> >
> > toolchain/install/log/autoproj_main_configuration-import.log for details
> >
> > last 10 lines are:
> >
> >
> > From
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/buildco
> > nf
> >
> > * branch master -> FETCH_HEAD
> >
> > Thu Dec 16 15:16:22 +0100 2010: running
> >
> > git update-ref -m updated by autobuild
> > refs/remotes/autobuild/master
> >
> > cf10a8154670f0a2598201f24e587c9ad633de3c
> >
> > Thu Dec 16 15:16:22 +0100 2010: running
> >
> > git checkout -b master FETCH_HEAD
> >
> > error: You have local changes to 'config.yml'; cannot switch
> > branches.
> >
> > It tries to check out the master branch, while we're working on
> > toolchain-2.2. Did you test your script using a branch other than
> > 'master' ?
>
> The script does not take a branch name, and my guess is that there is
> therefore a mixup between the "git clone"/ add config.yml and the
> bootstrap line.
>
> You must:
>
> * in the "adding config.yml part", make sure you add it to the right
> branch

I did:

+ git checkout -b toolchain-2.2 origin/toolchain-2.2
Branch toolchain-2.2 set up to track remote branch toolchain-2.2 from origin.
Switched to a new branch 'toolchain-2.2'
+ cp -f /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/config.yml
config.yml
+ git add -f config.yml
+ git commit -a -m build server configuration
[toolchain-2.2 13da46d] build server configuration
1 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 config.yml

> * when bootstrapping, make sure you give the right branch to bootstrap

I did:

+ ruby autoproj_bootstrap git /home/kaltan/vbox/hudson/jobs/bootstrap-
toolchain/workspace/buildconf branch=toolchain-2.2

Peter

Build server script for autoproj-based installs

On 12/16/2010 03:42 PM, Peter Soetens wrote:
>> * in the "adding config.yml part", make sure you add it to the right
>> branch
>
> I did:
>
> + git checkout -b toolchain-2.2 origin/toolchain-2.2
> Branch toolchain-2.2 set up to track remote branch toolchain-2.2 from origin.
> Switched to a new branch 'toolchain-2.2'
> + cp -f /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/config.yml
> config.yml
> + git add -f config.yml
> + git commit -a -m build server configuration
> [toolchain-2.2 13da46d] build server configuration
> 1 files changed, 11 insertions(+), 0 deletions(-)
> create mode 100644 config.yml
>
>
>> * when bootstrapping, make sure you give the right branch to bootstrap
>
> I did:
>
> + ruby autoproj_bootstrap git /home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/buildconf branch=toolchain-2.2

Then it seems that there is a bug in autoproj bootstrap

Can you send your config.yml as well ?

Build server script for autoproj-based installs

On Thursday 16 December 2010 15:52:19 Sylvain Joyeux wrote:
> On 12/16/2010 03:42 PM, Peter Soetens wrote:
> >> * in the "adding config.yml part", make sure you add it to the right
> >>
> >> branch
> >
> > I did:
> >
> > + git checkout -b toolchain-2.2 origin/toolchain-2.2
> > Branch toolchain-2.2 set up to track remote branch toolchain-2.2 from
> > origin. Switched to a new branch 'toolchain-2.2'
> > + cp -f
> > /home/kaltan/vbox/hudson/jobs/bootstrap-toolchain/workspace/config.yml
> > config.yml
> > + git add -f config.yml
> > + git commit -a -m build server configuration
> > [toolchain-2.2 13da46d] build server configuration
> >
> > 1 files changed, 11 insertions(+), 0 deletions(-)
> > create mode 100644 config.yml
> >
> >> * when bootstrapping, make sure you give the right branch to
> >> bootstrap
> >
> > I did:
> >
> > + ruby autoproj_bootstrap git /home/kaltan/vbox/hudson/jobs/bootstrap-
> > toolchain/workspace/buildconf branch=toolchain-2.2
>
> Then it seems that there is a bug in autoproj bootstrap
>
> Can you send your config.yml as well ?

It is generated by the hudson script I've sent you. It should be self-
containing (ie doesn't depend on hudson or my environment).

Peter

[Rock-dev] Build server script for autoproj-based installs

On Thursday 16 December 2010 13:54:19 Peter Soetens wrote:
> On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
> > Here it is
> >
> > http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-serve
> > r
> >
> > I hope the usage message is self-explanatory. If in doubt, ask !
> >
> > Sylvain
>
> I had to modify this script for my hudson build. Now for some reason, I get
> this error:
>
> + ruby autoproj_bootstrap git /home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master
> /buildconf branch=master
> autodetecting the operating system
> autoproj: installing a proper Ruby environment (this can take a long time)
> autoproj: installing autoproj and its dependencies (this can take a long
> time) installing/updating RubyGems dependencies: autobuild, rdoc
> Enclosing class/module 'mUtilrb' for class WeakRef not known
> Enclosing class/module 'cWeakRef' for class RefError not known
> Enclosing class/module 'mUtilrb' for class WeakRef not known
> Enclosing class/module 'cWeakRef' for class RefError not known
> installing/updating RubyGems dependencies: autoproj
> autodetecting the operating system
> checking out autoproj main configuration
> Access method to gitorious (git, http or ssh)
> Use 'ssh' only if you have a gitorious account and have commit rights
> on the Orocos projects. Otherwise, we advise you to use 'git' [git]
> /home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master
> /orocos- toolchain/autoproj/init.rb:66: end of file reached
>  in /home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master
> /orocos- toolchain/autoproj/init.rb:66
> ERROR: failed to run autoproj bootstrap git,
> /home/kaltan/vbox/hudson/jobs/bootstrap-
> toolchain/workspace/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/master
> /buildconf, branch=master
>
> I have no idea where this comes from, the init.rb file looks fine to me...
> ideas?
>
> I also had to remove the comitting of the config.yml file since autoproj
> refused to merge the upstream master branch with that local commit. I just
> removed the git add/commit for config.yml.
>

Something else strange. This is my own written config.yml file which I pass to
the script:

Build server script for autoproj-based installs

On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
> Here it is
>
> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-server
>
> I hope the usage message is self-explanatory. If in doubt, ask !

Hmm, I've run it like this:

sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git

And I still get questions asked:

...

2010-12-15 21:40:39 (39.8 KB/s) - `autoproj_bootstrap' saved [50426/50426]

autodetecting the operating system
autoproj: installing a proper Ruby environment (this can take a long time)
autoproj: installing autoproj and its dependencies (this can take a long time)
installing/updating RubyGems dependencies: autobuild, rdoc
Enclosing class/module 'mUtilrb' for class WeakRef not known
Enclosing class/module 'cWeakRef' for class RefError not known
Enclosing class/module 'mUtilrb' for class WeakRef not known
Enclosing class/module 'cWeakRef' for class RefError not known
installing/updating RubyGems dependencies: autoproj
autodetecting the operating system
checking out autoproj main configuration
Access method to gitorious (git, http or ssh)
Use 'ssh' only if you have a gitorious account and have commit rights
on the Orocos projects. Otherwise, we advise you to use 'git' [git]

Peter

Build server script for autoproj-based installs

On 12/15/2010 09:43 PM, Peter Soetens wrote:
> On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
>> Here it is
>>
>> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-server
>>
>> I hope the usage message is self-explanatory. If in doubt, ask !
>
> Hmm, I've run it like this:
>
> sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
>
> And I still get questions asked:
For bootstraps, you need to provide a config.yml file to the script (the
script can't guess them !)

sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
automated_build_config.yml

Build server script for autoproj-based installs

On Thursday 16 December 2010 09:59:16 Sylvain Joyeux wrote:
> On 12/15/2010 09:43 PM, Peter Soetens wrote:
> > On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
> >> Here it is
> >>
> >> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-serv
> >> er
> >>
> >> I hope the usage message is self-explanatory. If in doubt, ask !
> >
> > Hmm, I've run it like this:
> >
> > sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
>
> > And I still get questions asked:
> For bootstraps, you need to provide a config.yml file to the script (the
> script can't guess them !)
>
> sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
> automated_build_config.yml

Ooh... now I understand !

Peter

Build server script for autoproj-based installs

On 12/16/2010 10:40 AM, Peter Soetens wrote:
> On Thursday 16 December 2010 09:59:16 Sylvain Joyeux wrote:
>> On 12/15/2010 09:43 PM, Peter Soetens wrote:
>>> On Tuesday 14 December 2010 17:13:50 Sylvain Joyeux wrote:
>>>> Here it is
>>>>
>>>> http://gitorious.com/rock/admin_scripts/blobs/master/bin/rock-build-serv
>>>> er
>>>>
>>>> I hope the usage message is self-explanatory. If in doubt, ask !
>>>
>>> Hmm, I've run it like this:
>>>
>>> sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
>>
>>> And I still get questions asked:
>> For bootstraps, you need to provide a config.yml file to the script (the
>> script can't guess them !)
>>
>> sh rock-build-server.txt git://gitorious.org/orocos-toolchain/build.git
>> automated_build_config.yml
>
> Ooh... now I understand !
Yeah ... Let's say that the usage message is a bit sparse on the
explanations :P

Sylvain