mirror of
https://github.com/weaveworks/scope.git
synced 2026-03-03 18:20:27 +00:00
3881934fdc
e9e7e6bMerge pull request #26 from weaveworks/this-time-for-suredf494d6Remove dependenciesc045d16Properly exclude vendor from lint2cfcf08Add blacklist to wcloud clientca6ebfbMerge pull request #25 from weaveworks/fix-brokennessbfb1747Test directories need ./ prefixes, obviously.5b9b314Merge pull request #24 from weaveworks/find-files8786427Remove spurious debugging code from test8b7ec6eSpeed up test by using git ls-filescf53dc1Exclude vendor from shell lintingb2ab380Fix field namec86fd3dAdd notification config for wcloudf643920Merge pull request #23 from weaveworks/only-lint-git-files47a0152Only lint git files50d47f9Merge pull request #22 from weaveworks/shell-lint git-subtree-dir: tools git-subtree-split:e9e7e6b0f0
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.