Thanks to visit codestin.com
Credit goes to github.com

Skip to content

refactor GitHub build actions to reduce duplication #717

@mmguero

Description

@mmguero

See these workflows?

There's obviously a lot of duplication there. It would really be smart if we were to take about 95% of those and combine them into one action or a reusable action or something so we don't have all the duplication.

Some notes:

  • The reason I said 95% instead of 100% is because the actions to build the ISOs/raspi image, the ones related to handling issues, etc. will remain unique. We're just talking about the ones for building/pushing the non-ISO docker images
  • Each of those workflows has different triggers (e.g., so the zeek image gets built when the zeek code changes, etc.) so we'd want to somehow preserve that functionality so that we don't build everything when we only need to build one image
  • this documentation probably will need a little tweaking? Also we'd want to look closely at the docs and see if we reference any files that might be going away

Metadata

Metadata

Assignees

Labels

buildFor issues related to compilation/buildingdevelopmentdealing with the development process itselfenhancementNew feature or requestgithubDealing with Malcolm's GitHub repository

Projects

Status

Released

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions