From a711d9ebb34624433df177c09ee68cdf46f6d54a Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Tue, 3 Mar 2020 20:57:03 +0100 Subject: [PATCH] Rewrite logs.o.o post reference The instructions for getting logs of post jobs is not correct anymore, rewrite the section. Change-Id: I280b520db95648bccfffaf16b801de9b715c2ecc --- doc/source/developers.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/doc/source/developers.rst b/doc/source/developers.rst index 8cdd086..ec1f236 100644 --- a/doc/source/developers.rst +++ b/doc/source/developers.rst @@ -916,16 +916,10 @@ After patches land, jobs can be run in the post queue. Finding build logs for these jobs works a bit differently to the results of the pre-merge check and gate queues. -For jobs in the post queue, logs are found at -``http://logs.openstack.org//``. -For example, if a change is committed with the SHA 'deadbeef123456', -the logs will be found at ``http://logs.openstack.org/de/deadbeef123456``. - -.. Note:: In many cases (particularly for higher-churn projects) - the commit will be accompanied by a merge commit to stitch it into - the branch and it's that merge commit which is the subject of post - pipeline jobs. In that situation you will need to review the Git - log and use the SHA of that merge commit instead. +For jobs in the post queue, logs are found via the builds tab of +https://zuul.opendev.org/, for example to search for post jobs of the +openstack tenant, go to the `Zuul openstack build tab +`_ . Peer Review -----------