Jekyll Sites are not building

I was working on a new Jekyll project, I pushed it to github and then added it to Netlify and when it deployed, it would not build it as a Jekyll site.

After several attempts to deploy, I selected a seperate working Jekyll project (my main website), and it also deployed without building the site via jekyll. (Just serves the raw html).

This is terrifying as I have several live jekyll projects on Netlify, and I can’t make changes without the pages building wrong now.

Here is the build log from my personal website (every Jekyll project I try deploying has similar log, just doesn’t seem to be detecting Jekyll!):

5:01:04 PM: Build ready to start
5:01:05 PM: build-image version: d84c79427e8f83c1ba17bcdd7b3fe38059376b68
5:01:05 PM: build-image tag: v3.6.1
5:01:05 PM: buildbot version: f8648819b2de8637c0fbd87ac67f86c2856f6ad3
5:01:05 PM: Fetching cached dependencies
5:01:06 PM: Failed to fetch cache, continuing with build
5:01:06 PM: Starting to prepare the repo for build
5:01:06 PM: No cached dependencies found. Cloning fresh repo
5:01:06 PM: git clone GitHub - fevish/embark
5:01:07 PM: Preparing Git Reference refs/heads/master
5:01:09 PM: No build steps found, continuing to publishing
5:01:09 PM: Starting to deploy site from ‘/’
5:01:09 PM: Creating deploy tree
5:01:09 PM: Creating deploy upload records
5:01:09 PM: 30 new files to upload
5:01:09 PM: 0 new functions to upload
5:01:11 PM: Starting post processing
5:01:11 PM: Post processing - HTML
5:01:12 PM: Processing form - Homepage Contact
5:01:12 PM: Detected form fields:
5:01:12 PM: - email
5:01:12 PM: - first-name
5:01:12 PM: - last-name
5:01:12 PM: - message
5:01:12 PM: Finished processing build request in 7.022397776s
5:01:13 PM: Mixed content detected in: /assets/fonts/flaticon/font/flaticon.html
5:01:13 PM: → insecure link urls:
5:01:13 PM: -
5:01:13 PM: Post processing - header rules
5:01:13 PM: Post processing - redirect rules
5:01:13 PM: Post processing done
5:01:14 PM: Site is live :sparkles:

EDIT* Existing Jekyll Projects appear to deploy as Jekyll correctly. This issue only appears to be happening when you create a “New Site from Git” on Netlify.

I think this is your issue: 5:01:09 PM: No build steps found, continuing to publishing

What do you have set for your build configs?

Ah good catch, thank you @EdwardGoomba. My build command and publish dir were blank which is strange as I’ve never had to set build steps manually in the past – Netlify has always automatically recognized Jekyll sites and set my build commands for me, so I wonder if this is a Netlify glitch.

Something that’s strange, even after I set my build commands manually:

Build command: jekyll build
Publish directory: _site

I still had to “Clear cache and deploy site” three times before it actually built. The first two deploys kept showing an exit status 128

9:14:37 AM: Waiting for other deploys from your team to complete
9:14:42 AM: Build ready to start
9:14:44 AM: build-image version: d84c79427e8f83c1ba17bcdd7b3fe38059376b68
9:14:44 AM: build-image tag: v3.6.1
9:14:44 AM: buildbot version: f8648819b2de8637c0fbd87ac67f86c2856f6ad3
9:14:44 AM: Fetching cached dependencies
9:14:44 AM: Starting to download cache of 4.9MB
9:14:44 AM: Finished downloading cache in 159.262942ms
9:14:44 AM: Starting to extract cache
9:14:44 AM: Finished extracting cache in 86.710677ms
9:14:44 AM: Finished fetching cache in 247.32137ms
9:14:44 AM: Starting to prepare the repo for build
9:14:45 AM: Preparing Git Reference refs/heads/master
9:14:46 AM: Error fetching branch: refs/heads/master
9:14:46 AM: Failing build: Failed to prepare repo
9:14:46 AM: Failed during stage 'preparing repo': exit status 128
9:14:46 AM: Finished processing build request in 2.289007788s

Well at least it is working now, but it appears I have to take extra steps to deploy new Jekyll sites on Netlify now.

Appreciate the help. Hopefully if this is a glitch, a Netlify team member sees this and can escalate it.

hi there, the “preparing repo” happens when we are having some difficulty cloning your repository. usually this happens because either the git repo has been corrupted in some way, or our permissions are not set up correctly to retrieve your repo.

Can you try a fresh, bare clone into a new folder locallly and see if that works?

Then, please try revoking access for netlify through github and then re-authorizing things. that might fix the issue.