Hi all, I'm on the eng team for this service. Happy to answer any questions, and I'll do my best to monitor the threads.
Introducing Google Cloud Container Builder
11–20 of 114 posts
Re: Introducing Google Cloud Container Builder
#12I'd love to see that target the market for CI/CD tools which cost an arm and leg while offering a shiny UI but only a minor convenience. That would require an extended tutorial section and an ecosystem of plugins.
We agree! We maintain the official plugins (which we call "build steps" or "builders") here: https://github.com/googlecloudplatform/cloud-builders
Support is limited, more or less, to what I am really familiar with. If you have other use cases that we could support with other builders, I'd love to see a FR on that GitHub repo.
Also, you can use literally any container image as a build step. Details about how to make that happen are here: https://cloud.google.com/container-builder/docs/api/custom-b...
Re: Introducing Google Cloud Container Builder
#13With appengine exposing instances and cloud container facilitating the deployment of software packages, i wonder how long it'll take until the two merge.
That's basically what App Engine Flexible [0] is. It's yet to reach General Availability, but all you have to do is define a bunch of containers and a dispatch.yaml file [1], and App Engine then takes care of deploying/routing/scheduling it for you. [0] https://cloud.google.com/appengine/docs/flexible/ [1] https://cloud.google.com/appengine/docs/flexible/python/how-...
[deleted]
Re: Introducing Google Cloud Container Builder
#14Could someone explain specifically what problem Container Builder solves?
I think it's sort of container building as a service. It moves the burden of building Docker container from your laptop (or from your CI tool) to the GCE. It takes away the docker push, as it goes straight to the GCE registry (I guess).
So if you need to do docker build too often, or maybe your container-release process feels a bit quirky, you might want to do it with the container builder.
It doesn't seem too ground-breaking, people probably already have it automated somehow, or they use sth from Docker hub (https://docs.docker.com/docker-hub/builds/#remote-build-trig...), or quay.
Re: Introducing Google Cloud Container Builder
#15"First 120 build-minutes per day" : FREE Nice for Hobby projects...
We haven't had many projects exceed their daily free tier so far, and we've been backing all App Engine Flexible deployments for a while.
If you do exceed your daily free tier, you're only billed $0.0034/minute, on a per-second basis, so we expect the cost of using this product to be very low.
(disclaimer: I work on this product)
Re: Introducing Google Cloud Container Builder
#16I'd love to see that target the market for CI/CD tools which cost an arm and leg while offering a shiny UI but only a minor convenience. That would require an extended tutorial section and an ecosystem of plugins.
We agree! We maintain the official plugins (which we call "build steps" or "builders") here: https://github.com/googlecloudplatform/cloud-builders Support is limited, more or less, to what I am really familiar with. If you have other use cases that we could support with other builders, I'd love to see a FR on that GitHub repo. Also, you can use literally any container image as a build step. Details about how to make…
I like how Codeship approaches the problem - see here for inspiration https://documentation.codeship.com/pro/getting-started/steps... Still, they're super expensive and not very performant, so I welcome competition.
What I'm missing here is an easy way to link a container being tested with external containers (eg DB).
Re: Introducing Google Cloud Container Builder
#17Could someone explain specifically what problem Container Builder solves?
I think it's sort of container building as a service. It moves the burden of building Docker container from your laptop (or from your CI tool) to the GCE. It takes away the docker push, as it goes straight to the GCE registry (I guess). So if you need to do docker build too often, or maybe your container-release process feels a bit quirky, you might want to do it with the container builder. It doesn't seem too ground…
In addition to the "typical" kinds of builds you'll get with existing services (ie run 'docker build' and 'docker push' for me), we offer a flexible and powerful configuration language: https://cloud.google.com/container-builder/docs/api/build-st...
One of the goals is to make it easy to separate the build-time environment from the run-time environment. eg, keep the JDK out of your deployable.
We do this by letting you choose arbitrary container images to run with your source volume-mounted in. We provide some simple ones, like one that runs the 'docker' CLI, and we take care of authenticated docker pushes to GCR.
But, you can use whatever you like as a builder.
Re: Introducing Google Cloud Container Builder
#18Hi all, I'm on the eng team for this service. Happy to answer any questions, and I'll do my best to monitor the threads.
Thanks skj.. any plans of supporting containers other than docker ?
Re: Introducing Google Cloud Container Builder
#19Earlier quoted context omitted.
We agree! We maintain the official plugins (which we call "build steps" or "builders") here: https://github.com/googlecloudplatform/cloud-builders Support is limited, more or less, to what I am really familiar with. If you have other use cases that we could support with other builders, I'd love to see a FR on that GitHub repo. Also, you can use literally any container image as a build step. Details about how to make…
I like how Codeship approaches the problem - see here for inspiration https://documentation.codeship.com/pro/getting-started/steps... Still, they're super expensive and not very performant, so I welcome competition. What I'm missing here is an easy way to link a container being tested with external containers (eg DB).
re: link the container with external containers, that's a bit tricky and generally I think that's a space you should use a "dev" environment for.
We like to be the connection between source and registry, with your dev environment being after the registry.
Re: Introducing Google Cloud Container Builder
#20Was just reading about this today. Didn't know it was new.