We are using Bamboo to deploy an application using Maven which is connecting to the Weblogic server. We are getting the error:
[ERROR] Failed to execute goal ***.maven-plugins:deploy-maven-plugin:1.0.27:deploy-request (default-cli) on project standalone-pom: Could not execute request: java.io.IOException: Server returned HTTP response code: 500 for URL: https://****/wdb-ctx-svc/service/deploy-log
Even though bamboo build fails the deployment continues in the background and is successful. Any help will be much appreciated.
Two points : Firstly, if your build is failing, your deployment should not trigger ideally. You can add a trigger to your deployment , that is , to run it only after successful build. Secondly is your web-logic server reachable ? I mean are you able to ping it or telnet to it ? I guess more of a network issue .
Related
I keep running into the same error with my setup. I want to configure jenkins and gitlab to automatically build some code on push events. I´m running the docker version of gitlab, while jenkins is running on localhost.
I tried setting up GitLab Jenkins Integration according to the documentation but the connection is continuously refused and I am asked to check my jenkins details(which are 100% correct, since Im using the standard configuration.)
When I tried setting up the webhook manually I´m confronted with a 422 error:
Picture of the response body
I think that this problem might be connected to the fact that I´m trying to set up everything locally. Any help would be appreciated.
When I am running sonarQube job in jenkins, it shows console output as in image. While downloading boot strap index, it shows an error as sonarQube server cannot be reached, but I am able to connect to that server from my local PC using that URL. Can anyone give me solution for this.
The above problem has resolved by doing two things
1) Installed java in sonarqube server that is accessible from jenkins
2) Installed right certificates
I'm trying to make sure that all tests complete before making a deployment. For this I have enabled Jenkins for my app. I can run builds successfully from git push and from Jenkins UI if myapp-bldr node is up and running, however if I try to run a build after a period of inactivity (basically wait for myapp-bldr to go down and free up a gear in my account), Jenkins build fails with below details:
> rhc app-deploy HEAD --app myapp
Deployment of git ref 'HEAD' in progress for application myapp ...
Executing Jenkins build.
You can track your build at https://jenkins-mydomain.rhcloud.com/job/myapp-build
Waiting for build to schedule............................................................................................
**BUILD FAILED/CANCELLED**
Please see the Jenkins log for more details via 'rhc tail'
!!!!!!!!
Deployment Halted!
If the build failed before the deploy step, your previous
build is still running. Otherwise, your application may be
partially deployed or inaccessible.
Fix the build and try again.
!!!!!!!!
An error occurred executing 'gear deploy' (exit code: 1)
Error message: CLIENT_ERROR: Failed to execute: 'control post-receive' for /var/lib/openshift/581e42c10c1e6666270001d8/jenkins-client
While Waiting for build to schedule... line is displayed in console, I can see build being queued in Jenkins UI, but since no builder nodes are available, it doesn't get picked up.
I'm guessing the issue is related to some timeout setting somewhere, but I can't tell for sure which one and whether I have the ability to tweak it.
I found this bug reported linking to the following pull request but I don't know if this is related and how to check if my app has the above config change applied to it.
I'm using "old" console (v2, not "NextGen" v3) with Jenkins ver. 1.642.2
I am using Jenkins along with Parameterized Trigger Plugin for triggering a job remotely. The build trigger is failed with console output as below
Server returned HTTP response code: 403 for URL: http://x.x.x.x:8080/job/jobname/buildWithParameters?token=buildcommand&build&delay=0
Connection to remote server failed, waiting for to retry - 10 seconds until next attempt.
Retry attempt #1 out of 5
Server returned HTTP response code: 403 for URL: http://x.x.x.x:8080/job/jobname/buildWithParameters?token=buildcommand&build&delay=0
Connection to remote server failed, waiting for to retry - 10 seconds until next attempt.
ERROR: Remote build failed for the following reason:
The build with URL 'http://x.x.x.x:8080/job/jobname/build?token=buildcommand&build&delay=0' from a browser is able to trigger the build remotely.
I only see the difference between two URL is one uses 'build' and other has 'buildWithParameters'.
Could you please help me to resolve the same.
Had the same issue where my remote jenkins was using credentials that were passed in by the master build.
To fix it I had to disable CSRF protection on the target Jenkins:
Log into your target Jenkins and go to Manage Jenkins
Go to Configure Global Security
Scroll down to Prevent Cross Site Request Forgery exploits
Uncheck it
Save changes
No need to restart Jenkins, just try the master job again.
Caveat: Obviously your Jenkins server is without CSRF protection... but it's probably safely behind a corporate firewall anyway, right?
I am using Jenkins Version 1.545 and Sonarqube Version 4.2.When I execute Sonarqube analysis using jenkins build,my build fails with the following error:-
Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.3.1:sonar (default-cli) on project : Can not execute SonarQube analysis: Unable to request: /batch_bootstrap/properties?project=abc.project:abc.project-java:javascript: Read timed out.
This cannot be a network issue because sonar and jenkins are on same server.
This was intermittent issue earlier but has now become very frequent.
Kindly help to resolve the issue.