#5636: Use a staging area for test composes and safe practices when naming them

Fedora Release Engineering rel-eng at fedoraproject.org
Tue Oct 15 10:28:58 UTC 2013


#5636: Use a staging area for test composes and safe practices when naming them
------------------------------+-----------------------
  Reporter:  kparal           |      Owner:  rel-eng@…
      Type:  task             |     Status:  reopened
 Milestone:  Fedora 19 Final  |  Component:  other
Resolution:                   |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+-----------------------
Changes (by kparal):

 * resolution:  fixed =>
 * status:  closed => reopened


Comment:

 Dennis, status shuffling is not helpful. Could you please clarify what the
 current (new) practice is and what is preventing you from improving it?
 Thanks.

 I have to confirm I saw some empty dirs created in advance for some of the
 previous composes, so the problem is really not fully fixed yet. Some of
 our QA processes require manual intervention and it's very problematic and
 inefficient for us if we can't rely on compose consistency. Andre Robatino
 creates deltaisos, zsync files and wiki test matrices for us, and I'm very
 grateful for that. We would love to automate that, but for that we need
 some automation (or at least safe practices) on your side. We need staging
 areas, we need stable naming policy and we need fedmsg notifications. Or
 at least some of that.

 I would be willing to devote some of my time to help you improve your
 releng scripts in these regards. As a consequence we would save a lot of
 time in our QA tasks. Where can I find the scripts, please?

 As a side note, I have a couple of wishes. If a compose (say TC3) fails to
 compose:
 a) could we not make the compose public? There's no reason for it, it just
 wastes the bandwidth for infra and for all people syncing it. Just delete
 it and start again.
 b) could the next compose be again named TC3? (that implies a) of course)

 Thanks for info.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5636#comment:12>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project


More information about the rel-eng mailing list