I am facing below issue when generating provisioning profiles from Jenkins pipeline script, please let me know the reason for this.
Finally, the issue is not related IOS, its with Jenkins master slave connectivity.
I have setup jenkins master slave using user name and Private key, in this case XCode commands are not able to connect to internet, but when I setup master slave using username and password, XCode is able to connect to Apple and I am not facing any issue in this case.
But, I need to find why this is not working in case user name and private key.
Thanks,
Raj4MS
Related
Azure DevOps Server 2020 with self hosted agents on a different server
I have a build, which is creating an artifact in Azure Artifacts, then a release pipeline is triggered which should download this artifact and do something with it. Previously, the output of a build was on a file share and it work as expected. When I switched to Azure Artifacts - the download artifact task (which is added automatically by Azure DevOps) fails with following:
All other build tasks work on this server without a problem, and also this release pipeline works as expected on other servers. How I can start to troubleshoot this issue as I don't see any meaningful error message?
According to your screenshot, I could reproduce the similar issue in Azure Devops Server.
But in the task, I could see the error message:
Failed in getBuildApi with error: Error: self signed certificate.
If you have the same issue, you could try the following methods:
1.You could re-config the agent with the self signed certificate.
.\config.cmd --sslcacert ca.pem xxxx
Here is a ticket about the detailed steps, you could refer to it.
2.You could check if you have set the firewall. Firewalls could block the download of artifacts
3.You could set the system environment :NODE_TLS_REJECT_UNAUTHORIZED=0 and restart the agent services.
We had similar problem with self-hosted agents but there was a minor difference - our agents were deployed in vnet.
If that's the case make sure that in vnet's subnet you have enabled Microsoft.Storage service endpoint.
Hope this will save someone tons of time.
I'm trying to configure Jenkins permanent node for remote Linux server.
My Jenkins master is on Windows.
Unfortunately I do not get the option to enter the hosts details and it populates by login ID in place of Hosts. (Please see snapshot)
I'm using ssh keys in the credentials for user root.
I guess I have all the required plugins.
I'm on the latest version of Jernkins.
Can you please suggest how can i fix the problem ?
I found out that my username was for someone reason set in the hostname under credentials for Jenkins.
Deleting the same from the Jenkins credentials resolved the hostname issue for the slave node and now I m able to enter the correct IP.
Im new on jenkins technologie.
I started with creating a jenkins job that pull code from gitlab to jenkins. this job did not worked as I had an issue tells that jenkins does not trusted the self signed certificate used by the gitlab server
issue in screenshot
Can I did some configuration from the jenkins inetrface (from web site) to allow cloning the self signed certificate.
Any help is really appreciated.
Thank you
Caution: To be used only by understanding the security issues that will crop-up by this behaviour.
My company is hosting github enterprise with a custom certificate and hence faced similar situation. Following is the work-around I've done to mitigate the issue.
Login to jenkins server as jenkins user (I've used sudo su jenkins to do this in my case).
Add the following lines to ~/.gitconfig and save.
[http]
sslVerify = false
Restart jenkins server.
From the image you haven't specified any credentials when trying to access your repo generally you would mention some form of credentials
apart from that your computer doesn't trust the certificate from gitlab you have to add the certificate into your git(installed location)
This link will give you a detailed explaination :)
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
I am trying to create pipeline via BlueOcean, however creation got stuck at the connection stage despite there is no error on connection.
After choosing "Where is your Bitbucket Server?" and
Putting credentials to "Connect to Bitbucket"
Pressing button "connect" see icon that it progressing for a second, but it do not progress to next step.
No error messages. Credentials are definitely correct, I had tested with wrong credentials and saw "Invalid username and/or password"
Details for Bitbucket and Jenkins
I have admin rights in both Bitbucket and Jenkins
Bitbucket
Installed v5.8.0 for testing new version on my desktop http://pc_name.company.com:7990
It seems working ok, I can add users, create repo, clone repo in jenkins
Jenkins
ver. 2.89.3 as well installed at the same PC, working ok as well
Installed Blueocean plugin 1.4.2
Screenshot attached link to screenshoot
I was stuck in a similar situation. I'm selecting "Bitbucket Cloud" as the selected repository.
I resolved my issue by giving full access to "Generate Password" option in my Bitbucket - in case it helps someone else
I need to run Jenkins over HTTPS.
I created the certificate and put it into the keystore. Then I launched Jenkins with the following options:
--httpsPort=8443 --httpsKeyStore=/etc/pki/java/cacerts --httpsKeyStorePassword=changeit
So far so good. But I had "peer not authenticated" error when deploying a file in the Artifactory.
According to a solution here I added my artifactory certificate to the keystore.
Now I can deploy files on Artifactory but Jenkins picked up the wrong entry from the keystore (the one of Artifactory). And I have a wrong certificate associated with Jenkins.
I was not able to specify the alias which should be used by Jenkins.
According to Jenkins docs it's possible to run Jenkins with the following options:
--httpsPort=443 --httpsCertificate=path/to/cert --httpsPrivateKey=path/to/privatekey
But in this case I'm not able to use my Artifactory certificate.
How can I run Jenkins with both Jenkins and Artifactory certificates ?
Trying different things I came to an idea to rename the alias of jenkins certificate.
The new alias is jenkins.
Strangely enough it solved my problem. For me it looks more like a hack than a solution. Put your real solution here and I'll accept it.