[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24100#comment-24100 ] Barak Korren commented on OVIRT-918: ------------------------------------ That is not a job, its a special screen that is part of the [Gerrit trigger plugin|https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger]. We do seem to be a couple releases behind (2.21.1) the latest plugin release (2.23.0). So we may upgrade, but nothing in the plugin changelog implies that this issue was dealt with. We may as well just go and report this on the [Jenkins issue tracker|http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27gerrit-trigger-plugin%27].

Special characters escaped in Jenkins manual triggering of CI -------------------------------------------------------------

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

If a subject of a change has special characters, they get HTML-encoded when presenting it in the Jenkins manual trigger job. See screenshot for an example: http://imgur.com/G1M7vNu

-- This message was sent by Atlassian JIRA (v1000.620.0#100023)