Access to the GitLab CE repository through TeamCity is limited to using only ssh key - login and password does not accept.
Error `Connection refused`
GitLab allow to log in using browser by ssh, access key and username/password.
My problem was the wrong value system var TEAMCITY_SERVER_OPTS on master server TeamCity
My GitLab CE is located at https://gitlab.org.com, but the value was not specified by -Dhttp.nonProxyHosts=*.org.com to exclude local addresses
That's all
Related
Having issues creating an ssh credential in Jenkins that allows access to GitLab. I have 2 AWS instances, one with GitLab and one with Jenkins. I would like to setup a multibranch pipeline in Jenkins to run a GitLab repo. I am able to create the pipeline and can access GitLab if I use a username/password credential (using "root"/initial password) but would like to use the more secure route of using a username/SSH credential. I have generated the SSH (of the ed25519 variety) in the GitLab instance (while in root). Then, in GitLab, supplied the public key to the root user. Then, in Jenkins, provided the private SSH key and set username as "root" in a username/SSH credential. When I try to run the pipeline using the username/SSH credential I get an error indicating that it is not authorized. Should I be using a different username? Should I be generating the SSH key in a different location?
Well, I figured it was something small I was missing. I was configuring the pipeline job for the http url of the repo rather than the SSH url. Once I changed that, it worked right away.
I want to make a webhook for when I push something to Git lab. Git lab is hosted by school and I've installed Jenkins locally. Now when I want to make a webhook http://localhost:8080/project/timely-frontend
Gitlabs says: "URL is blocked: Requests to localhost are not allowed". Are there any other possible ways to make a push webhook?
If Jenkins and Gitlab are both installed on the same internal (school) network, try using the internal private IP address of Jenkins as the webhook URL instead of localhost.
On the Jenkins host, this can be obtained using a command line ip addr show on Ubuntu and put that in the Gitlab webhook.
Keep in mind that especially if Jenkins is running on a non-standard port (8080), other firewalls outside your control could still block the connection.
I have Jenkins installed on an Ubuntu 18.04.3 LTS desktop PC on my localhost.
I also have an AzureDevOps repo on which I can successfully run a build, through a Jenkins pipeline job, connecitivity achieved via my AzureDevOps personal access token (PAT).
I am now trying to set up a Jenkins service connection or endpoint in AzureDevOps, to enable me trigger an Azure DevOps pipeline release whenever a Jenkins build completes successfully.
To achieve this in AzureDevOps, I am trying to set up access to Jenkins via a Jenkins service endpoint. The endpoint configuration requires among others, a Jenkins "Server URL" (screenshot below). Not surprisingly, AzureDevOps is unable to connect to my Jenkins instance as it's running on my local machine and therefore not publicly accessible.
Any suggestions on how I can overcome this hurdle would be most appreciated.
How to set up an Azure DevOps service connection or endpoint to my localhost Jenkins install
As we know, in order to receive the service hook notifications, you'll need to expose a port to the public internet.
To expose a port to the public internet, you can try to use the tool ngrok:
ngrok exposes local servers behind NATs and firewalls to the public
internet over secure tunnels.
Please check the document Configure a service hook for PR events for some more details.
Hope this helps.
I'm trying to setup an External Git Endpoint for out TFS 2015 update 4 system. I can't find any documentation on the correct way to set this up. What user name and password should I use? The build server service account?
It has nothing to do with the build service account if you mean creating a service connection (External Git service connection here).
For External Git service connection
The username should be the one which can connect to the external
Git repository server.
And the Password/Token Key should be the password or access token
for the specified username.
I'm currently playing around with Jenkins on Raspi within Docker (using dilgerm/rpi-jenkins image).
Now I have a problem with connecting to a Bitbucket Git repository.
When entering the repository url, I get (the commonly known) "Failed to connect to repository"
When using https and providing credentials (via Jenkins Credentials store), I get the error.
When using ssh and configuring the keys properly, I get the same error.
Now I am wondering if I have to configure the ssh-key withing the docker container (for the Jenkins user?). Currently, I have implemented the key on the hosting Raspi itself.
Or may it be required to configure/publish the ssl port of the Docker container on startup (-p parameter)?
Any help appreciated.