-
Notifications
You must be signed in to change notification settings - Fork 21
No Log output after neoDeploy failed #16
Comments
I refer to commit 78400cad9bdce2b1b638726eee16ee9e03202c9f in the piper-lib. Tried to dive into that issue: Findings up to now: This triggers an Next steps: 1.) Try to understand why the source cannot be found. Should be set earlier by @citoki : In order to circumvent the issue we should provide the deployable via signature on neoDeploy: neoDeploy ./. source: for now and check if that resolves the issue. By the way: I tried to reproduce the issue here, but on my side the logs folder is present and neo gets called ... |
Can you please check what happens if you use the version provided in branch This will not solve the issue, but currently we catch an exception, try to provide the logs, receive another exception while doing this and forget the first one. This should be fixed with the version above. |
@marcusholl The error was:
***
hudson.AbortException: File my-very-own-build-artifact.mtar cannot be found.
*** |
yes, I already saw this. Providing additional commits now with branch |
It is an issue with stashing.
|
Fixed with #632 in SAP/jenkins-Library. Please switch back to master branch and come back if it does not work. Otherwise close this issue, please. |
With the following
Jenkinsfile
wants to deploy the artifact to NEO, it fails and cannot write any logs.The text was updated successfully, but these errors were encountered: