Release builds

Alexis BRENON @Xfce brenon.alexis+xfce at
Wed Sep 15 07:59:01 CEST 2021

Hi Simon,

I'm not used to Xfce releasing process but this is a very nice pattern.
At my company we use a similar one, publishing the archives directly on the
archive server. This prevents the need for storage on the CI server. We use
Jenkins instead of GitLab CI, and I hope that most knowledge can be reused.
Do not hesitate if you wish to discuss some ideas.

Kind regards,

Le mer. 15 sept. 2021 à 02:41, <andre at> a écrit :

> Hi Simon,
> That's awesome, anything that facilitates releases is more than welcome!
> Do you have plans for next steps? Maybe create issues in dev-tools or
> housekeep?
> I'm available to test, at the very least with reviewing/testing :)
> Oh, we need to keep in mind this means more disk space will be used, not
> long ago we had outages exactly due running out of disk space.
> Cheers,
> Andre Miranda
> Sep 14, 2021, 12:00 by simon at
> Hey everyone,
> I just quickly wanted to let you know that I merged a PR[1] that enables
> "release builds" whenever we push a new tag to GitLab (at least I hope it
> does :D).
> What happens then is that a new stage ("release") is triggered that runs
> distcheck but at the same time retains the resulting tar.bz2 as a
> downloadable artifact along with the CI run.
> Obviously this is duplicating what we already do as part of releasing by
> pushing to archive.x.o, but consider this a starting step to automating
> this part of our release and to building the release tarballs not locally
> but in our CI. (Ofc anyone who wants to use the tarballs to upload them to
> the release tool can do so.)
> Among the current limitations is also that only tarballs with the tar.bz2
> extension are caught, but we can fix these things over time.
> Cheers
> Simon
> [1]
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Xfce4-dev mailing list