I have the latest version of Jenkins, and I launched it with
"java -jar jenkins.jar."
Then I got an error
????: Failed Loading plugin rest-plugin hudson.util.IOException2: Unable to create instance of org.hudsonci.rest.plugin.RestPlugin from rest-plugin
After that, when I visit Jenkins at localhost:8080, Jenkins shows "New version of Jenkins (2.1.0) is available", and download link to Hudson.war 2.1.0**
Did the Jenkins merge back into Hudson? As far as I know, most people are saying Jenkins will be better than Hudson.
Is there anybody that knows what happened?
It sounds like what happened is this: you kept your old settings when you upgraded to Jenkins. This included the update URL, so Jenkins is polling the old Hudson url for updates. Once you fix this, you should be golden. To fix it, just do this:
Under Manage Jenkins, go to Manage Plugins and click on the advanced tab. Make sure that the Update URL is set to http://updates.jenkins-ci.org/update-center.json
Related
Whenever i try to save a new Maven Project in Jenkins i can press apply or save without anything happening or any error messages showing up. When i switch from Chrome to Firefox i get a "Error" popup which just contains an empty http body.
The logs dont show any problems or errors. The weird thing is Freestyle project do work just fine.
What i've tried :
-Update Jenkins & Plugins
-Rollback some plugins to older versions
-deinstall some unused plugins
-set java home for maven
Is there any way to fix it?
Same configuration is working with window 10. but when i tried same configuration run with ubuntu, its showing an error.
error message while running with jenkins
The clean plugin cannot delete the named folder. Make sure the Jenkins has the right to delete the folder and that it is not locked in some other way.
By the way: Copy the text of your error into the question, don't make a bad photo.
Some process has hold of the file /home/xelpmoc-06/Documents/Doc/zerodha/target/classes/LoginZerodha/Zerodha/App.class.
Java process or Eclipse or some other program is doing some job with it. So that's why its showing that error. So please kill Java Process or restart Eclipse. May be your jenkins build failure, also can cause this to happen. So if nothing works out please restart your jenkins itself.
Here I am attaching a link that may be helpful to you. Please go through this. Hope this helps.
I installed Jenkins on to 2 new machines no-problemo!
But, when attempting to integrate Maven, I am having "command not found" in my Jenkins log, yet I can run mvn no problem in the command line.
So, I thought it was a PATH issue - so I added the /bin and also the / (of the location where Maven is extracted to), yet I'm still getting the error.
I tried adding the PATH to my ~/.bash_profile as well, so my current PATH is:
$PATH:/usr/local/bin:/Users/jenkins/apache-maven-3.5.2/bin:/Users/jenkins/apache-maven-3.5.2
Still, Jenkins will not find Maven. I do NOT want to globally install Maven, as it may affect the other 5 build servers we have that are working with Maven correctly (not sure how it's working).
The issue was resolved by simply re-connecting the Jenkins Slave. Thanks for your feedback!
I am using selenium maven project with Jenkins and when I run build now, execution is running in background for which I am able to see output in consol but my browser and all execution on browser is NOT visible.
I tried searching around and change Jenkins service by checking allow window interaction checkbox but still not able to view it. I m running on window 10 and running with local(http://localhost:8080). I tried with Chrome, firefox & IE and all have same behavior of Not visible.
I used command "mvn clean test" in Build - Execute Windows batch command.
Same project is running with Eclipse & CMD very well with visible execution.
I am using Jenkins version 2.46.3.
Anyone experienced this? Any idea ?
Run Jenkins or slave from command line using war or jar provided, other option to try: check 'Allow service to interact with desktop' in Services.
After lots of search & troubleshoot, I found solution as I installed Jenkins as Window version (.exe) so I uninstalled it and downloaded Jenkins from official jenkins website(https://jenkins.io/download/) by clicking on Generic Java Package(.war) and then went into Command prompt and went to path where my Jenkins.war file dowloaded and install using java -jar jenkins.war and reregister with different accountname and password (created new account so it won't pull up the old account) and the Execution started DISPLAYING ON BROWSER. Hope this helps.
I'm setting up Jenkins for the first time and running into an issue where Jenkins does not appear to even attempt to execute the Ant task I've specified.
I've defined my JDK and Ant installations under Manage Jenkins.
I've setup my Job to Invoke Ant using the Targets 'war-all'
Whether I force a build or wait for it to naturally execute after the next commit, there is nothing in the Build Console Output about attempting to execute the ant task.
Here is a sample Console Output:
Any ideas as to why it might not be executing would be appreciated. Also tips on how I can find more logging from Jenkins which might provide clues as to why it is not executing would be helpful. I'm not sure what Logger I might specify or even then where the logging information is written on the file system.
The problem was that I was selecting "Build multi-configuration project" as the type of my job. When I select "Build a free-style software project" as my job type the Ant task will execute after the SVN update.
Looks like your svn doesn't see any changes and therefor is not re-building the module.
Try deleting the workspace and re-trigger the build, or change the check-out strategy to 'Always check out a fresh copy'.
I faced the same problem when upgraded to 1.417 from 1.413.
The combobox "Ant version" disappeared from "Invoke ant" build step. It should be here.
I just downgraded to 1.413 and continue to work.
So, the answer is - you should specify "Ant version" in project settings. But you cannot do it in 1.417.
It seems like Jenkins doesn't like when you create a job before configuring JDK. If that happens, job will never work properly. So, for me the solution was:
Delete job.
Configure JDK
Re-create job.
Probably the same problem may arise when job's JDK is deleted.
In my case,ant default target was not being picked up from build.xml so I had to explicitly mention the target in jenkins option.
I resolved this by changing the jdk to default and then again switched to what was set earlier.This is a workaround but not sure how this resolved.