Timeline for How to capture tools release to trigger upgrade?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2017 at 13:29 | history | edited | Tensibai | CC BY-SA 3.0 |
added 190 characters in body
|
| Apr 6, 2017 at 13:28 | comment | added | Tensibai | @DanCornilescu added this was my opinion in the answer, all in all this is a little aside of the question itself. | |
| Apr 6, 2017 at 13:26 | comment | added | Dan Cornilescu | @Tensibai - it's up to the respective team to decide if it's worthy or not. | |
| Apr 6, 2017 at 13:24 | comment | added | Tensibai | @DanCornilescu That means 4 CI/CD systems, one test and prod in two groups for cross validation... sounds really overkill for this use case. | |
| Apr 6, 2017 at 13:23 | history | edited | Tensibai | CC BY-SA 3.0 |
added 4 characters in body
|
| Apr 6, 2017 at 13:20 | comment | added | karthikeayan | i meant continuous deployment in a way that it includes some quality checks | |
| Apr 6, 2017 at 13:18 | comment | added | Dan Cornilescu | It might not be trivial, but not impossible. But it is not the same pipeline - it's a different system being upgraded, with its own pipeline. | |
| Apr 6, 2017 at 13:15 | comment | added | Tensibai | Because here you're upgrading your pipeline infrastructure... It will have a hard time validating itself. (inception ?) And in the context of the question I understand the quote as 'install updates as soon as available directly into prod' which is not a good idea IMHO. | |
| Apr 6, 2017 at 13:12 | comment | added | Dan Cornilescu | As long as you have a proper QA validation pipeline for the upgrade - I don't see what's the difference between deploying some piece of sw vs another :) | |
| Apr 6, 2017 at 11:55 | history | edited | Tensibai | CC BY-SA 3.0 |
added 17 characters in body
|
| Apr 6, 2017 at 11:46 | history | answered | Tensibai | CC BY-SA 3.0 |