Re: Setting up port builds on Azure using master branch of macports

[Rainer Müller]

On 2019-08-09 11:23, Ruben Di Battista wrote:

What are the longest ports to build?

In my experience paraview and mame, also probably the compilers. And
they should fit the 360 minutes, right?


I do not think any single port build will take that long. However, we 
first need to install all dependencies before we can actually test the 
submitted port. In case there are no binary packages for the 
dependencies, these also have to be compiled from scratch first and that 
might take a long time.


Rainer

Re: Setting up port builds on Azure using master branch of macports

[Ruben Di Battista]

What are the longest ports to build?

In my experience paraview and mame, also probably the compilers. And they
should fit the 360 minutes, right?

On Fri, 9 Aug 2019, 07:35 Zero King,  wrote:

> On Thu, Aug 08, 2019 at 08:59:46PM +0200, Rainer Müller wrote:
> >On 04/08/2019 17.34, Ryan Schmidt wrote:
> >> On Aug 1, 2019, at 10:50, Blair Zajac wrote:
> >>
> >>> Why Azure?
> >>
> >> We already use Azure to test pull requests, but we test against the
> released version of MacPorts base, currently 2.5.4. I guess Mojca is
> suggesting we add another builder that uses the newer MacPorts base master,
> to discover if some ports are not compatible with that.
> >>
> >> We also already use Travis CI for pull requests, but Travis was
> purchased by another company known for allowing its services to languish
> and die, hence our desire to find alternatives.
> >>
> >> It would need to be free and support building on macOS with root access
> and not have such a low time limit that our builds would time out. Travis
> for example has a time limit of 50 minutes which has already been
> problematic for some ports. If you know of other services that offer that,
> let us know.
> >
> >GitHub announced GitHub Actions today, which is a CI system provided for
> free on
> >public repositories. It even supports macOS.
> >
> >https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/
> >
> >However, the announcement does not mention any limits such as the maximum
> >per-job execution time, which has been our main problem with other
> services so
> >far. I guess this might be something they will still try to figure out
> during
> >the beta.
>
> The default limit is 360 minutes. Not sure if it could be extended.
>
>
> https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes
>
> >In any case, it might be worth a try. It will be available in November for
> >everyone. Just in case anyone wants to experiment with it earlier, I
> signed up
> >the @macports organization for the GitHub Actions Beta and we are now on
> the
> >waitlist.
> >
> >Rainer
>
> --
> Zero
>

Re: Setting up port builds on Azure using master branch of macports

[Zero King]

On Thu, Aug 08, 2019 at 08:59:46PM +0200, Rainer Müller wrote:

On 04/08/2019 17.34, Ryan Schmidt wrote:

On Aug 1, 2019, at 10:50, Blair Zajac wrote:


Why Azure?


We already use Azure to test pull requests, but we test against the released 
version of MacPorts base, currently 2.5.4. I guess Mojca is suggesting we add 
another builder that uses the newer MacPorts base master, to discover if some 
ports are not compatible with that.

We also already use Travis CI for pull requests, but Travis was purchased by 
another company known for allowing its services to languish and die, hence our 
desire to find alternatives.

It would need to be free and support building on macOS with root access and not 
have such a low time limit that our builds would time out. Travis for example 
has a time limit of 50 minutes which has already been problematic for some 
ports. If you know of other services that offer that, let us know.


GitHub announced GitHub Actions today, which is a CI system provided for free on
public repositories. It even supports macOS.

https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/

However, the announcement does not mention any limits such as the maximum
per-job execution time, which has been our main problem with other services so
far. I guess this might be something they will still try to figure out during
the beta.


The default limit is 360 minutes. Not sure if it could be extended.

https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes


In any case, it might be worth a try. It will be available in November for
everyone. Just in case anyone wants to experiment with it earlier, I signed up
the @macports organization for the GitHub Actions Beta and we are now on the
waitlist.

Rainer


--
Zero


signature.asc
Description: PGP signature

Re: Setting up port builds on Azure using master branch of macports

[Mark Anderson]

I've had the actions beta for a while - I'm actually playing with it right
now to see if I can get my local fork to build. I wonder if I can add my
beta-ness to MacPorts somehow. They ask me the org, but I bet I can't turn
it on even with the right permissions.

—Mark
___
Mark E. Anderson 
Find me on LinkedIn 


On Thu, Aug 8, 2019 at 3:00 PM Rainer Müller  wrote:

> On 04/08/2019 17.34, Ryan Schmidt wrote:
> > On Aug 1, 2019, at 10:50, Blair Zajac wrote:
> >
> >> Why Azure?
> >
> > We already use Azure to test pull requests, but we test against the
> released version of MacPorts base, currently 2.5.4. I guess Mojca is
> suggesting we add another builder that uses the newer MacPorts base master,
> to discover if some ports are not compatible with that.
> >
> > We also already use Travis CI for pull requests, but Travis was
> purchased by another company known for allowing its services to languish
> and die, hence our desire to find alternatives.
> >
> > It would need to be free and support building on macOS with root access
> and not have such a low time limit that our builds would time out. Travis
> for example has a time limit of 50 minutes which has already been
> problematic for some ports. If you know of other services that offer that,
> let us know.
>
> GitHub announced GitHub Actions today, which is a CI system provided for
> free on
> public repositories. It even supports macOS.
>
> https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/
>
> However, the announcement does not mention any limits such as the maximum
> per-job execution time, which has been our main problem with other
> services so
> far. I guess this might be something they will still try to figure out
> during
> the beta.
>
> In any case, it might be worth a try. It will be available in November for
> everyone. Just in case anyone wants to experiment with it earlier, I
> signed up
> the @macports organization for the GitHub Actions Beta and we are now on
> the
> waitlist.
>
> Rainer
>

