You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When job Pipeline settings is set to 'Pipeline As Yaml from SCM' and a custom path to the Jenkinsfile.yaml is given, the location is not saved even after hitting the 'Save' button.
Steps to reproduce the behavior:
Create a new job
Setup the pipeline section with 'Pipeline As Yaml from SCM' and feed it with SCM/repo/credentials/branch and script path, if Jenkinsfile.yaml is in a subdirectory of a (git) projet.
Click Save
If you check the job configuration again, everything is fine except that the specified path as been replaced by "Jenkinsfile.yaml"
Expected behavior
A script path location taken into account
Versions:
Jenkins Version : 2.249.2
plugin version : 0.12-rc
The text was updated successfully, but these errors were encountered:
Describe the bug
When job Pipeline settings is set to 'Pipeline As Yaml from SCM' and a custom path to the Jenkinsfile.yaml is given, the location is not saved even after hitting the 'Save' button.
Steps to reproduce the behavior:
Expected behavior
A script path location taken into account
Versions:
The text was updated successfully, but these errors were encountered: