Skip to content

Fix the nightly image.#216

Merged
fredvd merged 1 commit into
6.2.xfrom
maurits-fix-nightly
Jul 20, 2026
Merged

Fix the nightly image.#216
fredvd merged 1 commit into
6.2.xfrom
maurits-fix-nightly

Conversation

@mauritsvanrees

Copy link
Copy Markdown
Member

I have daily been getting an error about the nightly image job failing.

It fails with: ModuleNotFoundError: No module named 'pkg_resources' This is because we have a too new setuptools version, which fails with any version of zc.buildout. And we need zc.buildout in our pip-from-buildout-coredev.py helper script.

Actually we could probably rewrite this to use code from plone.releaser. Or really nothing like that should be needed, because the coredev buildout already keeps the pip files up to date.

So this part could need a bit of rethinking. Also see if we want to maintain a nightly image at all. The workflow runs go back to June last year, and I don't see a single one that passes. They all seem to have the same error.

Anyway, let's fix the immediate error by explicitly using setuptools 81.

Also upgrade other versions:

  • Python 3.13 to 3.14
  • Plone coredev branch 6.1 to 6.2
  • Latest from requirements.txt
  • Update other packages, like pip and Relstorage

It [fails](https://github.com/plone/plone-backend/actions/runs/29706368959/job/88243965444#step:7:1081) with:
`ModuleNotFoundError: No module named 'pkg_resources'`
This is because we have a too new `setuptools` version, which fails with any version of `zc.buildout`.
And we need `zc.buildout` in our `pip-from-buildout-coredev.py` helper script.

Actually we could probably rewrite this to use code from `plone.releaser`.
Or really nothing like that should be needed, because the coredev buildout already keeps the pip files up to date.

So this part could need a bit of rethinking.  Also see if we want to maintain a nightly image at all.
The [workflow runs](https://github.com/plone/plone-backend/actions/workflows/nightly.yml) go back to June last year, and I don't see a single one that passes.  They all seem to have the same error.

Anyway, let's fix the immediate error by explicitly using `setuptools` 81.

Also upgrade other versions:

* Python 3.13 to 3.14
* Plone coredev branch 6.1 to 6.2
* Latest from requirements.txt
* Update other packages, like pip and Relstorage
@mauritsvanrees

Copy link
Copy Markdown
Member Author

FWIW, locally the nightly image now works fine. make image-nightly and then docker run -p 8080:8080 plone/plone-backend:nightly gives me a backend where I can create both Classic UI and Volto sites, and they seem to have the expected versions:

Screenshot 2026-07-20 at 11 26 13

@fredvd fredvd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@fredvd
fredvd merged commit 6481425 into 6.2.x Jul 20, 2026
3 checks passed
@fredvd
fredvd deleted the maurits-fix-nightly branch July 20, 2026 11:07
@davisagli

Copy link
Copy Markdown
Member

fwiw, I thought we already decided to stop releasing the nightly image. As far as I know no one is using it.

@mauritsvanrees

Copy link
Copy Markdown
Member Author

fwiw, I thought we already decided to stop releasing the nightly image. As far as I know no one is using it.

Mostly I wanted to get rid of the daily mail that I got for a failing job that was easy enough to fix.

At least there is a nightly tag now that is up to date:
https://hub.docker.com/r/plone/plone-backend/tags

Let me open an issue for discussing (or confirming) if we want to remove the nightly job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants