#51996: Buildbot: create a new factory to aid with new MacPort releases -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Changes (by mojca): * keywords: => buildbot Old description:

It would be helpful to have a new buildbot factory to create [browser:trunk/base/portmgr/ReleaseProcess everything needed for a new release], other than messing up with svn (tagging, updating the docs, ...) and signing the archives.

Creating a new release is a bit problematic because it requires access to: * all the supported OS versions * payed developer account to sign the packages

We cannot avoid the need to sign the packages (unless the server can do that automatically, but even then it might be a security concern), but we could use the existing infrastructure to compile the components of MacPorts on the target architecture and create the unsigned pkg/dmg files. Well, we would still need a virtual machine for Tiger and Leopard, but 6-7 (or more if we also count the libc++-based builds) could be catered for by the existing infrastructure.

New description: It would be helpful to have a new buildbot factory to create [browser :macports-base/portmgr/ReleaseProcess everything needed for a new release], other than messing up with the repository (tagging, updating the docs, ...) and signing the archives. Creating a new release is a bit problematic because it requires access to: * all the supported OS versions * payed developer account to sign the packages We cannot avoid the need to sign the packages (unless the server can do that automatically, but even then it might be a security concern), but we could use the existing infrastructure to compile the components of MacPorts on the target architecture and create the unsigned pkg/dmg files. Well, we would still need a virtual machine for Tiger and Leopard, but 6-7 ~~(or more if we also count the libc++-based builds)~~ could be catered for by the existing infrastructure. -- -- Ticket URL: <https://trac.macports.org/ticket/51996#comment:4> MacPorts <https://www.macports.org/> Ports system for macOS