Hey Everyone! The cutoff for the next beta is just around the corner (Monday, March 21)! In order to meet this cutoff, please pay attention to the CI reports [0] on your branches and address failures on your branch when they arise.
To avoid wasting CI test time on branches with known errors, we will be introducing a way to skip CI runs for those feature branches. If your branch has a unique failure, or has not pulled in an updated master containing fixes for known CI bugs, a bug will be opened against your branch with the "block-ci-testing" tag[1]. Branches with "block-ci-testing" bugs in a non-Fix Committed state will not be run through CI. For example, master is currently blocked because of bug #1558158[2]. Once that bug is fixed, your branch will not be tested until you pull in an updated version of master which contains that fix. Feature branches without pre-existing "block-ci-testing" bugs are being tested until that bug is marked as Fix Released. Once you have brought in the latest master, and / or addressed the unique-to-your-branch bug, set the "block-ci-testing" bug against your branch to Fix Committed to signal that your branch is ready for CI testing. Please let me know if you have any questions. Thanks! -Cheryl [0] http://reports.vapour.ws/releases [1] https://bugs.launchpad.net/juju-core/+bugs/?field.tag=block-ci-testing [2] https://bugs.launchpad.net/juju-core/+bug/1558158
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
