Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

GH plugin tries to consume gerrit's projects

Description

Jenkins logs are flooded with:
Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create
WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git
Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create
WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git
Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create
WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git
Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create
WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git

While the messages itself are harmless they floods the logs and consume jenkins master's resources.
See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details.

Activity

Show:

Former user April 11, 2017 at 2:16 PM

These warning messages are still present on both production and staging Jenkins instances. The GitHub plugin tries to match a string like <protocol>://<server>/<project>/<repo> and this fails since our Gerrit URL uses a different format: <protocol>://<server>/<repo>

The unclear thing is why GitHub plugin is invoked at all on jobs that are only using Gerrit. The staging instance only has a single GitHub job and that one does not have any mentions of gerrit as a repo URL. Same for other jobs - they consume Gerrit directly and have all GitHub settings unset. It may be related to hook setup or something similar. Will try to troubleshoot more on the staging instance.

Fixed

Details

Assignee

Reporter

Priority

Parent

Created March 23, 2017 at 10:42 AM
Updated August 29, 2019 at 2:12 PM
Resolved December 15, 2018 at 3:29 PM