Congratulations and thumbs up for you and the team for the support - I guess this is good news for our hub based projects.
On Sun, 1 Oct 2017 at 14:19 Barak Korren <bkor...@redhat.com> wrote: > Over the next few days we're going to review and merge a new patch [1] > that will finally provide the capability to trigger STDCI jobs when PRs are > merged in GitHub. > > Once this patch is merged, projects in GitHub that have the proper hook > configured, can have 'check-merged' jobs be triggered for them when patches > are merged (Please note that this is a different hook then the one that is > used for triggering on PR events). > > Following this we will also review and merge a series of patches [2] which > closes our GitHub functionality gap further by providing the ability to > automatically build merged PRs or pushed commits and submit them to the > change queue for OST testing and publishing. > > This essentially means that, once mentioned patches are merged, projects > in GitHub will be able to fully participate in all the oVirt CI processes. > > Some aspects of the GitHub functionality are actually a little more > advanced then what is currently available for Gerrit. It is not longer > needed to specify complex YAML in the 'jenkins' repo. Instead, only a > single line is needed to enable the functionality (We left this requirement > because we don't want to blindly run jobs for everything that hits the > webhook). Everything else, including target platforms and versions can no > be specified via a simple YAML file in the project's own source repository. > > An example of this yaml file can be seen in the 'ovirt-ansible' project. > We are working on further documentation and will update when its ready. > > [1]: https://gerrit.ovirt.org/c/81971/ > [2]: > https://gerrit.ovirt.org/q/topic:%2522change-queue-github%2522+(status:open%20OR%20status:merged) > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > _______________________________________________ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
