Timeline for Simple explanation of Continuous Integration
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 20, 2019 at 16:48 | history | suggested | Géry Ogam | CC BY-SA 4.0 | fix punctuation |
| Sep 19, 2019 at 16:16 | review | Suggested edits | |||
| S Sep 20, 2019 at 16:48 | |||||
| Jun 13, 2013 at 10:49 | comment | added | c_maker | @Shubham: Well if you are looking at 'continuous integration' (in a lower case sense) it can mean a lot more than what I explained, like what Kate Gregory's answer was. However the question has diagrams of a CI system so I chose to explain CI in that context. I also think that CI is synonymous with a CI system for most developers... | |
| Jun 13, 2013 at 9:23 | comment | added | Shubham | I always thought that CI meant to continously update the working copy so that code you are working on is not out of date. | |
| May 17, 2013 at 20:12 | comment | added | c_maker | @user828584: In my answer, I imply that 'test' is part of a build. And as a side note, TDD is different than having tests to check quality. As a side-effect of TDD, you will have well written tests, but you can have tests without doing any TDD at all. | |
| May 17, 2013 at 19:54 | comment | added | mowwwalker | Is this dependent on test-driven development? Code that compiles isn't always code that works right? Without tests to fail when the code isn't ready, how would the CI system know if the code really was successfully integrated? | |
| May 17, 2013 at 14:01 | comment | added | c_maker | Since the question asked for a simple explanation I left out many (most of the time project/team specific) details that might go into a CI system. | |
| May 17, 2013 at 13:36 | comment | added | gbjbaanb | and deployment, its not enough to compile, and run tests, but you also should ship the binaries to an environment so it can be tested by people (or automated tools) too. | |
| May 17, 2013 at 13:24 | comment | added | Quentin Pradet | Continuous Integration cares about build status, but also about tests. | |
| May 17, 2013 at 13:16 | history | edited | c_maker | CC BY-SA 3.0 | Added explanation about feedback mechanism |
| May 17, 2013 at 12:42 | vote | accept | icc97 | ||
| May 17, 2013 at 12:27 | history | answered | c_maker | CC BY-SA 3.0 |