Hi Daniel,
You were right, it was an archiveArtifacts step that was failing without
any output whatsoever.
Thanks,
Raj
On Tuesday, January 3, 2017 at 12:22:07 PM UTC-8, Daniel Beland wrote:
>
>
> I had a similar problem today and sadly my conclusion is it can be
> anything.
>
> In my case
Take care a ill formated script part make the build as failing. use some
print line to make sure you reach the end of the script. Many script error
are way too silent into JenkinsFile.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
Hi David,
Here is a gist of the grepped failure output. I had to remove two segments
of the output but I looked over them, very carefully, for any sort of
failure indication and there was none.
https://gist.github.com/rajsahae/743aed54f145bd664f65051082c622a5
The rest of the output, you can
Hi David,
I'm looking through the output and there is no way for me to fully sanitize
this without deleting large swaths of output at which point I can't
guarantee that you would find the output complete enough.
Are there any questions or analysis of the output that I could communicate
to you
Hi David,
Thanks for your reply. I can certainly attempt to post the output but I
will have to go through and sanitize it a bit. That might take some time.
Will try to post back here ASAP with something for you to look at.
On Wednesday, December 28, 2016 at 3:52:52 PM UTC-8, David Karr wrote:
I'd say we would need to see all of the console output, even though
you say it reports failure.
On Tue, Dec 27, 2016 at 11:59 PM, Raj Sahae wrote:
> Hi all,
>
> I have a pipeline that I consider to be pretty basic. Nothing complicated in
> terms of the logic. Here is a gist
>
Hi all,
I have a pipeline that I consider to be pretty basic. Nothing complicated
in terms of the logic. Here is a gist (
https://gist.github.com/rajsahae/961350d0d4ea14b6b5246767ce2ab5af)
where I have anonymized the jenkinsfile but other than the specific names
being changed, this file is