+1 for [1] Jenkins (A setup separated from Apache Jenkins) - with various plugins.
Bhavin Thaker. On Fri, Nov 10, 2017 at 11:39 AM, Madan Jampani <[email protected]> wrote: > +1 for (1) > > On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal <[email protected]> > wrote: > > > Hi All, > > A need has been identified for MXNet’s CI/CD setup to move away from the > > Apache Jenkins Service. Over the past few days there has been active > > discussion on the necessary and advanced features for such a system and > the > > various options available. These are being tracked in this Google Doc > > <https://docs.google.com/document/d/17PEasQ2VWrXi2Cf7IGZSWGZMawxDk > dlavUDASzUmLjk/edit> (and > > are also in the pdf attached). > > > > I would like to start a vote to choose the framework for this new CI/CD > > system. The options are - > > [1] Jenkins (A setup separated from Apache Jenkins) - with various > plugins > > [2] TeamCity > > [3] Travis CI > > [4] GitLabCI > > [5] BuildBot > > [6] Other - Please Name > > > > Please feel free to add a comment to support your choice. > > This vote will be open from now until the end of the day on Monday > > 11/13/2017 > > > > Thanks, > > Meghna Baijal > > > > > > >
