thanks
Stephan van Hulst wrote:
You got it the wrong way around.
Code gets checked into version control by a developer, which in turn triggers build pipelines that build and test the software.
Yes. I realize that mistakenly I said in the wrong order and code check-in is the first step.
Stephan van Hulst wrote:
When tests pass, the next step is triggered, which usually is not related to version control, but rather to some form of deploying the build artefacts.
Is it correct to say that preparing the build artefacts is CI and deploying the build artefacts is CD. If not, then up to what stage exactly does it come under CI and from where stage does CD begin?
Stephan van Hulst wrote:
Jenkins is a good example of a CI tool
Is it correct to say that Jenkins can do things like build pipeline (involving running the unit testes and preparing the build artefacts) but it cannot do the Deploy part and for that we require something?
Stephan van Hulst wrote:
Continuous Delivery can also just mean bundling the deployable artifacts together and putting them in a shared folder or making them available for download on a website.
Is it correct to say that in any case the end result of continuous delivery, would be that code is ready to be run now from wherever it is intended to be run from?
Stephan van Hulst wrote:
Again, these are common scenarios, but far from the only ones.
If the code is to be deployed and run from Cloud then, it requires things like CodeDeploy or Spinnaker, but if the code is required to be just deployed on
Tomcat then what is required as CD tool and can it be done without using a CD tool too, if so how?