Workflow proposal

[nradakovic]

This is a workflow proposal for baselibs. It includes check, nightly and release verification. If approved, needs to be merged over internal mirror.

[FScholPer]

Can we please move that to cicd-workflows (or parts)?!
And whats about https://github.com/eclipse-score/baselibs/pull/29/files?

[nradakovic]

Can we please move that to cicd-workflows (or parts)?! And whats about https://github.com/eclipse-score/baselibs/pull/29/files?

That PR looks outdated. We have helper script set already on main. Not sure why the PR is open.
Regarding moving this stuff to ci-cd, well these are dedicated configurations and targets only for baselibs. I don't see benefit moving them there if we keep workflows in these forms.
My plan would be that we have some sort of setup where I only provide targets and configs while everything else is done by parent script. Like for example:

jobs:
    build_host_x86-64_linux:
        uses:  /path/to/cicd_repo/docker-build.yml
        with:
            targets:
              - "//path/to/target:1"
              - "//path/to/target:2"
            configs:
              - "bl_x86-64_linux"
            options: # for flags
              - "-//path/to/flag"
            exclude_targets:
              - "//path/to/exclude/target:1"

We already had this setup (similar) on PoC but due to time preasure we never migrate it to here. Docker build should provide more options like:

1. docker to use
2. secrets setup (or we keep it inside but then this is only for S-CORE usage. I had some bigger plans with it).
3. caching options.

This PR is small step towards this since to make such workflow (generic one) is not weekend job.