jlse.yaml

name: Run job on JLSE

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on: [push]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: [self-hosted, linux, jlse]
    if: startsWith(github.event.head_commit.message, '[jlse-run]')

    # Steps represent a sequence of tasks that will be executed as part of the job
    defaults:
      run:
        working-directory: run/automake
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2
        with:
          submodules: recursive


      - name: Update subpackages
        run: |
            (cd ../../analysis/spec/ && python setup.py develop --user --no-deps)
            (cd ../../qtree/ && python setup.py develop --user --no-deps)

      - name: Remove previous result.md
        run: |
            rm results/result.md
            touch results/result.md

      - name: Checks
        run: |
            echo $PATH
            pwd
            tail -f tmp &
            /usr/bin/whoami

      - name: Run run/automake/run.sh
        run: ./run.sh

      - name: Publish a summary
        env:
          repo_token: ${{ secrets.GITHUB_TOKEN }}
        run: ./publish.sh

      - name: Commit results
        uses: EndBug/add-and-commit@v4  # You can change this to use a specific version
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Leave this line unchanged
        with:
          add: '.'
          author_name: Actions Runner
          author_email: mail@example.com
          message: '[jlse-results] for `${{github.event.head_commit.message}}`'