On Mon, May 20, 2019 at 4:41 PM Ondřej Čertík <ond...@certik.us> wrote:
>
>
>
> On Mon, May 20, 2019, at 4:15 PM, Aaron Meurer wrote:
> > On Mon, May 20, 2019 at 3:51 PM Ondřej Čertík <ond...@certik.us> wrote:
> > >
> > >
> > >
> > > On Mon, May 20, 2019, at 3:44 PM, Isuru Fernando wrote:
> > > >
> > > >
> > > > On Mon, May 20, 2019 at 4:30 PM Aaron Meurer <asmeu...@gmail.com> wrote:
> > > > > On Mon, May 20, 2019 at 2:45 PM Isuru Fernando <isu...@gmail.com> 
> > > > > wrote:
> > > > >  >
> > > > >  >
> > > > >  > On Mon, May 20, 2019 at 3:34 PM Aaron Meurer <asmeu...@gmail.com> 
> > > > > wrote:
> > > > >  >>
> > > > >  >> Thanks. My biggest question has been how we can do it in the 
> > > > > cloud.
> > > > >  >> Most CI services run multiple concurrent jobs on the same machine,
> > > > >  >> making the performance inconsistent. Does drone.io let you have a
> > > > >  >> dedicated machine?
> > > > >  >
> > > > >  >
> > > > >  > Drone.io has a shared cloud offering which we don't want. As you 
> > > > > mentioned we can buy a cheap dedicated machine and install drone on 
> > > > > it for free.
> > > > >  >
> > > > >  > Drone might support dedicated machines on the cloud, but I'm not 
> > > > > sure. Travis-CI supports dedicated machines, but we looked at this 
> > > > > for conda-forge and they were quite expensive.
> > > > >
> > > > >  I see, so Drone is a CI software, similar to gitlab CI or Azure.
> > > >
> > > > Yes
> > > > >  We
> > > > >  will need to decide which of those is the most appropriate to use.
> > > > >  I've heard good things about GitLab CI. Can it not be used with 
> > > > > GitHub
> > > > >  repos?
> > > >
> > > > I though it couldn't, but looks like they do,
> > > > https://about.gitlab.com/handbook/marketing/product-marketing/enablement/github-ci-cd-faq/#open-source-projects-opportunity
> > > > I like Gitlab CI and I know Ondrej has experience setting up Gitlab
> > > > runners on dedicated machines.
> > > >
> > > > >
> > > > >  Regarding the hardware, the question is if there are cloud providers
> > > > >  that provide dedicated machines, and how much they cost. If anyone 
> > > > > has
> > > > >  any suggestions for this let me know.
> > > >
> > > > If we go with Gitlab CI with github integration, we can use something
> > > > like https://aws.amazon.com/ec2/pricing/dedicated-instances/
> >
> > That could work. We could use one of the cheaper Linux instances. We
> > only need one CPU (I don't know if it's safe to run benchmarks in
> > parallel on multicore machines), and it doesn't matter how fast the
> > machine is, so long as it is consistent. I guess a faster machine
> > would make the CI finish faster, but for now the benchmarks only take
> > about 5 minutes or so to run, so it shouldn't be a big deal.
>
> Yes, those dedicated instances might work.

We should shop around more too. $2/hour comes out to $17520/year if
run 24/7. Even if it's only up 50% of the time that's still a chunk of
money. But it might be worth it compared to setting up and maintaining
a physical machine.

>
> >
> > >
> > > I would suggest to go with GitLab CI if at all possible. It's a solid 
> > > product, and it can be used with GitHub via mirroring on GitLab:
> > >
> > > https://about.gitlab.com/solutions/github/
> >
> > Does that work with pull requests?
>
> Yes, but not by default, one has to setup a bot to do that. Here is how 
> somebody already did exactly that:
>
> https://gitlab.com/gitlab-org/gitlab-ee/issues/5667#note_144893904
>
> Here is an example GitHub PR:
>
> https://github.com/coq/coq/pull/9648
>
> if you click on the green check mark, there is a link to the GitLab-CI 
> pipeline.

Looks like the bot has to set the status too.

But it's all doable, and still probably easier to manage than Azure.

Aaron Meurer

>
> >
> > >
> > > and it can be run on either dedicated machine, or in the cloud.
> > >
> > > I think the way forward is to set this up, and for testing we can use the 
> > > runners at gitlab.com which are free. Then we can move to a dedicated 
> > > machine, say at linode.com. And finally we can move to our custom server. 
> > > It's just about where the GitLab-CI runner executes, the rest of the 
> > > configuration does not change.
> >
> > Does the GitLab runner take care of running things in an isolated
> > Docker container, or do we have to do that ourselves (for the case
> > where we use our own hardware)?
>
> gitlab-runner takes care of that.
>
> Ondrej
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sympy+unsubscr...@googlegroups.com.
> To post to this group, send email to sympy@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/6925d408-d39f-494f-8a09-019e0f09da2d%40www.fastmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAKgW%3D6LiVsV2PwyL_WPWqucPt8jr%3DWSnZwSww%3DKTR5HHkdKmig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to