I have installed the HockeyApp plugin (v1.2.0) on Jenkins (v1.590), restarted Jenkins but the "Upload to HockeyApp" option is not showing in the list of post build actions.
What am I missing?
I had this same problem with Jenkins v1.609 and HockeyApp plugin v1.2.0.
I got the plugin to work by upgrading Java to version 8 (installed as a homebrew cask).
Related
I am facing issue in jenkins job(jenkins running docker) Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.
I have checked java version in docker it is openjdk version "11.0.12" 2021-07-20
we can solve this in Android Studio but how can we solve while running gradle build in jenkins.
Below is the error I am getting
Build file '/var/jenkins_home/workspace/CICDDemo_master/app/build.gradle' line: 2
What went wrong:
An exception occurred applying plugin request [id: 'com.android.application']
Failed to apply plugin 'com.android.internal.application'.
Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.
You can try some of the following options:
- changing the IDE settings.
- changing the JAVA_HOME environment variable.
- changing org.gradle.java.home in gradle.properties.
In your Jenkins project choose the "configure" tab on the left side, then scroll down to "Properties Content" and write there:
JAVA_HOME=C:\Program Files\Java\jdk-11.0.12
GRADLE_USER_HOME=C:\
In Jenkins, currently there is only JDK8 and maven 3.5.2 installed. I downloaded JDK11 to it. I ran a pipeline project to build a springboot Java11 project and it ran fine using maven 3.5.2. There is no reference to any maven source or target versions in the pom of the project. Currently I don't see any issues with JDK11 with maven 3.5.2 due to simplicity of the project. Any idea if it might cause issues with complex projects? Is it good to update Maven version in Jenkins and the spring boot projects?
After an upgrade got a red box in jenkins:
There are dependency errors loading some plugins:
When I visit plug in page: there are no upgrades available:
When I visit Available tab, Ruby run-time is already installed with 0.12 version and there are no updates for the Gitlab Hook Plugin
How do I fix this?
I had the same issue on Ubuntu 16.04 + with openjdk 9. I switched to oracle JDK 8, the plug-in installed properly.
Check the plug-in if it's installed. It wasn't installed with gitlab plug-in install for me.
Hope this helps !
In case of windows issue with Jenkins try reinstall Jenkins from "Program Files x86" to C:\Jenkins.
This solved issue with GitLab Hook and Ruby-runtime plugins.
I am using Jenkins for CI and added the sonar plugins for Jenkins. After sonar scan Technical Debt shown Zero.
But actually its is not zero previously was using latest version of sonar there it was showing Technical Debt but after downgrading it is not shown .(Duplicate code ,Lines of code ,complexity are shown)
Below are the version of sonar used
Before Downgrading following version are used (Working fine)
sonar scanner 2.5.1 , Sonar Plugin 2.3 , SonarQube 5.4 , Jenkins version. 1.651
After Downgrading (Technical Debt not shown)
Sonar scanner 2.5, sonar plugin 2.1 , SonarQube 4.5 , Jenkins version 1.651
How this problem can be solved ?
Thanks
Ganesh
I found the reason for this , posting here so that it can be helpful for others.
In latest version of SonarQube 5.4 there is no need to refer to 'binaries' ,from 'src' only Technical Debt will be calculated.But in case of older version 4.5 need to refer binaries also for sonar scan(Because find-bugs requires binaries in new one find bugs are integrated to sonar way profile)
I had the same problem, I missed deleting data/es folder during upgrade process. After deleting the data/es folder and restarting the sonarqube server solved my problem. More information is here
We recently migrated jenkins to the LTS version 1.532.2. Ever since, we have been experiencing problems with maven builds failing frequently and claims the entire build took only 0ms as seen in the build trend.
The maven project plugin itself wasn't upgraded as he latest version had a different issue. The current maven project plugin in use is 2.0
Has anyone experienced this behavior?