On Sep 9, 2020, at 06:31, Zero King wrote:
> However, GitHub Actions does not provide a list of IP addresses
> AFAIK, so integration with paste.macports.org would be difficult. Maybe
> I should just use the other pastebin and hardcode the URL into mpbot-ci
> to avoid it being inherited in macpo
On Tue, Sep 08, 2020 at 10:12:08PM +0200, Mojca Miklavec wrote:
On Tue, 8 Sep 2020 at 20:49, Zero King wrote:
> I forgot why we never switched from Azure to GitHub Actions.
Done in commit db7b40d8691e1fcd8b6be5e3c2a2a00a7ce0bdf4. We should
remove Travis CI and Azure Pipelines soon.
Awesome,
On Tue, 8 Sep 2020 at 19:25, Ralph Seichter wrote:
>
> * Mojca Miklavec:
>
> >> If I can assist, let me know, but I don't think it likely at this
> >> point.
> >
> > Because you lack time or for some other reason?
>
> I would make the time for MacPorts. My assumption is just that I still
> know to
On Tue, 8 Sep 2020 at 22:43, Clemens Lang wrote:
> On Tue, Sep 08, 2020 at 06:48:58PM +, Zero King wrote:
> > On Tue, Sep 08, 2020 at 06:39:41PM +0200, Mojca Miklavec wrote:
> > > After a while Azure came around with 6 hours of timeout which was a
> > > lot more useful, and the same solution wa
Hi,
On Tue, Sep 08, 2020 at 06:48:58PM +, Zero King wrote:
> On Tue, Sep 08, 2020 at 06:39:41PM +0200, Mojca Miklavec wrote:
> > After a while Azure came around with 6 hours of timeout which was a
> > lot more useful, and the same solution was ported from Travis to
> > Azure. I forgot why we n
On Tue, 8 Sep 2020 at 20:49, Zero King wrote:
>
> > I forgot why we never switched from Azure to GitHub Actions.
>
> Done in commit db7b40d8691e1fcd8b6be5e3c2a2a00a7ce0bdf4. We should
> remove Travis CI and Azure Pipelines soon.
Awesome, thank you very much!
I'm just confused about one thing. The
On Tue, 8 Sep 2020 at 19:11, Ralph Seichter wrote:
>
> * Ryan Schmidt:
>
> >> Tries being the operative word here. ;-)
> >
> > What are you trying to say?
>
> Did I step on somebody's toes?
I'm not aware why you would step on anyone's toes, but I also didn't
understand what you tried to say in tha
Hello,
On Tue, Sep 08, 2020 at 06:39:41PM +0200, Mojca Miklavec wrote:
On Mon, 7 Sep 2020 at 20:25, Ralph Seichter wrote:
If you ignore Travis results, why run Travis CI in the first place?
Travis was the first CI that we supported for pull requests.
@l2dy wrote the initial support as a GSOC
* Mojca Miklavec:
>> If I can assist, let me know, but I don't think it likely at this
>> point.
>
> Because you lack time or for some other reason?
I would make the time for MacPorts. My assumption is just that I still
know to little about how the MacPorts builds work to be of assistance,
and th
* Ryan Schmidt:
>> Tries being the operative word here. ;-)
>
> What are you trying to say?
Did I step on somebody's toes? I am saying that the build that concerns
me timed out setting up the dependencies. That, from my understanding,
means the dependencies were either unavailable in binary form,
On Sep 8, 2020, at 11:39, Mojca Miklavec wrote:
> On Tue, 8 Sep 2020 at 18:28, Ryan Schmidt wrote:
>> On Sep 7, 2020, at 11:24, Ruben Di Battista wrote:
>>
>>> Would à Linux machine with some virtualization method (libvirt?) be
>>> acceptable as CI runner?
>>
>> I can't see how, since we're try
On Sep 7, 2020, at 13:25, Ralph Seichter wrote:
> * Mojca Miklavec:
>
>> It tries to install dependencies as binaries, provided the binaries
>> are available.
>
> Tries being the operative word here. ;-)
What are you trying to say? It uses binary archives if available, and they
should be av
On Mon, 7 Sep 2020 at 20:25, Ralph Seichter wrote:
> * Mojca Miklavec:
>
> > We should figure out:
> > - which dependencies time out
> > - why they are not installed from (the private) binary package repository
>
> I'm guessing that "we" means the devs who maintain the build config.
Oh, no, that's
On Sep 7, 2020, at 11:24, Ruben Di Battista wrote:
> Would à Linux machine with some virtualization method (libvirt?) be
> acceptable as CI runner?
I can't see how, since we're trying to verify builds of ports, and there is no
general expectation that port builds would work on non-Mac opera
* Mojca Miklavec:
> What we need is:
> - a list of recipes to set up images for a bunch of different macOS
> versions (as far back into history as possible)
> - a recipe for how to fire up a VM, do something basic (port install
> foo) and trash the result
Looking at the Travis CI config and the r
* Mojca Miklavec:
> It tries to install dependencies as binaries, provided the binaries
> are available.
Tries being the operative word here. ;-)
> We should figure out:
> - which dependencies time out
> - why they are not installed from (the private) binary package repository
I'm guessing that
On Mon, 7 Sep 2020 at 18:25, Ruben Di Battista wrote:
>
> I was wondering... Would à Linux machine with some virtualization method
> (libvirt?) be acceptable as CI runner?
This is something we've been looking at, among others.
Now, a Linux machine with libvirt is probably not entirely legal, but
On Mon, 7 Sep 2020 at 18:44, Ralph Seichter wrote:
> * Joshua Root:
>
> >> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780
> >
> > It's just a matter of how long your port takes to build (including
> > installing all its dependencies).
>
> Notmuch, which is what was built in
On 2020-9-8 02:44 , Ralph Seichter wrote:
> * Joshua Root:
>
>>> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780
>>
>> It's just a matter of how long your port takes to build (including
>> installing all its dependencies).
>
> Notmuch, which is what was built in the job [1
* Ryan Schmidt:
> I feel that the Azure Pipelines are already giving us good results on
> current systems, and we could probably turn off the Travis builds for
> the systems that Azure also covers.
That seems like a reasonable approach to me.
-Ralph
* Mojca Miklavec:
> If you volunteer to do some research / work in this area ... that
> would likely be the most significant step in "increasing your chances"
I actually have some experience in this field. I use GitLab (Omnibus
edition), Docker, and GitLab Runners inside Docker for CI/CD. That's
* Joshua Root:
>> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780
>
> It's just a matter of how long your port takes to build (including
> installing all its dependencies).
Notmuch, which is what was built in the job [1], is small and builds in
less than a minute on my Mac
I was wondering... Would à Linux machine with some virtualization method
(libvirt?) be acceptable as CI runner? Any of you has experience in terms
of performance?
Also, Gitlab CI allows to attach personal runners to project very easily
(just a package to install from the os package manager) . How
> On Sep 7, 2020, at 08:50, Mojca Miklavec wrote:
>
> On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote:
>>
>> I fail to remember the last time one of my builds successfully passed
>> Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently
>> make it through Travis OK, so I wande
On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote:
>
> I fail to remember the last time one of my builds successfully passed
> Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently
> make it through Travis OK, so I wander what I can do to increase my
> chances?
By far the best thin
On 2020-9-7 18:45 , Ralph Seichter wrote:
> I fail to remember the last time one of my builds successfully passed
> Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently
> make it through Travis OK, so I wander what I can do to increase my
> chances?
>
> [1] https://travis-ci.org/g
26 matches
Mail list logo
