On 10 June 2018 at 09:42, Barak Korren <bkorren@redhat.com> wrote:


On 8 June 2018 at 12:47, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

As Microsoft engineers say - this is not a bug, its a feature.

That event triggering this was a tag push, it is not actually supported by STDCI ATM.

To rebuild this commit we need to find merge event for it on GitHub and re-fire it.
I've tried to do this but had no success so far since the branches on that repo look a little strange to me.


Actually, my mistake - this fired on a push to the 'BZ1588465' branch.

It probably would have ran the check-merged scripts if there were any. Since there aren't it is not running anything.

If you want to get artifacts built - you need to push to a branch that is defined to build and push into a change-queue, which is to say, a branch that is configured in 'release-branches'.

In any case - since you seem to want a build of that commit, and I do know the GH triggering mechanisms were malfunctioning for a while up to a couple of weeks ago, I re-fired the merge event for the master HEAD commit. The build is currently running here:
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-disaster-recovery_standard-on-ghpush/200
 
 
Thanks,

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

sbonazzo@redhat.com   


_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
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/infra@ovirt.org/message/WNY5ZCMV35GFASFAFSZ4LW23AYV6GERO/




--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted



--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted