You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An example for this is if the Github workflow has pre-commits, tests etc. and multiple trigger points on tags and manual run, while the CirrusCI is complementing the CD by building for arm/mac-arm architectures. There it would make sense for the GH action to be in charge of triggering CirrusCI workflows.
The text was updated successfully, but these errors were encountered:
It would be nice if it was possible to join somehow both GitHub Actions and CirrusCI, like you create a task that has dependencies in CirrusCI and GitHub Actions, so it waits all those to finish, and then it runs - and then it would be possible to get an artifact that was built in GitHub Actions to the CirrusCI pipeline and use it.
Actually I do have something that I am slowly working my way through LecrisUT/cirrusci-action. I would appreciate some comments on the interface, common packages, etc. It is based on the CircleCI action. Also if there are some CirrusCI resources or mocking that can be done for the tests, that would be great.
Description
An example for this is if the Github workflow has pre-commits, tests etc. and multiple trigger points on tags and manual run, while the CirrusCI is complementing the CD by building for arm/mac-arm architectures. There it would make sense for the GH action to be in charge of triggering CirrusCI workflows.
The text was updated successfully, but these errors were encountered: