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.

Sign up for GitHub

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

Jump to bottom

Git Branch 'null' when not using multi-branch pipeline job #73

Closed

kmanning opened this issue Sep 3, 2019 · 1 comment

Collaborator

kmanning commented Sep 3, 2019

If you create a single branch pipeline Jenkins job, and use the terraform-pipeline. When Jenkinsfile checks the current branch, for some reason it returns 'null'
The default behavior of terraform-pipeline is to not allow 'terraform apply' unless you're on the master branch. So incorrectly detecting a branch of 'null' makes terraform-pipeline unusable.
Figure out what's going on here, and try to fix it.

Collaborator Author

kmanning commented Sep 3, 2019

There's an open issue for this in Jenkinsfile - the branch is simply not available, and there doesn't seem to be any interest in fixing it.

https://issues.jenkins-ci.org/browse/JENKINS-47226

kmanning closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment