[MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
----------------------------+--------------------
 Reporter:  mkae            |      Owner:  raimue
     Type:  defect          |     Status:  new
 Priority:  Normal          |  Milestone:
Component:  server/hosting  |    Version:  2.3.4
 Keywords:                  |       Port:
----------------------------+--------------------
 On 01 Nov 2016, at 02:02 , Rainer Müller <[hidden email]> wrote:

 > Can we maybe decide on special commands in commit messages that cause
 the buildbot to completely ignore the commit? Such things should not limit
 us to what we can commit or not.
 >
 > Perhaps a footer line (similar to Signed-off-by) at the end, such as:
 >
 > buildbot: ignore
 >
 >
 > For reference, other services seem to use "[ci skip]" as a keyword that
 can appear anywhere in the commit message.

 +1

 I’d also suggest to use this also to specify which buildbots should be
 triggered for a commit along those lines:
 {{{
 buildbot: Mavericks Sierra
 }}}
 I think that can be very helpful in some cases.

--
Ticket URL: <https://trac.macports.org/ticket/52769>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+--------------------
  Reporter:  mkae            |      Owner:  raimue
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+--------------------

Comment (by mkae):

 Sorry, @raimue, I meant to enter your handle into the CC field, but I
 inadvertently made you owner of this ticket!

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+--------------------
  Reporter:  mkae            |      Owner:  raimue
      Type:  enhancement     |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+--------------------
Changes (by mkae):

 * type:  defect => enhancement


--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+--------------------
  Reporter:  mkae            |      Owner:  raimue
      Type:  enhancement     |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+--------------------
Description changed by mkae:

Old description:

> On 01 Nov 2016, at 02:02 , Rainer Müller <[hidden email]> wrote:
>
> > Can we maybe decide on special commands in commit messages that cause
> the buildbot to completely ignore the commit? Such things should not
> limit us to what we can commit or not.
> >
> > Perhaps a footer line (similar to Signed-off-by) at the end, such as:
> >
> > buildbot: ignore
> >
> >
> > For reference, other services seem to use "[ci skip]" as a keyword that
> can appear anywhere in the commit message.
>
> +1
>
> I’d also suggest to use this also to specify which buildbots should be
> triggered for a commit along those lines:
> {{{
> buildbot: Mavericks Sierra
> }}}
> I think that can be very helpful in some cases.

New description:

 On 01 Nov 2016, at 02:02 , Rainer Müller wrote:

 > Can we maybe decide on special commands in commit messages that cause
 the buildbot to completely ignore the commit? Such things should not limit
 us to what we can commit or not.
 >
 > Perhaps a footer line (similar to Signed-off-by) at the end, such as:
 >
 > buildbot: ignore
 >
 >
 > For reference, other services seem to use "[ci skip]" as a keyword that
 can appear anywhere in the commit message.

 +1

 I’d also suggest to use this also to specify which buildbots should be
 triggered for a commit along those lines:
 {{{
 buildbot: Mavericks Sierra
 }}}
 I think that can be very helpful in some cases.

--

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------
Changes (by neverpanic):

 * owner:  raimue => larryv
 * status:  new => assigned


Comment:

 Larry has worked on the buildbot lately and provided the GitHub webhook
 integration. He might now if there's an easy way to do this.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by larryv):

 From a policy standpoint: I don’t like the idea of polluting our
 (permanent!) commit history with transient administrivia like this. Will
 continue discussing on macports-dev.

 From a technical standpoint:
 - It would be easy enough to filter out something simple like “buildbot:
 ignore”. Not so easy to parse OS names and match them to builders.
 - Either Ryan or Rainer (can’t recall at the moment, would have to search
 email) has expressed a desire to remove builder-aware logic from
 `master.cfg`, which I agree with. This would restrict us to substring
 /regex-based line noise, like
   {{{
   buildbot: ports-10.9_x86_64 ports-10.12_x86_64
   }}}
 - Accepted changes get sent to all builders. I don’t know off the top of
 my head whether there is a way for builders to filter requests.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by raimue):

 This Stackoverflow answer describes a possible implementation of what we
 want: http://stackoverflow.com/a/30670892/67498

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by larryv):

 This "modify a magic file" idea is intriguing.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by neverpanic):

 How is modifying a magic file (which is also in the history of the
 repository) different from putting the skip command in the commit message?
 Additionally, the magic file potentially increases the likelihood of merge
 conflicts and puts a useless file into the repository. I'd rather see the
 commit message approach than the file approach.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by mkae):

 Replying to [comment:9 neverpanic]:
 > ... I'd rather see the commit message approach than the file approach.
 +1

 The KDE folks also control a variety of git hooks through their commit
 messages. See [https://quickgit.kde.org/?p=macports-
 kde.git&a=blob&h=14f952f776b9f54263671cc2aba5886c6ebee75b&f=contrib%2Fgit-
 setup%2F.git-commit-template&o=plain their commit template]. I believe we
 should also have a common template for our devs which
 [https://trac.macports.org/wiki/WorkingWithGit#commitmessages takes all
 the hints found in our "Commit messages" section of the "Working with git"
 wiki page on board].

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by larryv):

 I don’t think it’s necessary or desirable to bother with this. In any
 case, wholly off-topic.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.3.4
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------

