2 ms·
It doesn't appear to be a rebranding, but an upgrade or a rewrite, since the site mentions the first two points (that I checked): https://cloud.google.com/clou
by puzzle 8y ago
It doesn't appear to be a rebranding, but an upgrade or a rewrite, since the site mentions the first two points (that I checked):
https://cloud.google.com/cloud-build/ https://cloud.google.com/cloud-build/
"Set up triggers to automatically build, test, or deploy source code when you push changes to GitHub, Cloud Source Repositories, or a Bitbucket repository."
https://cloud.google.com/cloud-build/docs/configure-third-party-notifications https://cloud.google.com/cloud-build/docs/configure-third-pa...
I looked at Container Builder before and, like you, was not impressed, but this is something else.
- antoncohen 8y agoContainer Builder has been able to trigger based on changes to GitHub repos for a while (tags and merges to branches). What it (and the new branding) can't do, and what the parent comment is referring to, is trigger builds when PRs are opened, and update the PR with the build status.
- puzzle 8y agoDon't you need an existing branch to open a PR? I get your second point about updating the PR itself: everything needs to go through PubSub. Edit: I found the changelog (https://cloud.google.com/cloud-build/release-notes https://cloud.google.com/cloud-build/release-notes), which confirms that this is both a rebranding and update, but also points to a new alpha GitHub app: https://cloud.google.com/cloud-build/docs/run-builds-on-github https://cloud.google.com/cloud-build/docs/run-builds-on-gith... "Observe that the Google Cloud Build app builds your code on creating a pull request." "Go to the Checks tab. You'll see that Cloud Build has built your changes and you should see that your build has succeded. You'll also see other build details such as the time it took to build your code, the build ID, etc." There might be hope...