Skip to content

2.2.0
Compare
Choose a tag to compare
@doudou doudou released this 05 Oct 16:54
· 621 commits to master since this release
v2.2.0
457388d

New features:

  • Added --auto-exclude to build and update

Auto-exclusion deals with builds where a package can either not be checked out, or when its manifest.xml contains errors. The current behavior would be to fail, regardless of whether -k (--keep-going) is provided or not, as a valid version of the package is not available.

The old behavior is still the default, as it would be the expected behavior on a developer's workflow. However, in CI environments, it makes "meta-builds" (as e.g. rock.all) fail. Given that we can't control what people do with their packages, freezing the CI environment because of one misbehaving package is definitely not a good idea.

--auto-exclude will exclude packages like this. The failure or not of the whole build is still governed by exclusion rules: a package explicitly selected in the manifest, or a package that is part of a metapackage not marked as 'weak' will still fail.

Assets 2
Loading