I am trying to execute a CI/CD project. Everytime i am trying to create a job and trying to save my job it pops up an error. I have gone through a few issues available on the internet, but none of them have resolved the issue.
Can anybody help in this regard? Thanks
Tomcat 9 Server
Java 16.0.1
Jenkins 2.361.1
I would suggest do following:
Check the Jenkins logs on server and try to fix.
If don't work, try to restart your Jenkins.
Related
I have a job running on a WindowsServer2012R2 agent. The job is pausing between 2 plugins (BuildNameSetter v1.6.8 and DiscardOldBuilds v1.0.5) as you can see below:
13:05:25 Set build name.
13:05:25 New build name is '5.0.811.0'
13:20:21 Discard old builds...
I've started to notice this strange behavior after upgrading Jenkins Master from 2.89 to 2.190.3.
It's frustrating to see your job taking a 15 minutes nap!
Is this a server side issue or a agent side one?
Can someone give me some hints about how to tackle this problem?
Did you experience something similar?
you could have a look at jenkins central logs /log/all to see if there is any java stacktrace error in there
Then you should first try to isolate the issue. try deactivating the build name setter step first. then try to disable the discard old build. then enable build name setter again and keep discard old build deactivated
now you know which plugin is causing the issue try to downgrade or upgrade the plugin that makes your build hang
if the issue comes from discard old build, I would try to remove clean the job's workspace and remove builds manually
look for your issue on jenkins's jira system, upvote. create a ticket if you have not found another user experiencing the same issue
Finally you should be able to find workarounds for these plugins
Today I've upgraded Jenkins to a newer version (2.263.2) on the Jenkins server and the 15 minutes pause dissapeared.
I have a problem where the build status from my jenkins server is not showing in Bitbucket. I have followed every step here: Bitbucket Cloud Build Status Notifier Plugin and I have also added the Bitbucket Oauth plugin.
The system log looks like this:
It seems like there is something wrong with the build data. I am not an expert and I have followed all the steps as I should, what could the problem be?
Feel free the ask questions if you need more info!
I have the same issue after upgrade Jenkins... I don't know where is the problem, the warning message is at:
https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/scm/GitScmAdapter.java#L59
Update:
Ok I solve the issue after downgrade Git plugin to 3.9.1
Cheers
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
As the stated title I ran into a problem when trying to hook TFS to Jenkins in order to trigger build automatically when code is committed to the server.
Here's the detailed picture.
FYI: I setup Jenkins on my localhost:8080 as default, my project I use on TFS also coded on local machine and use local DB (no idea if that's the problem). Project built successfully on Jenkins.
Please help me fix this problem and explain details if possible, since I'm new to Jenkins as well as CI/CD. Thanks in advance! :)
Use IP address instead of localhost in Jenkins base URL.
Make sure you have projects configured in Jenkins.
https://www.visualstudio.com/get-started/integrate/integrating-with-service-hooks-vs
I'm trying not (not hard enough it seems) to get our jenkins server to provision a jenkins-slave using docker.
I have installed the Docker-plugin and configured it according to the description on the page. I have also tested the connectivity and at least this part works.
I have also configured 1 label in the plugin and in my job. I even get a nice page showing me the connected jobs for this slave.
When I then try to start a build nothing really happens. A build is scheduled, but never started - (pending—Waiting for next available executor).
From the message it would seem like jenkins is not able to start the slave via docker....
I'm using docker 1.6.2 and the plugin is 0.10.1.
Any clue to what is going on would be much appreciated!
It seems the problem was that I had added the docker version in the plugin config. That is apparently a no-go according to this post