[FOLIO-3775] POC to create Composite Github Actions combining steps from current workflows Created: 22/May/23 Updated: 12/Jun/23 Resolved: 12/Jun/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Ankita Sen | Assignee: | Ankita Sen |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 160 |
| Development Team: | FOLIO DevOps |
| RCA Group: | TBD |
| Description |
|
Github Actions allow creation and use of custom actions and as discussions are going on about maintaining the Action workflows - one probable solution is to create a composite action which combines multiple workflow steps within one action to ease maintaining the workflow files. |
| Comments |
| Comment by Ankita Sen [ 12/Jun/23 ] |
|
Created and published a sample composite action build-npm-action Substituted the said action in ui-users github actions workflow to replace the yarn install, build, test steps. It ran all the steps using the actions successfully and the remaining steps can also be added into the action to essentially make the entire workflow run via the said action. This will essentially mean that each repository only maintains a build-npm.yml and build-npm.yml release workflow with all their ENV variables and just call the actions to run the step, thereby making workflow maintenance easier. The actions can be updated and released with latest versions and published in Github Actions Marketplace but can also be kept private only available for the organisation. |
| Comment by Ankita Sen [ 12/Jun/23 ] |
|
See comment section for detailed description |