mirror of
https://github.com/weaveworks/scope.git
synced 2026-03-03 18:20:27 +00:00
b92447c6ab
9e32194 Secure GCP servers for Scope: open port 80. a22536a Secure GCP servers for Scope. 89c3a29 Merge pull request #78 from weaveworks/lint-merge-rebase-issue-in-docs 73ad56d Add linter function to avoid bad merge/rebase artefact git-subtree-dir: tools git-subtree-split: 9e32194cf16f8f6eee7acb5dbf311c9003f0fedb
Weaveworks Build Tools
Included in this repo are tools shared by weave.git and scope.git. They include
provisioning: a set of Terraform scripts to provision virtual machines in GCP, AWS or Digital Ocean.config_management: a set of Ansible playbooks to configure virtual machines for development, testing, etc.cover: a tool which merges overlapping coverage reports generated by go testfiles-with-type: a tool to search directories for files of a given MIME typelint: a script to lint go, sh and hcl files; runs various tools like golint, go vet, errcheck, shellcheck etcrebuild-image: a script to rebuild docker images when their input files change; useful when you using docker images to build your software, but you don't want to build the image every time.shell-lint: a script to lint multiple shell files with shellchecksocks: a simple, dockerised SOCKS proxy for getting your laptop onto the Weave networktest: a script to run all go unit tests in subdirectories, gather the coverage results, and merge them into a single report.runner: a tool for running tests in parallel; given each test is suffixed with the number of hosts it requires, and the hosts available are contained in the environment variable HOSTS, the tool will run tests in parallel, on different hosts.scheduler: an appengine application that can be used to distribute tests across different shards in CircleCI.
Requirements
lintrequires shfmt to lint sh files; get shfmt withgo get -u gopkg.in/mvdan/sh.v1/cmd/shfmt
Using build-tools.git
To allow you to tie your code to a specific version of build-tools.git, such
that future changes don't break you, we recommendation that you git subtree
this repository into your own repository:
git subtree add --prefix tools https://github.com/weaveworks/build-tools.git master --squash
To update the code in build-tools.git, the process is therefore:
- PR into build-tools.git, go through normal review process etc.
- Do
git subtree pull --prefix tools https://github.com/weaveworks/build-tools.git master --squashin your repo, and PR that.