I just started working on a project that was created with Nuxt and a CI pipeline using Cirlce CI that detects changes in the repository and upload files via SFTP to DreamHost.
We also have a netlify cms setup that sends .md files to the repository that are read and displayed on the page.
Now to the weird part.
Whenever I change something in the repository (push from my local repo, or use the cms) the changes appear on the site as they should. They correctly trigger a rebuild within circle.ci, which completes successfully and when I look at the live site they are present.
However when checking back a couple hours later they have dissapeared. The changes are still present in the github repository, but they are inconsistent with the state of the live page which has reverted to its previous state.
I can manually trigger rebuilds within circle.ci but the same thing occurs, i can see the changes for some time, then they dissapear.
I don't even know where to start looking for the problemect.
Any leads, or well aimed shots in the dark would be greatly appreciated, many thanks!
Edit.
I think this might be relevant: Every 12 hours we trigger a rebuild on the page, mostly to check for outdated content and deliver freshly rendered pages. When i checked the site index under the _nuxt pages, i see the following:
There are older versions of the scripts that are correct and new versions that are incorrect, those new versions are then referenced, resulting in the content being false.
Why are the automatic rebuilds 'overwriting' the old build?
Where can i find out more about those triggers?
OP's issue was mainly coming from the fact that the app was pulling from the wrong branch.
Fixing that one, did it.
Related
Let me start by saying that I'm very new to this. I have little to no technical background, so this might just be a simple problem, or I did something I shouldn't have done. It's my first time using the command line and dealing with static pages.
I recently deployed my Hugo site to GitHub pages. I only changed the configuration file, and that's it. (I followed this and this.)
The site is now live at https://USERNAME.github.io/. It's still showing the content of my chosen theme.
A few hours after deploying, I edited some of the local markdown files and pushed the changes. However, the changes aren't reflected on the site.
Now that I realize it, GitHub only displays my site's "public" folder and not all of the files in my local folder.
So, my question is, how can I change and update my site content locally and make sure that the changes are shown on the live site?
Any help is appreciated. Thanks so much!
I see when I pushed a text file to github it reflects immediately but when I am pushing a binary file it takes a minute or so to reflect back. I am using GitHub's API to push my changes. Is there any official docs which explains this?
Any help will be appreciated.
I tried searching and found out like GitHub is not very good with very files but didn't find anything which can explain this behaviour.
This probably has nothing to do with text files vs. binary files.
GitHub Pages sites are build using background jobs. Depending on how busy the Pages servers are, how many jobs are ahead of yours, etc. you may see a build happen very quickly, or you may have to wait a while.
I have a github project and I am using Github pages.
I can see the newest code changes on the gh-pages branch on my github account(web-interface) but the same changes are not visible on the Github page.
Note : I have given it more than a day to assuming that it will take some time for the actual deployment. In fact github.org mentions that it might take upto half an hour. So I am not sure why it is taking so long.
The issue was because of a browser cache. Clear your browser cache and you should see the changes after half an hour.
Have you checked your email? There could be errors in your code which prevent page builds. See https://help.github.com/categories/github-pages-troubleshooting/ for more.
I've been recently trying out Jekyll. Everything works fine. I've deployed my initial site successfully but, after then while I'm trying to commit and push everything looks good and reflected in the repository page, but on the main pages.
I'm pushing only the deployment files from the _source folder in the main branch.
UPDATE: The changes are now shown. But, why it takes so much time to do that? Is it normal?
It usually takes up to 10 minutes for the pages to get updated as described here.
Tip: After the first push, it can take up to ten minutes before the content is available.
I'm using Travis-CI with GitHub.
I would like to know if is possible to reset the build number and/or delete the related Travis page.
I tried to delete my repo on GitHub but this is not affecting the related Travis page.
Even if I create a new repo, with the same name of the previous, the build number starts from the previous one, and the builds are linking on 404 on GitHub. I know that isn't a big issue, but I would like to keep consistent all my solution.
Unfortunately we don't have a way to delete repositories or builds. If any private data has been exposed, you can always email us to have the logs stripped.
We are working on a way to archive repositories, which basically means that they'll be hidden until a new build is run, see the issue for more information on that.