Heroku recently released a new ".deb packages" buildpack that looks similar to the custom apt buildpack we are now using in Toolforge.
We should look into migrating to using the Heroku buildpack, and delete our fork of the custom apt buildpack that we maintain at https://gitlab.wikimedia.org/repos/cloud/toolforge/buildpacks/apt-buildpack.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dcaro | T381923 Toolforge Build Service does not support .python-version | |||
| Resolved | BUG REPORT | dcaro | T390845 [builds-builder] Golang buildpack does not allow using Procfiles so can't use custom scripts/entrypoints | ||
| Resolved | BUG REPORT | dcaro | T363417 [builds-builder] golang based images get infinite nested loops for procfile entries | ||
| In Progress | Feature | None | T380127 [builds-builder] Add support for Heroku's "24" builder stack based on Ubuntu 2024.04 noble | ||
| Open | None | T403509 Migrate Wikidata Shape Expressions Inference from Aptfile to project.toml | |||
| Open | None | T387141 [builds-builder,apt] migrate from apt buildpack to Heroku's .deb packages buildpack |
Related tickets:
Note that a newer version of the upstream deb packages buildpack allows specifying external repos, that feature should be gated as it is currently: https://github.com/heroku/buildpacks-deb-packages/pull/116
T422384: [builds-builder] incompatibility of fagiani/apt and builder stack "24" is reporting the bug I filed as T394466: [build-service] remove legacy fagiani/apt 0.2.5 builder from `--use-latest-versions` stack which was merged into this task but not actually fixed before the Buildpack environment version upgrade happened.
Yep, sorry for the confusion, this should get people unblocked https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-builder/-/merge_requests/86 until we do a migration before not supporting the old apt anymore.