Oh hey, Heroku and friends are actually making this easier https://buildpacks.io/

As an update, I'm now working on this for the Cloud Services team. We're starting with a PoC of having a tool running using a buildpack-based image rather than one of the fixed ones: T265681: [tbs.tools] Deploy a tool using a buildpack-based image on Toolforge. Then will come setting up a CD pipeline (T265684: Figure out CI solution for building buildpack-based images for Toolforge) and then hooking it up to a webhook endpoint of some kind.

Started working on design documentation to organize the project and get things moving.

Change 683415 had a related patch set uploaded (by Bstorm; author: Bstorm):

[labs/tools/registry-admission-webhook@master] toolsbeta: For testing, I'd rather not upload tekton to the internal reg

https://gerrit.wikimedia.org/r/683415

Change 683415 merged by jenkins-bot:

[labs/tools/registry-admission-webhook@master] toolsbeta: For testing, I'd rather not upload tekton to the internal reg

https://gerrit.wikimedia.org/r/683415

Does the push-to-deploy pipeline accept early adopters? I’d gladly volunteer as a guinea pig.

@Sascha That would be wonderful to get feedback! What tool / language are you hoping to try out?

@nskaggs, it’s in Go, although I’m working on a web frontend that’ll eventually have a part written in JavaScript/React. Here’s my current “release process” that I’m hoping to make less manual. The environment variable GOOS=linux can be omitted when the compiler runs on a Linux machine.

git clone https://github.com/brawer/wikidata-qrank && cd wikidata-qrank
go test ./cmd/...
for tool in `ls cmd` ; do GOOS=linux go build -ldflags="-s -w" ./cmd/$tool && scp ./$tool sascha@bastion.toolforge.org:/data/project/qrank/bin/$tool ; done

Hi @Sascha, there's no timeline yet, but I'll ping you whenever the pipeline is ready to try, I'll really appreciate your input :)

We will support three main builders, paketo that supports building golang apps (you code might need some tweaking for this one), google cloud, that also supports golang, and our own toolforge one that does not support golang yet, though might in the future.

If you have any other needs please share and we'll try to accommodate for them too.