mirror of
https://github.com/grafana/grafana.git
synced 2024-12-28 01:41:24 -06:00
4e99cd2860
* Edit deprecation-policy * Edit drone-pipeline * Docs: Edit of 4 files, part 2 of quality improvement * Update contribute/developer-guide.md * Update contribute/developer-guide.md Co-authored-by: J Stickler <julie.stickler@grafana.com> * Changes from feedback * Properly style UNIX * Update contribute/drone-pipeline.md * Update contribute/feature-toggles.md Co-authored-by: J Stickler <julie.stickler@grafana.com> * Format with prettier --------- Co-authored-by: J Stickler <julie.stickler@grafana.com>
18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
# Making changes to the Drone pipeline
|
|
|
|
> Only members of the Grafana organization can make changes to the Drone pipeline.
|
|
|
|
The Drone pipelines are built with [Starlark](https://github.com/bazelbuild/starlark), a similar language to Python. The Starlark files are located in [`scripts/drone`](https://github.com/grafana/grafana/tree/main/scripts/drone).
|
|
|
|
## Drone setup
|
|
|
|
1. Set environment variables `DRONE_SERVER` and `DRONE_TOKEN` found in your [Drone account](https://drone.grafana.net/account). These environment variables are used to verify that only Grafana employees can make changes to the pipelines.
|
|
1. Install [buildifier](https://github.com/bazelbuild/buildtools/blob/master/buildifier/README.md), and use it to format the Starlark files you want to edit.
|
|
|
|
## Drone development
|
|
|
|
1. Open a pull request where you can do test runs for your changes. If you need to experiment with secrets, create a pull request in the [`grafana-ci-sandbox repo`](https://github.com/grafana/grafana-ci-sandbox) before opening a pull request in the main repo.
|
|
1. Run `make drone` after making changes to the Starlark files. This builds the `.drone.yml` file.
|
|
|
|
For further questions, reach out to the `grafana-release-guild` squad.
|