1343960 - Update to newer versions of the Heroku python/nodejs buildpacks

Status: RESOLVED FIXED

(Tree Management :: Treeherder: Infrastructure, enhancement, P2)

Description

[Ed Morley [:emorley]]

Currently:

=== treeherder-prod Buildpack URLs
1. https://github.com/memcachier/memcachier-tls-buildpack.git#6ca0ea51b98ab0ee76f24c1f25fe8c5a66e75db9
2. https://github.com/heroku/heroku-buildpack-nodejs.git#v91
3. https://github.com/heroku/heroku-buildpack-python.git#v82

We're already using the latest memcachier-tls-buildpack version.

Changes for the others:
https://github.com/heroku/heroku-buildpack-nodejs/compare/v91...v98
https://github.com/heroku/heroku-buildpack-python/compare/v82...v99

Notably:
* nodejs: Adds supports for yarn (needed for bug 1343928)
* nodejs: Improved node_modules caching
* python: Updated pip/setuptools
* python: Improved build caching + less time spent copying

Instead of just straight updating to the newer git version tags, I think we should switch to using the official aliases (map to the curated stable release), since that way we don't have to constantly update.

For things like Python packages pinning versions is essential, however for build toolchain it doesn't directly affect production (any errors mean the deploy just stops) and is easy enough to roll back if we have to.

Comment 1

[Ed Morley [:emorley]]

$ ths buildpacks:set -i 2 heroku/nodejs
Buildpack set. Next release on treeherder-stage will use:
  1. https://github.com/memcachier/memcachier-tls-buildpack.git#6ca0ea51b98ab0ee76f24c1f25fe8c5a66e75db9
  2. heroku/nodejs
  3. https://github.com/heroku/heroku-buildpack-python.git#v82
Run git push heroku master to create a new release using these buildpacks.

$ ths buildpacks:set -i 3 heroku/python
Buildpack set. Next release on treeherder-stage will use:
  1. https://github.com/memcachier/memcachier-tls-buildpack.git#6ca0ea51b98ab0ee76f24c1f25fe8c5a66e75db9
  2. heroku/nodejs
  3. heroku/python
Run git push heroku master to create a new release using these buildpacks.

A test build on stage worked fine, so I ran the same against prototype and prod.

I also used the heroku-repo plugin to run clear the cache (using `heroku repo:purge_cache`).