4 ms·
There are many way to do this but we (distelli) recommend the following: 1. Run automated tests during container build (maybe in the AfterBuildSuccess step) 2
by kt9 10y ago
There are many way to do this but we (distelli) recommend the following:
1. Run automated tests during container build (maybe in the AfterBuildSuccess step)
2. Have a single image that goes to both staging and production. Pass in environment variables or configs to operate the image differently in staging or prod
3. Don't include test dependencies in the image so the image is smaller. So if you're running tests etc don't add the tests and dependencies in the Dockerfile. Instead have your CI system run the tests.
- gkop 10y ago> Instead have your CI system run the tests. Is "your CI system" typically distelli or another vendor?
- kt9 10y agoWe (distelli) do provide our own CI system but you don't have to use ours. You can use your own CI system and kick off the pipeline from that. Some of our customers use Jenkins while others use one of the many hosted CI systems.
- gkop 10y agoI like the flexibility from the point of view of minimizing the initial configuration work when we already have a CI vendor in place. To be precise - Can distelli work with GitHub's CI API so that the distelli container build kicks off only after GitHub reports a CI pass?
- kt9 10y agoYes, we can kick off a kubernetes deployment based on the pipeline rules you specify from any CI server that can make an API call to our service. So you can use Jenkins or Gitlab CI or any other CI you like and when that system reports a CI pass we can kick off the deploy to your k8s cluster.
- gkop 10y agoThanks for explaining!