![]() If your network allows outbound call to our api endpoint:, then option 1: License Key (online activation) will work. Notice the regex defined in the pattern field below specifies to upload all files from the “jenkins-pipeline-examples/resources/” directory that match the “.*Atifactory.*.zip” or “.*(A|a)rtifactory.*.zip” patterns.įor example: “ArtifactoryPipeline.zip” and “ArtifactoryPipelineNoProps.zip”.Railflow provides two license activation models. Below is an example script showing how to upload a file to Artifactory in a Jenkins pipeline job. Jenkinsįile specs are supported for both generic and pipeline Jenkins jobs using the Jenkins Artifactory plugin. Let’s get started with some interesting examples that implement these functionalities. You can even use file specs with cloud CI servers, such as Travis-CI and Circle CI, using JFrog CLI! What’s even better is that you can actually define a single File Spec that can be used with your favorite CI server, including Jenkins, TeamCity and Bamboo. You can also use placeholders to determine the name of the artifact once downloaded or uploaded. Advanced users can also benefit from the power of regex and AQL to define file source patterns and targets when uploading and downloading artifacts. With only 2 mandatory fields, source (referred to as pattern) and target, you can find the artifacts you need according to the specifications that you define. Getting creative with how you manage your artifacts in JFrog Artifactory? It’s time to get familiar with File Specs.įile specs allow you to specify the files you want to upload and download to and from Artifactory with a simple configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |