Re: Triggering rtd-merge job after release-merge?
toggle quoted message Show quoted text
I checked the JJB code for the controller rtd-merge-master, the Gerrit triggers seem to work as expected triggering the required jobs. Ex: Job #4 was triggered from a merge from the change request 94725.
From what I understand, the release merge job are responsible for promoting the staging repo, which should create a new version ex: 3.0.6 in RTD.org/$project.
Every new release on the self-managed projects would require activating the new version on RTD (as admin). That should trigger a new build to update the docs for the $project.
I am not sure if triggering rtd-merge as a downstream job on every release merge would be the right way for this. Will need to dig in a bit and get back to you.
+docs folks on any suggestions.
On Wed, Jun 9, 2021 at 7:27 PM Robert Varga <nite@...> wrote: