I have upgraded my Jenkins server to 1.505 but unexpectedly building with Maven plugin is not working and it throws an exception in the Jenkins logs
Error injecting constructor, java.lang.NoClassDefFoundError: hudson/ivy/AntIvyBuildWrapper
and after an hour googling this issue I found that Maven plugin guys upgrade their code base and it failed on an "optional" dependency, so I added the "optional plugin" but still it fails silently without any exception in the Jenkins logs.
the error appears on the console log is ERROR: Couldn't find Maven executable.
any hints ?!
The new maven plugin adds a new option to the Jobs I have (under the build section -> Invoke Maven 3 there is a new field called Maven version).
So what we need to do is open each job configuration page and hit the save button in order to save the default value and it will solve the problem.
Related
Trying to deploy an artifact using Jenkins WebLogic Deployer Plugin.
Getting following error:
Error: Could not find or load main class weblogic.Deployer
According to the documentation I should be using wlthint3client.jar (WebLogic version 12.1.3) but this client jar doesn't contain above class (Deployer), tried using the wlfullclient.jar which is said to be deprecated but if that throws another exception:
Hi, I want to install a war file generated from Jenkins to WebLogic, both on different machines, but when the installation runs an error is generated:
java.lang.NoClassDefFoundError: weblogic/deploy/api/spi/DeploymentOptions
at weblogic.deploy.api.tools.deployer.Jsr88Operation.init(Jsr88Operation.java:70)
Any ideas what could be the issue?
Regards!
I am having the same problem. I solved it actually adding all of these three libraries to the Additional Classpath:
wlthint3client.jar:weblogic.jar:wlfullclient.jar
I am getting Insufficient privileges error running sonar. This started happening after I upgraded sonarQube to 5.0.
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: Fail to decorate 'org.sonar.api.resources.File#152f931e[key=........]'
ERROR: Caused by: {"errors":[{"msg":"Insufficient privileges"}]}
For the existing projects, I renamed the key and now I have new sonar projects. Those seems to be working fine for now. The new projects that are created are throwing this error. Any suggestions?
The issue appears to be a bug in the Sonar Server 5.0 release.
https://jira.codehaus.org/browse/SONAR-6091
In order to work around it the 'SEE SOURCE CODE' project permissions can be set to include 'Anyone' from the admin page as in the below screen shot:
Obviously, this is not ideal in an unprotected environment because the source code can be viewed by anyone with access to the Sonar server API, but hopefully its addressed in the 5.1 release of Sonar Server.
The problem for me (Sonar 6.1) was caused by the creation of the project in SonarQube: at the first execussion of the scanner, it creates the corresponding project in SonarQube, what I didn't allow for all users...
Restore the right for creating projects allow the scanner to successfully work.
I upgraded to IDEA 14 (from 13) and when I attempt to run my grails 2.2.0 application, I am getting the following error:
FAILURE: Build failed with an exception.
* Where:
Build file '/Users/gdboling/Projects/GenRocket/web/build.gradle' line: 92
* What went wrong:
A problem occurred evaluating root project 'web'.
> No such property: environment for class: org.gradle.api.internal.project.DefaultProject_Decorated
It would seem that IDEA is attempting to use my build.gradle as part of the grails build process. IDEA 13 didn't do this. I use the build.gradle for some other non-grails related tasks for the project.
If I remove the build.gradle file all together, I get this error:
FAILURE: Build failed with an exception.
* What went wrong:
Task 'grails-run-app' not found in root project 'web'.
* Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
I do see the Grails View in the IDE but when I try and do a Make, it is telling me to re-import the gradle project. So it would seem that IntelliJ think this is a gradle project. How I can tell it that is is just a grails project?
To confirm my suspicions, I've opened a grails project that did not contain a build.gradle and it works just fine.
I had faced similar issue when unknowingly kept on hit next next in hurry. So, you probably mistakenly created a gradle project as shown in screenshot.
And when you recreated the project created it as "Create project from existing source" which idea well knows as grails-app (default for idea).
See if you can reproduce the error by re-importing the project using import project form external module.
I have created a Grails plugin using Grails 2.3.3 and trying to use the plugin in a Grails application which was also created using Grails 2.3.3. Now, to use the plugin in the application, it needs to be published to a plugin repository first. So I attempted to publish the plugin into the local repository by using the commands:
grails clean
grails compile
grails maven-install
For the grails maven-install command I selected the option 2)InstallPlugin. But then got an error:
Error installing plugin: No such property: ERROR_MESSAGE for class: Inst
allPlugin (Use --stacktrace to see the full trace)
Ran the last command above with option --stacktrace and --verbose but did not get any clue as to what the problem might be. I also removed %HOME%/.grails directory and reran the above commands and still came with the same error.
After googling, I found a JIRA for this issue which was closed stating that it happens when Grails version is changed and cleaning up cache files will get rid of this issue. However, that solution is not working for me and, by now, I have spent couple of hours trying to fix this. Also I did not change my Grails version.
Has anyone faced this issue with Grails 2.3.3 or with any recent version of Grails? What was the solution?
Don't use install-plugin, add a dependency in BuildConfig.groovy.
I don't know where the 2)InstallPlugin "option" is coming from. The maven-install script packages your plugin and generates a POM file and the other files needed to be a valid published plugins. Then it copies these files to your local M2 directory, e.g. if your plugin name is "mycoolplugin" the files are copied to $HOME/.m2/repository/org/grails/plugins/mycoolplugin
Now you can "install" the plugin as if it had been published in a remote repo. Add a dependency in the app's BuildConfig.groovy using the usual format, e.g.
plugins {
build ":tomcat:7.0.50"
compile ":scaffolding:2.0.1"
runtime ":hibernate:3.6.10.7"
...
compile ":mycoolplugin:0.1"
}
Jenkins:http://jenkins-ci.org/changelog
What's new in 1.426 (2011/08/15)
Auto Install JDK asks for Oracle account, but the link goes 404.
(issue 10556)
Record and display who aborted builds.
Added API token support. (issue 9363)
Maven Plugin can use settings and global settings files provided by
the config provider plugin Fixed background of title image (issue
9571)
when i run mvn project,failed.
13:10:22 Waiting for Jenkins to finish collecting data
13:10:23 channel stopped
13:10:25 FATAL: null
13:10:27 java.lang.NullPointerException
13:10:27 at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:833)
13:10:27 at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:448)
13:10:27 at hudson.model.Run.run(Run.java:1376)
13:10:27 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479)
13:10:27 at hudson.model.ResourceController.execute(ResourceController.java:88)
13:10:27 at hudson.model.Executor.run(Executor.java:230)
i rollback 1.424,it work.
This also happened in our environment after upgrading to 1.426. (Windows running a multi-slave-setup).
The issue is now registered in the Jenkins issue tracker:
JENKINS-10715
Finishing with a Null Pointer Exception after a successful build., and the duplicate
JENKINS-10755
NPE after successful project build with maven