workflows: add 1.8 branch container build

[patrick-stephens]

Signed-off-by: Patrick Stephens pat@calyptia.com

After removal of 1.8 build support, this re-introduces a separate workflow to provide a container build for a 1.8 based branch.

---

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

• Example configuration file for the change
• Debug log output from testing the change

• Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

• Attached local packaging test output showing all targets (including any new ones) build.

Documentation

• Documentation required for this feature

Backporting

• Backport to latest stable release.

---

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

[edsiper]

why master and not 1.8 branch ? (just curious)

[patrick-stephens]

why master and not 1.8 branch ? (just curious)

There's no real technical reason, just a philosophical one.

Primarily for simplicity: we have a single source of truth rather than having to merge/duplicate every change across them plus figuring out which workflows should fire (e.g. for PRs) is more straightforward. Initially as well I did not want to touch the workflows for the old branch (1.8) when I started so it made a nice separation.

It also means you do not have to remember to run the workflow on the right branch and we can instigate some protection via environments (e.g. you can only release from a master workflow).

[patrick-stephens]

There are some other issues as well with using the non-default branch: https://devopsjournal.io/blog/2022/08/12/workflows-not-starting

@edsiper @lecaros : in this case we want a new workflow to be available as a manual trigger so it must be on the default branch at least to enable the workflow (even if you then target another branch) - we could then also merge it to 1.8 but that seems pointless when we can do the build regardless.

[lecaros]

Great explanation. Thanks @patrick-stephens!

[lecaros]

can we merge this?

[lecaros]

thanks!