build-pipeline-plugin

问题 I have a strange behaviour with my jenkins agent. i have a master and a seperate build agent, which has access to docker. while i'm running the following pipeline script on the build agent: node { sh "id" sh "echo $PATH" sh "docker ps" docker.image("node:latest").inside("") { sh "npm --version" } } i get the following output: Running on docker-agent in /home/jenkins/workspace/test [Pipeline] { [Pipeline] sh [test] Running shell script + id uid=1000(jenkins) gid=1000(jenkins) groups=900(docker

问题 When attempting to query a build using groovy, I call myBuild.getCauses() I can see in the interface of Jenkins (the build screen) that this build has two causes, a UserIdCause, and an UpstreamCause. However, when I interrogate the same build with the groovy above, I only get a single cause back, which is the UserIdCause. There must be some method of getting the UpstreamCause from the build, or it wouldn't be present in the user interface. I am using the Build Pipeline plugin to manually

问题 Is it possible that for a given Build Pipeline job (which has downstream jobs either in the build or post build action as " Trigger build on other projects "), I can get a Tree listing view showing which Pipeline job# N called, what child jobs in the calling order (sequential or parallel) with child build# for that pipeline run build#. For ex: If my pipeline job has this view: then, I'm expecting to get a listing of the top run similar to ( in case I just put in simple text format ): vac-3.0