mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Olivier <cjolivie...@gmail.com>
Subject Re: [VOTE] A Separate CI System for Apache MXNet (incubating)
Date Fri, 10 Nov 2017 05:37:18 GMT
+1 for 1) — Jenkins


On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy <mnnaveen@gmail.com> wrote:

> +1 on 1)
>
> > On Nov 9, 2017, at 8:59 PM, Steffen Rochel <steffenrochel@gmail.com>
> wrote:
> >
> > voting for [1]
> > We will need to setup testing on MAC. I will explore for AWS to cover the
> > costs.
> > Steffen
> >
> > On Thu, Nov 9, 2017 at 4:41 PM Meghna Baijal <meghnabaijal2017@gmail.com
> >
> > 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/17PEasQ2VWrXi2Cf7IGZSWGZMawxDkdlavUDASzUmLjk/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
> >>
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message