Autoproj 1.13.0 has been released !

Apart from the usual bunch of bugfixes, some important changes are
getting into this release. They are described in more detail below:
- retry behaviour
- versioning support
- autoproj log
- testing support
- forcing the build of excluded packages

Autoproj will update itself the next time you either run "autoproj
update" without arguments, or aup --all

Retry behaviour
=============
autoproj will retry a lot less than before, especially when running
git commands. The only commands that should retry are the ones
accessing the network.

Versioning Support
===============
An overrides.d/ directory can be created in the main autoproj
configuration. This directory can hold override files, whose format is
the same than the overrides: section of overrides.yml. e.g.:
- tools/autobuild:
branch: master

These files are loaded in alphabetical order. One would usually want
to prefix them with two numbers to make the ordering clearer
(00-initial.yml or 99-last.yml)

The use of overrides.yml for this purpose is still supported, but deprecated

[Rock-dev] Autoproj 1.13.0 has been released !

Hello,

The rock buildserver produces following error using Autoproj 1.13.0:

/data/jenkins/workspace/workspace/rock-basic/FLAVOR/master/node/Ubuntu_current/dev/.gems/gems/autoproj-1.13.0/lib/autoproj/vcs_definition.rb:179:in
`create_autobuild_importer': undefined method `local' for
Autobuild:Module (NoMethodError)

See the full log here:

http://rock-robotics.org/status/job/rock-basic/lastBuild/FLAVOR=master,n...

I don't really know what to do to fix it.

Kind regads,

Steffen

Am 26.03.2015 um 18:07 schrieb Sylvain Joyeux:
> Apart from the usual bunch of bugfixes, some important changes are
> getting into this release. They are described in more detail below:
> - retry behaviour
> - versioning support
> - autoproj log
> - testing support
> - forcing the build of excluded packages
>
> Autoproj will update itself the next time you either run "autoproj
> update" without arguments, or aup --all
>
> Retry behaviour
> =============
> autoproj will retry a lot less than before, especially when running
> git commands. The only commands that should retry are the ones
> accessing the network.
>
> Versioning Support
> ===============
> An overrides.d/ directory can be created in the main autoproj
> configuration. This directory can hold override files, whose format is
> the same than the overrides: section of overrides.yml. e.g.:
> - tools/autobuild:
> branch: master
>
> These files are loaded in alphabetical order. One would usually want
> to prefix them with two numbers to make the ordering clearer
> (00-initial.yml or 99-last.yml)
>
> The use of overrides.yml for this purpose is still supported, but deprecated
>

[Rock-dev] Autoproj 1.13.0 has been released !

Hello,

The rock buildserver produces following error using Autoproj 1.13.0:

/data/jenkins/workspace/workspace/rock-basic/FLAVOR/master/node/Ubuntu_current/dev/.gems/gems/autoproj-1.13.0/lib/autoproj/vcs_definition.rb:179:in
`create_autobuild_importer': undefined method `local' for
Autobuild:Module (NoMethodError)

See the full log here:

http://rock-robotics.org/status/job/rock-basic/lastBuild/FLAVOR=master,n...

I don't really know what to do to fix it.

Kind regads,

Steffen

Am 26.03.2015 um 18:07 schrieb Sylvain Joyeux:
> Apart from the usual bunch of bugfixes, some important changes are
> getting into this release. They are described in more detail below:
> - retry behaviour
> - versioning support
> - autoproj log
> - testing support
> - forcing the build of excluded packages
>
> Autoproj will update itself the next time you either run "autoproj
> update" without arguments, or aup --all
>
> Retry behaviour
> =============
> autoproj will retry a lot less than before, especially when running
> git commands. The only commands that should retry are the ones
> accessing the network.
>
> Versioning Support
> ===============
> An overrides.d/ directory can be created in the main autoproj
> configuration. This directory can hold override files, whose format is
> the same than the overrides: section of overrides.yml. e.g.:
> - tools/autobuild:
> branch: master
>
> These files are loaded in alphabetical order. One would usually want
> to prefix them with two numbers to make the ordering clearer
> (00-initial.yml or 99-last.yml)
>
> The use of overrides.yml for this purpose is still supported, but deprecated
>