search

NYPL / engineering-general

Standards, values, and other information relevant to the NYPL Engineering Team.
48 stars 3 forks source link

Should talk about limiting Travis builds in travis-ci documentation #89

Closed nonword closed 3 years ago

nonword commented 5 years ago

In our travis coverage, we should note ways to better leverage our common travis acct. Suggestion from @nodanaonlyzuul and @gkallenberg :

I think we can get more mileage out of the limited number of concurrent builds our Travis plan gives us by:

  1. Doing fewer builds.
  2. Making builds faster. Doing fewer builds is easy - by doing: 
    only:
- master
- deployable-branch1
- deployable-branch2

If you do this - TravisCI will not do builds for feature branches but WILL do builds for PRs. We can make builds faster by asking travis to cache gems, node modules, (maybe even apt packages) https://docs.travis-ci.com/user/caching/.

mattkoch614 commented 3 years ago

This issue is quite old, over a year. Closing, with a tag of archived. @nonword FYI!