Re: Setting up port builds on Azure using master branch of macports

[Rainer Müller]

On 04/08/2019 17.34, Ryan Schmidt wrote:
> On Aug 1, 2019, at 10:50, Blair Zajac wrote:
> 
>> Why Azure?
> 
> We already use Azure to test pull requests, but we test against the released 
> version of MacPorts base, currently 2.5.4. I guess Mojca is suggesting we add 
> another builder that uses the newer MacPorts base master, to discover if some 
> ports are not compatible with that.
> 
> We also already use Travis CI for pull requests, but Travis was purchased by 
> another company known for allowing its services to languish and die, hence 
> our desire to find alternatives.
> 
> It would need to be free and support building on macOS with root access and 
> not have such a low time limit that our builds would time out. Travis for 
> example has a time limit of 50 minutes which has already been problematic for 
> some ports. If you know of other services that offer that, let us know.

GitHub announced GitHub Actions today, which is a CI system provided for free on
public repositories. It even supports macOS.

https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/

However, the announcement does not mention any limits such as the maximum
per-job execution time, which has been our main problem with other services so
far. I guess this might be something they will still try to figure out during
the beta.

In any case, it might be worth a try. It will be available in November for
everyone. Just in case anyone wants to experiment with it earlier, I signed up
the @macports organization for the GitHub Actions Beta and we are now on the
waitlist.

Rainer

Re: Setting up port builds on Azure using master branch of macports

[Ryan Schmidt]

On Aug 1, 2019, at 10:50, Blair Zajac wrote:

> On Aug 1, 2019, at 2:01 AM, Mojca Miklavec wrote:
> 
>> Is anyone willing to set up one Azure build instance running macports
>> master when building the ports?
>> 
>> This could help us spot any potential issues with our code in the
>> master branch in the future.

> Why Azure?

We already use Azure to test pull requests, but we test against the released 
version of MacPorts base, currently 2.5.4. I guess Mojca is suggesting we add 
another builder that uses the newer MacPorts base master, to discover if some 
ports are not compatible with that.

We also already use Travis CI for pull requests, but Travis was purchased by 
another company known for allowing its services to languish and die, hence our 
desire to find alternatives.

It would need to be free and support building on macOS with root access and not 
have such a low time limit that our builds would time out. Travis for example 
has a time limit of 50 minutes which has already been problematic for some 
ports. If you know of other services that offer that, let us know.

Re: Setting up port builds on Azure using master branch of macports

[Mojca Miklavec]

> On Aug 1, 2019, at 9:55 AM, Blair Zajac wrote:
>
> By Azure, you’re referring to Microsoft’s Azure cloud offering?

Azure pipelines.
https://dev.azure.com/macports/macports-ports/_build?definitionId=1&_a=summary

> I’m wondering why not Google Compute Engine or AWS?

Do they offer free resources on macOS?

Mojca

Re: Setting up port builds on Azure using master branch of macports

[Blair Zajac]

Adding back macports-dev@.

> On Aug 1, 2019, at 9:55 AM, Blair Zajac  wrote:
> 
> By Azure, you’re referring to Microsoft’s Azure cloud offering? I’m wondering 
> why not Google Compute Engine or AWS? This appears to be independent of 
> Travis?
> 
> Blair
> 
>> On Aug 1, 2019, at 9:17 AM, Mojca Miklavec  wrote:
>> 
>> What othet suggestion do you have? Travis is useless.
>> 
>> Mojca
>> 
>> 
>> V čet., 1. avg. 2019 17:50 je oseba Blair Zajac  
>> napisala:
>> Why Azure?
>> 
>>> On Aug 1, 2019, at 2:01 AM, Mojca Miklavec  wrote:
>>> 
>>> Hi,
>>> 
>>> Is anyone willing to set up one Azure build instance running macports
>>> master when building the ports?
>>> 
>>> This could help us spot any potential issues with our code in the
>>> master branch in the future.
>>> 
>>> Thank you,
>>>   Mojca
>>> 
>> 
> 

Re: Setting up port builds on Azure using master branch of macports

[Blair Zajac]

Why Azure?

> On Aug 1, 2019, at 2:01 AM, Mojca Miklavec  wrote:
> 
> Hi,
> 
> Is anyone willing to set up one Azure build instance running macports
> master when building the ports?
> 
> This could help us spot any potential issues with our code in the
> master branch in the future.
> 
> Thank you,
>Mojca
> 

Setting up port builds on Azure using master branch of macports

[Mojca Miklavec]

Hi,

Is anyone willing to set up one Azure build instance running macports
master when building the ports?

This could help us spot any potential issues with our code in the
master branch in the future.

Thank you,
Mojca