grafana/contribute/drone-pipeline.md
Joseph Perez 4e99cd2860
Docs: Edit of "Developer Guide" and other topics (part 2 of doc quality project) (#86072)
* 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>
2024-05-29 11:08:41 -07:00

1.2 KiB

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, a similar language to Python. The Starlark files are located in scripts/drone.

Drone setup

  1. Set environment variables DRONE_SERVER and DRONE_TOKEN found in your Drone account. These environment variables are used to verify that only Grafana employees can make changes to the pipelines.
  2. Install buildifier, 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 before opening a pull request in the main repo.
  2. 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.