[Gluster-Maintainers] [gluster-packaging] glusterfs-3.12.14 released

Niels de Vos ndevos at redhat.com
Thu Sep 13 14:10:02 UTC 2018

On Thu, Sep 13, 2018 at 09:43:41AM -0400, Shyam Ranganathan wrote:
> On 09/11/2018 04:44 AM, Niels de Vos wrote:
> > On Thu, Sep 06, 2018 at 08:39:50PM +0200, Niels de Vos wrote:
> >> On Thu, Sep 06, 2018 at 05:07:21PM +0000, jenkins at build.gluster.org wrote:
> >>> SRC: https://build.gluster.org/job/release-new/68/artifact/glusterfs-3.12.14.tar.gz
> >>> HASH: https://build.gluster.org/job/release-new/68/artifact/glusterfs-3.12.14.sha512sum
> >>
> >> These packages have been built in the CentOS Storage SIG. Please enable
> >> the testing repository and try them out (might take a few hours for the
> >> packages to become available).
> >>
> >> Once done testing, let me know and I'll mark them as stable. There are
> >> normally no pushes to the CentOS mirrors done on Friday, so Monday is
> >> the earliest next slot.
> > 
> > There has been no confirmation that these packages work as expected.
> > Could someone try them out and update the lists?
> @Jiffin are you taking care of this? (same for 4.1.4)

Jiffin mentioned yesterday (over the phone) that he tested the latest
versions (3.12.14 and 4.1.4). He would also send and email with a
confirmation. I've tagged the packages yesterday, so they might have
been signed+pushed today (depending on the CentOS team).

> @Niels, can we make this part the CentOS package manager responsibility?
> As it is mostly me who does this testing, just waiting for the build and
> then using the bits, it would be more efficient if done at the source
> IMO. Thoughts?

I actually would love to have this automated, and that should be good
possible. Even once I've done the builds for CentOS-6 and 7, the
packages are not immediately available in the testing repository. It
really does not matter who checks when the packages can be installad and
runs some tests.

Anyone that can provide me with an ansible playbook, or even scripts
that need to run on server and client systems is strongly encouraged to
share them. We can then include them in the CentOS CI where client and
server systems can get reserved with different CentOS releases.

At the moment I do not have any automation to easily run tests locally.
I will rather invest time in setting up jobs in a real CI.


More information about the maintainers mailing list