add generic bazel toolchain job

[odra]

Changes

• adds an autosd workflow to build a Bazel target with a specific config (I think we can be turned in a generic "platform build" job)

Sample Usage

name: AutoSD Build
on:
 workflow_dispatch:
 pull_request_target:
   types: [opened, reopened, synchronize]
 merge_group:
   types: [checks_requested]
jobs:
 autosd-build:
   uses: odra/cicd-workflows/.github/workflows/autosd-build.yml@autosd-bazel-ci
   permissions:
     contents: read
     pull-requests: read
   strategy:
     matrix:
       config:
         - autosd-x86_64
   with:
     bazel-target: '//score/...'
     bazel-config: ${{ matrix.config }}
     bazel-disk-cache: ${{ github.workflow }}-${{ github.job }}-${{ matrix.config }}

It still requires modules to register toolchains as:

module(name = "mymodule")

bazel_dep(name = "score_bazel_cpp_toolchains", version = "0.5.1")

bazel_dep(name = "platforms", version = "1.0.0")
bazel_dep(name = "score_bazel_platforms", version = "0.1.2")

gcc = use_extension("@score_bazel_cpp_toolchains//extensions:gcc.bzl", "gcc")

gcc.toolchain(
    name = "score_autosd10_x86_64_toolchain",
    runtime_ecosystem = "autosd10",
    target_cpu = "x86_64",
    target_os = "linux",
    use_default_package = True,
)

use_repo(
    gcc,
    "score_autosd10_x86_64_toolchain"
)

[AlexanderLanin]

I'm not sure what this is? Maybe this should be setup-bazel? As wrapping a simple bazel run doesnt seem worth it. It adds more complexity than just running it on command line.

[odra]

I started working on an autosd one but It felt to simple to be autosd specific. I could still try to force a config or container image to be autosd specific, instead of the generic one, if that makes sense.

[AlexanderLanin]

Where would you like to use this? Sorry, I dont get it yet. Workflow is called toolchain test. It sets up qemu. And the name is target-build. Thats three mismatching things :D

[AlexanderLanin]

@odra sorry this was stuck so long.

Should we merge this with https://github.com/eclipse-score/cicd-workflows/blob/main/.github/workflows/qnx-build.yml?
My idea would be adding flags like "qemu" and "qnx", which will run the respective step on demand.

[odra]

so was trying to create a job to run builds that use autosd's toolchain for different modules to use, let me update this patch with a new proposal (which I have conflicting opinions about its implementation)

[odra]

@AlexanderLanin I created a new "autosd-build.yml" workflow, which was my original intention. An example of the workflow usage can be found here: https://github.com/eclipse-score-fork-rh/rh-sample-autosd-toolchain/blob/main/.github/workflows/build-autosd.yml.

It still requires modules to setup the toolchain in their MODULE.bazel files but it "injects" a bazelrc file with a specific config.

My motivation is that I wanted to add autosd toolchain usage to N modules but I didn't want to "copy and paste" the same source code everywhere.

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.