<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fscrypt.git/bin/files-changed, branch v0.2.5</title>
<subtitle>Go tool for managing Linux filesystem encryption
</subtitle>
<id>https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.5</id>
<link rel='self' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.5'/>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/'/>
<updated>2018-02-12T05:38:13Z</updated>
<entry>
<title>travis: use multiple build stages</title>
<updated>2018-02-12T05:38:13Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2018-02-12T05:22:53Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=b330463662825a7d7b22efabb2b7a40640d2b18e'/>
<id>urn:sha1:b330463662825a7d7b22efabb2b7a40640d2b18e</id>
<content type='text'>
This change rewrites .travis.yml to use many build stages/jobs. This
allows our build to run faster, as almost all jobs run in containers.

Stage 1: Run on all pushes to all branches
  - Job Build: just runs "make" to make sure everything is OK

Stage 2: Run on all PRs and pushes to master
  - Job Lint: Makes sure dep, "make gen", "make format", and "make lint"
              are all happy.
  - Job Build 1: Make sure "go get" and "make" will work. This job will
                 later run unit tests.
  - Job Build 2: Same as Job Build 1, except with another go version.
  - Job Integeration: Run integration tests (needs sudo, so needs VM)

Stage 3: Run on releases (if other stages pass)
  - Job Deploy: Publishes amd64 binaries to GitHub.
</content>
</entry>
</feed>
