We've been configuring an automated deployment using WebSphere Deployer Plugin v 1.3.4 for IBM WAS 8.5.
We have finished all the pipeline and checked the conecction to SOAP, all works right, but we have one last problem, jenkins throws this failure:
Jenkins Console Output
Generating EAR For Artifact: xxxxxxxxxx
Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact 'xxxxxxxxxx' is installed: ADMA0089E: The AppManagement MBean is not found.
We have researched a lot, but we can determine which is the problem?
Note: We configure the Generic JVM arguments with the IBM suport, these are the arguments we added:
Generic JVM arguments
-Dcom.ibm.team.server.monitoring.mbean.server=WebSphere
-Djavax.management.builder.initial=
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=10033
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Check WebSphere Connectivity Port setting in Jenkins, it should be SOAP port of Deployment Manager(default: 8879), not SOAP port of Websphere Application Server.
Related
I am in the process of upgrading jenkins server to latest LTS version (2.204.2 to 2.251.2) in my current work environment.
In present scenario jenkins installation and configuration is an automated process via chef.
The problem starts here :
i need to upgrade my jenkins server to latest LTS version via chef cookbook
remoting option has been obsolete in latest jenkins version
my present cookbook uses jenkins_script resource (using jenkins 6.0 cookbook from supermarket) to run groovy scripts
i am able to upgrade my jenkins server but unable to execute groovy scripts via jenkins-cli, its picking remoting option all the time and failing even though its obsolete in latest version
Is there any automated way to change protocol from remoting to ssh/http when chef client runs
.
Any valuable inputs will be helpful
Getting below error in Jenkins during the last step of creating pipeline from github using personal access token -
Sep 03, 2017 7:34:43 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?
Jenkins ver. 2.78
openjdk version "1.8.0_141"
I am running jenkins using vagrant inside CentOS 7.
It worked fine after changing my machine from Mac OS to Ubuntu & upgrading the blueocean plugin to "1.3.0-beta-2".
The reason could be proxy or some other setting which was not allowing the communication to happen.
Since it took fair amount to time to debug, I hope someone else doesn't waste their time & check their machine configs before putting a bug.
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 am getting error while integrating jenkins with JIRA.
Both JIRA and jenkins are hosted on same server.
Provided application URL in JIRA is my-ip:8080
error: No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue.
What ports are JIRA & Jenkins running on? Usually JIRA and Jenkins like to run on the same port (8080) by default. You can change the default port for starting Jenkins as ala something like java -jar jenkins.war --httpPort=9090
Did you see this link: Configuring the Atlassian JIRA plugin to work with Jenkins CI system
My Grails jobs fails on Jenkins provided by Cloudbees because they require to accept UAA agreement.
Is there a way to accept agreements?
Jenkins Grails plugin can be configured to run in non-interactive mode, that should fix this issue