Re: [Xen-devel] Xen project CI systems and committer workflow

[Doug Goldstein <cardoe@xxxxxxxxxx>]

On Thu, Apr 18, 2019 at 02:59:17PM +0100, Andrew Cooper wrote:
> On 18/04/2019 13:31, Wei Liu wrote:
> > Hi all
> >
> > We now have Gitlab CI as a complementary system to Osstest and have planned 
> > to
> > add bots. It's high time we think about how we integrate them and how it may
> > improve our workflow.
> >
> > ## Requirements
> >
> > 1. We want to have light weight build tests before a patch series is 
> > reviewed
> > or committed.
> >
> > 2. We don't want to push broken patches to central repository such that
> > everyone is blocked.
> >
> > 3. We don't want to significantly change committer workflow.
> >
> > Requirement 2 means that our current branching model will need to be 
> > changed.
> > Details will follow.
> 
> While everything presented here is fine to do as a matter of policy, the
> committers still need to retain the ability to actually push directly to
> the staging branches on xen.git
> 
> The security team needs to be able to make embargoed content appear at
> the point of public disclosure.  The security team already takes
> responsibility for all testing of this content before the public embargo
> point, and this policy will need to continue.
> 
> ~Andrew

What about the ability to push a branch to the CI loop with the highest
priority so that its picked up immediately? There has been more than one
XSA where the patches provided in the emails don't apply cleanly or
don't build so it does seem valuable to still run the CI loop.

--
Doug

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel