Last modified by Boris Folgmann on 2026/01/19 11:04

From version 1.2
edited by Boris Folgmann
on 2026/01/19 10:56
Change comment: There is no comment for this version
To version 2.2
edited by Boris Folgmann
on 2026/01/19 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -121,25 +121,23 @@
121 121  
122 122  === (% style="color:#172b4d" %)Cloning a project does not work. Why do I get an "fatal: unable to access ... Could not resolve host" error from Bitbucket?(%%) ===
123 123  
124 -(% style="letter-spacing:-0.006em" %)Mostly, this is due to a missing proxy configuration in your Git client. The following example uses git bash to configure the proxy. As an example, we
124 +(% style="letter-spacing:-0.006em" %)Mostly, this is due to a missing proxy configuration in your Git client. The following example uses git bash to configure the proxy of your company.
125 125  
126 126  1. Order or install git bash. You can install it yourself from [[https:~~/~~/git-scm.com/downloads>>https://git-scm.com/downloads]]
127 127  1. (((
128 -After installation start git bash and use these commands to configure git:
128 +After installation, start git bash and use the following commands to configure git. (% style="letter-spacing:-0.006em" %)You have to replace (%%)PROXY_NAME and PROXY_PORT by the correct values to make it work.
129 129  
130 130  {{code}}
131 -git config --global user.name "John Doe"
132 -git config --global user.email johndoe@example.com
131 +git config --global user.name john.doe@example.com # Jenkins will use this field to map commits to your user identified by your email address
132 +git config --global user.email john.doe@example.com # Bitbucket will use this field to map commits to your user identified by your email address
133 133  # Use the following only if you do not use any Intranet Git repos:
134 -# git config --global http.proxy http://sia-lb.telekom.de:8080/
134 +# git config --global http.proxy http://PROXY_NAME:PROXY_PORT/
135 135  # This one is better, you can specify the domain "devops.t-systems.net" you want to use the proxy for:
136 -git config --global http.https://devops.t-systems.net.proxy http://sia-lb.telekom.de:8080
136 +git config --global http.https://devops.t-systems.net.proxy http://PROXY_NAME:PROXY_PORT
137 137  {{/code}}
138 138  
139 -This config will be automatically saved to your user's //.gitconfig//. In case you use a different proxy to access DevOps-as-a-Service hosted BitBucket projects, use that in the statements above instead of `sia-lb.telekom.de:8080`
139 +This global git config will be automatically saved to the file //.gitconfig// located in the home directory of your user.
140 140  )))
141 -1. Older git versions might show TLS errors when connecting to HTTPS servers. Then only a more recent git bash will help.
142 -1. (% id="cke_bm_750982S" style="display:none" %) (%%)On some notebooks, Windows saves the global .gitconfig to the network drive. Switch it offline if you would not lose your .gitconfig from time to time ...
143 -1. Best solution to let git use a global config on your local drive is to set the env var {{code language="none"}}XDG_CONFIG_HOME{{/code}} since git will use the file {{code language="none"}}$XDG_CONFIG_HOME/git/config{{/code}} instead if the envvar is set. See [[https:~~/~~/git-scm.com/docs/git-config>>url:https://git-scm.com/docs/git-config||rel="nofollow" shape="rect" style="text-decoration: none;" class="external-link"]]
141 +1. You can set the env var {{code language="none"}}XDG_CONFIG_HOME{{/code}} if you want to have the config placed in another folder. When this env var is set, git will use the file {{code language="none"}}$XDG_CONFIG_HOME/git/config{{/code}}. See [[https:~~/~~/git-scm.com/docs/git-config>>url:https://git-scm.com/docs/git-config||rel="nofollow" shape="rect" style="text-decoration: none;" class="external-link"]]
144 144  
145 145