-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Description
I keep getting an error using the most barebones configuration, I will skip to the part when the runner finishes installing all dependencies and tries to run the sigstore action.
Run D:\a\_actions\sigstore\gh-action-sigstore-python\v1.2.3/action.py "./build/test.dist/test.exe"
D:\a\_temp\4cbeed94-1ea6-46c1-a605-345eda4ef060.sh: line 1: D:a_actionssigstoregh-action-sigstore-pythonv1.2.3/action.py: No such file or directory
Error: Process completed with exit code 127.
Note: Isn't this D:a_actionssigstoregh-action-sigstore-pythonv1.2.3/action.py path kind of broken? I feel like it's missing a backslash or two. Maybe this action is not suitable for a windows runner?
I tested on this workflow.
name: Python application
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
permissions:
contents: read
id-token: write
jobs:
build:
# Windows is currently the only platform Nuitka action supports apparently?
runs-on: windows-latest
steps:
# Check-out repository
- uses: actions/checkout@v3
# Setup Python
- uses: actions/setup-python@v4
with:
python-version: '3.10'
architecture: 'x64'
- name: Compile to executable
uses: Nuitka/Nuitka-Action@main
with:
nuitka-version: main
script-name: test.py
standalone: true
onefile: false
- name: Sign
uses: sigstore/[email protected]
with:
inputs: build/test.dist/test.exe
# Uploads artifact
- name: Upload Artifact
uses: actions/upload-artifact@v3
with:
name: Windows Build
path: build/test.distNote: The input path seems to be correct, as removing the whole signing step uploads the artifact correctly.
Version
[email protected]
windows-latest
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working