I’ve having issues with updating my website. After I make a new commit on my jekyll website and let gitlab-ci build my website and upload the public folder it still seems to not update my website to the latest version.
Is gitlab pages having issues these last few days? Or is it just me?
PS: The weird thing is the gitlab pages subdomain page is up to date with the latest versoin but my domain name I hosted is still on older versions? I’ve updated this yesterday and it still the old version.
No one?
Experiencing the same issue: custom domain doesn’t update while Gitlab’s does. “last-modified” response header for my custom domain is stuck in the past while it’s recent for *.gitlab.io. Tried multiple things like retrigger pipeline, readd custom domain, readd pages without any luck (in fact it’s weird that when I remove pages/custom domain, I can still access the website). Contacted support, will see how it goes.
Yeah. Please let me know if they have any more information or reason why this is happening.
It is driving me crazy.
Hi did you find a solution for the issue by any chance? I’m currently having a similar issue the only difference is I’m hosting a plain HTML page with a custom domain.
Having the same issue.
…and let gitlab-ci build my website and upload the public folder it still seems to not update my website to the latest version.
I’m seeing the same thing—no update in several days.
Perhaps this is a jekyll problem. An obscure meta flag? idk. Anyway, I’m completely stuck. Maybe time to abandon ship as this is unworkable and basic and there’s nothing in the FAQs.
I have a Jekyll flag that works OK via pages, so I doubt it’s that.
I’m seeing the same thing—no update in several days.
My mistake. Deployment is working correctly. There was a subtle change in the pipeline to rename from pages: to pages:pages:, which apparently doesn’t comply with what Gitlab expects. Once I switched back to just pages:, everything worked as expected.
Just regenerate from scratch add file> .gitlab-ci.yml > template got success for me !
i have the same issue today
What’s in your .gitlab-ci.yml file for the pages job?
my cicd pretty simple
pages:
stage: deploy
script:
- mkdir .public
- cp -r * .public
- mv .public public
artifacts:
paths:
- public
only:
- main
That looks fine to me.
This is probably a stupid question, but are you sure that it’s not a caching issue in your browser?
i even try on incognito browser, issue still remain
Hi, is there any update for this thread? I am experiencing the same issue my gitlab io page (no personal domain used) is not updated after successful pages job.
Also I can verify my artifacts generated in public is updated and I can view the updated content via https://<demo>.gitlab.io/-/<project>/-/jobs/<job_id>/artifacts/public/index.html but not able to see the latest content via https://<demo>.gitlab.io/-/<project>
Also I tried incognito and it is still not working
Update: turned out it is due to my gitlab ci job name is not explicit pages hence gitlab ci not pick it up with pages:deploy
Thank you, this was the key to my problem! For some reason I had renamed pages: to dist: a few commits ago and forgot to check if that broke anything.
It does not work for me now, the target is still “pages”. no changes in that area. Anyone else facing this issue?
I’m also experiencing this problem.
This is my .gitlab-ci.yml:
pages:
image: node:latest
stage: deploy
script:
- npm ci
- npm run build
- mv build public
artifacts:
paths:
- public
only:
- master
I also tried with pages:deploy as I understood from a suggestion, but that didn’t make a difference. Also not in private mode. The pages site just doesn’t seem to update. But the pipeline is successful and I see the updated code on Gitlab.
But I also see weirdness in the Gitlab pipeline Jobs, because in my last deploy I see a pages job and a pages:deploy job, while in that deploy I already removed the pages:deploy job and changed it to just pages. So there seems to be something weird going on with the caching.
Btw the last lines of my pages job output is:
Run npm run preview to preview your production build locally.
> Using @sveltejs/adapter-static
Wrote site to "build"
✔ done
✓ built in 6.29s
$ mv build public
Uploading artifacts for successful job 00:06
Uploading artifacts...
public: found 146 matching artifact files and directories
WARNING: Upload request redirected location=https://gitlab.com/api/v4/jobs/<my-id-not-sharing>/artifacts?artifact_format=zip&artifact_type=archive new-url=https://gitlab.com
WARNING: Retrying... context=artifacts-uploader error=request redirected
Uploading artifacts as "archive" to coordinator... 201 Created id=<my-id-not-sharing> responseStatus=201 Created token=65_k4LSz
Cleaning up project directory and file based variables 00:00
Job succeeded
And btw, when I download the artifacts file, it also contains my changes, which I don’t see back on the Gitlab pages site.