I am trying to setup jenkins on ec2 instance,
but when I was installing default plugins on homepage,
it failed over and over again without any prompts.
Thank you
I had tried to reboot my instance and setup a new instance, but not worked.
Related
Before installing Git plugin in my Jenkins all my jobs were working properly. After installing the Git plugin, my Jenkin get restart and after that my jobs are not displaying in dashboard. When I check in system log, I found issue stating "Failed to load struct, Failed to load x job, Failed to load Y job..... And so on".
How can I resolve this?
You need to upgrade Jenkins to the latest version. This will solve the problem.
Jenkin Project - I configure the Build setup in Batch file in below statement
aws s3 cp ./dist/first-ci-project s3://first-ci-cd-project --recursive
but result is
'aws' is not recognized as an internal or external command,
But Command Prompt i run the above command its working good. Pl help me.
Are you running the aws command in a jankins slave? If so please check whether aws cli command tool is installed on the slave and the location of the aws cli is added to the environment variables.
If you are running on the jenkins master, same as above. Please check if you have added the aws cli folder location is added as environment variable under jenkins master.
I had the similar issue, I had make sure that the user with which aws CLI is installed is same as the one which Jenkins is using during the runtime
I installed Jenkins on my -AWS EC2 Ubuntu- and on the same server I'm running Docker. what I'm trying to do is to build a pipeline via Jenkins on that EC2 Instance. my jenkinsfile stored on Github
When I run the pipeline I get the following error:
Jenkins’ doesn’t have label ‘docker'
How to solve this problem?
I went to manage Jenkins -> global tools and also to configure system
but non of these solve the problem.
Any suggestions?
I migrated Jenkins with thinBackup plugins. When I restart my new Jenkins master, accessing it via http://new_jenkins_ip:8080 will redirect me to https://old_jenkins_domain.
My old Jenkins runs with services, it was setup long ago. My new Jenkins runs in k8s, I edited stable/jenkins chart and deployed it with Helm.
At first, I thought Jenkins URL is the cause, so I change configuration in jenkins.model.JenkinsLocationConfiguration.xml (according to this) and restart Jenkins by killing its pod (I deploy new Jenkins in k8s). But it's still redirecting to https://old_jenkins_domain.
I also try copying entire JENKINS_HOME (this) directory and yes, it's still redirecting to https://old_jenkins_domain.
Another problem is that I'm using github-oauth and matrix-auth plugins and if I don't install these before performing thinBackup migration, Jenkins will fail to start up and restart itself forever. I want to know why.
I actually can access http://new_jenkins_ip:8080/login but when I hit login, github-oauth just throw an NullPointerException.
I might try this python to migrate plugins because I think thinBackup can't migrate all the github-oauth config.
It's github-oauth plugins that keep directing me to my old site. I new oauth app in github and let it redirecting to my new IP.
I was using Jenkins 1.7.4 version in RHEL Linux server. I can able to configure the slave using "launch agent via execution of command on the master" option during slave setup.
Now we have upgraded jenkins to 2.121.1 version. Now we unable to find that option in the upgraded version.
How to fix this issue.
Manually I Installed command-launcher, jdk-tools plugin. Then it works.