Manually running a rebuild

@JulienPalard

We should write down the steps to properly running a rebuild, e.g. on release day or for end-of-life versions. I ran the rebuild on Monday to ensure that /3/ was promptly updated, but there was no process to follow.

Likewise, for versions that become unsupported, we should trigger one final rebuild so that the "outdated" header/warning is added. For example, we need to do this now with https://docs.python.org/3.8/.

cc @JulienPalard -- I'm not sure how you've handled this in the past (especially EOL versions), and if there is a process you would recommend?

A

@JulienPalard

Friendly ping @JulienPalard -- would it be best to say that manual builds are unsupported perhaps? The Python 3.8 docs still lack the "outdated" banner, so I'm not sure what the best method would be here.

A

Manual builds are needed EOL and security branches, for example:

And it's part of PEP 101 for EOL transitions:

Add a retired notice to each release page on python.org for the retired branch.

https://peps.python.org/pep-0101/#moving-to-end-of-life

I agree we should write down the steps on how to actually perform a manual build.

(Yeah I'm under 500 unread github notifications \o/)

For manual rebuild I do:

$ ssh docs.nyc1.psf.io
$ screen -DUR
$ sudo su --shell=/bin/bash docsbuild
$ /srv/docsbuild/venv/bin/python /srv/docsbuild/scripts/build_docs.py --branch 3.8

That's not ideal, but that's not often needed.

Sometimes killing a running build is needed so the manual one can start :D

I just started the rebuild for 3.8.

3.8 rebuild done.

Hmm, https://docs.python.org/3.8/ is still missing the banner and says "Last updated on Sep 08, 2024".

3.8 is still waiting for a rebuild, and we now also need rebuilds for the 3.9-3.11 security branches:

I've kicked off a 3.11 build using the instructions above 🤞

3.11 finished!

2024-12-07 11:37:08,426 INFO: Full build done (16h 18m 2s).

I've started 3.10, but opened the screen under the docsbuild user instead of my own:

ssh docs.nyc1.psf.io
sudo su --shell=/bin/bash docsbuild
screen -DUR
/srv/docsbuild/venv/bin/python /srv/docsbuild/scripts/build_docs.py --branch 3.10

screen -DUR will either create a new screen session, or if there's already one running, it'll connect you to it. So others with server access can also check on the progress.

3.10 finished!

2024-12-08 00:38:35,718 INFO: Full build done (12h 49m 46s).

3.9 started.

It would be useful to be able to manually build a bunch of these with a single command in the future, like:

/srv/docsbuild/venv/bin/python /srv/docsbuild/scripts/build_docs.py --branch 3.11 3.10 3.9 3.8

Please see PR #235.

3.9 finished!

2024-12-09 09:35:58,914 INFO: Full build done (15h 18m 37s).

And now let's retry 3.8.

Please see PR #236 to add the instructions to RELEASING.md.

And 3.8 now has the banner.

It didn't after my first run, so I did it a second time and it's okay now. Not sure if it was some caching/purging issue.

Navigation Menu

Repository navigation

Manually running a rebuild #216

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Manually running a rebuild #216

Description

Activity

AA-Turner commented on Oct 31, 2024

hugovk commented on Nov 1, 2024

JulienPalard commented on Nov 22, 2024

JulienPalard commented on Nov 23, 2024

hugovk commented on Nov 24, 2024

hugovk commented on Dec 6, 2024

hugovk commented on Dec 7, 2024

hugovk commented on Dec 8, 2024

hugovk commented on Dec 8, 2024

hugovk commented on Dec 9, 2024

hugovk commented on Dec 9, 2024

hugovk commented on Dec 10, 2024

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions