Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE]: unsupported extension name extensions.worktreeconfig #1115

Closed
2 tasks done
pascalgulikers opened this issue Apr 22, 2024 · 6 comments
Closed
2 tasks done

[ISSUE]: unsupported extension name extensions.worktreeconfig #1115

pascalgulikers opened this issue Apr 22, 2024 · 6 comments

Comments

@pascalgulikers
Copy link

Prerequisites

  • I have written a descriptive issue title
  • I have searched issues to ensure it has not already been reported

GitVersion package

GitHub Actions

What are you seeing?

unsupported extension name extensions.worktreeconfig
Looks like issue #1090 is suddenly back

What is expected?

No error

Steps to Reproduce

The error is suddenly back:

Run actions/checkout@v4
with:
fetch-depth: 0
fetch-tags: true
repository: /
token: ***
ssh-strict: true
persist-credentials: true
clean: true
sparse-checkout-cone-mode: true
show-progress: true
lfs: false
submodules: false
set-safe-directory: true

/usr/bin/git version
git version 2.34.1

Run gittools/actions/gitversion/setup@v1
with:
versionSpec: 5.x
preferLatestVersion: true
includePrerelease: false
ignoreFailedSources: false

Run gittools/actions/gitversion/execute@v1
with:
disableShallowCloneCheck: true
useConfigFile: false
disableCache: false
disableNormalization: false
configFilePath: GitVersion.yml
updateAssemblyInfo: false
Resulting in:

INFO [04/22/24 15:49:41:90] Working directory: /home/ubuntu/_work//
unsupported extension name extensions.worktreeconfig
INFO [04/22/24 15:49:41:95] Done writing
Error: Error: The process '/home/ubuntu/_work/_tool/GitVersion.Tool/5.12.0/x64/dotnet-gitversion' failed with exit code 1

Output log or link to your CI build (if appropriate).

No response

@mikeclayton
Copy link

Same issue here - I had an actions workflow that worked fine today (22/04/2024) at 15:11 (GMT + 1), and then started failing with the same error - "unsupported extension name extensions.worktreeconfig" at 15:28 for no obvious reason.

The original error came from a custom workflow we've written that calls the dotnet-gitversion tool v5.10.3 (and not changed recently), but I can reproduce it with the latest version (v5.12.0) and with the gittools actions in a vanilla config:

    steps:
      - uses: actions/checkout@v4
        with:
          # needed for gitversion to work
          fetch-depth: 0

      - name: gitversion setup
        uses: gittools/actions/gitversion/[email protected]
        with:
          versionSpec: 5.x

      - name: gitversion execute
        uses: gittools/actions/gitversion/[email protected]

The result is:

... snip ...
Command: git -C /opt/actions-runner/_work/devops-github-runners/devops-github-runners rev-parse --is-shallow-repository
... snip ...
unsupported extension name extensions.worktreeconfig
... snip ...
Error: Error: The process '/opt/actions-runner/_work/_tool/GitVersion.Tool/5.12.0/x64/dotnet-gitversion' failed with exit code 1

(full "debug" logs available if it's useful, but I can't anonymise them right now)

@mikeclayton
Copy link

Update: If I ssh onto my self-hosted ubuntu 22.04 github runner and run the dotnet-gitversion command manually I get the same issue:

mike.clayton@ghrunner01:/opt/actions-runner/_work/devops-github-runners/devops-github-runners$ dotnet-gitversion /opt/actions-runner/_work/devops-github-runners/devops-github-runners /output json /output buildserver
INFO [04/22/24 18:38:51:93] Working directory: /opt/actions-runner/_work/devops-github-runners/devops-github-runners
unsupported extension name extensions.worktreeconfig
INFO [04/22/24 18:38:51:97] Done writing

@pascalgulikers
Copy link
Author

pascalgulikers commented Apr 22, 2024

Temporary workaround is placing this between the setup and execute action:

- name: Temporary workaround for GitVersion
  continue-on-error: true
  shell: bash
  run: |
    git config --unset-all extensions.worktreeconfig
    # See https://github.com/GitTools/actions/issues/1115

EDIT: added continue-on-error: true since the command is throwing errorcode 5 since 2024-04-26. Looks like this issue only occurred between 2024-04-22 and 2024-04-26..

@mikeclayton
Copy link

@pascalgulikers - just found the same workaround :-).

I put it straight after the actions/checkout@v4 and before both gitversion steps, which works as well.

@mikeclayton
Copy link

Temporary workaround is placing this between the setup and execute action:

- name: Temporary workaround for GitVersion
  continue-on-error: true
  shell: bash
  run: |
    git config --unset-all extensions.worktreeconfig
    # See https://github.com/GitTools/actions/issues/1115

EDIT: added continue-on-error: true since the command is throwing errorcode 5 since 2024-04-26. Looks like this issue only occurred between 2024-04-22 and 2024-04-26..

This works too, if you don't want to disable error checking in the entire step:

        if (git config --get extensions.worktreeconfig > /dev/null); then
            git config --unset-all extensions.worktreeconfig
        fi

arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
arturcic added a commit to arturcic/gittools-actions that referenced this issue Jul 9, 2024
@arturcic
Copy link
Member

arturcic commented Jul 9, 2024

@arturcic arturcic closed this as completed Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants