[JIRA] (JENKINS-53778) jenkinsfile-runner needs verbose output or logs

1 view
Skip to first unread message

jenkinsmail@peter-jenkins.com (JIRA)

unread,
Sep 26, 2018, 3:41:01 AM9/26/18
to jenkinsc...@googlegroups.com
Peter Jenkins created an issue
 
Jenkins / Improvement JENKINS-53778
jenkinsfile-runner needs verbose output or logs
Issue Type: Improvement Improvement
Assignee: Nicolas De Loof
Components: jenkinsfile-runner
Created: 2018-09-26 07:40
Priority: Minor Minor
Reporter: Peter Jenkins

jenkinsfile-runner looks awesome, but it doesn't give any meaningful output when it fails. There seems to be no verbose mode and no obvious log files with useful output. The docs lack any kind of troubleshooting guide, so I'm basically no able to evaluate this further.

docker run -it -v $PWD/jenkinsfile-runner:/var/jenkinsfile-runner -v $PWD/smartly-ansible:/workspace  -v jenkinsfile-runner-cache:/var/jenkinsfile-runner-cache jenkins/jenkinsfile-runner
Downloading latestCore ...
Running Pipeline on jenkins 2.138.1
Starting Jenkins...
Running from: /var/jenkinsfile-runner-cache/war/jenkins-2.138.1.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
Jenkins home directory: /var/jenkinsfile-runner found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Started
Running in Durability level: PERFORMANCE_OPTIMIZED
cmd.Start() failed with exit status 255Something went wrong running your Jenkinsfile.
If you think this is a bug, please report on https://github.com/ndeloof/jenkinsfile-runner/issues
and if you miss some feature, please join https://gitter.im/jenkinsci/jenkinsfile-runner to discuss about it.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

nicolas.deloof@gmail.com (JIRA)

unread,
Sep 26, 2018, 4:42:04 AM9/26/18
to jenkinsc...@googlegroups.com


cmd.Start() failed with exit status 255

nothing more we can offer, until pipeline has some extra verbose mode we can enable ?

m.vilacides@gmail.com (JIRA)

unread,
Jan 15, 2019, 4:29:08 AM1/15/19
to jenkinsc...@googlegroups.com
Isa Vilacides assigned an issue to Oleg Nenashev
 
Change By: Isa Vilacides
Assignee: Nicolas De Loof Oleg Nenashev

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 15, 2019, 4:33:02 AM1/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: documentation quick-win triaged

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 18, 2019, 2:23:04 AM3/18/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Improvement JENKINS-53778
 
Re: jenkinsfile-runner needs verbose output or logs

I agree with the comment from Nicolas De Loof, we cannot offer better diagnostics in JFR for this case.

There is an option to set higher system logging level in JFR via system properties, and it fully covers the Jenkins system logging.

 

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 17, 2019, 4:40:03 AM7/17/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated Improvement JENKINS-53778
 

Resolving, because there was no follow-up from the reporter, and it is not clear what is the expectation

Change By: Oleg Nenashev
Status: Open Fixed but Unreleased
Resolution: Incomplete
Reply all
Reply to author
Forward
0 new messages