When building a maven project on Jenkins its possible to specify the build trigger:
Build whenever a SNAPSHOT dependency is built
This works out of the box.
I have a Gradle project that I build with gradle (v. 1.2) on Jenkins (ver. 1.483) using Artifactory as my binary storage. But cannot find the same option. Are there any Gradle plugins for Jenkins that enables this functionality or is it possible to configure it globally in a .gradle file?
Related
I use gitlab and jenkins.
Here is my structure:
branch: master
Inside the app_folder I have the following files:
app_folder
solution_folder
core_library
other services
3rd party dll
services_folder
service1_folder
service2_folder
service3_folder
service_sln
All three services use same services_sln file.
Now these services use the core libraries in the other directory which was mentioned above.
How do I configure the jenkins build?
Jenkins doesn't build your project. In order for jenkins to build successfully, your project should have the right configuration done in the solution file. With your problem statement, the project will not even build locally.
So get your basics right first
I am using Visual Studio Artifactory deployer to deploy jar files built by maven to Artifactory maven repo. If I use maven artifactory plugin the jar file gets deployed to right folder structure and maven setting stay as per the jar but from CLI if i push the jar file, it only get deployed as a jar file to the folder I specify. For example
Using CLI push a artifact.jar to target libs-snapshot/com/foo/bar
gets file uploaded to libs-snapshot/com/foo/bar and artifactory has
no information about jar version, group id , artifact id. I could not
find any options on the CLI to specify those.
While using Maven Artifactory plugin, a pushed jar ends up in
libs-snapshot/com/foo/bar/artifact/version folder and maven
properties stay intact
How do I achieve same behaviour from CLI as maven artifactory plugin does.
Just to make sure, how do you use the CLI for the deployment? In order to have it deployed to Artifactory using the CLI, you will have to specify the right Maven coordinates. For example:
jfrog rt u mySnapshot-1.0.0-SNAPSHOT.jar “libs-snapshot-local/path/to/folder/mySnapshot/1.0.0-SNAPSHOT/”
This will deploy your snapshot file to Artifactory and Artifactory, base on your repository configuration will replace the “SNAPSHOT” with a timestamp.
If you meant that you want to deploy 5 different files, to 5 different paths and that you wish that the JFrog CLI to extract the maven layout and deploy by it, then this is not possible by using the CLI.
Mainly used for : C# project, nuget package dependencies, MSBuild build tool (no TFS)
We are evaluating Artifactory Pro eval version, Jenkins for CI & dependency management. Currently, I have setup Jenkins to use the "Generic-Artifactory integration" build environment to resolve/restore nuget packages from Artifactory. I am able to access artifactory from Jenkins and see the various repos.
All I am looking to see is to have the Jenkins CI use the Artifactory plugin to fetch Nuget packages from Artifactory. If the nuget packages are not cached currently in Artifactory, I will go fetch it from Nuget gallery (https://www.nuget.org) and cache them in one of remote repos in Artifactory. Then the subsequent builds can then fetch from this Artifactory cache repo for any nuget dependencies. How do i do this with Jenkins CI, MSbuild tool, Artifactory Pro eval version.
IMO the fastest and easiest way to do that is to use the MsBuild Artifactory plugin.
This plugin is a simple extension for Visual Studio which allows you to add a new project type to your solution.
By doing it you will be able to control how to resolve nuget dependencies from Artifactory and what you want to publish in your repos.
Also I recommend using a single virtual repository for your case and to aggregate in it a local which will be your target for deployment and a remote connected to the official nuget gallery.
Also you can watch this webinar about the MsBuild Artifactory plugin. It is showing how to use it with TFS but the idea is the same for Jenkins as the plugin is simply an extension to the MsBuild process.
currently we are using manual upload through GUI of nexusI have a Java project (which is not a maven project means no POM.xml) and SVN repo and jenkins(using ant script for build) for CI. The build process creating War and Ear files locally in jenkins workspace. I want to upload this EAR to Nexus repository. It doesn't use Maven for builds. And I'd rather not introduce Maven/POM files just to get files into Nexus.
So, what's the best (or any reasonable) way to upload build artifacts to a Nexus repository without Maven?
for my project i am customizing the jenkins plugin.
when i build the Junit reporter plugin, it successfully creates hpi plugin file, since it has no dependencies.
for **testng-plugin** build fails. since it needs maven plugin dependencies.
how to build the hpi plugin from source of the exisitng customized
jenkins plugin which has dependencies?