Bug 256537

Summary: Please publish the list of servers running poudriere by architecture, build system version
Product: Ports & Packages Reporter: Yuri Victorovich <yuri>
Component: Package InfrastructureAssignee: Port Management Team <portmgr>
Status: New ---    
Severity: Affects Only Me CC: adamw, antoine, bdrewery, evgeniy, grahamperrin, lwhsu, philip
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Yuri Victorovich freebsd_committer 2021-06-10 17:42:19 UTC
I am trying to find the poudriere URL for arm64, FreeBSD 13.

I found:
* ampere1.nyi.freebsd.org - runs {12*,13*}-arm64-quarterly
* ampere2.nyi.freebsd.org - runs {head,main}-arm64-default

But it isn't obvious how to find 13-arm64-default.

Is there a list or table of all poudriere servers by architecture, system version? Maybe porters' handbook (https://docs.freebsd.org/en/books/porters-handbook/testing/#testing-poudriere) is the right place?
Comment 1 Li-Wen Hsu freebsd_committer 2021-06-10 17:55:10 UTC
Pkg building infra is mainly maintained by portmgr, with help from clusteradm like preparing the installation image of the base system.

I guess https://pkg-status.freebsd.org helps a little bit?
Comment 2 Yuri Victorovich freebsd_committer 2021-06-10 18:08:51 UTC
(In reply to Li-Wen Hsu from comment #1)

Yes, but the only 13*arm64 build listed there is 130arm64-quarterly. 130arm64-default isn't listed.
Comment 3 Philip Paeps freebsd_committer 2021-06-11 03:24:35 UTC
I asked Antoine (added to Cc:) about this a couple of days ago.  We are reportedly not running 13-arm64-default builds at this time.  I do not know why this is.  I thought that we had started doing this when we promoted aarch64 to Tier-1.  This is a portmgr decision, not a clusteradm decision.

As for your original question about publishing a list of servers, I agree with Li-Wen that the closest we have to that currently is https://pkg-status.freebsd.org.  The code for that is on https://github.com/bdrewery/pkg-status.freebsd.org if you'd like to help make that information clearer.

Since there is no public (or even developer) access to the beefy* and ampere* machines, there's little point in tracking their configurations in the doc tree.  The physical machines run reasonably up to date builds of CURRENT (up to about six months old).  The poudriere jails track releases and stable branches.
Comment 4 Yuri Victorovich freebsd_committer 2021-06-11 03:47:33 UTC
(In reply to Philip Paeps from comment #3)
Comment 5 Yuri Victorovich freebsd_committer 2021-06-11 03:50:13 UTC
(In reply to Philip Paeps from comment #3)

Ok, thank you.

One user asked me why packages for one particular port aren't up-to-date for the 13-arm64-default architecture, and I asked here.

Now the question is why don't we run builds for 13-arm64-default.
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2021-06-11 10:26:54 UTC
I offered portmgr a mockup for of the following page, but it attracted no interest:

https://people.freebsd.org/~linimon/tmp/matrix.html
Comment 7 Graham Perrin 2021-06-14 21:13:49 UTC
(In reply to Philip Paeps from comment #3)

> …  no public (or even developer) access to the beefy* and ampere* machines, …

From posts such as <https://forums.FreeBSD.org/threads/80708/post-517089> and <https://forums.FreeBSD.org/threads/80708/post-517129>, it seems that there's: 

* public access
* limited to IPv6.

----

Side note, re: <https://forums.FreeBSD.org/threads/80878/post-517188> it seems that my ISP at home does not provide IPv6 service. So far, none of the computers to which I have remote access can reach <http://beefy3.nyi.freebsd.org/> (DNS_PROBE_FINISHED_NXDOMAIN and so on) so I guess that these networks, similarly, are without IPv6 connectivity.
Comment 8 Bryan Drewery freebsd_committer 2021-06-17 19:58:32 UTC
https://pkg-status.freebsd.org/builds?type=package is the public interface.
Comment 9 Adam Weinberger freebsd_committer 2021-06-18 02:07:15 UTC
(In reply to Bryan Drewery from comment #8)

Perhaps we should link to this from some public places. There's real value in developers and admins being able to keep an eye on builds and logs.