If we use this I think it's main purpose should be to facilitate CI and
integration testing of the apache/cloudstack repo.
The first hurdle in using this repo for CI work is the fact that none of
the open PRs from apache/cloudstack are available in the
cloudstack/cloudstack repo. If we are only u
Will,
I think you are putting the carriage before the horse, sort of speak.
I would suggest you make a dummy PR to cloudstack/cloudstack (just one, let’s
not talk about migration or anything like that).
then you can use this as a playground to see how you could improve our CI…
The main idea be
I mentioned it here since that was the thread that Sam and Chris were most
engaged in, so I wanted the people who were watching these other threads be
aware of that thread as we were getting good traction there.
On Mar 19, 2016 9:57 AM, "Daan Hoogland" wrote:
> Will,
>
> On Fri, Mar 18, 2016 at 7
I agree that your title better describes what we are trying to achieve.
On Mar 19, 2016 9:57 AM, "Daan Hoogland" wrote:
> Will,
>
> On Fri, Mar 18, 2016 at 7:03 PM, Will Stevens
> wrote:
>
> > Please be advised this conversation is continuing in a thread titled: Re:
> > External fork of Cloudsta
Will,
On Fri, Mar 18, 2016 at 7:03 PM, Will Stevens wrote:
> Please be advised this conversation is continuing in a thread titled: Re:
> External fork of Cloudstack
>
> Mailing list link:
>
> http://markmail.org/message/53ct2mma4x4jm6s2?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Re:+Extern
The copying existing PRs would be for the purpose of running CI against it
in the context of being able to automate what happens next given the
result.
I am going to be putting time into fixing marvin tests and also merging in
any fixes to marvin to try to get the CI runs as bulletproof as possibl
Please be advised this conversation is continuing in a thread titled: Re:
External fork of Cloudstack
Mailing list link:
http://markmail.org/message/53ct2mma4x4jm6s2?q=list:org%2Eapache%2Eincubator%2Ecloudstack-%2A+Re:+External+fork+of+Cloudstack
Please come join the conversation in that thread..
On Wed, Mar 16, 2016 at 8:46 PM, Will Stevens wrote:
> If we use this I think it's main purpose should be to facilitate CI and
> integration testing of the apache/cloudstack repo.
>
> The first hurdle in using this repo for CI work is the fact that none of
> the open PRs from apache/cloudstack ar
On Tue, Mar 15, 2016 at 11:07 PM, Daan Hoogland
wrote:
> devs,
>
> There is a github organisation called cloudstack, to which we have more
> control then to the apache/cloudstack repo on github. We need to decide as
> community what to do with it.
>
> What are we going to do in this new organisat
I am in favor of having a few volunteers start experimenting with it.
Especially with/for CI
I don’t think we have urgency to make any bold move right now.
One thing we could do for sure, is to move everything that’s in
CloudStak-Extras to cloudstack org.
> On Mar 15, 2016, at 11:43 PM, Nux!
It seemed pretty obvious that being hold back by Apache's traditional infra was
a big problem.
I am not a developer, but even I have noticed the revolution github brought
with it.
I say we push it forward.. I am not exactly sure how this will affect our
Apache status..
Lucian
--
Sent from the
11 matches
Mail list logo
