artifactory

问题 We'd like to introduce a naming convention as we have a large number of both internal and external repositories and thus we'd like to make it obvious what's what. At the time these repositories were added, nobody expected things to grow this much. I was wondering if it would be possible to rename the repositories? I know I can create new ones and copy/move the artifacts there, but that looks like a bigger effort than I'd like. Is there a reasonable way to do this? 回答1: No and yes. You shouldn

问题 My gradle version is 2.2.1. I am trying to use the artifactory plugin in gradle ( apply plugin: 'artifactory' ) This is my code: buildscript { repositories { maven { url 'http://172.14.3.93/artifactory/plugins-release' } } dependencies { classpath(group: 'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '2.0.9') } } allprojects { apply plugin: 'artifactory' } artifactory { contextUrl = "${artifactory_contextUrl}" //The base Artifactory URL if not overridden by the publisher

问题 I am working on implementing a build job using Jenkins Multibranch Pipelines. The final stage is uploading the build output to Artifactory. When configuring a standalone job via the interface, there is an option to "Discard old builds from Artifactory" which allows me to only keep the same number of builds as specified in "Max # of builds to keep" setting. The upload stage in my Jenkinsfile is configured like this: https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+-+Working+With+the

问题 I'm tring to use the artifactory-maven-plugin to upload a maven build to my artifactory server. Uploading with the jfrog cli works, so it seems not a permission problem. Here is my pom.xml: <plugin> <groupId>org.jfrog.buildinfo</groupId> <artifactId>artifactory-maven-plugin</artifactId> <version>2.6.1</version> <inherited>false</inherited> <executions> <execution> <id>build-info</id> <goals> <goal>publish</goal> </goals> <configuration> <deployProperties> <gradle>awesome</gradle> <review.team

问题 I have cloud servers located in separate data centers across the world. Each data center is separate from the others. I'm looking for an easy way to deploy artifacts to individual clusters of servers (that may be running different versions of software i.e. a dev, test, and production cluster) in each of these regions with ease and consistency. It seems to me that an artifact server is what I need because I could execute an install script on the cloud server, which pulls down the correct

问题 I am trying to build multiple Maven profiles in a single Jenkins job. Each profile changes some code and then creates a jar by executing mvn -Pdev install then mvn -Pprod install in the command line (According to Maven using mvn -Pdev,prod install is supposed to work but it isn't working for me). Here are the two profiles in my project's pom.xml : <profiles> <!-- prod profile --> <profile> <id>prod</id> <build> <plugins> <plugin> <groupId>com.google.code.maven-replacer-plugin</groupId>

问题 When I try to deploy my application, I got this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project acme-db: Failed to deploy artifacts: Could not transfer artifact com.acme:acme-db:jar:0.8.1 from/to artifactory.acme.com (http://artifactory.acme.com/libs-release-local): Access denied to: http://artifactory.acme.com/libs-release-local/com/acme/acme-db/0.8.1/acme-db-0.8.1.jar, ReasonPhrase:Forbidden. -> [Help 1] [ERROR]

问题 I am trying to get the Gradle Artifactory Plugin to resolve artifacts. My build.gradle file is below with the being replaced with the correct hostname buildscript { repositories { maven { url 'http://jcenter.bintray.com' } } dependencies { classpath(group: 'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '3.0.1') } } apply plugin: 'com.jfrog.artifactory' artifactory { contextUrl = 'http://<URL>:8081/artifactory' //The base Artifactory URL if not overridden by the publisher

问题 I have read this tutorial about setting Chef repositories in Artifactory ("my own" from Git and official Chef supermarket - two remotes). Everything works fine, but I don't really understand, how to "pin" it with Chef. I know that you can use ChefDK to easy install cookbooks locally and push them to repository. My question is about end-users: how they can use this virtual Chef repository to easy use cookbooks? I mean, end-user should run command like: chef-client -j params.json , where it has

问题 In our company we are establishing Artifactory into our toolchain. We have now a remote repository for the CocoaPods repository. As we are required to control the pods that are used, we would like to white list allowed pods with the include function. So if we use a repository without restriction, everything works fine. But if we have an include pattern for a library, e.g. see print screen, then we get an error on the fetchIndex request of Artifactory. In the logs, this is what it looks like: