The pipeline is defined in Starlark and transformed to YAML upon pipeline run. This enables us to do a highly dynamic and non repeating pipeline configuration. We enforce Starlark format guidelines with Bazel Buildifier. You can format the .drone.star file by running
Upon running the pipeline, your branch gets merged to the master branch. This ensures that we always test your changeset if as it was applied to the master of oCIS. Please note that this does not apply to the pipeline definition (
- static code analysis
- running UI tests
- running ownCloud 10 test suite against oCIS
- build and release docker images
- build and release binaries
- build and release documentation
You may add flags to your commit message or PR title in order to speed up pipeline runs and take load from the CI runners.
[CI SKIP]: no CI is run on the commit or PR
[full-ci]: deactivates the fail early mechanism and runs all available test (as default only smoke tests are run)
[docs-only]: please add this flag, if you only changed documentation. This will only trigger documentation related CI steps.
[tests-only]: please add this flag, if you only changed tests or test-related tooling. You do not need to add a changelog for tests-only changes.
My pipeline fails because some CI related files or commands are missing.
Please make sure to rebase your branch onto the latest master of oCIS. It could be that the pipeline definition (
.drone.star) was changed on the master branch. This is the only file, that will not be auto merged to master upon pipeline run. So things could be out of sync.
How can I see the YAML drone pipeline definition?
In order to see the Yaml pipeline definition you can use the drone-cli to convert the Starlark file.
If you experience a
"build" struct has no .title attributeyou need a newer version of drone-cli.