suggested workflow for artifactory and jenkins

0
votes

I'm new to artifactory, have some basic question. Unfortunately did not find best practices/suggested workflows in the jfrog docs.. As far as I understand there are 2 basic flows for generic build to work with Jenkins:

  1. Create tar and with naming convention that holds the build number in it's name (for example my-build-dev-128.tar.gz) and a file ( last-build.txt) that will hold the last build string. So when Jenkins/user needs to download the latest build I download the last-build.txt and get the build number from the string, then download the last artifact.
  2. Add server.publishBuildInfo buildInfo to the artifactory upload and then each file has it's own build and that way when you download it has build properties you can work with - however I was not able to pull specific build (have to specify the files that I need and it's always downloading the last build of the file) .

So, what is the best workflow practice for Jenkins/Artifactory marriage ( push , pull, get latest and get older artifacts in automatic way (cli/API/Jenkins plugin - but not GUI)?

1
jenkinsartifactory
Hi! Is the artifact you want to upload to Artifactory in a maven project? If so, take a look at this link. - dalmo.santos
no, it is generic project - oTolev

1 Answers

0
votes

Best practice is to publish a build info like you mentioned. The build doesn't have to be for a single file, it can include multiple ones. See these examples for declarative or scripted workflows.

When you download, the download command accepts a file spec. In the build field of the file spec you can specify a build name without a build number which will download the artifacts of the latest build. When you specify a build, the aql and pattern fields are optional. You can still use them if you'd like to filter some of the build artifacts.

An additional file to hold the build details is redundant, this is what the build info is for.