From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 709] 2021 Epic: Lab operations, maintenance, and community access
Date: Mon, 17 May 2021 21:04:41 +0000 [thread overview]
Message-ID: <bug-709-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=709
Bug ID: 709
Summary: 2021 Epic: Lab operations, maintenance, and community
access
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: UNH infra
Assignee: ci@dpdk.org
Reporter: lylavoie@iol.unh.edu
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Summary: The following work items relate to support community access of the lab
to provide better visibility into lab status, coverage, support, and
operations.
* Q1 Story: Migrate to a template based Jenkins pipeline, that will enable
“sorting” of jobs based on what code was changed by a patch (i.e. documentation
changes won’t trigger performance testing, but would trigger spell checker
run).
* Q1 Story: Update DTS deployments on all bare-metal systems to a more uniform
deployment and configuration.
* Completed Q1 Story: Report patch apply issues as warning to patchworks
(BUG-686).
* Completed Q1 Story: Create a report of test job run times for the tech board.
This is to better allow understanding of time required to complete full test
runs on submitted patches.
* Q2 Story: Pull Jenkins pipelines from a public git, where the community could
make merge requests on the repo to disable, enable, and change the running job.
* Q3 Story: Monitor for and report via email to ci mailing list, when the same
test fails for 5 consecutive patch test runs, where this could indicate a
failure in caused by a bad merge to the base repo or a failure in the test
infrastructure.
* Story: Deliver a blog each quarter on the lab status.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-17 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly 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=bug-709-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).