Libelektra: Jenkins: git tag sometimes fails
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 😭.
sanssecours
All 20 comments
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.
markus2330
on 26 Sep 2019
@Mistreated any progress on Debian packaging?
I met Djordje yesterday. As far as I know generating packages for Ubuntu Bionic should work now.
sanssecours
on 26 Sep 2019
I think the problem lies somewhere in the following code for the Pipeline SCM Step Plugin:
. Here is some documentation for the plugin.
sanssecours
on 26 Sep 2019
@ingwinlu do you have an idea?
markus2330
on 26 Sep 2019
@Mistreated can you reenable the buster packages together with the Ubuntu packages?
markus2330
on 27 Sep 2019
Seems like commit 883e0e7 did not fix this problem.
sanssecours
on 29 Sep 2019
Master builds now: https://github.com/ElektraInitiative/libelektra/commits/master#
Did you see the problem also somewhere else or can this be closed now?
markus2330
on 30 Sep 2019
Looks like building the packages still fails sometimes.
sanssecours
on 2 Oct 2019
Why are the git config commands missing there? 794cfdf7747423ed0240c82987dec69ee2065f01
markus2330
on 2 Oct 2019
Why are the
git configcommands missing there? 794cfdf
As far as I know that is the case, because the build step fails before these commands are executed (see also https://github.com/ElektraInitiative/libelektra/issues/3009#issuecomment-535405854)
sanssecours
on 3 Oct 2019
Build 1040 and Build 1041 also failed, because of this issue.
sanssecours
on 3 Oct 2019
Is there something wrong in the Jenkins configuration? Seems like some module of Jenkins already does this git tag.
markus2330
on 3 Oct 2019
It still happens but not so often anymore. I removed "urgent".
markus2330
on 15 Nov 2019
I think it still happens from time to time. @Mistreated did you already investigate?
markus2330
on 12 Apr 2020
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.
mpranj
on 12 Apr 2020
Can you link the build that fails with this error?
dbulatovic
on 13 Apr 2020
Here is one example from master.
mpranj
on 13 Apr 2020
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
on 24 Apr 2020
Anyone encountered this problem last 10 days?
dbulatovic
on 5 May 2020
This error does not repeat after a default git user is set:
[user]
name = Jenkins
email = Jenkins <[email protected]>
Closed.
dbulatovic
on 7 Aug 2020
Related issues
mpranj
·
3Comments
mpranj
·
3Comments
dmoisej
·
3Comments
sanssecours
·
3Comments
markus2330
·
4Comments
Most helpful comment
Here is one example from master.