I'm trying to install Jenkins on win 10.
all the plugins failed to install on the startup process and even after that for jenkins GUI.
i'm running with jenkins 2.264,jdk-8u271-windows-x64 and windows 10 pro.
please advise what am I doing worng.
this is one of my error messages ->
most of the errors look the same. (Java issue)
java.io.IOException: Failed to load: Build Timeout (1.20)
- Plugin is missing: token-macro (1.5.1)
at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:951)
at hudson.PluginManager$2$1$1.run(PluginManager.java:551)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:1129)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2020-12-24 18:52:29.987+0000 [id=46] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin ECharts API Plugin v4.9.0-2 (echarts-api)
java.io.IOException: Failed to load: ECharts API Plugin (4.9.0-2)
What you have posted is an incomplete pair of error segments (they should start w/timestamp). Nevertheless, not sure how you installed the plugins, but you appear to be missing some key dependencies.
Failed to load: Build Timeout (1.20) - Plugin is missing: token-macro (1.5.1)
token-macro is a dependency on Build Timeout, and appears not to installed.
Failed to load: ECharts API Plugin (4.9.0-2)
This error is incomplete, but I would suspect is also missing a dependency. You can see what is installed on the ${JENKINS_URL}/systemInfo page, "Plugins" section. Not sure what you will see on the ${JENKINS_URL}/pluginManager/installed, but I suspect many plugins will be greyed out. It should explain why (ie: missing).
You would have to explain how you installed what you did to guess how got are missed. Rarely plugins simply declare as "optional" what should be declared as required, but goes undetected since almost everyone always installs the dependency.
Usually, they all point to a single missing plugin or a chain up from one. Check the logs and trace. Get all the pairs Failed to load: x - Plugin is missing: y. Install the ones said to be missing. Failing that, stop Jenkins, delete the /plugins directory and install them from scratch again. If the hpi/jpi package is corrupted, you may need to stop Jenkins, delete the package and the exploded directory inside plugins.
You may also find this response useful, as well as the Jenkins Book Managing Plugins and the new Plugin Installation Manager Tool for Jenkins
Related
I have two Jenkins both on the same version 2.289.3. One has this plugin working fine (plugin version 1.54) but the other is failing with the error in the below error code. It's failing on the plugin extensions
io.jenkins.plugins.casc.ConfiguratorException: No configurator for the following root elements jobs
at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:734)
at io.jenkins.plugins.casc.ConfigurationAsCode.checkWith(ConfigurationAsCode.java:776)
at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:761)
at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:637)
at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:306)
at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:298)
Caused: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)
These two Jenkins run off of different config repositories but the major files are all the same. I removed the plugin from the startup plugins.txt file and tried installing it on a running Jenkins but that results in the same problem when I then restart Jenkins (below image and error)
org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
I've also tried copying the plugins from other repositories that have no problems but here it just keeps failing. Any advice on what the problem might be would be great
The solution to my problem was that I was missing another plugin. The plugin in question was job-dsl - specifically version 1.74 of this plugin. I found some of the later version also caused problems so had to pin it to 1.74
I am facing some issue while installing "Deliver Pipeline Plugin" .The dependency plugin "Jquery Plugin" not installing . I am getting the following error:
I am following your Jenkin's tutorial . I am facing some issue while installing "Deliver Pipeline Plugin" .The dependency plugin "Jquery Plugin" not installing . I am getting the following error:
java.io.IOException: Downloaded file C:\Program Files (x86)\Jenkins\plugins\jquery.jpi.tmp does not match expected SHA-1, expected 'eOnfdKAq1jTJLA6XJ5qfQiXBY6o=', actual 'DIij6KoUcjAFwoa79NMRslzuINs='
at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1810)
at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:149)
at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1963)
at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194)
at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1680)
at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1874)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Unknown Source)
Please help me to resolve this issue.
Please help me to resolve this issue.
One reason for the above error is the network connectivity.
If you are in any corporate network and you have not set proxy in jenkins then you will get the above error.
Please open C:\Program Files (x86)\Jenkins\plugins\jquery.jpi.tmp and see what is written in the file.
To set proxy in jenkins please refer the link in comment section.
Regards,
Anil
I upgraded Jenkins to 2.32.3 version (in place upgrade) after taking necessary backups (THIN) or $JENKINS_HOME and Jenkins is now UP and running.
Under Manage Jenkins > Manage Plugins, I see the following RED error:
Manage Jenkins
Correct
There are dependency errors loading some plugins:
Environment Injector Plugin v2.1.3
envinject-api v1.2 is missing. To fix, install v1.2 or later.
While trying to install Environment Inject Plugin 2.1.3, the logs (during download/install) shows the same error:
Installing Plugins/Upgrades
Preparation
Checking update center connectivity
Success
Environment Injector Plugin
Failure -
java.io.IOException: Failed to dynamically deploy this plugin
at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1895)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1652)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Failed to install envinject plugin
at hudson.PluginManager.dynamicLoad(PluginManager.java:873)
at hudson.PluginManager.dynamicLoad(PluginManager.java:813)
at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1891)
... 5 more
Caused by: java.io.IOException: Environment Injector Plugin v2.1.3 failed to load.
- envinject-api v1.2 is missing. To fix, install v1.2 or later.
at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)
at hudson.PluginManager.dynamicLoad(PluginManager.java:863)
... 7 more
Where can I get this envinject-api 1.2 plugin? Should I go grab the Github project (clone it) and build the Maven project and put the hpi file under $JENKINS_HOME/plugins folder?
Under Available plugins tab, I don't see an option to select a given version (only 2.1.3 is available). I don't see envinject-api 1.2 plugin listed there either that I can select. My understanding it, selecting Environment Inject 2.1.3 should auto grab all of its dependent plugins for free per it's MANIFEST file.
$ cat $JENKINS_HOME/plugins/envinject/META-INF/MANIFEST.MF
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: nenashev
Build-Jdk: 1.8.0_121
Extension-Name: envinject
Specification-Title: The Jenkins Plugins Parent POM Project
Implementation-Title: envinject
Implementation-Version: 2.1.3
Plugin-Class: org.jenkinsci.plugins.envinject.EnvInjectPlugin
Group-Id: org.jenkins-ci.plugins
Short-Name: envinject
Long-Name: Environment Injector Plugin
Url: https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin
Compatible-Since-Version: 2.0
Plugin-Version: 2.1.3
Hudson-Version: 1.625.3
Jenkins-Version: 1.625.3
Plugin-Dependencies: envinject-api:1.2,ivy:1.21;resolution:=optional,m
atrix-project:1.7,script-security:1.22
Plugin-Developers: Gregory Boissinot:gbois:gregory.boissinot#gmail.com
,Oleg Nenashev:oleg_nenashev:o.v.nenashev#gmail.com,Manuel Recena:rec
ena:recena#gmail.com
For some reason Jenkins plugins (didn't download the dependent plugins per the Manifest file).
As envinject-api plugin was not listed in the AVAILABLE plugin tab (under Manage Jenkins > Manage Plugins section), I had to manually download the .hpi / .jpi file directly from the following download plugins URL and then I placed the file in $JENKINS_HOME/plugins folder.
https://updates.jenkins-ci.org/download/plugins/
wget https://updates.jenkins-ci.org/download/plugins/envinject-api/1.2/envinject-api.hpi
Restarted Jenkins sudo service jenkins restart (or any other way you have setup) and this issue went away from both Jenkins GUI and from tail -f /var/log/jenkins/jenkins.log
PS: Don't just randomly select a latest version of any plugin or it's dependent plugin. It may not work and break more other plugins as it depends upon your current Jenkins version.
Found this link for Juseppe, not sure how relevant is this but seems interesting: https://github.com/yandex-qatools/juseppe
Trying to install "Build Pipeline Plugin v1.5.6" fails due to:
hudson.util.IOException2: Failed to download from
http://updates.jenkins-ci.org/download/plugins/jquery/1.11.2-0/jquery.hpi
(redirected to:
http://ftp.tsukuba.wide.ad.jp/software/jenkins/plugins/jquery/1.11.2-0/jquery.hpi)
at
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1172)
at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1678)
at
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1876)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1652)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Thread.java:745) Caused by:
java.io.IOException: Inconsistent file length: expected 3003464 but
only got 872533 at
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1155)
... 7 more
The jQuery plug-in is nowhere to be found as part of the plug-in installation...
Googling for a workaround did not give fruitful results. Maybe the Jenkins community knows how to workaround this?
Looks like downloading the plug-in's .hpi file from the FTP site and uploading it via the Jenkins UI followed by restarting Jenkins resolved the issue...
It is unclear why the plug-in installation fails otherwise.
I am somewhat familiar with Gauge testing tool and am now working on executing it via Jenkins.
First: i set gauge --version in the "Execute Windows Batch Command" field. This was the output:
Started by user anonymous
Building in workspace C:\jenkins\workspace\Run_Gauge_Test
[Run_Gauge_Test] $ cmd /c call C:\WINDOWS\TEMP\hudson8329964667758110371.bat
C:\jenkins\workspace\Run_Gauge_Test>gauge --version
Gauge version: 0.6.2
Plugins
-------
No plugins found
Plugins can be installed with `gauge --install {plugin-name}`
C:\jenkins\workspace\Run_Gauge_Test>exit 0
Finished: SUCCESS
Compare this to the output I get if I run Gauge directly in command line:
C:\jenkins\workspace\Run_Gauge_Test>gauge --version
Gauge version: 0.6.2
Plugins
-------
html-report (2.1.1)
java (0.5.1)
xml-report (0.1.3)
So i put the same command in a batch file and ran it only to get the "no plugins found" message again.
As a last option I ticked the Use custom workspaceand set my directory to a folder where I usually run gauge tests from command line but still it is "no plugins found"
Then i tried running it as a shell command. Output:
Started by user anonymous
Building in workspace C:\jenkins\workspace\Run_Gauge_Test
[Run_Gauge_Test] $ sh -xe C:\WINDOWS\TEMP\hudson211231385407124893.sh
The system cannot find the file specified
FATAL: command execution failed
java.io.IOException: Cannot run program "sh" (in directory "C:\jenkins\workspace\Run_Gauge_Test"): CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
(truncated)
at hudson.model.Executor.run(Executor.java:404)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 16 more
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Of course, I am going to actually run the gauge tests(and it doesnt work) rather than just get the version; but I thought it would be simpler to troubleshoot why it doesnt get plugin details correctly.
Any clues?
Gauge plugins should be installed via user/admin account with which the Jenkins agent executes commands. Have a look at following doc for more on integrating with GoCD and few other CI tools.
https://docs.gauge.org/latest/howto/index.html#tutorials
Long answer:
Currently, Gauge executable is installed at system level. Whereas Gauge plugins(language runners, reporting plugins etc) are installed at a user level. So if you install plugins as one user manually and on CI if task is run against different user, gauge will not be able to find plugins.
To fix this, you should run plugin install commands from the account with which CI runs. Or as Srikanth's comment says, you can have gauge --install-all task in pipeline. This installs all required plugins on the fly.
I suspect that you are installing and using Gauge as different users. As with a lot of CI tools, often the tasks are executed under a different users than one would use to log into the agent.
Currently the way Gauge works is: gauge.exe is available at a system level. However, the plugins are installed at a user level.
So if you login as user1 and do gauge --install java, gauge --version will list java as a plugin only when you are logged in as user1.
This is also true if you are running your CI agent under a local system account.
One way you can address this is if you include setup as a task in your pipeline, i.e. have a gauge --install-all from your project root before attempting to run your specs.