[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38892#comment-38892 ] Barak Korren commented on OVIRT-2662: ------------------------------------- No he does not. He either need to be in the org or added via the bot command. Adding via the bot command saves the user name in the job XML file, so if we refresh the XML for some reason, like updating the job with JJB, the added user list goes away. I think we merged a few patches that refreshed all the jobs in the system recently, so that explains why the adding seems to fail from [~gshereme@redhat.com]'s point of view. Since we're making our own Ansible code for the job updates for the containerized masters now, we can consider adding a feature to preserve user whitelists there. Here are a few other tickets where issues and improvements to the whitelist mechanism have been discussed in the past: * OVIRT-1154 * OVIRT-1657

jenkins whitelist issue in ovirt-web-ui ---------------------------------------

Key: OVIRT-2662 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra

Please see https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 "As a security measure, I will not run automated tests on PRs that are not from white-listed contributors." The bot is lying -- I have 'add to whitelist' for Bohdan several times now. How do we cure this? -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)