From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <bugzilla@dpdk.org>
Received: by dpdk.org (Postfix, from userid 33)
id 73B2B5F27; Tue, 5 Feb 2019 19:14:03 +0100 (CET)
From: bugzilla@dpdk.org
To: ci@dpdk.org
Date: Tue, 05 Feb 2019 18:14:03 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: lab
X-Bugzilla-Component: dashboard
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jplsek@iol.unh.edu
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: ci@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-154-149-rjmOfVfiC5@http.bugs.dpdk.org/>
In-Reply-To: <bug-154-149@http.bugs.dpdk.org/>
References: <bug-154-149@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-ci] [Bug 154] Add a way to select what branch a patchset was
meant for
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
<mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
<mailto:ci-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2019 18:14:03 -0000
https://bugs.dpdk.org/show_bug.cgi?id=3D154
Jeremy Plsek (jplsek@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek@iol.unh.edu) ---
Logged in users can now select which branch/repo a patchset should be appli=
ed
to, and retry building, if an apply error or build error occurs.
Not all branch have been tested to rebuild properly. This may be because we
don't have a job set up yet (we will fix this when it occurs), or the branc=
h is
not meant to be used for applying patchsets, such as tags.
This is essentially a more manual version of bug 166.
--=20
You are receiving this mail because:
You are the assignee for the bug.=