Difference between revisions of "Infra/tickets"
From fd.io
(→Broken) |
(→Broken) |
||
Line 32: | Line 32: | ||
Broken: | Broken: | ||
− | <strike> | + | # <strike> [https://rt.linuxfoundation.org/Ticket/Display.html?id=22117 DPDK bundles incorrectly put up on nexus] </strike> |
# [https://rt.linuxfoundation.org/Ticket/Display.html?id=18811 Unable to open log and report html files in jenkins] | # [https://rt.linuxfoundation.org/Ticket/Display.html?id=18811 Unable to open log and report html files in jenkins] | ||
# [https://rt.linuxfoundation.org/Ticket/Display.html?id=22030 jenkins job csit-vpp-master-verify-weekly - taqgging still not working] | # [https://rt.linuxfoundation.org/Ticket/Display.html?id=22030 jenkins job csit-vpp-master-verify-weekly - taqgging still not working] |
Revision as of 14:53, 6 May 2016
Contents
Intro
This page is to try to provide some community visibility into infra tickets while we wait to get general visibility. It intrinsically cannot be realtime ( :( ).
Prioritization Heuristic
The initial proposed Prioritization Heuristic is to bucket things into categories (in descending order of priority):
- Blocking - Things which are blocking verify/merge for a project
- New Projects: Provision new project resources, should happen by Monday after their approval
- Release - Things needed to facilitate immanent release
- Broken - Fixing other breakage
- Jira Workflow Changes
- New Services Requested - requests for new services, like OpenGrok
This is a first attempt, and should evolve and improve over time with community input
Tickets
Blocking
New Projects
Release
Broken
Broken:
-
DPDK bundles incorrectly put up on nexus - Unable to open log and report html files in jenkins
- jenkins job csit-vpp-master-verify-weekly - taqgging still not working