mirror of
https://github.com/weaveworks/scope.git
synced 2026-05-06 01:08:03 +00:00
37ea4937a4
604e133c2 Merge pull request #167 from weaveworks/update-scheduler-instructions bdd647e92 Merge pull request #169 from weaveworks/go-1.14.4 2c2792e7d Upgrade to Go 1.14.4 e6dd5e8f0 Merge pull request #168 from weaveworks/downgrade-werkzeug 144aa64c0 Restruct scheduler to use compatible version of werkzeug library cc807901d Update instructions on how to deploy gc/scheduler 51a217660 Merge pull request #166 from weaveworks/165-rename-circleci-to-wksctl bfd7a2bbe Renames circleci project wks -> wksctl afte code move a5f7be3cc Note that the API token was revoked 15e4cfb94 Merge pull request #164 from weaveworks/improve-lint dc8722589 Fix lint errors in Python code 8cb6a62a2 Set failure state if lint_files fails c635ce412 Simplify the no-arguments case 167b7ed57 Skip entire directories that match filter patterns 1caa455a6 Refactor: read filter patterns once at start 4cc7911e5 Merge pull request #163 from weaveworks/fix-lint 393808dab Merge pull request #162 from weaveworks/golang-python3 3c5fcd16e Make lint run on CircleCI f0936a1e9 lint all directories if not given a list 68f62a393 Fix typo in lint script 9ef44b057 Stop installing promtool 882df5ec5 Install python 3 instead of obsolete v2.7 988002377 Update Go to latest 1.13.3 2a2df5278 Merge pull request #161 from murali-reddy/terraform-update bf8ed23b9 update google_compute_instance arguments as per the latest documentation git-subtree-dir: tools git-subtree-split: 604e133c2b7eb805766eab7be28723ef1ccd32aa
Weaveworks Build Tools
Included in this repo are tools shared by weave.git and scope.git. They include
bazel-rules: Bazel build rules used in our projectsbuild: a set of docker base-images for building weave projects. These should be used instead of giving each project its own build image.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 with
curl -fsSLo shfmt https://github.com/mvdan/sh/releases/download/v1.3.0/shfmt_v1.3.0_linux_amd64
chmod +x shfmt
(we pin that version, and it doesn't build from the source repo any more)
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.
Getting Help
If you have any questions about, feedback for or problems with build-tools:
- Invite yourself to the Weave Users Slack.
- Ask a question on the #general slack channel.
- File an issue.
Your feedback is always welcome!