On Sat, Sep 26, 2015 at 2:52 AM, Michael Neale <[email protected]> wrote:
In various blogs, books and conferences like citcon <http://citconf.com/> I have > heard the term "continuous delivery" used to mean the overarching concepts > that you mention needs a new name at the end. > > Those blogs/books/conferences are doing exactly what I said we shouldn't. Continuous Delivery comes after Continuous Integration in the lifecycle and is a separate process. If we were to pick something that covers all of them, the only thing I've heard of is the IT term DevOps that is catching on in the IT (as opposed to sw dev) world. But DevOps doesn't necessarily have to have continuous processes, and it typically is described as covering the whole lifecycle... hmm.... if IT DevOps is overarching and doesn't have to imply continuous processes, what do we think of Continuous DevOps CDO? Sure we aren't explicitly covering requirements and design *now* but I can think of primitive continuous processes to just publish the latest changes to those artifacts... and I know there are some automated validation techniques for them as well... so we *COULD* potentially have Jenkins controlling continuous cycles in every phase. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFzFsaoTF3BztDd_hfnAHE4HoWkueduQM_48cwvB8aOny-65Jw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
