5 ms·

I'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 e

I'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.

skj 10y ago
We agree! We maintain the official plugins (which we call "build steps" or "builders") here: https://github.com/googlecloudplatform/cloud-builders 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-build-steps https://cloud.google.com/container-builder/docs/api/custom-b...
- fishnchips 10y ago
  I like how Codeship approaches the problem - see here for inspiration https://documentation.codeship.com/pro/getting-started/steps/ 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).
  - skj 10y ago
    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.
    - fishnchips 10y ago
      That's not how I expect CI to work. I might be wrong though.
  - kellyjandrews 10y ago
    Disclaimer: Codeship employee. Glad you like our approach. We are constantly working on performance, for sure. Since we offer dedicated build machines, there are always options for better performance. Appreciate the feedback, and feel free to reach out to me directly anytime if you have other questions or thoughts on how we can get better.
    - fishnchips 10y ago
      I did have a call some 3 months ago with your support rep and a sales person and provided extensive feedback - which was acknowledged and ignored. Which is precisely why I welcome new competitors that could wake you up from your comfy slumber ;)

skj 10y ago

We agree! We maintain the official plugins (which we call "build steps" or "builders") here: https://github.com/googlecloudplatform/cloud-builders 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-build-steps https://cloud.google.com/container-builder/docs/api/custom-b...

fishnchips 10y ago
I like how Codeship approaches the problem - see here for inspiration https://documentation.codeship.com/pro/getting-started/steps/ 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).
- skj 10y ago
  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.
  - fishnchips 10y ago
    That's not how I expect CI to work. I might be wrong though.
- kellyjandrews 10y ago
  Disclaimer: Codeship employee. Glad you like our approach. We are constantly working on performance, for sure. Since we offer dedicated build machines, there are always options for better performance. Appreciate the feedback, and feel free to reach out to me directly anytime if you have other questions or thoughts on how we can get better.
  - fishnchips 10y ago
    I did have a call some 3 months ago with your support rep and a sales person and provided extensive feedback - which was acknowledged and ignored. Which is precisely why I welcome new competitors that could wake you up from your comfy slumber ;)