Troubleshooting Gitlab - Revision history

Carignani at 12:22, 24 July 2019

2019-07-24T12:22:06Z

← Older revision		Revision as of 14:22, 24 July 2019
Line 25:		Line 25:
	Check the following:		Check the following:

	=== ~~Log~~ into Gitlab with your EOL ===		=== 1. Check logging into Gitlab with your EOL ===
	Are you able to sign in at https://forge.etsi.org/gitlab/users/sign_in with your EOL account?		Are you able to sign in at https://forge.etsi.org/gitlab/users/sign_in with your EOL account?

	=== Check group membership and permissions ===		=== 2. Check group membership and permissions ===
	Once logged in, visit <nowiki>https://forge.etsi.org/gitlab/mec</nowiki> . In case you have “Request group access” below the group name please click on it.		Once logged in, visit <nowiki>https://forge.etsi.org/gitlab/mec</nowiki> . In case you have “Request group access” below the group name please click on it.

	=== Check your SSH setup ===		=== 3. Check your SSH setup ===
	Once set up your SSH keys, to verify they are working you need to issue:		Once set up your SSH keys, to verify they are working you need to issue:
	ssh [[Mailto:git@forge.etsi.org\|git@forge.etsi.org]]		ssh [[Mailto:git@forge.etsi.org\|git@forge.etsi.org]]
	And verify that you see the following:		And verify that you see the following:
	''PTY allocation request failed on channel 0''		'' PTY allocation request failed on channel 0
			Welcome to GitLab, <YOUR_EOL_USER>!
			Connection to forge.etsi.org closed.''
			'' ''

	~~''Welcome to GitLab, <YOUR_EOL_USER>!''~~		=== 4. Verify that remote URL is correct ===

	''~~Connection to forge.etsi.org closed.~~''		The URL for the ''origin'' remote should be in the following format (where 'group' and 'project' are replaced by your group and project names):
	'' ''
	~~# Change the URL for the~~ ''~~origin~~'~~' remote to: [[Mailto:~~git@forge.etsi.org:~~mec~~/~~gs011-app-enablement-api~~.git~~\|git@~~forge.etsi.org~~:mec~~/~~gs011-app-enablement-api~~.git]]		* '''git@forge.etsi.org:<group>/<project>.git''' for SSH access,
	$ git remote set-url origin ~~[[Mailto:git@forge.etsi.org:mec/gs011~~-~~app-enablement-api.git\|git@forge.etsi.org:mec/gs011-app-enablement-api.git]]~~		* '''https://forge.etsi.org/rep/<group>/<project>.git''' for SSH access,

			To change the remote URL, use:

			$ git remote set-url origin <CORRECT-URL>

Carignani at 12:16, 24 July 2019

2019-07-24T12:16:13Z

@@ Line 1: / Line 1: @@
 === Clone on Windows: Could not resolve hostname ===
 __FORCETOC__
 If you clone a project using SSH, Windows may answer:
@@ Line 20: / Line 21: @@
 For example, if you developed a new feature you would like to contribute in a new branch called "new-feature", you will want to issue the command:
   git push origin new-feature:new-feature

Carignani at 11:51, 12 November 2018

2018-11-12T11:51:59Z

← Older revision		Revision as of 13:51, 12 November 2018
Line 1:		Line 1:
	== Clone on Windows: Could not resolve hostname ==		=== Clone on Windows: Could not resolve hostname ===
			__FORCETOC__
	If you clone a project using SSH, Windows may answer:		If you clone a project using SSH, Windows may answer:

Line 11:		Line 11:
	# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code>		# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code>
	# Try using HTTPS instead of SSH		# Try using HTTPS instead of SSH
	~~__FORCETOC__~~
			=== "Authentication Failed" when pushing on master ===
			If you receive a "Authentication error" while pushing your changes to the ''master'' branch, you most probably have a role "Developer" in the project, which does not allow you to push onto the master branch.

			You will want to push to another branch (an existing one or a newly created), by issuing the following git command (or similar operation using a visual tool):
			git push origin <local-branch>:<remote-branch>

			For example, if you developed a new feature you would like to contribute in a new branch called "new-feature", you will want to issue the command:
			git push origin new-feature:new-feature

Carignani at 13:20, 2 July 2018

2018-07-02T13:20:36Z

← Older revision		Revision as of 15:20, 2 July 2018
Line 11:		Line 11:
	# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code>		# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code>
	# Try using HTTPS instead of SSH		# Try using HTTPS instead of SSH
			__FORCETOC__

Carignani: Created page with "== Clone on Windows: Could not resolve hostname == If you clone a project using SSH, Windows may answer: ssh: Could not resolve hostname forge:etsi.org:_username_: Name or..."

2018-07-02T13:19:56Z

Created page with "== Clone on Windows: Could not resolve hostname == If you clone a project using SSH, Windows may answer: ssh: Could not resolve hostname forge:etsi.org:_username_: Name or..."

New page

== Clone on Windows: Could not resolve hostname ==

If you clone a project using SSH, Windows may answer:

ssh: Could not resolve hostname forge:etsi.org:_username_: Name or service
not known.

How to fix:

# Check that there are not mispellings in the URL
# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code>
# Try using HTTPS instead of SSH