poudriere VS icecream

poudriere is a powerful port/package build and test system with a focus on package production and bulk building for FreeBSD. This easy-to-use, parallelized solution relies solely on the base system and can build the entire portstree. Supports building packages for different FreeBSD versions, and ensures compatibility with any package management tool by organizing packages in an identical layout to official mirrors. qci considers it a favorite tool.

poudriere(8) command synonyms: jail, jails … · Issue #1053 · freebsd/poudriere

95% of the time the only thing you have to do is install a package and enable the service. So what's the value in having a centralized repository of pre-configured images? Sure, if you want to roll out an image to thousands of servers - make an image using poudriere image](https://github.com/freebsd/poudriere/wiki/poudriere-image.8-devel) and send them out. It's not really any easier - and is definitely not better - to use an image that someone else made.

> pkg is an amazing system that beats dpkg or rpm

What's your reasoning for this statement? I find poudriere[1] handy for compiling one's own packages from ports configured to fit one's goals, but I see nothing outstanding in plain pkg.

It has issues when there's an IPv6 address up (even link-local) but no egress v6 routing. It would hang and wait for a timeout when an IPv6 address is selected from resolved addresses. After a timeout - pkg connects to v4 endpoint but if there's several packages to be downloaded, it can fall back to trying to connect to v6 with the next package.

On the other hand, I've recently had Ubuntu 22.04 register Python-related packages which were not successfully installed, resulting in all dpkg/apt/apt-get commands failing due to py3clean script throwing trackbacks, until /var/lib/dpkg/status was edited and these packages were in fact installed and then removed.

[1] https://github.com/freebsd/poudriere/wiki

poudriere-devel has a bug where it tries to delete the incorrect zpool when building a zfs image fails. There's a pull request that addresses it, but I have no idea when that will get merged. I also don't know how long it will be before there's a new poudriere release after it gets merged. The current ports version was last updated in 2022-09, so it could be months.

I use this with Poudriere to speed up my FreeBSD pkg host building multiple Sets of ports https://github.com/freebsd/poudriere/wiki/ccache

Also jails is a terrific concept with poudriere and bastille

https://github.com/freebsd/poudriere/wiki/ and more.

Related

https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case.

https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.

Of course! The github readme provides a lot of info - https://github.com/icecc/icecream

If you like distcc, did you ever give icecc a try?

https://github.com/icecc/icecream

I never had the time to set it up properly, but by the looks of it, it should be even better.

I would like to have a icecc setup I can vpn into. It seems that with normal configs the clients can talk to the scheduler, but the scheduler cant connect to the clients as it tries to connect to the device running the openvpn server not the one behind it. How could I make my openvpn clients appear almost as physical devices on the network, with unique IP's that local devices can connect to; or if that is unnecessary how could I solve this?

Glad to see a new release on this! I've read worrying news about the state of icecc, and the followup uncertain news on sccache, so I hope at least some part of the tooling is in a good shape.

I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.