Ticket #421 (closed task: fixed)

Opened 12 years ago

Last modified 12 years ago

autodebathenified packages should go straight into production

Reported by: broder Owned by:
Priority: normal Milestone:
Component: development Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Right now packages built by the autodebathenifier are going into proposed, and require a manual move by a maintainer to move into production. In theory, this is to prevent a successful build of a mysteriously broken package from screwing everything.

I don't think this makes sense. I think we should be moving autodebathenified packages (and especially openafs modules) immediately into production. We don't perform any testing of autodebathenified packages before making the move. Nor do we have any automated infrastructure that does it for us. Nor do we seem to have made any progress at all in writing such an infrastructure.

And I'm not even clear what sort of mysterious bug we're concerned with. To the autodebathenifier has been running as part of the Athena 10/Debathena infrastructure for well over a year now, and it's never failed in a way that caused it to upload a broken package.

All this extra step is serving to do is create more work for debathena-root without any apparent gain, and it causes additional delays for packages that users may be expecting. Therefore, I'm going to plan to reconfigure the autodebathenificator to upload directly to production in a week.

Change History

comment:1 Changed 12 years ago by broder

  • Status changed from new to closed
  • Resolution set to fixed

This is now done; a18r builds go directly into production.

I've also stepped it up to run every 2 hours, instead of every 4.

Note: See TracTickets for help on using tickets.