[ https://ovirt-jira.atlassian.net/browse/OVIRT-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19046#comment-19046 ] Evgheni Dereveanchin commented on OVIRT-665: -------------------------------------------- The recommended workaround is to whitelist the parameters in hudson.model.ParametersAction.safeParameters For gerrit trigger they are: GERRIT_EVENT_TYPE,GERRIT_EVENT_HASH,GERRIT_BRANCH,GERRIT_TOPIC, GERRIT_CHANGE_NUMBER,GERRIT_CHANGE_ID,GERRIT_PATCHSET_NUMBER, GERRIT_PATCHSET_REVISION,GERRIT_REFSPEC,GERRIT_PROJECT,GERRIT_CHANGE_SUBJECT, GERRIT_CHANGE_COMMIT_MESSAGE,GERRIT_CHANGE_URL,GERRIT_CHANGE_OWNER, GERRIT_CHANGE_OWNER_NAME,GERRIT_CHANGE_OWNER_EMAIL, GERRIT_PATCHSET_UPLOADER,GERRIT_PATCHSET_UPLOADER_NAME To add them we can set the list in JENKINS_JAVA_OPTIONS of /etc/sysconfig/jenkins

Jenkins: gerrit trigger plugin issues after update --------------------------------------------------

Key: OVIRT-665 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-665 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Evgheni Dereveanchin Assignee: infra

It looks like the Gerrit trigger plugin is broken after yesterday's release due to SECURITY-170 implemented in the new Jenkins version: https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECU... Sample failing triggered build: http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests_...

-- This message was sent by Atlassian JIRA (v1000.184.1#100008)