[JENKINS-75780] git-parameter-plugin | Reactive parameters

Hello!

I posted a query on StackOverflow to ask this question initially, as I didn't think it is possible without using the Active Choices plugin and creating an ugly script, that cannot use a credentialsId. You can see it here, but I will also explain in this ticket.

Basically, I want the ability to choose a branch in the 1st parameter and then choose a commitId in the 2nd parameter. The commitId's or revisions would be dependent on the branch chosen in the 1st parameter. This would allow choosing a specific commit to build, deploy, run automated tests against, etc. (whatever you want to do in your CI pipeline).

Again, I don't think this is possible without using the Active Choices plugin parameter types, but it would require writing a groovy script for it and I don't know how a `credentialsId` would be accessible and usable within that script.

That's it! Just the ability to have a 2nd git parameter be reactive to a git parameter that comes before it.

---
Originally reported by wmoorby, imported from: git-parameter-plugin | Reactive parameters

• status: Open
  
• priority: Minor
  
• component(s): git-parameter-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251216-182730
  

Raw content of original issue

Hello!


I posted a query on StackOverflow to ask this question initially, as I didn't think it is possible without using the Active Choices plugin and creating an ugly script, that cannot use a credentialsId. You can see it here, but I will also explain in this ticket.


Basically, I want the ability to choose a branch in the 1st parameter and then choose a commitId in the 2nd parameter. The commitId's or revisions would be dependent on the branch chosen in the 1st parameter. This would allow choosing a specific commit to build, deploy, run automated tests against, etc. (whatever you want to do in your CI pipeline).


Again, I don't think this is possible without using the Active Choices plugin parameter types, but it would require writing a groovy script for it and I don't know how a `credentialsId` would be accessible and usable within that script.


That's it! Just the ability to have a 2nd git parameter be reactive to a git parameter that comes before it.