From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 181] Don't run doc patches if only the doc folder has been changed
Date: Fri, 04 Jan 2019 16:14:33 +0000 [thread overview]
Message-ID: <bug-181-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=181
Bug ID: 181
Summary: Don't run doc patches if only the doc folder has been
changed
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
Currently we ignore the doc folder when applying patches to avoid apply errors
and in case a doc labeled series contains code changes.
We can also then check if any other files were modified after applying the
patch to determine whether to run performance testing on that series. (If only
the doc folder was modified, then don't run the performance tests.)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-01-04 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 16:14 bugzilla [this message]
2019-01-09 14:17 ` bugzilla
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-181-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).