Xen-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: Ian Jackson <ian.jackson@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: xen-devel@lists.xenproject.org
Subject: [Xen-devel] Notes from summit design session on branch management
Date: Fri, 12 Jul 2019 22:39:52 +0100
Message-ID: <23848.65064.511423.772481@mariner.uk.xensource.com> (raw)

Here are the photos I took of the flipchart:
  https://xenbits.xen.org/people/iwj/2019/summit-ci-branch-workshop/

My notes, in fairly unredacted form, are below.  We should to write
this up into a proper proposal.

-8<-

Phase 1

 A robot will create a Gitlab MR out of each of certain branches on
 xenbits

 Each such branch will be rebased onto staging and the result run
 through the existing Gitlab CI tests.

 After Gitlab CI has been run on each MR, if it passes, a robot pushes
 it to staging.

 After this has been running for a while, we ask maintainers to push
 to the new robot input branches (above) rather than directly to
 staging.

Phase 2

 Instead of testing staging, osstest will directly combine number of
 the outstanding gitlab MRs into a single candidate branch, and test
 that.  If it passes, it gets pushed to master.

 If it fails, osstest uses the Gitlab API to write a comment to the MR
 about this.  Other metadata such as a request by a committer to retry
 the branch, or priority information, can be handled the same way.

 The selection of outstanding branches uses some kind of heuristic to
 try to collect a combination which (a) bites of a good chunk of the
 outstanding work and (b) is likely to pass.

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

             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 21:39 Ian Jackson [this message]
2019-07-15  9:48 ` George Dunlap

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23848.65064.511423.772481@mariner.uk.xensource.com \
    --to=ian.jackson@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Xen-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/xen-devel/0 xen-devel/git/0.git
	git clone --mirror https://lore.kernel.org/xen-devel/1 xen-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 xen-devel xen-devel/ https://lore.kernel.org/xen-devel \
		xen-devel@lists.xenproject.org xen-devel@archiver.kernel.org
	public-inbox-index xen-devel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.xenproject.lists.xen-devel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox