Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: "Branch Specifier" can not be specified by an environment variable as dokumented #314

Open
brosmar opened this issue Feb 2, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@brosmar
Copy link

brosmar commented Feb 2, 2023

Jenkins Version

CloudBees CI Client Controller 2.375.1.1-rolling

JTE Version

2.5.3

Bug Description

When configuring a Jenkins job to use the JTE "From SCM/Git" the "Branch Specifier" is specifying the Branch to use. In help information it says:

${ENV_VARIABLE}
It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.
E.g. ${TREEISH}, refs/tags/${TAGNAME}, ...   

But when using as described the Variable Names are not substituted by their values.

Relevant log output

Started by user xyz
[JTE] Obtained Pipeline Configuration File (show)
[JTE] Pipeline Configuration Modifications (show)
hudson.plugins.git.GitException: Command "git fetch --tags --force --progress --prune -- origin +refs/heads/"${MY_GIT_BRANCH}":refs/remotes/origin/"${MY_GIT_BRANCH}"" returned status code 128:
stdout: 
stderr: fatal: couldn't find remote ref refs/heads/"${MY_GIT_BRANCH}"

Steps to Reproduce

Easy to reproduce.
Enter an Environment Variable at the "Branch Speifier"

@brosmar brosmar added the bug Something isn't working label Feb 2, 2023
@brosmar
Copy link
Author

brosmar commented Feb 2, 2023

I found that this "Feature" was discussed in Issue:
#165

I think there is an update for the issue: https://issues.jenkins.io/browse/JENKINS-60630

@brosmar
Copy link
Author

brosmar commented Feb 2, 2023

I have installed the git-5.0.0 Plugin and the Pipeline: groovy plugin 3520.va_8fc49e2f96f.
But the behaviour did not change.

What is missing?

@imaldonado1
Copy link

Any new about this case? Same problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants