Job concurrency does not run latest HEAD #26827

stefanbuck · 2021-09-20T13:12:53Z

stefanbuck
Sep 20, 2021

Hi there,

I came across a weird behaviour (at least not as expected) when using the concurrency field. I’m using a fixed concurrency group like concurrency: deploy-request. The related workflow creates a new commit whenever the repository_dispatch event occurs.

If I now trigger two jobs in a row, the first job creates a new commit and the job passes. However, the latter seems to operate on the previous HEAD. The step cat output.log does not contain the value generated by the first job see and git push fails.

As a workaround I run git pull origin main right after the checkout

  <a href="https://github.com/stefanbuck/workflow-concurrency-issue/blob/47bab81cd67f66ff84e18229f572e8d5768fea93/.github/workflows/deployment-request.yaml#L12" target="_blank" rel="noopener nofollow ugc">github.com</a>

stefanbuck/workflow-concurrency-issue/blob/47bab81cd67f66ff84e18229f572e8d5768fea93/.github/workflows/deployment-request.yaml#L12

    
      
          concurrency: deploy-request
          on:
            repository_dispatch:
              types: [deployment_request]
          jobs:
            deploy:
              name: Trigger deploy
              runs-on: ubuntu-latest
              steps:
                - uses: actions/checkout@v2
                - run: git pull origin main
                - run: cat output.log
                - run: cat $GITHUB_EVENT_PATH | jq --raw-output '.client_payload.message' >> output.log
          
          
      - name: Commit 
                  shell: bash
                  run: |
                    git config --global user.email "${{ github.actor }}@users.noreply.github.com" && \
                    git config --global user.name "${{ github.actor }}" && \
                    git add ./output.log && \
                    git commit -m 'Update file' && \

Is this behaviour intentional / by design?

Answered by stefanbuck

Sep 21, 2021

I had another look and turns out that all is needed is to set the default branch as ref to make the checkout action pull the latest HEAD

- uses: actions/checkout@v2
  with: 
    ref: 'main'

From the checkout docs

The branch, tag or SHA to checkout. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event. Otherwise, uses the default branch.

View full answer

stefanbuck · 2021-09-21T06:38:44Z

stefanbuck
Sep 21, 2021
Author

I had another look and turns out that all is needed is to set the default branch as ref to make the checkout action pull the latest HEAD

- uses: actions/checkout@v2
  with: 
    ref: 'main'

From the checkout docs

The branch, tag or SHA to checkout. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event. Otherwise, uses the default branch.

0 replies

MarcelWilson · 2021-09-21T21:00:25Z

MarcelWilson
Sep 21, 2021

I am so glad you posted this. I ran into the same issue thinking the default was to checkout HEAD already.

0 replies

stefanbuck · 2021-09-24T07:54:05Z

stefanbuck
Sep 24, 2021
Author

Great to see that posting the solution was already helpful to you 😀

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Job concurrency does not run latest HEAD #26827

{{title}}

Replies: 3 comments

{{title}}

{{title}}

{{title}}

Select a reply

GitHub Community

Job concurrency does not run latest HEAD #26827

stefanbuck Sep 20, 2021

stefanbuck/workflow-concurrency-issue/blob/47bab81cd67f66ff84e18229f572e8d5768fea93/.github/workflows/deployment-request.yaml#L12

Replies: 3 comments

stefanbuck Sep 21, 2021 Author

MarcelWilson Sep 21, 2021

stefanbuck Sep 24, 2021 Author

stefanbuck
Sep 20, 2021

stefanbuck
Sep 21, 2021
Author

MarcelWilson
Sep 21, 2021

stefanbuck
Sep 24, 2021
Author