+1 on Jenkins; makes sense to me to keep it within the same tech as used on
the Apache side.
(Noting that as this is not a required vote, I don't believe this needs to
go to general@incubator or need 3 mentor +1s). As long as 3 committers are
+1 it's good in my opinion.
Hen
On Tue, Nov 14, 2017
@Sandeep, while I've had good experiences with CodeBuild, I'm not sure if
it would address the needs of this project due to lack of instance type
options. For example I don't believe they support GPU instances, which are
required for a large portion of our build/test process. I'd propose we use
s
+1 for [1] (A setup separated from Apache Jenkins)
On Mon, Nov 13, 2017 at 4:50 AM, sandeep krishnamurthy
wrote:
> +1 for [1] Jenkins (A setup separated from Apache Jenkins) - with
> preferably AWS Code Build integration to reduce the size of infrastructure
> we need to maintain.
>
> Thanks,
> S
+1 for [1] Jenkins (A setup separated from Apache Jenkins) - with
preferably AWS Code Build integration to reduce the size of infrastructure
we need to maintain.
Thanks,
Sandeep
On Fri, Nov 10, 2017 at 11:57 AM, Bhavin Thaker
wrote:
> +1 for [1] Jenkins (A setup separated from Apache Jenkins) -
+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
wrote:
> +1 for (1)
>
> On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal
> wrote:
>
> > Hi All,
> > A need has been identified for MXNet’s CI/CD setup
+1 for (1)
On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal
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 th
+1 for 1) (binding)
On 10.11.2017 10:30, kellen sunderland wrote:
+1 for 1 (non-binding)
On Fri, Nov 10, 2017 at 6:37 AM, Chris Olivier
wrote:
+1 for 1) — Jenkins
On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy wrote:
+1 on 1)
On Nov 9, 2017, at 8:59 PM, Steffen Rochel
wrote:
voting
+1 for 1 (non-binding)
On Fri, Nov 10, 2017 at 6:37 AM, Chris Olivier
wrote:
> +1 for 1) — Jenkins
>
>
> On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy wrote:
>
> > +1 on 1)
> >
> > > On Nov 9, 2017, at 8:59 PM, Steffen Rochel
> > wrote:
> > >
> > > voting for [1]
> > > We will need to setup test
+1 for 1) — Jenkins
On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy wrote:
> +1 on 1)
>
> > On Nov 9, 2017, at 8:59 PM, Steffen Rochel
> 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
+1 on 1)
> On Nov 9, 2017, at 8:59 PM, Steffen Rochel 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
> wrote:
>
>> Hi All,
>> A need has been identified for MXNet’s CI/CD
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
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
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
12 matches
Mail list logo