| Just discovered this problem today while working on team adoption of Jenkins / BlueOcean. In our case, dev started out with placing the Jenkinsfile at the repo path /build/Jenkinsfile rather than at /Jenkinsfile and defining the path to the jenkinsfile in the job here http://<hostname>/jenkins/job/<jobname>/configure As others have mentioned, builds do run, but the BlueOcean editor does not show any stages or steps when a user looks there. This in turn creates confusion since they see the steps in the build results screen, but not in the editor screen where they expect to see them. At this point, I'm concerned of the psychology at play when working with teams to get started using this. One of the selling points on BlueOcean to management is that it makes it easy to use and build the job steps, and the code gets commited to your repo easily. So changes can be made in a UI or by hand. In practice, when one project keeps the Jenkinsfile at root and another stores it elsewhere, this confuses the newer user who may be looking at a job configured by someone else for inspiration on how to add steps to a project/pipeline they are working on themselves when they see stages and steps in one project that but another appears to have no steps when they look at it in the UI. |
