Upgrading Go or Node.js requires making changes in many different files. See below for a list and explanation for each.
- CircleCi
grafana/build-container
- Appveyor
- Dockerfile
- CircleCI
grafana/build-container
- Appveyor
- Dockerfile
The Grafana project uses Go modules to manage dependencies on external packages. This requires a working Go environment with version 1.11 or greater installed.
All dependencies are vendored in the vendor/
directory.
To add or update a new dependency, use the go get
command:
# Pick the latest tagged release.
go get example.com/some/module/pkg
# Pick a specific version.
go get example.com/some/module/[email protected]
Tidy up the go.mod
and go.sum
files and copy the new/updated dependency to the vendor/
directory:
Updated using yarn
.
package.json
Our builds run on CircleCI through our build script.
.circleci/config.yml
.
- nodejs
- golang
- grafana/build-container (our custom docker build container)
The main build step (in CircleCI) is built using a custom build container that comes pre-baked with some of the necessary dependencies.
Link: grafana-build-container
- fpm
- nodejs
- golang
- crosscompiling (several compilers)
Master and release builds trigger test runs on Appveyors build environment so that tests will run on Windows.
appveyor.yml
- nodejs
- golang
There is a Docker build for Grafana in the root of the project that allows anyone to build Grafana just using Docker.
Dockerfile
- nodejs
- golang
Please send out a notice in the grafana-dev slack channel when updating Go or Node.js to make it easier for everyone to update their local developer environments.