Pages successfully deployed but the opening the link presents a 404
Apologies I'm not too well versed with Github pages so may have made some obvious errors. I'm trying to push a html report from an Appium test run onto our orgs private pages repo. The folder I'm trying to upload looks as follows (it's a .tar):
As mentioned though I'm just getting 404 not found when trying to access the link. I'll post just the reporting job below:
report job YAML
reporting:
if: always()
needs: test
name: Put report onto GH pages
permissions:
pages: write # to deploy to Pages
id-token: write # to verify the deployment originates from an appropriate source
environment:
name: mobile-test-reports
url: ${{ steps.deployment.outputs.page_url }}ios-report
runs-on: ubuntu-latest
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/[email protected]
- name: Display URL to report
run: echo '## [Test Report] ('${{ steps.deployment.outputs.page_url }}')' >> $GITHUB_STEP_SUMMARY
Output from job status
Run actions/[email protected]
Fetching artifact metadata for "github-pages" in this workflow run
Found 1 artifact(s***
Creating Pages deployment with payload:
{
"artifact_id": 1952676[30](https://github.com/global-digital-dev/guacamole/actions/runs/10939969440/job/30371396627#step:2:31)6,
"pages_build_version": "843e4097e3d59d74c555e6a753713046e11743b7",
"oidc_token": "***"
}
Created deployment for 843e4097e3d59d74c555e6a753713046e11743b7, ID: 843e4097e3d59d74c555e6a753713046e11743b7
Getting Pages deployment status...
Reported success!
Thanks in advance for the help and let me know if you need more info
@AhmadMahmoodRana nice try
I have also started getting 404 with another action, it stopped working a few weeks ago.
I think it is a change on GHs end, see https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site And this part: "Commits pushed by a GitHub Actions workflow that uses the GITHUB_TOKEN do not trigger a GitHub Pages build."
@tking16 There's not enough visibility into the previous jobs, how you collect the data for the artifact, how you then use that for deployment etc. — you may need to make a minimal repro case in a public repository if you need help with this; generally there's no reason this should not be working. Try adding /_reports/ at the end of your 404 deployment URL etc., it might be just path issue or something as trivial. Also check you're not compressing the stuff twice, as artifact actions will do that for you so if you tar that yourself too, you may need to untar that before doing anything useful for web deployment.