Git - Revision history

Olibouban: /* SSH */

2022-04-01T20:22:10Z

SSH

← Older revision		Revision as of 20:22, 1 April 2022
Line 25:		Line 25:
	* https://help.github.com/articles/generating-an-ssh-key/ .		* https://help.github.com/articles/generating-an-ssh-key/ .

	If connections are required with multiple users or multiple Git repository hosting system, please follow the link on how to manage multiple ~~account~~:		If connections are required with multiple users or multiple Git repository hosting system, please follow the link on how to manage multiple accounts:
	* https://www.attosol.com/manage-multiple-git-accounts/		* https://www.attosol.com/manage-multiple-git-accounts/

Olibouban: /* SSH */

2022-04-01T20:21:56Z

SSH

← Older revision		Revision as of 20:21, 1 April 2022
Line 22:		Line 22:

	== SSH ==		== SSH ==
	One possibility is to have a user (jenkins on a Continuous Integration (CI) system) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH key if it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at https://help.github.com/articles/generating-an-ssh-key/ .		One possibility is to have a user (jenkins on a Continuous Integration (CI) system) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH key if it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at
			* https://help.github.com/articles/generating-an-ssh-key/ .

			If connections are required with multiple users or multiple Git repository hosting system, please follow the link on how to manage multiple account:
			* https://www.attosol.com/manage-multiple-git-accounts/

	== .netrc ==		== .netrc ==

Rdaly: /* .netrc */

2021-02-18T17:50:46Z

.netrc

← Older revision		Revision as of 17:50, 18 February 2021
Line 40:		Line 40:
	</pre>		</pre>

	In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token these steps ]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.		In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token these steps]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.
	<pre>		<pre>
	machine github.com		machine github.com

Rdaly: /* .netrc */

2021-02-18T17:50:15Z

.netrc

← Older revision		Revision as of 17:50, 18 February 2021
Line 40:		Line 40:
	</pre>		</pre>

	In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [[https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token \| these steps ]]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.		In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token these steps ]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.
	<pre>		<pre>
	machine github.com		machine github.com

Rdaly: /* .netrc */

2021-02-18T17:49:45Z

.netrc

← Older revision		Revision as of 17:49, 18 February 2021
Line 40:		Line 40:
	</pre>		</pre>

	In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [[~~these steps \|~~ https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token ]]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.		In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [[https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token \| these steps ]]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.
	<pre>		<pre>
	machine github.com		machine github.com

Rdaly: /* .netrc */

2021-02-18T17:49:02Z

.netrc

← Older revision		Revision as of 17:49, 18 February 2021
Line 39:		Line 39:
	git config --global user.name "Your Name"		git config --global user.name "Your Name"
	</pre>		</pre>

			In 2021, GitHub depreciated the use of the password and instead recommends using a personal access token instead or other authentication methods. To create a token, follow [[these steps \| https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token ]]. Save the token after creating it. Then in the <code>~jenkins/.netrc</code> file, replace the password with the new token.
			<pre>
			machine github.com
			login gitUserName
			password <personal access token>
			</pre>

			On the command line, if prompted for a password, use the token instead.

	== Test ==		== Test ==
	Make sure you can clone some repository using git clone, without having to enter at the prompt the login and password of the Git user.		Make sure you can clone some repository using git clone, without having to enter at the prompt the login and password of the Git user.

Rdaly: /* SSH */

2018-05-22T18:42:51Z

SSH

← Older revision		Revision as of 18:42, 22 May 2018
Line 22:		Line 22:

	== SSH ==		== SSH ==
	One possibility is to have a user (jenkins on a Continuous Integration (CI) system) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH is it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at https://help.github.com/articles/generating-an-ssh-key/ .		One possibility is to have a user (jenkins on a Continuous Integration (CI) system) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH key if it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at https://help.github.com/articles/generating-an-ssh-key/ .

	== .netrc ==		== .netrc ==

Rdaly: /* SSH */

2018-05-22T18:42:00Z

SSH

← Older revision		Revision as of 18:42, 22 May 2018
Line 22:		Line 22:

	== SSH ==		== SSH ==
	One possibility is to have a user (jenkins on a CI) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH is it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at https://help.github.com/articles/generating-an-ssh-key/ .		One possibility is to have a user (jenkins on a Continuous Integration (CI) system) have an SSH key to be added to the GitHub account for that Linux user. For instance, log in as 'jenkins' on the CI system. Then generate an SSH is it does not already exist, and add the SSH key to the GitHub account. To do so, follow the instructions listed at https://help.github.com/articles/generating-an-ssh-key/ .

	== .netrc ==		== .netrc ==

Rdaly: /* Storing the Git Credentials */

2018-03-21T21:32:28Z

Storing the Git Credentials

← Older revision		Revision as of 21:32, 21 March 2018
Line 10:		Line 10:

	== Storing the Git Credentials==		== Storing the Git Credentials==
	One possibility is to store the Git credentials on the command line as the Jenkins user that runs the scripts. To do so, please refer to the [https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage Git Tools Credentials ] documentation page:		One possibility is to store the Git credentials on the command line as the Jenkins user that runs the scripts. To do so, please refer to the [https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage Git Tools Credentials] documentation page:

	* ''The '''store''' mode saves the credentials to a plain-text file on disk, and '''they never expire'''. This means that until you change your password for the Git host, you won’t ever have to type in your credentials again.''		* ''The '''store''' mode saves the credentials to a plain-text file on disk, and '''they never expire'''. This means that until you change your password for the Git host, you won’t ever have to type in your credentials again.''

Rdaly: /* Git User */

2018-03-21T21:31:46Z

Git User

← Older revision		Revision as of 21:31, 21 March 2018
Line 6:		Line 6:
	A Git user must be provided by the development organization. This Git user must have <b>clone, pull, and push</b> access to the projects' repositories to be on-boarded. This Git user is used for <b>all</b> projects.		A Git user must be provided by the development organization. This Git user must have <b>clone, pull, and push</b> access to the projects' repositories to be on-boarded. This Git user is used for <b>all</b> projects.

	Scripts started by the <code>jenkins</code> user clone and push to and from the repository; The Git user login and password must be set ~~as per this page:~~		Scripts started by the <code>jenkins</code> user clone and push to and from the repository; The Git user login and password must be set
	[https://confluence.atlassian.com/display/STASH/Permanently+authenticating+with+Git+repositories#PermanentlyauthenticatingwithGitrepositories-Usingcredentialcaching]		[https://confluence.atlassian.com/display/STASH/Permanently+authenticating+with+Git+repositories#PermanentlyauthenticatingwithGitrepositories-Usingcredentialcaching as per this page:]

	== Storing the Git Credentials==		== Storing the Git Credentials==