On 25.07.2018 13:37, Barak Korren wrote:
> Hi all,
>
> Unfortunately, the s390x build host we've been using had gone off-line a
> couple of days ago, and the ETA for having it back up is unknown.
>
> The implication of having the host down is that projects that build on
> s390x have their builds be stuck forever waiting for the s390x node to
> become available.
>
> Sine the s390x builds are missing, builds for other platforms, while being
> successful do not get passed to the change queue and as a result are not
> being released to the nightly repos.
>
> As a work around for the current situation, we need to disable the s390x
> builds. Here is a patch that does this for vdsm:
> https://gerrit.ovirt.org/c/93316/
>
> For V2 projects the change should be done in the projects own repo, for
> example here is how we did it for the CI jobs of the 'jenkins' repo itself:
> https://gerrit.ovirt.org/c/93288/
>
>
As the s390x build machine is up again, we should enable it in Jenkins.
I've posted a patch here:
https://gerrit.ovirt.org/#/c/94041/
[...]
--
Regards,
Viktor Mihajlovski
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/ZMAF6UKNQ5EJZPUXKWKLFBD4YJJLZ7AP/
