actions / actions/deploy-pages
Invalid artifact URL with v1.2.9
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 953
- Forks
- 143
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Hi there
I saw that the invalid artifact url fix was backported into v1, however I'm still getting the Invalid artifact url message.
I'm using Github Enterprise Server 3.8.6
Could this be an error on my side, or some particular quirk with the 3.8 version?
Thanks in advance!
Run actions/deploy-pages@v1.2.9
with:
emit_telemetry: false
token: ***
timeout: 600000
error_count: 10
reporting_interval: 5000
artifact_name: github-pages
preview: false
Artifact exchange URL: https://***.com/_services/pipelines/z0Rk2ueWXp3kDK4JaspYI3r0zHdPc48yPbeq5Lx4ZyeInmcFuS/_apis/pipelines/workflows/2827897/artifacts?api-version=6.0-preview
Creating Pages deployment with payload:
{
"artifact_url": "https://**.com/_services/pipelines/z0Rk2ueWXp3kDK4JaspYI3r0zHdPc48yPbeq5Lx4ZyeInmcFuS/_apis/pipelines/1/runs/22/artifacts?artifactName=github-pages&%24expand=SignedContent",
"pages_build_version": "6e942b73c5261ea98bb46cd25574c13a306cb367",
"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: Invalid artifact url
at /runner/_work/_actions/actions/deploy-pages/v1.2.9/webpack:/deploy-pages/node_modules/@octokit/request/dist-node/index.js:86:1
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at createPagesDeployment (/runner/_work/_actions/actions/deploy-pages/v1.2.9/webpack:/deploy-pages/src/api-client.js:116:1)
at Deployment.create (/runner/_work/_actions/actions/deploy-pages/v1.2.9/webpack:/deploy-pages/src/deployment.js:59:1)
at main (/runner/_work/_actions/actions/deploy-pages/v1.2.9/webpack:/deploy-pages/src/index.js:30:1)
Error: Error: Failed to create deployment (status: 400) with build version 6e942b73c5261ea98bb46cd25574c13a306cb367. Responded with: Invalid artifact url
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at src/api-client.js:116, then follow the deployment flow through src/deployment.js:59 and src/index.js:30. Reproduce the failure on GitHub Enterprise Server 3.8.6 with actions/deploy-pages@v1.2.9 and compare the shown artifact URL with the backported fix. Done means the artifact URL is accepted or the incompatibility and required workaround are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100