Description of problem: There are no 3.7.x nightly build rpm's available via DGO:
Please could an RPM for the configuration required to test 3.7.x be added to the list of nightly build rpm's we can test with.
Also, could the nightly service build the required RPM's to install the dev verison of 3.7.x
if I install the 3.6 dgo-nightly rpm and edit it by replacing 3.6 with 3.7 I have been able to install this release today:
So its part way there, just seems that the gdo-nightly-3.7 rpm needs building.
changing version to mainline in order to retire pre-release.
If you know the appropriate, correct version for this bug, please
I can't set it, there is no option for ALL 3.7 releases. Basically I want to be able to install the 3.7 nightly builds via an RPM Repo provided from the dgo-nightly folder.
Going with the format of RPM's on the page listed in the opening comment of this bug report we need this created:
Where ???? is:
There are no longer packages for repository files to get the nightly builds. The nightly builds are hosted on the CentOS infrastructure and can be used withe the repo files from here:
@infra-team: the old nightly builds can be removed from download.gluster.org
I believe the Centos CI team strongly suggestings on having artifacts.ci.centos.org for internal consumption. We should probably sync it to downloads.gluster.org so our users don't DDoS artifacts.ci.centos.org.
Niels, what do you think?
(In reply to Nigel Babu from comment #7)
> I believe the Centos CI team strongly suggestings on having
> artifacts.ci.centos.org for internal consumption. We should probably sync it
> to downloads.gluster.org so our users don't DDoS artifacts.ci.centos.org.
Sure, we can do that as well.
- Would we then also (re)add the dgo-nightly 'release' RPMs?
- What can cause a sync from the artifacts server to d.g.o?
* Yep. If you have the xml from the last time, go ahead and add it back.
* I'll happily take a ticket to setup automation to sync that over to d.g.o.
We will not be providing nightly releases for older versions. Going forward, we plan to have this working as part of the pipeline work. But that wouldn't bring in 3.7 versions. We're shooting for next upcoming release.