From 2357f66a20ac433003cc9703df3e1b57c46d4fe5 Mon Sep 17 00:00:00 2001 From: Ralph Bean Date: May 04 2016 20:11:27 +0000 Subject: Diagram on the life of a package update. --- diff --git a/ditaa/README.rst b/ditaa/README.rst new file mode 100644 index 0000000..008ef40 --- /dev/null +++ b/ditaa/README.rst @@ -0,0 +1,7 @@ +These are diagrams kept in a text format for 'ditaa'. + +To render them, install ditaa and run:: + + $ ditaa FILENAME.txt + +and it will produce a file named ``FILENAME.png``. diff --git a/ditaa/life-of-a-package-update-current.txt b/ditaa/life-of-a-package-update-current.txt new file mode 100644 index 0000000..8b42e91 --- /dev/null +++ b/ditaa/life-of-a-package-update-current.txt @@ -0,0 +1,131 @@ +The life of a package update, as things currently stand. +This does not include how we handle Alphas or Betas. +Also does not include buildroot regeneration in koji. + + +------------------------------------------+ + | upstream releases a tarball | + +------------------------------------------+ + | + V + +------------------------------------------+ + | release-monitoring.org notices | + | via a cronjob | + +------------------------------------------+ + | + V + +------------------------------------------+ + | the-new-hotness service responds, | +----------+ + | files a bug, and kicks off a scratch |----------+------->| bugzilla | + | build of a hypothetical package update | | | {s}| + +------------------------------------------+ | +----------+ + | | + V | + +------------------------------------------+ | + | koji performs that scratch build | | + +------------------------------------------+ | + | | + V | + +------------------------------------------+ | + | the-new-hotness service responds, | | + | follows up on the bug as to whether |----------+ + | or not the build completed. | + +------------------------------------------+ + : + | + V + +------------------------------------------+ + | we wait for a human packager to read | + | their email and react to RHBZ | + +------------------------------------------+ + : + | + V + +------------------------------------------+ + | a packager applies patch in dist-git | + +------------------------------------------+ + : + | + V + +------------------------------------------+ + | a packager kicks off a rawhide build |---------------------------+ + +-------+-------------------+--------------+ | + | | | + +-------+ +--------+ | + | : | + | | | + | V V + | +------------------------------+ +------------------------------+ + | | a packager merges dist-git | | automatically, taskotron | + | | branches and kicks off koji |->| performs a subset of checks |--+ + | | builds for released branches | | on those builds | | + | | at their discretion | +------------------------------+ | + | +------------------------------+ | + | : | + | | | + | V | + | +------------------------------+ | + | | a human packager waits | | + | +------------------------------+ | + | : | + | | stores | + | V results | + | +------------------------------+ | + | | a human packager creates | | + | | bodhi updates for those | | + | | builds | | + | +------------------------------+ | + | : | + | | | + V V | ++---------------------------+ +------------------------------+ +------------------------------+ | +| autosigner signs all rpm | | human possibly manually | | taskotron automatically | | +| builds | | patches and rebuilds |->| runs some checks on the |--+ +| | | dependencies and bundles | | update as a whole | | +| | | them in that bodhi update. | +------------------------------+ | ++---------------------------+ +------------------------------+ | + | : | + | | | + V V | ++---------------------------+ +------------------------------+ V +| daily cronjob of pungi4 | | bodhi admins run tool to | automatically checks with +-----------+ +| rebuilds and syncs out | | create updates-testing yum |----------------------------->| resultsdb | +| the rawhide repo | | repos and sync those out to | | {s}| ++---------------------------+ | the mirrors. | +-----------+ + | signing is the main blocker | ^ + | to automating this | | + | bodhi here also updates koji | | + | tags and bugzilla bugs | | + | | | + +------------------------------+ | + : | + | | + V | + +------------------------------+ | + | end powerusers install those | | + | from the testing repos, and | | + | provide feedback to bodhi. | | + +------------------------------+ | + | : | + | | | + V V | + +----------------------------------+ | + | the update is promoted to stable | | + | either automatically on feedback | | + | or on request of the packager. | | + +----------------------------------+ | + : confers again with | + | +-------------------+ + V | + +----------------------------------+ | + | rpms are signed manually, sigul | | + +----------------------------------+ | + : | + | | + V | + +----------------------------------+ | +------+ +----------+ + | bodhi admins run tool to create |--------------+ +->| koji | +->| bugzilla | + | updates yum repos and sync those | adjusts koji tags | | {s}| | | {s}| + | out to the mirrors. |-------------------+ +------+ | +----------+ + | | updates bugzilla bugs | + | |-------------------------------+ + +----------------------------------+