Maybe I'm missing something, or maybe they haven't rolled out all the new features yet, but this product looks identical to the GCloud Container Builder that's been on GCP for at least a year. Its even got all the old container builds from that product, and the UI is identical.<p>Is there anything actually new here? I can't find any indication in their documentation that its different; seems like it's just a different name?
This may be a nice time and place to ask ... I have docker problems.<p>We have a monorepo in GitLab and that works nicely. Many Dockerfiles are present in this repo in various folders. They all build private docker images pushed to AWS ECR. They all depend on each other and some have multiple parents, so this sort of forms a family tree.<p>It is a major pain to know what docker images are stale and need to be rebuilt, and to ensure that it's parents are also up to date. We do all this manually and it sucks.<p>Some images take hours to build and we only want to rebuild them when necessary.
It would be great if the build server cached build-steps so that the resulting images could share more layers with previously downloaded images, saving hugely on disk space, time and bandwidth for people and servers.<p>We make sure to have one Dockerfile per folder and a file called "destination.txt" indicating the final image name adjacent to it, this allows scripts to easily build the entire tree of images and parents by scanning our repo.<p>We want nice automation. I don't even know what the best practices are here.<p>What should I do?
This Google Cloud Container Builder rebranded, which is a good thing. I've been abusing Container Builder as a general CI system for a while, I hope the rebranding indicates there will be more focus and feature development on general CI functionality.
I have been using this for several years now. Great stuff! :) The only part that was missing from this was something that can update your deployments on image build. That's when I built Keel <a href="https://github.com/keel-hq/keel" rel="nofollow">https://github.com/keel-hq/keel</a>.<p>Basically, I have one trigger to always build from master but the rest are triggered by tag, for example, "1.2.5" and it builds the same image, then Keel updates affected workloads. So far I have never had to pay for it, apparently managing to stay in the free tier :)<p>Works way faster than automated Docker cloud builds either.
I understand how great this is, but does anyone else get a little upset when GCP, AWS, and Azure are able to buy their way into a market and are pretty much guaranteed to hurt the small players in the infra tooling market?
I was really excited at first, but it's worth noting this does nothing for App Engine users. If you want CI there you still need to go to a third party. Disappointing considering how they're pitching this.
This is their container builder project re-branded.<p>Pretty nice product, but missing some LAUGHABLE features.<p>Specifically:<p>- Ability to start builds based on github pull requests<p>- Ability to send messages to slack on successful / failed builds<p>- Ability to update github PRs with build status<p>- Conditional build steps AT ALL<p>- Ability to start parameterized builds from GUI ( What if I want to deploy to a specific environment? )<p>- Any outside integrations AT. ALL.<p>- No story on how to store secrets<p>I've been running this product for about a year. I have a Jenkins job that detects github PRs, and then launches these builds. I would LOVE to delete that Jenkins VM, but for some reason a lot of basic functionality has been ignored.<p>edit:<p>People have informed me that Github PR building is in alpha! PRAISED BE THE GOOGLE!<p><a href="https://cloud.google.com/cloud-build/docs/run-builds-on-github" rel="nofollow">https://cloud.google.com/cloud-build/docs/run-builds-on-gith...</a>
How does the free tier work? Can you sign up so that you only use the free tier, and builds beyond the limit are queued for the next day or don't occur at all?<p>Or do you need to have a "card on file" to run the free tier at all, with the chance that you'll have to pay if you somehow exceed the free tier (stuck build, etc)?
How does this work for booting up a database or other systems to run integration tests and such? I don't see anything about that sort of thing. Is the idea to bake everything into a single docker image and run that? Also, what are the resource limits (really, just interested in ram) for that listed price?
Tried a simple curl cloud builder with passed in variables and it works pretty nice.<p>The only feature request I have is a way to mark variables as sensitive/secure and not show them in the build history step in plain text (mask the value) and change the input type from text to password.
That console, though. Most players in this space seem to invest heavily in a very feature complete configuration GUI but in this case, there's absolutely nothing. Just a build history page and a small wizard to set up triggers.
Is there any plan to make this a partner product ?<p>It's limited to 10 Concurrent Build for obvious reason, making it impossible for startup who want to create CI services on top of this product due to limitation.