Pipeline: Supporting APIs
List of issuesKey | Summary | Created | Updated |
---|
JENKINS-66001 | Want a way to disable fsync(2) for Pipeline but retaining atomicity | | |
---|
JENKINS-59990 | values set by environment directive are not captured for RunWrapper.getBuildVariables | | |
---|
JENKINS-57748 | CpsFlowExecution java.io.IOException in org.jenkinsci.plugins.workflow.support.DefaultStepContext.getListener | | |
---|
JENKINS-57103 | No signature of method: org.jenkinsci.plugins.workflow.job.WorkflowRun.getBuildVariables() | | |
---|
JENKINS-56252 | Futures.addCallback uses method deleted in Guava 21 | | |
---|
JENKINS-54535 | Expose build parameters in RunWrapper | | |
---|
JENKINS-54477 | Getting an accurate build result when sending a notification from Pipeline is harder than it needs to be | | |
---|
JENKINS-52416 | Random AccessDeniedExceptions in jenkins.err.log | | |
---|
JENKINS-51091 | Make test results available on currentBuild | | |
---|
JENKINS-46376 | Allow getting log through RunWrapper | | |
---|
JENKINS-40057 | Stage view is completely missing for long durations after restarts | | |
---|
JENKINS-32192 | Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect | | |
---|
JENKINS-32146 | Last step misleadingly marked as blue even though build status is FAILURE | | |
---|
JENKINS-27574 | RunWrapper.setResult() should be force set | | |
---|
JENKINS-25925 | More polite reporting of NotSerializableException | | |
---|