Hi iam trying to integrate jenkins with Udeploy server.
When i test the connection using IBM UrbanCode Deploy Pipeline Plugin Configuration and the test connection option iam getting the below error
Error connecting to IBM UrbanCode Deploy: 503using URI: https://udeploy.oe.company/rest/state
I could confirm there is no issue with firewall. i am able to do a curl successfully to the url.
Iam not able to see anything in jenkins logs.
https://jenkinsurl.org/log/all
is there anyway i could check the logs of the plugin to see what is happening during connection?
Any help appreciated.
You might have an SSL issue. If using self-signed certs, try swapping the self signed certs. Note that Urbancode might be using the IBM JDK which has its own truststore, and you'll need to store the Jenkins certs there.
Related
When I try to link a jenkins project to my gitlab project, I have the following error :
Here is the form and the error message.
The jenkins project "test" does exists and the credentials are good.
The issue is probably not about the credentials but that gitlab seem to not be able to read the fields.
I tried with both chrome and Firefox.
I also tried to use webhook, but for services hosted on the same network, doc says it may be hazardous. So I'd rather use the first method.
Some information about my environment:
Linux Centos 7
jenkins and gitlab are built by docker-compose
hosted on localhost
jenkins and gitlab use different ports (8080 and 8081)
I found only one thread on the internet about it here but no answer were given.
Any ideas?
Thanks
This is my first post, I hope I did not make any mistake.\
I am trying to setup a Jenkins server using one of the Chef cookbooks from the supermarket. Unfortunately it is failing with the below error. The plugin recipe requires for the Global security configuration - "Enable CLI with remoting" to be enabled. Can anybody help me to enable it from a Chef recipe so that
java -jar jenkins-cli.jar -s http://localhost:8080 -remoting
installs the plugin.
Thanks
Here is the error log
java.io.IOException: No X-Jenkins-CLI2-Port among [X-Jenkins, null, Server, X-Content-Type-Options, X-You-Are-In-Group-Disabled, X-Hudson, X-Permission-Implied-By, Date, X-Jenkins-Session, X-You-Are-Authenticated-As, X-Required-Permission, Set-Cookie, Expires, Content-Length, Content-Type]
at hudson.cli.CLI.getCliTcpPort(CLI.java:311)
at hudson.cli.CLI.<init>(CLI.java:137)
at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:82)
at hudson.cli.CLI._main(CLI.java:615)
at hudson.cli.CLI.main(CLI.java:426)
Suppressed: java.io.IOException: Server returned HTTP response code: 403 for URL: http://localhost:8080/cli?remoting=true
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at hudson.cli.FullDuplexHttpStream.<init>(FullDuplexHttpStream.java:101)
at hudson.cli.CLI.connectViaHttp(CLI.java:163)
at hudson.cli.CLI.<init>(CLI.java:141)
As per the official documentation, remoting option is disabled by default. you can enable it by going to Configure Global Security. I don't think by programatically we can't enable it. For more details use this official link. Remoting Connection Mode | official Jenkins
This is the solution they are providing for your problem. Hope this helps.
Go to Manage Jenkins > Configure Global Security and choose "Fixed" or "Random" under TCP port for JNLP agents.
You can enable the remoting option by writing a bit of Groovy that gets run when Jenkins starts, but a better option is to configure the proper authentication and use the ssh or http methods.
https://github.com/chef-cookbooks/jenkins#authentication
See also: https://stackoverflow.com/a/51106793/3794873
We're using sonar scanner in our Jenkins pipeline to scan our code in a JNLP slave.
Both Sonarscanner and SonarQube are running in Docker containers in Openshift.
Our SonarQube server is behind a proxy without authentication.
Sonar scanner doesn't read any proxy information we submit to it through either -D http.ProxyHost in start command or in the configuration file. There is no way to reach our Sonarqube server behind the proxy. Could you help us figure out what to do?
I tried all ways to fix it but nothing works:
Passing -D https.ProxyHost -D https.ProxyPort (without http:// header)
putting them into sonar-scanner.properties
Passing proxy values in environment variables HTTP_PROXY, HTTPS_PROXY, JAVA_OPTS...
Doing a curl to the SonarQube server works -> Firewall is ok, connectivity is ok.
I couldn't find any issues tracker regarding this project in Github and the Jira tracker is closed to submitting new issues.
Has anyone encountered the same issue? There is another question related to this but no answer have been given: SonarQube scanner can't connect to server
Thanks,
Lain92
I had the same problem, and the way I found to fix this is using an environment variable.
export JAVA_TOOL_OPTIONS="-Dhttp.proxyHost=<PROXY> -Dhttp.proxyPort=8080 -Dhttps.proxyHost=<PROXY> -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=\"localhost|127.0.0.1\""
Note that "-Dhttp.proxyHost" does not have space between D and http.proxy.
I've managed to modify CCTray using a transport extension to connect to a local Jenkins server running on my locahost. I cannot however connect to the openshift remote jenkins server which has been setup on my account.
I can access it correctly from the Openshift Jenkins Web URL however I can't connect to it using the CCTray transport extension, it just times out. I think it's because it tries to connect to the actual port the Jenkins server is running on and this is being blocked.
Would installing and running the client tools/ssh comms fix this problem?
Or is this impossible to do. It is a very nice notifications tray program so would be great to get it working.
Any ideas would be very much appreciated!
So openshift only has 80 and 443 open externally and so if CCtray is trying to connect to the port itself then it won't be get to it. Can you configure CCtray to use the public URL to interact with Jenkins?
I´m starting to use jenkins and I have problems with the authentication when I deploy the project. I dont know where to write the credentials.
Authentication failed: The host was not known and was not accepted by the configuration
Where could I write my credentials? I dont see that point in the configuration panel. Many thanks!
The problem came on settings.xml file (in .m2), that did not have the appropriate login and password.
If you use ssh keys for authentication a server section like this can be used:
<server>
<id>repository-id</id>
<username>john/username>
<privateKey>/home/john/.ssh/id_rsa</privateKey>
</server>
still you may run into trouble in jenkins. You might have to run the maven deploy once in interactive mode to accept the e.g. RSA host key.