I've followed the https://docs.mesosphere.com/1.8/usage/tutorials/deploy-on-marathon/ guide for deploying an app from jenkins to marathon on dcos. I'm using a private registry hosted inside the dcos, and jenkins as well.
I'm getting the following output from jenkins console output,
[Marathon] Failed to update Marathon application:
[Marathon] Unauthorized (http status: 401)
any idea whats wrong?
I tried to create the app manually via marathon ui and it works fine.
Just got the url all wrong, it should be http://leader.mesos:8080/
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'm trying to configure the Jenkins Master/Slave on our AWS windows server. I looked at other posts and researched online and followed the steps. I installed Jenkins on the server, and changed the jenkins url to the ip address of the server by command ipconfig: http://x.x.x.x:8080/. On the Jenkins xml file, I added the line to the argument: --httpListenAddress=0.0.0.0.
I followed the online tutorial step by step guide to set up master and agent. On the agent computer, when i try to access the url, it shows This site can’t be reached. I added the port 8080 to the firewall. I also tried to ping from the agent to the master and it failed, said lost 4 100%. I am not sure how can I access jenkins master url outside of the server. Any help is appreciated.
The root cause is hidden in the comments, so for clarity posting it as an answer - looks like the problem was that the agent is running on a users laptop and it's trying to connect on a private IP of the jenkins server running in AWS. Things should hopefully work after connecting the agent on a public IP of the master instead.
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.
I am trying to trigger jenkins build whenever there is a push to GitLab.
I am referring to https://github.com/jenkinsci/gitlab-plugin.
When I test the connection for webhook it shows execution expired.
I am using:
Jenkins ver. 2.60.1
GitLab version 9.4.0-rc2-ee
Git lab plugin 1.4.6
The exact error message, clicking "Test setting" from GitLab:
We tried to send a request to the provided URL but an error occurred: execution expired
As mentioned in issue 128:
This looks and sounds like a configuration or network error.
Maybe your machine is not publicly available on the webhook address (firewall etc).
For instance, on Digital Ocean server, you would need to open up the port (mentioned in git-auto-deploy.conf.json) in the firewall:
sudo ufw allow 8866/tcp
Double-check though what you put in Manage Jenkins > Configure in term of Gitlab information (connection name, host url, credentials), as mentioned in jenkinsci/gitlab-plugin issue 391.
See GitLab Integration Jenkins: Configure the Jenkins server
It means issues in between jenkins server and gitlab or github server.
Like what I did:
I have set my local-IP:port/project/jenkins_project_name
http://192.168.1.21:8080/project/jenkins_project_name
and set the above URL in the gitlab webhook, it shouldn't work - right?
Because it's an IP that's private and not routable.
SO later I realized and set the public-IP and then hook worked.
http://public_IP:8080/project/jenkins_project_name
Note: To routable public-IP, you should expose port in your router [e.g. 8080 was for me or anything want ]
Hope this works.
I have faced the same issue.
In my case Jenkins is running in an AWS EC2 instance. I have resolved the issue by whitelisting the Public IP addresses of Gitlab on port 443 into the instance security group.
I have an jenkins job that builds and deploys to a tomcat7 instance on OpenShift
Tomcat7 cartridge is copied from http://cartreflect-claytondev.rhcloud.com/github/worldline/openshift-cartridge-tomcat
....
....
Starting tomcat cartridge
Timed out waiting for http listening port
Error deploying to gear
The last command on the build is
gear remotedeploy --deployment-datetime $deployment_dir
So when this job runs, it always fails, however tailing the server logs shows deployment goes fine and application is deployed successfully. Seems to me the jenkins job waiting tomcat startup but never receives a signal. Therefore "Timed out waiting for http listening port" and job thinks deployment failed and so job fails.
Is there anything that I can do to fix this? May be inside build script? Or make remote deploy not to expect an signal?
Please advise, thanks.
Updating this ticket(10/13/2014);
I see a difference in the console output between this failing job and a successful job. below excerpt is always on the successful job (which is deploying to jbossews) and failing job (which is deploying to the aforementioned cartridge) doesn't have that part at all!
I thought this could be an important difference. See below console output;
+ hot_deploy_enabled_for_latest_deployment
++ ruby_sdk latest_deployment_metadata.hot_deploy
++ oo-ruby -I/usr/lib/openshift/cartridge_sdk -rruby/sdk -e 'include OpenShift::CartridgeSdk; puts latest_deployment_metadata.hot_deploy'
+ enabled=
+ '[' '' == true ']'
+ return 1
It would probably be worth logging an issue with the person who built the cartridge here https://github.com/worldline/openshift-cartridge-tomcat, or you could try using one of the standard jbossews (which is tomcat) cartridges that openshift offers. Seems that all they did for this cartridge was rename everything that said "jbossews" to "tomcat". OpenShift offers tomcat 6, tomcat7, jboss as 7, jboss eap, and wildfly cartridges, I am sure one of those would work equally as well, and work correctly with jenkins also.
You could try the worldline-openshift-origin-release-4, it may fix your issue : http://cartreflect-claytondev.rhcloud.com/github/worldline/openshift-cartridge-tomcat?commit=worldline-openshift-origin-release-4