Triggering rtd-merge job after release-merge?

Robert Varga


while resolving links to MRI projects, I have come
across a slight problem with having versions propagated.

Since MRI projects produce versions rather more often than their
documentation changes the admin interface does not see the new versions,
for example in

The list of versions is updated by $project-rtd-merge jobs, hence for
MRI projects (for example controller), I need to trigger

The idea is that controller-release-merge produces the version tag in
git repo, and controller-rtd-merge-master then picks it up and lets
ReadTheDocs know about it.

Is there a way to create this trigger in releng/builder's JJB?


Join to automatically receive all group messages.