Consolidate doc build steps into the nox "make" session

[x1101]

Converted docs builds to use nox -e make -- webdocs

Sample output for review from a run in my personal fork

[oraNod]

@x1101 I don't have permissions to your repo's gha runs but that's OK. I'll push your changes to my own fork and try it there. At first glance your changes look good. They make the workflow simpler by moving things into nox so +1 for that.

[oraNod]

@x1101 Hey, this looks pretty good to me but I think some of the commits don't look right. Could you rebase your branch against devel and update? I've tested this in my fork and think it's good to go. Thanks very much for this improvement!

[oraNod]

Thanks for this @x1101

[webknjaz]

@x1101 FYI it's best to split the nox invocation into two steps — provisioning the env and then running the actual thing. This makes stuff easily visible in CI logs.

[gotmax23]

That'll be handled once we switch to using the ansible-community nox action.

[webknjaz]

@gotmax23 not really. An action is always one step. Unless it can be called twice with different args.. This is why I prefer reusable workflows these days.

[x1101]

@webknjaz the way the ansible-community nox action is called is two steps (once for setup, once for running actions).

I've got an open PR #3194 that has an example of how that works. (Its still in Draft and I have some work to do, but you should see what I mean).

[webknjaz]

@webknjaz the way the ansible-community nox action is called is two steps (once for setup, once for running actions).

I've got an open PR #3194 that has an example of how that works. (Its still in Draft and I have some work to do, but you should see what I mean).

That's still one step per session. But sessions aren't split into provisioning the venv and executing main payload.