https://wiki.jenkins.io/display/JENKINS/Release+Plugin
Right now we have jenkins release plugin that works with freestyle jobs. Any idea if we have release plugin compatible with mutlibranch and multipipeline jobs.
I just want Release button to be there on Jenkins job and on clicking, it should work as build button do. I have release functionality defined in Jenkinsfile.
Thanks,
Release plugin is compatible already with jenkins pipeline, more information in this Jenkins ticket.
You can just use the release step from your pipeline.
Related
Does anybody know how to get feature "Incremental build - only build changed modules" from Maven Project Plugin available from inside jenkins declarative pipeline (Jenkinsfile)
While trying to upgrade SonarQube plugin from 2.2.1 to 2.4, it failed and the plugin is gone. I had to uninstall 2.4 and reinstall 2.3. Now all the SonarQube Analysis Step disappeared from all projects. I can see it's still in the config.xml, but can't see from the web UI. I tried:
Reload configuration from disk
Manually change from plugin="sonar#2.2.1" to plugin="sonar#2.3" in the config.xml
Uninstall and reinstall 2.2.1, reload from disk
Manually add the step, compare the result conf.xml to the original, there is no different at all for this step.
Still can't see the step in the job. please help.
This is fixed by restarting Jenkins.
I'm trying to use Google Cloud Endpoints with Android client, built by Maven.
The problem is that appengine-maven-plugin v1.8.3+ require Maven v3.1.0+
[ERROR] Failed to execute goal com.google.appengine:appengine-maven- plugin:1.8.4:endpoints_get_discovery_doc (default) on project pro-gae: The plugin com.google.appengine:appengine-maven-plugin:1.8.4 requires Maven version 3.1.0 -> [Help 1]
while android-maven-plugin v3.6.1 doesn't (and will not) work with Maven v3.1.0 (see devs discussion at https://code.google.com/p/maven-android-plugin/issues/detail?id=395). The error
A required class was missing while executing com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.6.1:generate-sources: Lorg/sonatype/aether/RepositorySystem;
So I'm kinda locked out. One plugin asks for v3.1.0+, while the other one claims Maven 3.1.0 to be fatally buggy. So I left out to generate Endpoints client sources manually.
Any other ideas, besides waiting for fixed Maven 3.1.1? It doesn't seem to happen soon, because Maven 3.1.0 was released more than two months ago.
The latest version of the Android Maven Plugin is 3.8.0 and it now requires Maven 3.1.1+. This should allow you to use the latest appengine plugin as well. And Maven 3.1.1 has been released in the meantime as well.
Update Sept 2015: Latest version of the plugin is 4.3.0 with 4.3.1 around the corner. The 4x branch works with Maven 3.0.5+ but we strongly encourage users to use the latest Maven release.
Hmm, looks resolved by just using older version (1.8.2) of appengine-maven-plugin.
One other way of building is to configure the Run Configuration to use an external Maven Runtime.
To do this in Eclipse for Windows :
Right Click Project -> Run Configuration -> Create a new configuration -> In Main tab configure Maven Runtime.
I hope this helps.
Friends,
I have already setup TFS build on my box. Currently the build can be triggered using VS IDE or Web interface. However i will like to hook existing TFS build process in to Jenkins as we use Jenkins as standard build tools for all platform builds. Is there any plugin available? I searched with available plugins but it has only MS build plugin.
Thanks
Bala
There is a TFS Plugin available & also Jenkin-TF tool available. Check this link, it has been For detailed instructions on how to configure TFS & Jenkins
http://blogs.msdn.com/b/visualstudioalm/archive/2012/10/19/building-ios-apps-in-tfs.aspx
Is there a way to give a custom message to the deployment with the Cloudbees Deployer plugin? We are used to putting the git version to the deployment so that it's easier to see which version we have running at run#cloud.
We've tried doing the deployment with the bees maven plugin and there it's possible to get the message parameter set from a build parameter. It just would be nice to be able to use the plugin instead of having to mess with the maven plugin, which is easier to get wrong in the configuration phase.
This feature was not available prior to version 4.4 of the CloudBees Deployer plugin.
Version 4.4 adds the ability to configure the description in the "Advanced" button:
The default value for this field is ${JOB_NAME} #${BUILD_NUMBER} so as to retain the previous behaviour.
The field supports all the usual Jenkins Environment token macro expansion, so you probably want to set it to something like ${GIT_COMMIT} or maybe ${GIT_COMMIT} ${JOB_NAME} #${BUILD_NUMBER}. In any case the standard token macros should provide the flexibility you require.
Note: If you are using DEV#cloud, and the Jenkins has a pre-4.4 version of the plugin you will have to wait until after 2013-04-15T15:00Z and restart your Jenkins instance to pick up the newer version of the plugin.
Note: If you are using the CloudBees Deployer plugin via the CloudBees Free Enterprise Plugins route, you will have to force the update center metadata to update or wait until after 2013-04-16T12:30Z to see the update in the list of plugins.