Please read! End of support for Xenial build image: Everything you need to know

How I can do that with a manually deployed site? At my site settings it looks like that:

Continuous Deployment
Settings for Continuous Deployment from a Git repository

Repository
Continuous Deployment works by connecting a Git repository to your Netlify site and keeping the two in sync. When you push to Git, we run your build tool of choice on our servers and deploy the result.
Current repository
Not linked

Do I need a Git repository?

1 Like

Same issue for me (no build image selection options, just the offer to link a repository)

2 Likes

I have this same issue. Following.

2 Likes

Hey team!

Is there a way to bulk-update build images? I counted and have 47 sites that use the old one, and I’d love to just do a “check all” for all of them to update. It’ll be fairly tedious to do that per site.

1 Like

Same issue, I am using manual depoy via netlify CLI.

under the Build / Continuous Deployment, I can’t see anything related to Build image selection.

Where’s the Build image selection under Continuous Deployment? I can’t find it! :fearful:

I deploy manually using the drag & drop feature.

Hey @jonkantner

When you deploy manually, there is no build image selection as you are not using continuous deployment.

Okay, so I deployed a build again with the same method and didn’t see the deprecation notice in my deploy log. There’s no warning icon next to my site name, yet the email sent out a couple hours ago still insists my site is impacted. Is my site still safe despite what the email says?

1 Like

I don’t believe you will see any impact to your site(s).

Team,

I have a site that I build on gatsbycloud and deploy on Netlify. The email says my sight will be impacted. I don’t think it will, but want to cofirm.

Thanks!

Hello folks :wave:

Thanks for all of your questions, I’ll try to address them all in this response.

Yesterday we sent out a deprecation notice letting some of our customers know about the need to move your existing builds to focal before the deprecation deadline.

Although we narrowed down the list to those potentially affected by this change (i.e. folks using xenial) we may have inadvertently sent you the email even though you may not be affected by this change.

Am I affected?

If you’re using our build system to deploy any particular site through our git integration you may be affected. Please reference this bullet point on how to check if you’re using xenial.

If you have a lot of sites, it can be confusing. Please make sure that no site is using xenial by checking in your site’s list for the yellow warning triangle indicator:

That means this site is affected by this change!

What do I need to do?

All instructions are available on our deprecation guideline forums post. Feel free to check that guide.

What sites are not affected

  • Sites not using the git-based builds (which include sites deployed manually)
  • Sites deployed through the API directly

We apologise for this inconvenience and are already working on improving the logic behind these emails!

Sites not using the git-based builds (ie: not linked to a git repository) won’t be shown the build image selection card in the UI:

If you have any questions or concerns let us know!

4 Likes

@cassidoo1 there’s no built-in bulk update option, but you can use this npm package created by our very own @jlengstorf ntl-focal-migrate - npm
It relies on the Netlify CLI to update sites via API calls.

2 Likes

Thanks. I must have received an email that was sent by mistake.

This saved me from a world of hurt. Awesome, thanks @jlengstorf @kito !!

2 Likes

Hi kito,
I know I’m a bit late for this post, but I couldn’t find theLock publishing to this deploy button at the top of the deploy’s log page. There’s only Lock to stop auto publishing button. Any suggestions?

This is the correct button @linchen5913.

1 Like

As @coelmay said, that’s the right button. Thanks for flagging it, I’ve updated the original post with the correct button copy.

1 Like

Support for Xenial has now ended, and all builds using this image will now fail going forward. Please follow the instructions in the original post to update your build image, and as usual let us know if you have any questions!

Hello, I am new to Netlify and working on a project created by someone else which uses Xenial build image.
I started today and figured out it has been deprecated. There’s another option for ‘Focal 20.4 (default)’, if I switch to that, will it affect the current site? Please give me suggestions to deploy changes in the existing website. Thank you.

Hi @kdesai24

Welcome to the community! :partying_face:

If you want to test the effects of switching to the new build image on your current site, you could try creating a new site with the same code as your production site and uses the Focal build image. Then you can do some testing to make sure it deploys before you switch the production site.

1 Like