-
Notifications
You must be signed in to change notification settings - Fork 5
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
git config always changes the encoding of .git/config
and ~/.gitconfig
to value of _ENCODE_FILE_NEW
#141
Comments
Is this only occurring within Jenkins or can you reproduce it manually with the same userid and environment variables? What environment variables are being set currently? It's very likely an environment variable setting as on my system it's still set as ISO8859-1:
|
Looks like it's the _ENCODE_FILE_NEW variable:
|
.git/config
and ~/.gitconfig
to IBM-1047.git/config
and ~/.gitconfig
to value of _ENCODE_FILE_NEW
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Introducing any
git config
commands into a Jenkins pipeline causes the next run that touches that repository to fail. Why? Because even if I chtag the config file to ISO8859-1, the moment git modifies it it goes back to IBM-1047.Jenkins does not tolerate a git config file anywhere that is encoded IBM-1047. If it finds one, the pipeline fails with the following error:
As you can imagine, I am interested in making sure that any git config files stay ISO8859-1.
The text was updated successfully, but these errors were encountered: