7 ms·

Google announces Cloud Build, its new continuous integration platform

227 points by AnatMl2 8y ago

thepumpkin1979 8y ago
Nice, all CI should be per minute.
- danpalmer 8y ago
  Why? I'd have thought CI is a place where per-second billing would be an advantage? A CI job is likely to take somewhere between 1 and 15 minutes, per second billing could be a significant saving for many users.
  - dkuebric 8y ago
    Sure that would be great, but the state of the art is actually worse. Some providers charge by concurrency limit, which means you're always paying for peak capacity.
    - LyndsySimon 8y ago
      Oh really? I never really considered that. Perhaps it'd be profitable to actually use that capacity for something when it's idle...
  - ImJasonH 8y ago
    GCB prices are described in terms of dollars-per-minute, but are actually calculated per-second. The price is actually $0.00005/second. :) disclosure: I'm an engineer on the GCB team
- hackergirl88 8y ago
  Bitbucket Pipelines charges per minute as well: https://bitbucket.org/product/features/pipelines https://bitbucket.org/product/features/pipelines
ccccccccccccc 8y ago
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?
- madrox 8y ago
  I take it as a sign that the value bar keeps getting raised for small players to exist. CI is becoming so commodity that it doesn't really matter if you get it from Google or Codeship. If a slow-moving corporate machine can replicate what you do...maybe you need to move faster.
  - ccccccccccccc 8y ago
    Understandable. I suppose as time goes on any product is going to be centralized among a handful of major players.
- magicalist 8y ago
  > does anyone else get a little upset when GCP, AWS, and Azure are able to buy their way into a market There's benefits to smaller, hungrier teams building things, but unless they have paying customers on day one they're also buying their way into the market one way or another...
- partiallypro 8y ago
  I understand this, my company is currently dealing with a similar situation. We have a small vendor that hosts things, but I am pushing to drop them for Azure because it offers so many more features and tools that the vendor just can't match. It's kind of an acquisition thing, we acquired a company that deals with this vendor, we were already using Azure. It's much harder to go off the cloud than to go on it, imo. You just lose so many great features when you move off of it. It's sad, but at the same time it's becoming impossible for smaller people to compete in a cloud world. I don't think that's going to change. My biggest fear is that once all the small players are killed off Google, Microsoft and AWS will agree in some back room to not compete on price to protect their margins. I have a feeling that something like that is merely a decade away, if not less.
013a 8y ago
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. 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?
- t3rabytes 8y ago
  It's the same product -- it was just renamed.
  - knicholes 8y ago
    "its new continuous integration platform." Pretty misleading title, if you ask me. I'd suggest it be titled, "Google renames its old build system."
antoncohen 8y ago
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.
madrox 8y ago
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.
- skybrian 8y ago
  I know next to nothing about this, but there seem to be instructions on how to deploy to App Engine. See the App Engine tab under "Deploying artifacts" [1]. Is there more that's needed? [1] https://cloud.google.com/cloud-build/docs/configuring-builds/build-test-deploy-artifacts https://cloud.google.com/cloud-build/docs/configuring-builds...
  - madrox 8y ago
    Ah you’re right. It was buried and non-obvious (to me).
- gipp 8y ago
  How do you figure this? There's certainly a `gcloud` step available, you can integrate with any GCP services here.
pspeter3 8y ago
Does this replace traditional providers such as CircleCI or TravisCI?
- ben_jones 8y ago
  It did for us, its really easy to create a trigger on a Github branch, run tests, build the executable, and deploy (in out case to k8s). Super quick builds too.
  - pspeter3 8y ago
    That's awesome! I'll have to spend more time looking into it then
  - wereHamster 8y ago
    How do you deploy to k8s? Do you run kubectl from within cloudbuild.yaml, as an additional step at the end?
    - ImJasonH 8y ago
      Yeah, just run kubectl from within your cloudbuild.yaml https://cloud.google.com/cloud-build/docs/configuring-builds/build-test-deploy-artifacts#deploying_artifacts https://cloud.google.com/cloud-build/docs/configuring-builds...
- IshKebab 8y ago
  Not if you want to build on Mac or Windows.
curiousgal 8y ago
I can't wait until they discontinue it!
- throw_away2 8y ago
  Maybe they'll just rename it in 18 months. That would be an improvement and someone can still get a promotion. Now, they just to think up a new name for Reader.
- v_lisivka 8y ago
  My thoughts exactly. Too much risk to commit to Google platform. I will wait for Mozilla cloud instead.
  - andybak 8y ago
    Because Mozilla have never cancelled a project...
    - v_lisivka 8y ago
      Because Mozilla cloud will be open, so if they drop it, an another firm or individual can continue to support it or host it. Rust is the ideal language (so far) for cloud software, so (if talks will materialize) Mozilla cloud software in Rust/Cargo will be much easier to write, support, and host by yourself, if necessary. Non-profit organizations are slower, but better in long term. Only non-profit organization can liberate us.
- andybak 8y ago
  You know this comment has become a cliche?
  - justinhj 8y ago
    So have the actual discontinuations
_5meq 8y ago
This is their container builder project re-branded. Pretty nice product, but missing some LAUGHABLE features. Specifically: - Ability to start builds based on github pull requests - Ability to send messages to slack on successful / failed builds - Ability to update github PRs with build status - Conditional build steps AT ALL - Ability to start parameterized builds from GUI ( What if I want to deploy to a specific environment? ) - Any outside integrations AT. ALL. - No story on how to store secrets 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. edit: People have informed me that Github PR building is in alpha! PRAISED BE THE GOOGLE! https://cloud.google.com/cloud-build/docs/run-builds-on-github https://cloud.google.com/cloud-build/docs/run-builds-on-gith...
- 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 ago
    Container 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 ago
      Don'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...
EngineerBetter 8y ago
I can't see any reason to favour this over Concourse.
- jacques_chester 8y ago
  I've been introducing Jason and Christopher from the Cloud Builder team to Concourse over the past few months. Jason & Co also developed Knative Build which closely tracks the Cloud Builder design. I am hoping to see Concourse come in through the Pipelines proposal on Knative, but it will be necessary to digest a Concourse-on-Kubernetes epic first. (Please come and sing the Concourse-is-amazing hymn with me on Knative, we both know it's for the good) Disclosure: for those who don't know, I work for Pivotal and I'm a bit of a Concourse fan.
deforciant 8y ago
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 https://github.com/keel-hq/keel https://github.com/keel-hq/keel. 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 :) Works way faster than automated Docker cloud builds either.
HillaryBriss 8y ago
The three most expensive words in software development are "Generous free tier"
nodesocket 8y ago
Tried a simple curl cloud builder with passed in variables and it works pretty nice. 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.
solidr53 8y ago
Do they have mac images for building with XCode?
etaioinshrdlu 8y ago
This may be a nice time and place to ask ... I have docker problems. 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. 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. 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. 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. We want nice automation. I don't even know what the best practices are here. What should I do?
- abatilo 8y ago
  I would make build triggers that are based on specific Dockerfiles changing in the repo. Many CI systems can watch a specific file being changed as the task trigger. So if container A is a dependency for container B, then make container B's task trigger be whenever the Dockerfile for container A changes.
- cutety 8y ago
  Several hour builds? I have to ask what kind of app this is for, because I haven’t ever had a build take more than 2 minutes. I’ve been using docker heavily in CI/dev for about 2ish years and the past couple months been getting some production stuff going. My first thought since you say you’re having issues with build caching, you might want to look into multi-stage builds[1], if you haven’t already. I haven’t gotten any “heavy” use from these since I mostly do web stuff in non compiled languages, so I can’t benefit from this feature as much as a compiled language than can just copy binaries around. But, it has been useful for like compiling JS, since it’s done in a separate stage, I a) don’t ever have to contaminate my final image with a node_modules at any point and b) can rebuild the image and used the cached stage if there are no changes in the front end, and that’s usually the longest parts of my builds anyway. However, if you’re in a compiled language (which from the sounds of it, I have a feeling you might be — long builds and multiple dependent components that have to be rebuilt), you can compile some core component in the first stage (A), then have multiple stages (B, C) that depend on that component’s compiled files, and then maybe a final stage (D) that depends on B & C. So then, if you make changes to just C, you’ll only have to rebuild the C & D stages, while the other two are cached. Each stage itself is just an intermediary image, so you can use them as you would the final, and you can even tell Docker to just build up to stage B, if you only need that image. [1] https://docs.docker.com/develop/develop-images/multistage-build/ https://docs.docker.com/develop/develop-images/multistage-bu...
cmjqol 8y ago
Is there any plan to make this a partner product ? 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.
whoisjuan 8y ago
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.
kazishariar 8y ago
I suppose re-enlivening build-bot is out of the question now?
marcrosoft 8y ago
How are you able to build windows or ARM builds with only docker?
BeeOnRope 8y ago
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? 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)?
bonsai80 8y ago
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?

227 points by AnatMl2 8y ago

thepumpkin1979 8y ago

Nice, all CI should be per minute.

danpalmer 8y ago
Why? I'd have thought CI is a place where per-second billing would be an advantage? A CI job is likely to take somewhere between 1 and 15 minutes, per second billing could be a significant saving for many users.
- dkuebric 8y ago
  Sure that would be great, but the state of the art is actually worse. Some providers charge by concurrency limit, which means you're always paying for peak capacity.
  - LyndsySimon 8y ago
    Oh really? I never really considered that. Perhaps it'd be profitable to actually use that capacity for something when it's idle...
- ImJasonH 8y ago
  GCB prices are described in terms of dollars-per-minute, but are actually calculated per-second. The price is actually $0.00005/second. :) disclosure: I'm an engineer on the GCB team
hackergirl88 8y ago
Bitbucket Pipelines charges per minute as well: https://bitbucket.org/product/features/pipelines https://bitbucket.org/product/features/pipelines

ccccccccccccc 8y ago

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?

madrox 8y ago
I take it as a sign that the value bar keeps getting raised for small players to exist. CI is becoming so commodity that it doesn't really matter if you get it from Google or Codeship. If a slow-moving corporate machine can replicate what you do...maybe you need to move faster.
- ccccccccccccc 8y ago
  Understandable. I suppose as time goes on any product is going to be centralized among a handful of major players.
magicalist 8y ago
> does anyone else get a little upset when GCP, AWS, and Azure are able to buy their way into a market There's benefits to smaller, hungrier teams building things, but unless they have paying customers on day one they're also buying their way into the market one way or another...
partiallypro 8y ago
I understand this, my company is currently dealing with a similar situation. We have a small vendor that hosts things, but I am pushing to drop them for Azure because it offers so many more features and tools that the vendor just can't match. It's kind of an acquisition thing, we acquired a company that deals with this vendor, we were already using Azure. It's much harder to go off the cloud than to go on it, imo. You just lose so many great features when you move off of it. It's sad, but at the same time it's becoming impossible for smaller people to compete in a cloud world. I don't think that's going to change. My biggest fear is that once all the small players are killed off Google, Microsoft and AWS will agree in some back room to not compete on price to protect their margins. I have a feeling that something like that is merely a decade away, if not less.

013a 8y ago

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. 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?

t3rabytes 8y ago
It's the same product -- it was just renamed.
- knicholes 8y ago
  "its new continuous integration platform." Pretty misleading title, if you ask me. I'd suggest it be titled, "Google renames its old build system."

antoncohen 8y ago

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.

madrox 8y ago

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.

skybrian 8y ago
I know next to nothing about this, but there seem to be instructions on how to deploy to App Engine. See the App Engine tab under "Deploying artifacts" [1]. Is there more that's needed? [1] https://cloud.google.com/cloud-build/docs/configuring-builds/build-test-deploy-artifacts https://cloud.google.com/cloud-build/docs/configuring-builds...
- madrox 8y ago
  Ah you’re right. It was buried and non-obvious (to me).
gipp 8y ago
How do you figure this? There's certainly a `gcloud` step available, you can integrate with any GCP services here.

pspeter3 8y ago

Does this replace traditional providers such as CircleCI or TravisCI?

ben_jones 8y ago
It did for us, its really easy to create a trigger on a Github branch, run tests, build the executable, and deploy (in out case to k8s). Super quick builds too.
- pspeter3 8y ago
  That's awesome! I'll have to spend more time looking into it then
- wereHamster 8y ago
  How do you deploy to k8s? Do you run kubectl from within cloudbuild.yaml, as an additional step at the end?
  - ImJasonH 8y ago
    Yeah, just run kubectl from within your cloudbuild.yaml https://cloud.google.com/cloud-build/docs/configuring-builds/build-test-deploy-artifacts#deploying_artifacts https://cloud.google.com/cloud-build/docs/configuring-builds...
IshKebab 8y ago
Not if you want to build on Mac or Windows.

curiousgal 8y ago

I can't wait until they discontinue it!

throw_away2 8y ago
Maybe they'll just rename it in 18 months. That would be an improvement and someone can still get a promotion. Now, they just to think up a new name for Reader.
v_lisivka 8y ago
My thoughts exactly. Too much risk to commit to Google platform. I will wait for Mozilla cloud instead.
- andybak 8y ago
  Because Mozilla have never cancelled a project...
  - v_lisivka 8y ago
    Because Mozilla cloud will be open, so if they drop it, an another firm or individual can continue to support it or host it. Rust is the ideal language (so far) for cloud software, so (if talks will materialize) Mozilla cloud software in Rust/Cargo will be much easier to write, support, and host by yourself, if necessary. Non-profit organizations are slower, but better in long term. Only non-profit organization can liberate us.
andybak 8y ago
You know this comment has become a cliche?
- justinhj 8y ago
  So have the actual discontinuations

_5meq 8y ago

This is their container builder project re-branded. Pretty nice product, but missing some LAUGHABLE features. Specifically: - Ability to start builds based on github pull requests - Ability to send messages to slack on successful / failed builds - Ability to update github PRs with build status - Conditional build steps AT ALL - Ability to start parameterized builds from GUI ( What if I want to deploy to a specific environment? ) - Any outside integrations AT. ALL. - No story on how to store secrets 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. edit: People have informed me that Github PR building is in alpha! PRAISED BE THE GOOGLE! https://cloud.google.com/cloud-build/docs/run-builds-on-github https://cloud.google.com/cloud-build/docs/run-builds-on-gith...

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 ago
  Container 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 ago
    Don'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...

EngineerBetter 8y ago

I can't see any reason to favour this over Concourse.

jacques_chester 8y ago
I've been introducing Jason and Christopher from the Cloud Builder team to Concourse over the past few months. Jason & Co also developed Knative Build which closely tracks the Cloud Builder design. I am hoping to see Concourse come in through the Pipelines proposal on Knative, but it will be necessary to digest a Concourse-on-Kubernetes epic first. (Please come and sing the Concourse-is-amazing hymn with me on Knative, we both know it's for the good) Disclosure: for those who don't know, I work for Pivotal and I'm a bit of a Concourse fan.

deforciant 8y ago

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 https://github.com/keel-hq/keel https://github.com/keel-hq/keel. 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 :) Works way faster than automated Docker cloud builds either.

HillaryBriss 8y ago

The three most expensive words in software development are "Generous free tier"

nodesocket 8y ago

Tried a simple curl cloud builder with passed in variables and it works pretty nice. 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.

solidr53 8y ago

Do they have mac images for building with XCode?

etaioinshrdlu 8y ago

This may be a nice time and place to ask ... I have docker problems. 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. 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. 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. 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. We want nice automation. I don't even know what the best practices are here. What should I do?

abatilo 8y ago
I would make build triggers that are based on specific Dockerfiles changing in the repo. Many CI systems can watch a specific file being changed as the task trigger. So if container A is a dependency for container B, then make container B's task trigger be whenever the Dockerfile for container A changes.
cutety 8y ago
Several hour builds? I have to ask what kind of app this is for, because I haven’t ever had a build take more than 2 minutes. I’ve been using docker heavily in CI/dev for about 2ish years and the past couple months been getting some production stuff going. My first thought since you say you’re having issues with build caching, you might want to look into multi-stage builds[1], if you haven’t already. I haven’t gotten any “heavy” use from these since I mostly do web stuff in non compiled languages, so I can’t benefit from this feature as much as a compiled language than can just copy binaries around. But, it has been useful for like compiling JS, since it’s done in a separate stage, I a) don’t ever have to contaminate my final image with a node_modules at any point and b) can rebuild the image and used the cached stage if there are no changes in the front end, and that’s usually the longest parts of my builds anyway. However, if you’re in a compiled language (which from the sounds of it, I have a feeling you might be — long builds and multiple dependent components that have to be rebuilt), you can compile some core component in the first stage (A), then have multiple stages (B, C) that depend on that component’s compiled files, and then maybe a final stage (D) that depends on B & C. So then, if you make changes to just C, you’ll only have to rebuild the C & D stages, while the other two are cached. Each stage itself is just an intermediary image, so you can use them as you would the final, and you can even tell Docker to just build up to stage B, if you only need that image. [1] https://docs.docker.com/develop/develop-images/multistage-build/ https://docs.docker.com/develop/develop-images/multistage-bu...

cmjqol 8y ago

Is there any plan to make this a partner product ? 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.

whoisjuan 8y ago

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.

kazishariar 8y ago

I suppose re-enlivening build-bot is out of the question now?

marcrosoft 8y ago

How are you able to build windows or ARM builds with only docker?

BeeOnRope 8y ago

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? 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)?

bonsai80 8y ago

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?