I don't understand how this fixes the publishing. We tested setting PAGURE_DOC_REPO_NAME in manual job run last time and it did not work.

The variable should be set through c3i role: https://pagure.io/c3i-library/blob/fa4a65843539e1a171a448ba03cfdebc6d3a2211/f/roles/c3i/defaults/main.yml#_57

What I did not find anywhere is PAGURE_MAIN_BRANCH parameter. Instead there seems to be GIT_MAIN_BRANCH.

cc @mkovarik

I don't understand how this fixes the publishing. We tested setting PAGURE_DOC_REPO_NAME in manual job run last time and it did not work.

The variable should be set through c3i role: https://pagure.io/c3i-library/blob/fa4a65843539e1a171a448ba03cfdebc6d3a2211/f/roles/c3i/defaults/main.yml#_57

What I did not find anywhere is PAGURE_MAIN_BRANCH parameter. Instead there seems to be GIT_MAIN_BRANCH.

cc @mkovarik

I've tested this script here and it works:
https://jenkins-waiverdb-test.cloud.paas.psi.redhat.com/job/waiverdb-test/job/waiverdb-test-waiverdb-postmerge/138/

I don't see any reason to have PAGURE_DOC_REPO_NAME parametrized, the same for PAGURE_MAIN_BRANCH.

+1 From me.

I don't see any reason to have PAGURE_DOC_REPO_NAME parametrized, the same for PAGURE_MAIN_BRANCH.

@mkovarik Any comments about this?