Boguslaw Klimas I figured it out! Ok, so if your build fails for any reason the first time you run it (which happened for me in my pipeline script), Jenkins will then become "parameter aware" and will create the Git parameter for you. After this, you are screwed. The only way around it is to edit the job, explicitly remove the parameter from the top of the job definition (i.e. not from the Pipeline script itself, but rather from the "This project is Parameterized" area. Then you can run it again as if it were your first time running the job, wait for it to finish, and then go back and "Build with Parameters" and the Git parameter will correctly show the branches, instead of the error message.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.