# Impossible to build Elasticsearch 9.0 anymore

**URL:** https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364
**Category:** Elasticsearch
**Created:** [November 11, 2025, 10:59am UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364 "2025-11-11T10:59:44Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![benjamingdocker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamingdocker/32/145707_2.png) [@benjamingdocker](https://discuss.elastic.co/u/benjamingdocker)
#### Post date: [November 11, 2025, 10:59am UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/1 "2025-11-11T10:59:44Z")

</div>

Good morning 👋

I was trying to build ES 9.0.8 from sources but I am facing some issues. I am not a Java expert so please bear with me I probably do silly things here. However, I do need to build ES from source.

I figured that the gradle build process reads the branches.json file from the main branch to know what are the development branches. But since Oct 15, the 9.0 [has been removed](https://github.com/elastic/elasticsearch/pull/136620) from it which makes gradle to fail with

```auto
Build file '/private/tmp/elasticsearch/rest-api-spec/build.gradle' line: 6

A problem occurred evaluating project ':rest-api-spec'.

Failed to apply plugin 'elasticsearch.yaml-rest-compat-test'.
No value present

```

I am not clear whether 9.0 entered end-of-life and according to the [EOL policy](https://www.elastic.co/support/eol) I don't think it is.

Is there a workaround the branches.json file not containing what's needed to build the 9.0 branch ?

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 11, 2025, 3:05pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/2 "2025-11-11T15:05:56Z")

</div>

Hi @benjamingdocker,

Welcome! The latest available version is 9.2. Are you able to successfully build the latest branch? Is there a reason you're trying to build 9.0?

Let us know!

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [November 11, 2025, 4:19pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/3 "2025-11-11T16:19:33Z")

</div>

> [@benjamingdocker](#):
>
> I am not clear whether 9.0 entered end-of-life and according to the [EOL policy](https://www.elastic.co/support/eol) I don't think it is.

From the doc you shared:

> Elastic will provide Maintenance to **the most recent two Minor Releases** of the then-current Major Release, and the final Minor Release of the previous Major Release.

In the case of branch 9, the most recent are 9.2 and 9.1, so I think that 9.0 is not maintained anymore.

---

<div class="post-metadata">

### Author: ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)
#### Post date: [November 11, 2025, 4:45pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/4 "2025-11-11T16:45:58Z")

</div>

> [@benjamingdocker](#):
>
> Is there a workaround the branches.json file not containing what's needed to build the 9.0 branch ?

that commit just changed a list of versions, did you try just editing it ?

---

<div class="post-metadata">

### Author: ![benjamingdocker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamingdocker/32/145707_2.png) [@benjamingdocker](https://discuss.elastic.co/u/benjamingdocker)
#### Post date: [November 11, 2025, 5:39pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/5 "2025-11-11T17:39:36Z")

</div>

I didn't try and I don't see how I could since the gradle build code downloads it and parses it.

---

<div class="post-metadata">

### Author: ![benjamingdocker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamingdocker/32/145707_2.png) [@benjamingdocker](https://discuss.elastic.co/u/benjamingdocker)
#### Post date: [November 11, 2025, 5:40pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/6 "2025-11-11T17:40:43Z")

</div>

I am working on providing docker images and I have to rebuild ES with the latest versions of Java.  
But if 9.0.x is eol, as @leandrojmp pointed out ()thank you by the way for clarifying, I should have read closer…), then I will not do that anymore. So that might be the answer I am looking for.

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 12, 2025, 11:19am UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/7 "2025-11-12T11:19:24Z")

</div>

Interesting. Is there a particular reason you're not using the official docker images?

> **[elasticsearch | Docker @ Elastic](https://www.docker.elastic.co/r/elasticsearch)**

---

<div class="post-metadata">

### Author: ![Rene\_Groschke](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rene_groschke/32/146390_2.png) [@Rene\_Groschke](https://discuss.elastic.co/u/Rene_Groschke)
#### Post date: [December 15, 2025, 2:00pm UTC](https://discuss.elastic.co/t/impossible-to-build-elasticsearch-9-0-anymore/383364/8 "2025-12-15T14:00:30Z")

</div>

I just stumbled over this thread. I think this is a limitation in our build process that should be addressed. At least we should provide a decent fallback.
