Check existing issues
Request
Remote building can sometimes be flaky due to builder availability and infrastructure stability. In most cases, AMD and ARM successfully finish packing. However, plenty of times, S390x and PPC64el take longer to complete, possibly due to runner unavailability. In such cases, it would be better if the artifacts that were successfully built are returned.
The problem it solves
Some of our release workflows rely on remote building (using charmcraft 3.5.3). These workflows tend to be flaky when LP is experiencing extra load. We often need to re-run these workflows multiple times. On almost all runs, the logs indicate that the build succeeded for ARM and AMD. In such cases, if we can get those artifacts and release them, we can probably hold off on S390x and PPC64el builds. This ensures we release the charms to Charmhub faster and reduces the number of retries, easing pressure on LP.
Check existing issues
Request
Remote building can sometimes be flaky due to builder availability and infrastructure stability. In most cases, AMD and ARM successfully finish packing. However, plenty of times, S390x and PPC64el take longer to complete, possibly due to runner unavailability. In such cases, it would be better if the artifacts that were successfully built are returned.
The problem it solves
Some of our release workflows rely on remote building (using
charmcraft 3.5.3). These workflows tend to be flaky when LP is experiencing extra load. We often need to re-run these workflows multiple times. On almost all runs, the logs indicate that the build succeeded for ARM and AMD. In such cases, if we can get those artifacts and release them, we can probably hold off on S390x and PPC64el builds. This ensures we release the charms to Charmhub faster and reduces the number of retries, easing pressure on LP.