Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions .github/workflows/bot_build.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
name: Bot build script

on:
pull_request:
branches: [ "main" ]

jobs:
check_symlinks:
runs-on: ubuntu-latest

steps:
- name: Checkout repo
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1

- name: Git clone software-layer
run: git clone https://github.com/EESSI/software-layer.git

- name: Run symlink commands
run: |
set -e

for file in $(ls software-layer | egrep -v 'easystacks|LICENSE|README.md|^bot'); do
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if @casparvl had the same idea in https://gitlab.com/eessi/support/-/work_items/241, but I would basically run it in the exact same way as the one in software-layer:

  • clone the software-layer repo
  • clone software-layer-scripts in a subdir of software-layer
  • run the symlinks commands as in software-layer's bot/build.sh script (i.e. with ls software-layer-scripts on this line)

This should ensure that the ln commands in software-layer always work. By having the same check on both sides, no duplicates can be introduced on either side.

ln -s software-layer/${file}
done

for file in $(ls software-layer/bot | grep -v '^build.sh'); do
ln -s ../software-layer/bot/${file} bot/${file}
done