Jenkins: git tag sometimes fails

[sanssecours]

Description

Seems like the Jenkins build now fails every time when its time to build Debian packages. According to the build server the command

git tag -a -f -m Jenkins Build #1007 jenkins-master-1007 # timeout=10

does not work, printing the error message:

Could not apply tag jenkins-master-1007

. This failure happened at least in build 1005 up until build 1009 of the master branch. The last time the Debian packages were built successfully was build 983. The last overall successful Jenkins build was build 982 😭.

[markus2330]

Thank you for reporting the problem!

@Mistreated any progress on Debian packaging?

Alternatively, I think it is best to disable Debian Buster packages until @Mistreated has progress.

[sanssecours]

@Mistreated any progress on Debian packaging?

I met Djordje yesterday. As far as I know generating packages for Ubuntu Bionic should work now.

[sanssecours]

I think the problem lies somewhere in the following code for the Pipeline SCM Step Plugin:

libelektra/scripts/jenkins/Jenkinsfile

Lines 1050 to 1059 in 5519cb8

	checkout scm: [
	$class: 'GitSCM',
	branches: scm.branches,
	extensions: scm.extensions + [
	[$class: 'PerBuildTag'],
	[$class: 'RelativeTargetDirectory',
	relativeTargetDir: targetDir]
	],
	userRemoteConfigs: scm.userRemoteConfigs
	]

. Here is some documentation for the plugin.

[markus2330]

@ingwinlu do you have an idea?

[markus2330]

@Mistreated can you reenable the buster packages together with the Ubuntu packages?

[sanssecours]

Seems like commit 883e0e7 did not fix this problem.

[markus2330]

Master builds now: https://github.com/ElektraInitiative/libelektra/commits/master#

Did you see the problem also somewhere else or can this be closed now?

[sanssecours]

Looks like building the packages still fails sometimes.

[markus2330]

Why are the git config commands missing there? 794cfdf

[sanssecours]

Why are the git config commands missing there? 794cfdf

As far as I know that is the case, because the build step fails before these commands are executed (see also #3009 (comment))

[sanssecours]

Build 1040 and Build 1041 also failed, because of this issue.

[markus2330]

Is there something wrong in the Jenkins configuration? Seems like some module of Jenkins already does this git tag.

[markus2330]

It still happens but not so often anymore. I removed "urgent".

[markus2330]

I think it still happens from time to time. @Mistreated did you already investigate?

[mpranj]

I think it still happens from time to time.

Happens on a regular basis. Sometimes many rebuilds do not help to the point that I gave up on this. Would be great if someone knows how to fix it.

[dbulatovic]

Can you link the build that fails with this error?

[mpranj]

Here is one example from master.

[dbulatovic]

If this mistake happens from now on again. I would appreciate, if someone could link it if I do not see it immediately (debugging purposes).

[dbulatovic]

Anyone encountered this problem last 10 days?

[dbulatovic]

This error does not repeat after a default git user is set:

[user] name = Jenkins email = Jenkins <autobuilder@libelektra.org>

Closed.

[markus2330]

It looks like this issue popped up again! It is some undocumented assumption of how build server agents are configured.

The error occurs on master: https://build.libelektra.org/blue/organizations/jenkins/libelektra/detail/master/793/pipeline

 > git tag -a -f -m Jenkins Build #793 jenkins-master-793 # timeout=10

Could not apply tag jenkins-master-793

@lukashartl can you please fix the Ansible scripts that the default git user will be set (see post directly above) and apply it to l1? I disabled l1 till then.

[markus2330]

@lukashartl any update here? I see l1 is enabled again?

[lukashartl]

has been fixed

[markus2330]

Thx, so this issue can be closed!