I’ve managed to move off Netlify to GitHub Pages with actions. I realise that’s not for everyone.
I hope the netlify team will fix this, but if anyone else is being left in a bind like us, you can use my sample below:
I’ve managed to move off Netlify to GitHub Pages with actions. I realise that’s not for everyone.
I hope the netlify team will fix this, but if anyone else is being left in a bind like us, you can use my sample below:
To anyone who is in crisis right now, don’t forget you can run the build locally and perform manual deployment using Netlify CLI. Not great for anyone with clients, but hey ho.
same here:
ptweb
Could not find ‘bundler’ (2.3.19) required by your /opt/build/repo/Gemfile.lock.
Hey all!
Could you please try building again? This might be related to a bad rollout which has now been reverted.
Apologies for the impact.
All good here. Thanks
Build is OK now (without changing the source code/configuration).
Thanks Netlify for having fixed this quickly
Thank you, all is OK now!
It looks like this is happening again. With a simple copy change yesterday, our builds started failing, and we have the same pattern as reported earlier in this thread, the log tells me it successfully installed the right bundler version:
2:32:06 PM: Using Ruby version 2.7.7
2:32:06 PM: Using Bundler version 2.3.26 from Gemfile.lock
2:32:07 PM: Successfully installed bundler-2.3.26
and then proceeds to install all the Gemfile dependencies successfully, then while running bundle exec jekyll build
it says:
2:32:47 PM: $ bundle exec jekyll build
2:32:47 PM: Activating bundler (~> 2.3) failed:
2:32:47 PM: Could not find 'bundler' (2.3.26) required by your /opt/build/repo/Gemfile.lock.
2:32:47 PM: To update to the latest version installed on your system, run `bundle update --bundler`.
2:32:47 PM: To install the missing version, run `gem install bundler:2.3.26`
My site is crankwheel-www-prod
Happening for me as well. Is there any work around or reason for this coming back?
This was caused by a migration we are currently rolling out. We have rolled back the changes as we investigate, please retry your build.
If this fails, retry the build without cache
Still fails, even retrying without cache
I assume this should be good enough for you to find?
Edit:
Found the build ID in the output.
641d8a2836a7fa099d68b5f2
641d89a0429c4b099c6208f6