Libelektra: Jenkins server config issue
It seems the Jenkins server is not configured quite right...
The latest run from #3447 is falsely reported as successful.
AFAICT debian-stretch-full was aborted for unknown reasons, which caused the build to stop after the "Full Builds" stage. But for some reason the build is now reported as successful, even though the "Build artifacts" stage did not run at all.
kodebach
All 5 comments
@Mistreated can you take a look?
markus2330
on 23 Sep 2020
I checked it right away.
This must have been some odd termination, because:
Caught the following exception: null
Since it did not catch any exception it went on, although the process was terminated.
If something like this happens again, please link it here.
dbulatovic
on 24 Sep 2020
Is there maybe some other way to get more information about the current state beside from the Exception? The null exception is unfortunately not very rare.
markus2330
on 26 Sep 2020
This problem has been reoccurring since the new build server setup. I just did some maintenance on the build system, but this will likely not fix the issue. A fix would be great but I also don't know how to debug this. 馃し
mpranj
on 26 Sep 2020
The last time I remember something like this happened was when there was a bug in publishing, which was resolved.
But if this happens again, just post the build here.. I will see what can I do about this.
dbulatovic
on 26 Sep 2020
Related issues
sanssecours
路
4Comments
mpranj
路
3Comments
mpranj
路
4Comments
markus2330
路
4Comments
dmoisej
路
3Comments
Most helpful comment
The last time I remember something like this happened was when there was a bug in publishing, which was resolved.
But if this happens again, just post the build here.. I will see what can I do about this.