From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 233] Create a way to share artifacts
Date: Tue, 26 Mar 2019 17:45:30 +0000 [thread overview]
Message-ID: <bug-233-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=233
Bug ID: 233
Summary: Create a way to share artifacts
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: Normal
Component: dashboard
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
Currently, artifacts are only accessible to the members who own the
environment.
For easier troubleshooting between members, add a way to create a sharable
link.
The other option is to give the "primary contact" the ability to make all
artifacts public.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-03-26 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 17:45 bugzilla [this message]
2019-08-08 13:07 ` 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-233-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).