-
Notifications
You must be signed in to change notification settings - Fork 4
ACS-4456 Add reusable workflow for basic Maven build and release #225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fa4ba97
Added some changes to make the workflow more generic, by allowing the consumer of the workflow to specify if they want the release to be happening automatically or manually induced via Tests I've run with several input permutations:Test #1 default input: https://github.com/Alfresco/alfresco-tas-email/actions/runs/4065941509/jobs/7001345703 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Great stuff!
4c9573e
Adding a reusable workflow to match the most common Travis workflow we have at the moment, which seems to simply be build (sometimes with tests) -> release.
Example of usage: https://github.com/Alfresco/alfresco-tas-ftp-test/actions/runs/4016617042
Note: this is a work in progress, and will be merged only once most if not all repositories that should use such a basic workflow have been tested and therefore the workflow has become at least abstract enough to be utilized properly within all ACS repositories with similar, simple workflows.