AIOSAIand@devpulse
b25fc5c2fd
PR #330 fixed the pip bootstrap (ensurepip error-swallowing in setup.sh). With that fix working, the Verify step in windows-test.yml now fails at 'drone: command not found' (exit 127). Root cause: each CI step spawns a fresh shell, so the venv activation from setup.sh doesn't carry to Verify. drone lives at .venv/Scripts/drone.exe which isn't on the default PATH. Fix: prepend 'source .venv/Scripts/activate' to the Verify step so drone is findable. Stacked on PR #330 conceptually — both fixes needed for windows-test.yml to actually pass. Co-Authored-By: @devpulse <devpulse@aipass>
40 lines
827 B
YAML
40 lines
827 B
YAML
name: Windows Setup Test
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
paths:
|
|
- 'setup.sh'
|
|
- 'src/aipass/*/apps/handlers/__init__.py'
|
|
- 'src/aipass/drone/cli.py'
|
|
- 'pyproject.toml'
|
|
pull_request:
|
|
paths:
|
|
- 'setup.sh'
|
|
- 'src/aipass/*/apps/handlers/__init__.py'
|
|
- 'src/aipass/drone/cli.py'
|
|
- 'pyproject.toml'
|
|
|
|
jobs:
|
|
windows-setup:
|
|
runs-on: windows-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- uses: actions/setup-python@v5
|
|
with:
|
|
python-version: '3.12'
|
|
|
|
- name: Run setup.sh
|
|
shell: bash
|
|
run: bash setup.sh
|
|
|
|
- name: Verify drone CLI
|
|
shell: bash
|
|
run: |
|
|
source .venv/Scripts/activate
|
|
export PYTHONUTF8=1
|
|
drone --version
|
|
drone systems
|
|
drone @seedgo --help
|