quay automated builds for container images via latest commit.

[zak-hassan]

quay automated builds for container images via latest commit.

[zak-hassan]

Hi @4n4nd I was wondering if you did something like this before?

[durandom]

I actually love building the image on openshift. Why dont we stick with that?

[zak-hassan]

We could do that too. Just was looking for a more automated build process.

[vpavlin]

What is the problem with automating builds on OpenShift?

If you want to build in Quay or DockerHub we have to ditch the s2i and build from Dockerfile

[zak-hassan]

We could still have s2i it doesn't have to go away. I was suggesting to have the commits trigger a build of the latest image. Of whatever is in upstream/master

[vpavlin]

How do you build s2i in Quay?

[zak-hassan]

I don't know if quay supports s2i. But my thought was just to include a dockerfile that uses centos-py36 base image.

[4n4nd]

I think keeping an archive of old images is a good idea, but triggering a build on every commit seems like an overkill. Maybe we can do releases and each release can trigger a new build.

[zak-hassan]

So seems like we don't have consensus on automated build process with quay.io . I'll close this issue and assume that we don't have this requirement on automated image builds.