Comment (by larryv):

 Replying to [comment:9 neverpanic]:
 > How is modifying a magic file (which is also in the history of the
 > repository) different from putting the skip command in the commit
 > message?

 The difference is that one won’t see the magic file when one is looking
 through a list of commit messages.

 If you want to argue that it pollutes the list of changes…I can’t really
 deny it. Different side of the same coin, I guess.

 > Additionally, the magic file potentially increases the likelihood of
 > merge conflicts

 That’s true, but I’m assuming that skipping out on the buildbot run would
 be a rare thing. If people start doing it whenever they don’t feel like
 getting a build failure email (which I’m frankly afraid they will), I’d
 rather we not implement this at all and just manually disable the webhook
 on the rare occasions that we need to do a mass commit.

 > and puts a useless file into the repository.

 Got me there.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------
Changes (by mojca):

 * keywords:   => buildbot
 * version:  2.3.4 =>


--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by ryandesign):

 The buildbot is supposed to automatically build all changes. Why do we
 want to give committers the ability to override that?

 I feel there are real underlying problems that we should be fixing
 instead. For example, annoyance with failure emails due to known failures
 needs to be addressed by allowing a portfile syntax for indicating that a
 port is known to fail in certain configurations, not by making the
 committer exclude a particular builder every time they commit to that port
 by using commit message syntax.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:15>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + builbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + builbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by mkae):

 Replying to [comment:15 ryandesign]:
 > The buildbot is supposed to automatically build all changes. Why do we
 want to give committers the ability to override that?

 Very simple: in case a committer knows in advance that only a specific
 platform is affected. Why to bug all other builders with Sierra-related
 build trials if you know that those won't give any valuable result on
 older platforms?!?

 This potentially could lower the load on our buildbot system during the
 development of port (group) files which require testing on a buildbot.

 P.S.: But, as always, this is only a suggestion (from someone not
 professionally involved in any kind of software development, so my ideas
 might be misleading/irrelevant).

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:17>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + buildbot: post-commit-hook selecting which buildbots should be used for CI (was: Git + builbot: post-commit-hook selecting which buildbots should be used for CI)

MacPorts
In reply to this post by MacPorts
#52769: Git + buildbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:17 mkae]:
 > Very simple: in case a committer knows in advance that only a specific
 platform is affected. Why to bug all other builders with Sierra-related
 build trials if you know that those won't give any valuable result on
 older platforms?!?
 >
 > This potentially could lower the load on our buildbot system during the
 development of port (group) files which require testing on a buildbot.

 The ideal solution in that case is to verify your changes on your local
 Sierra system before committing. If you have no local Sierra-capable
 system then committing hypothetical fixes and letting the buildbot test
 them is acceptable. We should [ticket:52765 implement the "successcache"]
 to reduce the load on the buildbot.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:18>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + buildbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + buildbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by mkae):

 Replying to [comment:18 ryandesign]:
 > The ideal solution in that case is to verify your changes on your local
 Sierra system before committing.

 Of course it is. That's what I always do. Still, sometimes things slip
 through, because it is sometimes not so easy to have everything
 identically set up like it is for the buildbots. I do try not to cause
 trouble, but I do sometimes and for that I'd like a feature like this
 which decreases the damage which I could do.

 > If you have no local Sierra-capable system then committing hypothetical
 fixes and letting the buildbot test them is acceptable.

 I know.

 > We should [ticket:52765 implement the "successcache"] to reduce the load
 on the buildbot.

 I didn't know about this ticket.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:19>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + buildbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + buildbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by larryv):

 Replying to [comment:15 ryandesign]:
 > The buildbot is supposed to automatically build all changes. Why do we
 > want to give committers the ability to override that?

 I am not keen on "buildbot: ignore" and am strongly opposed to the
 individual builder selection.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:20>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + buildbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + buildbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by mojca):

 I would say that what we desperately need is:
 * "success cache" (#52765)
 * a way to disable builds for known-to-be-broken configurations (for
 example disable ports that require C++11 on certain platforms, disable
 software that fails to build on newer OSes, ...); not sure if there's a
 ticket, but Ryan posted an email to the list a while ago
 * more efficient setup to avoid crashing the system after a "mass commit"
   * less important: being able to merge multiple commits into a single
 portwatcher job

 Once we have that in place, I don't see that much need for hacking
 buildbot instructions into commit messages. If one port fails to build
 just on Sierra and builds successfully everywhere else, the next commit
 doesn't have to do a revbump and then the buildbot would only consume
 resources of Sierra anyway.

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:21>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #52769: Git + buildbot: post-commit-hook selecting which buildbots should be used for CI

MacPorts
In reply to this post by MacPorts
#52769: Git + buildbot: post-commit-hook selecting which buildbots should be used
for CI
-----------------------------+----------------------
  Reporter:  mkae            |      Owner:  larryv
      Type:  enhancement     |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:  buildbot
      Port:                  |
-----------------------------+----------------------

Comment (by mkae):

 Fine, so, feel free to close this ticket as 'wontfix' then, I am not
 insisting on it. :-)

--
Ticket URL: <https://trac.macports.org/ticket/52769#comment:22>
MacPorts <https://www.macports.org/>
Ports system for macOS
12