Timeline for Exact gap from Continuous Integration to Continuous Delivery
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11 at 16:24 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 874 characters in body
|
| Dec 1, 2019 at 18:27 | comment | added | Thomas Owens♦ | @josef98 I've been thinking a little more and I think it's important to define who you deliver to. So...who are you delivering to? An integration and test team? An independent quality assurance team? A customer or end user? If you define your process such that a test team is the customer of the development team (based on your process definition), you could refer to continuous deployment to refer to deploying to their environment. They would gate a deployment to end users, perhaps. | |
| Dec 1, 2019 at 15:26 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 21 characters in body
|
| Dec 1, 2019 at 14:03 | comment | added | Thomas Owens♦ | @josef98 It depends. Do people have access to this test environment? How long do these tests take to run? Continuous Integration needs rapid feedback to developers. My initial thinking is that I would be using Continuous Delivery to put the software in this test environment, where it undergoes more extensive testing. | |
| Dec 1, 2019 at 13:54 | comment | added | Josef | Let's say my software is automatically being built and then deployed to a testing environment so that some automated integration tests can be run against it to ensure that the cooperation with other services is working. Now is the process of deploying to that test environment a part of continuous integration (since the goal of the deployment is running the tests) or is it part of continuous delivery (since, like you said, deploying in a test environment is the end result of CD)? | |
| Dec 1, 2019 at 13:30 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |