The approach we use in our projects has grown up without any formal rules from C4. Anyone who wants to add a CI target can do so. So there are CI targets for Travis, Jenkins, AppVeyor, etc. Lots of them. This is disjoint from the development process in that it does not affect e.g. whether a pull request is merged or not.
Most CI setups trigger on any change to the branch (master) that they are watching. And most people will build separate environments for test and prod, yes. Again, outside the scope of C4. -Pieter On Fri, Jun 3, 2016 at 10:15 PM, Kevin Meredith <[email protected]> wrote: > Hi - > > I read about C4 in Pieter's Social Architecture book and > http://rfc.zeromq.org/spec:22/. > > On my work project (web service), I'd like to move forward with C4's > branching, i.e. a single `master` branch on the main repo, deployment model. > > However, I'm curious how to implement this from a Jenkins/CI perspective > > For a web service using the C4 protocol, does a merge pushed into `master` > result in an auto-CI build (compile + test + deploy web service)? > > Lastly, are separate environments, e.g. Dev, Non-Prod, Prod, for web service > deployments compatible with C4? > > Thank you! > Kevin > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
