Open e88z4 opened 2 years ago
I found an interesting JTE log only from from the tag build.
[JTE] FileSystemWrapperFactory: Unable to create SCMFileSystem: job: cloud-engineering/container-build-test/0.1.0, scm: null
This is actually a bug / missing feature with BitBucket. JTE uses the Jenkins SCM API 2.0 to do a lightweight checkout of the code. BitBucket does not support this for Pull Requests.
See:
Path Forward:
SCMFileSystem
based on the source branch of the Pull RequestIn either case, because there's no actual git ref for the PR - so you'd have to approximate what code to check out. Assuming the target branch has been merged into the source branch, there'll be no impact.
Changing this to an enhancement instead of a bug. Nothing wrong with JTE here. We'd have to write code to make up for BitBucket's inadequacies.
Hi @steven-terrana ,
The build is not a pull request build. This build is a tag build instead.
Jenkins Version
2.346.2
JTE Version
2.5.2
Bug Description
My multibranch build is successfully build the job on the branch build. After the branch build is successful, I add a tag on the same commit to produce a tag build. The tag build fails to load the pipeline_config.groovy to load all the necessary libraries on the repository.
Relevant successful log output from branch build
Relevant log output from tag build on the same commit with error
Steps to Reproduce