mirror of
https://github.com/weaveworks/scope.git
synced 2026-03-03 18:20:27 +00:00
21cfc83a56
* Squashed 'tools/' changes from e9e7e6b..db5efc0db5efc0Merge pull request #28 from weaveworks/mike/add-image-tag5312c40Import image-tag script into build tools so it can be shared7e850f8Fix logs pathdda9785Update deploy apif2f4e5bFix the wcloud client3925eb6Merge pull request #27 from weaveworks/wcloud-events77355b9Lintd9a1c6cAdd wcloud events, update flags and error nicely when there is no config git-subtree-dir: tools git-subtree-split:db5efc0537* Remove ./image-tag and use ./tools/image-tag instead image-tag is now shared code from the build-tools repo
Weaveworks Build Tools
Included in this repo are tools shared by weave.git and scope.git. They include
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 project; runs various tools like golint, go vet, errcheck 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.
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.