Broken CI initialization scripts

Description

Hi,
I was checking why
https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console
was failing and noticed:

Cloning the remote Git repository

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L20>Cloning
repository https://gerrit.ovirt.org/ovirt-appliance.git

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L21>
> git init /home/jenkins/workspace/ovirt-appliance_4.3_build-artifacts-el7-x86_64/ovirt-appliance

  1. timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L22>Fetching
upstream changes from https://gerrit.ovirt.org/ovirt-appliance.git

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L23>
> git --version # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L24>
> git --version # 'git version 1.8.3.1'

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L25>
> git fetch --tags --progress
https://gerrit.ovirt.org/ovirt-appliance.git
+refs/heads/:refs/remotes/origin/ # timeout=30

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L26>
> git config remote.origin.url
https://gerrit.ovirt.org/ovirt-appliance.git # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L27>
> git config --add remote.origin.fetch
+refs/heads/:refs/remotes/origin/ # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L28>Avoid
second fetch

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L29>
> git rev-parse FETCH_HEAD^{commit} # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L30>Checking
out Revision a32357d1d353ce90fe26125e761d2f91f2dd572a
(origin/ovirt-4.3)

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L31>
> git config core.sparsecheckout # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L32>
> git checkout -f a32357d1d353ce90fe26125e761d2f91f2dd572a #
timeout=30

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L33>Commit
message: "answer file: Disable grafana setup"

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L34>
> git rev-parse FETCH_HEAD^{commit} # timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L35>
> git rev-list --no-walk f751f03d3dac7228022a78abab4a54bed87f0ef9 #
timeout=10

<https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/639/console#L36>
> git tag -a -f -m Jenkins Build #639
jenkins-ovirt-appliance_4.3_build-artifacts-el7-x86_64-639 #
timeout=10

The line that worries me is
*Checking out Revision a32357d1d353ce90fe26125e761d2f91f2dd572a
(origin/ovirt-4.3)*
because for ovirt-appliance origin/ovirt-4.3 is
at c9977fdd9f856124bb4976c60aea239448337c2b
while https://gerrit.ovirt.org/#/q/a32357d1d353ce90fe26125e761d2f91f2dd572a
is only on master and ovirt-4.4 branches.

Looks like CI is taking wrong commits from git. Can you please check?

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Activity

Show:
Evgheni Dereveanchin
October 9, 2020, 2:54 PM

I took a quick look and the differences in clonging start at the new "Avoid second fetch" message introduced with Git plugin 4.4

There seems to be an override checkbox to keep the old behavior, testing on Staging now to see if this helps retain the refspec which seems to be lost.

Evgheni Dereveanchin
October 9, 2020, 3:10 PM

Reverting to the old behavior does seem to help so I’ve enabled this checkbox on jenkins.ovirt.org and triggered a new build for appliance-4.3: https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/640/console

 

So far it looks like the correct commit message is visible so the right branch is being cloned. I will go ahead and report this behavior upstream as this does seem to be some kind of a bug in the plugin.

Assignee

Evgheni Dereveanchin

Reporter

Sandro Bonazzola

Blocked By

None

Priority

Medium
Configure