Open mbruzek opened 7 years ago
Indeed, the ci-info.yaml is required. bundlebuilder.py check
will have exit code 0
in case the there is a potential update on the bundle. Potential update is essentially a new revision of a charm appearing on the store. The ci-info.yaml is needed to specify what charms should we keep an eye, on which channel, and what should we do with in case of a passing bundle test (should we push the bundle to the store, should we also pull the charms, if so in which channel).
The script should handle the missing file and report an error rather than a difficult to read stack trace when the ci-info.yaml is missing.
To integrate with this system I had to create 3 different yaml files that were not previously in my bundle
ci-info.yaml
tests/tests.yaml
matrix.yaml
Can we not fold this functionality into one yaml file to reduce the burden on the developers/users of this system?
This might be fixed since the refactor.
I am using cwr-ci and build-bundle command that creates a jenkins job with the
bundlebuilder.py check
command. The check never completes successfully.I don't have a ci-info.yaml (because Cory said I didn't need it) but apparently that is mandatory.
Here is the output of the check command when I tried running this on the jenkins server manually.