I'm trying to setup Artifactory(free version) and Hudson to deploy artifacts.
The main stuff already works, i can deploy to Artifactory via Hudson. Using the Artifactory Hudson Plugin with generic deployment.
I am also able to browse the deployed stuff via the Tree & Simple Browser.
What not works correctly is the Build Browser, it does show everything except the artifacts deployed by the build. In the published modules view it should show all artifacts, but the tables are just greyed out for me.
Example how it should look:
Link to the official Jfrog Artifactory demo repository
Does anyone know if this view is maybe a pro feature, or any other tips how to resolve this problem?
The build integration feature is limited in the OSS version. You need the Pro version to get the full deal.
I've used the description setter plugin https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin . In my case i take the last revision and put a link to the artifact in artifactory. In this way on every build i can see a direct link to the artifact changing the path like you want.
Related
I am using Free Style Projects (in Jenkins) to schedule a regression test.
1. Get Source From BitBucket
2. Execute Windows Batch Command.
Earlier we are allowed to upload the jar files in Bitbucket. So we did not face any issue. Now Presently due to some changes in the process, we are not allowed to upload binaries which is affecting to upload jars in the Bitbucket.
Now, They gave given the artifactory url to set up for Maven. But we don't have any Maven projects.
It seems that artifactory is getting populated when it is hosted in the local. But we wanted to use the artifactory which is shared..
Can any one let me know the set up for free style project and the artifactory hosted in other machine and we have only URL.
Thanks
Here is documentation:
https://www.jfrog.com/confluence/display/RTF/Jenkins+Artifactory+Plug-in
I recommend to use Maven Project.
I use a script in Jenkins to build delphi projects and I want to deploy their .exe outputs to Artifactory server but I dont know how. Is there any plugin to deploy exe files to Artifactory?
Is it a good idea to deploy them to Artifactory?
The best would be using the Jenkins Artifactory plugin.
The plugin allows your build jobs to deploy artifacts automatically to Artifactory and have them linked to the build job that created them.
The support for generic (freestyle) builds is probably the most suitable one for deploying the .exe files. As part of the support for generic builds, you will be able to defined patterns for selecting which files would be deployed and to where.
I need to promote debian packages build in jenkins to the repo (aptly.. maybe artifactory). However, the available plugins seem to be broken for multiple branch projects. Has anybody found a solution to get around this?
You can use Artifactory Jenkins plugin for that. Define the deb files you want to upload (metadata will be generated by Artifactory for you).
Please note that you need to attach some properties to the uploaded files. From Jenkins you don't need to craft the URL, instead add the properties in the "Deployment properties" textfield.
We have successfully our deployed artifacts with Jenkins - Artifactory plugin, however we cannot see them in Artifacts => Builds => Published Modules tab.
We can see the link as below:
If we click onto this link, the upcoming screen is completely disabled and empty.
Shouldn't we have the downloadable link of our deployed artifacts in this final screen?
You are using Opensource version of Artifactory, which only allows browsing the buildInfo JSON file, not the Build Browser tabs.
You can replace the artifactory.war file to a pro version one (free 30 days trial), restart Artifactory and see all the information in the tabs.
I'm wondering if there is an easy way to "publish" p2 update sites in Jenkins (built with Tycho) so that they can easily be accessed in downstreams jobs? Currently I'm doing it semi-manually using Jenkins support for copying artifacts between jobs, and then specifying a repository-mirror element in a job-specific settings.xml which refers to the artifacts copied into the job, but this is all a little tricky and requires configuring jobs and build settings in a number of different places.
Is there any nicer way short of using an external solution such as Artifactory?
The only solution involving a repository manager that I am aware of is to use a Nexus and the Unzip Plug-in. (Disclaimer: The Unzip Plug-in is provided by the Tycho project, of which I am a committer.)
With such a setup, you could have one job deploy an update site to Nexus, and the next job use the update site via the unzip URL of the deployed site. Example: If the site was deployed under the GAV project.abc:site:1.0.0-SNAPSHOT, you could then access it via http://<nexus>/content/repositories/<unzip-repo-name>/project/abc/site/1.0.0-SNAPSHOT/site-1.0.0-SNAPSHOT-unzip/.
Note that you are slightly less flexible with such a setup that with what you have set up now: You need to have a version number for what your upstream project is building, so this may become tricky if you have multiple feature branches developing towards the same release version.
If you don't need this, you have the benefit of getting a portable build of your downstream project, i.e. developers build the project in the same way as your Jenkins does.