[JENKINS-65448] [Git][Parameterized Trigger] 'Pass-through Git commit' does not include repo URI and breaks pipeline build

Consider the following situation:

• job1 (classical freestyle)
  
  
  
  • build
    
    
    
    • git: https://build/repo.git
    
    
    
    
  
  
  • post
    
    
    
    • Trigger parameterized build on other projects
      
      
      
      • job2 
      
      
      • [x] Pass-through Git Commit that was built
      
      
      
      
    
    
    
    
  
  
  
  


• job2 (pipeline):
  
  
  
  • pipeline src
    
    
    
    • from SCM: https://pipeline.repo/pipeline.git
    
    
    
    
  
  
  • inside pipeline
    
    
    
    • step1: git 'https://build/repo.git'
    
    
    • step2: git 'https://another/repo.git'
    
    
    
    
  
  
  
  

This constellation will fail to build, because the commit-ID passed-through from build of job1 is being used to fetch the pipeline of job2 and also (if it would get so far) would be used for the step2 of the pipeline, but it should only apply to step1.

The technical issue is that in

hudson.plugins.git.GitRevisionBuildParameters

no repoURL is passed to the constructor of

hudson.plugins.git.RevisionParameterAction.

That one then, in canOriginateFrom() always returns true and uses the revision ID for all git repos involved in the pipeline.

---
Originally reported by sratz, imported from: [Git][Parameterized Trigger] 'Pass-through Git commit' does not include repo URI and breaks pipeline build

• status: Open
  
• priority: Minor
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-02
  

Raw content of original issue

Consider the following situation:



	
job1 (classical freestyle)

	


		
build

		


			
git: https://build/repo.git

		

		

		
post

		


			
Trigger parameterized build on other projects

			


				
job2 

				
[x] Pass-through Git Commit that was built

			

			

		

		

	

	

	
job2 (pipeline):

	


		
pipeline src

		


			
from SCM: https://pipeline.repo/pipeline.git

		

		

		
inside pipeline

		


			
step1: git 'https://build/repo.git'

			
step2: git 'https://another/repo.git'

		

		

	

	



This constellation will fail to build, because the commit-ID passed-through from build of job1 is being used to fetch the pipeline of job2 and also (if it would get so far) would be used for the step2 of the pipeline, but it should only apply to step1.


The technical issue is that in


hudson.plugins.git.GitRevisionBuildParameters


no repoURL is passed to the constructor of


hudson.plugins.git.RevisionParameterAction.


That one then, in canOriginateFrom() always returns true and uses the revision ID for all git repos involved in the pipeline.

environment

```
Jenkins 2.277.3

git-plugin 4.7.1

parameterized-trigger 2.40
```

1 attachment

- [image-2021-04-23-14-35-32-951.png](https://issues.jenkins.io/secure/attachment/54658/image-2021-04-23-14-35-32-951.png)
>