Supported platforms and CI

EPICS-env builds the Experimental Physics and Industrial Control System (EPICS) base and modules on six Linux operating systems (OS). Each OS has one continuous integration (CI) workflow in .github/workflows/ that builds and checks the whole environment in a container. Two more workflows lint the Bash sources and publish this book. Every workflow runs on a GitHub Actions ubuntu-latest runner.

Supported operating systems and containers

The supported OS list is the set of OS workflows. README.md shows one status badge for each of them and one for the Linter Run workflow.

Package setup in the OS workflows

Each OS workflow prepares its container in the Install required packages step:

• It installs git, make, sudo, bash, wget, and unzip with apt or dnf. The Rocky 8 workflow runs dnf update first and also installs tree.
• It clones pkg_automation from https://github.com/jeonghanlee and runs pkg_automation.bash -y to install the build dependencies.
• The Rocky 8 workflow then installs python3-pip and libusbx-devel, and installs numpy and nose with pip3.
• The Ubuntu workflows set the time zone to America/Los_Angeles and export LC_CTYPE and LC_ALL as C.UTF-8.

Vendor library build in the OS workflows

Each OS workflow builds the uldaq and open62541 libraries before EPICS-env. The vendor directory is the vendor directory of the installed tree, the value of make print-INSTALL_LOCATION_EPICS followed by /vendor. The workflow first writes configure/RELEASE.local with VENDOR_ULDAQ_PATH set to that directory and OPEN62541_PATH set to a path relative to the opcua configuration. It then clones uldaq-env and open62541-env from https://github.com/jeonghanlee and installs both into the vendor directory.

Both vendor repositories provide conf.rocky10 as an alias of the existing conf.rocky8 configuration recipe. Both names preserve the Red Hat linker settings and installation prefix. Rocky 10 prints each vendor checkout’s commit immediately after cloning it to identify the consumed source.

Build sequence in each OS workflow

The EPICS installation step runs these make targets in order. github.check runs init, patch, vars, conf, check.module-deps, build, and symlinks.

All six OS workflows run the module dependency gate check.module-deps after patching and configuration and before compilation. A failing audit stops the build.

Final checks in each OS workflow

The EPICS Environment Check step runs the same three targets in every OS workflow, after the install:

1. make exist prints the installed tree to depth 2.
2. make check.env fails the job when the installed setEpicsEnv.bash adds a pvxs/bundle path to LD_LIBRARY_PATH, or when it cannot be inspected.
3. make check.deps fails the job on any runpath finding in the installed executables and shared libraries.

Tools and scripts reference lists the exit status of each check.

Workflow triggers and path filters

A paths-ignore filter skips a push only when every changed file matches one of its patterns. A push that changes at least one other file runs the workflow. A pull request runs every workflow that has a pull_request trigger, with no path filter. The push triggers of the OS workflows and Linter Run have no branch or tag filter, so a tag push also runs them; GitHub Actions does not apply path filters to tag pushes.

The workflow file names in the OS filters are paths under .github/workflows/. An OS workflow does not ignore its own file, so a push that changes only one OS workflow file runs that OS workflow and Linter Run.

Linter Run workflow steps

The Linter Run workflow has one job, Lint Code Base:

1. It checks out the full history with fetch-depth: 0 and without stored credentials.
2. It runs super-linter/super-linter@v8.7.0 with VALIDATE_BASH set to true.

The workflow grants no permissions at the top level. The job receives contents: read, packages: read, and statuses: write.

Deploy Docs workflow steps

The Deploy Docs workflow builds this book with mdBook and publishes it to GitHub Pages. It runs in the concurrency group pages and does not cancel a run in progress. It holds contents: read, pages: write, and id-token: write.