DPDK CI discussions
 help / color / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 292] Allow members to stop future jobs from running on their host from the dashboard
Date: Mon, 24 Jun 2019 18:33:52 +0000
Message-ID: <bug-292-149@http.bugs.dpdk.org/> (raw)


            Bug ID: 292
           Summary: Allow members to stop future jobs from running on
                    their host from the dashboard
           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: ---

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.

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-292-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 \
	public-inbox-index ci

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox