As a brief summary, here is what we discussed at the XenSummit design session
on CI;
# What is needed to run CI on patches posted to the list:
1. Get a patch series. Determine if it's for Xen or not.
2. determine the base branch (staging, staging-4.13, staging-4.12, etc)
("for-4.14" after a branch) (actually, probably everything should go into
staging first)
3. Apply that patch series to a branch.
4. Push to a git repo (while developing push it somewhere other than the main
repo)
5. Let CI run
6. Add step at the end of the CI run to comment on the ML list (ideally reply
to series on list)
7. Have an opt-out flag.
patchew already pushes to github.com, so we just need to get it to push to
gitlab. So the plan is:
# Plan
- fix current CI loop built failure
- Get an account for patchew on gitlab
- Reconfigure patchew.org to push there instead
- Reconfigure patchew.org to reply to mailing list w/ result
We’d also discussed dropping the “test every commit” script.
Andy said he would volunteer to chase this.
At the most recent community call, Andy recommended we form a working group
with regular meetings to make sure things keep moving forward. Shall we say
biweekly? Any preferences for meeting time / venue?
I also propose we enable issue tracking on gitlab.com/xen-project, at least for
project members, to collect and track this sort of thing. Any objections?
-George
