Closed usingtechnology closed 1 year ago
@gavinok
Nightly builds would be sufficient. Building on merge to main would cause unnecessary strain on Hyperledger's GitHub actions runner time allotments.
The nightly builds should incorporate the nightly test runs and only build/publish on success. The workflow should only run if there are changes to the repo since the previous run, there is no point in wasting precious runner time. This would be a good enhancement for the nightly tests regardless.
The workflows you want to look at are:
https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/nightly-tests.yml
https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish.yml
nightly
.https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/pythonpublish.yml
Ignore https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish-indy.yml, because we're dropping support for the indy-sdk releases and this workflow will go away.
For developers that require access to bug fixes, we should provide nightly builds (or build on merge to main?) of the ACA-Py images.
Investigate if we can leverage a nightly build in AATH or other testing situations.