* [dpdk-ci] [Bug 292] Allow members to stop future jobs from running on their host from the dashboard
@ 2019-06-24 18:33 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-06-24 18:33 UTC (permalink / raw)
Bug ID: 292
Summary: Allow members to stop future jobs from running on
their host from the dashboard
Target Milestone: ---
At the moment, I think it is possible for members to log into Jenkins and
disable jobs via the matrix permissions that we have set up.
But it would be nice for this functionality to exist in the dashboard.
Sometimes we have members that are on the system trying to fix issues, while
the CI could be potentially running. Aside from members going on Jenkins,
typically I'll stop the CI for a period of time before putting it back online,
for this maintenance to take place.
This system would need these features:
Some way of notifying that the job has been manually disabled and enabled from
the dashboard (most likely email).
Notify via email every 24 hours to the user who stopped the CI, to remind them
that the job is disabled and should be re-enabled asap.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-24 18:33 [dpdk-ci] [Bug 292] Allow members to stop future jobs from running on their host from the dashboard bugzilla
DPDK CI discussions
Archives are clonable:
git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox