artifactory

问题 We are using Artifactory pro 5.10.4 version. We are migating from a simple installation on a VM and apache reverse proxy for docker registries to docker swarm cluster. We are convinced that Traefik is the best alternative when it comes to dynamic configuration. We are facing some docker push with traefik. Our compose file for Artifactory service is: version: '3.7' services: artifactory: image: docker.bintray.io/jfrog/artifactory-pro:5.10.4 environment: EXTRA_JAVA_OPTIONS : > '-Xms2g' '-Xmx2g'

问题 I'm using Artifactory 3.5. My artifacts have custom properties. I want to be able to query for all artifacts that have that property and I want the result to show the property and its value. I know I can use: items.find(...).include("property.*") However, this returns all properties for the item matching the find criteria. How can I display only the specific property that I want? 回答1: The include element allows you to include only specific properties in the results For example, the following

问题 This question already has answers here : How do I use variables in single quoted strings? (7 answers) Closed last year . I would like to be able to use bash variable replacement in the following query to Artifactory Query Language api (AQL) In the shell, the command works like this: $ curl -H 'content-type: text/plain' -H 'X-Api-Key: APIKEYGOESHERE' -X POST https://foo.jfrog.io/foo/api/search/aql -d ' > items.find({ > "repo":{"$eq":"foo-docker"}, > "path":{"$match":"REPONAME/*"} > }) > .sort(

问题 This question already has answers here : How do I use variables in single quoted strings? (7 answers) Closed last year . I would like to be able to use bash variable replacement in the following query to Artifactory Query Language api (AQL) In the shell, the command works like this: $ curl -H 'content-type: text/plain' -H 'X-Api-Key: APIKEYGOESHERE' -X POST https://foo.jfrog.io/foo/api/search/aql -d ' > items.find({ > "repo":{"$eq":"foo-docker"}, > "path":{"$match":"REPONAME/*"} > }) > .sort(

问题 Artifactory version: 6.16.2 rev 61602900, Artifactory Pro license. In Artifactory, I have added a REMOTE repository, with the following settings: Package Type: NuGet Repository Key: chocolatey-remote URL: https://chocolatey.org/ Test: Successfully connected to server Repository Layout: nuget-default Include Patterns: **/* NuGet Download Context Path: api/v2/package NuGet Feed Context Path: api/v2 NuGet v3 Feed URL: (empty) Screenshots: On the host, I have configured Chocolatey sources: choco

问题 Artifactory version: 6.16.2 rev 61602900, Artifactory Pro license. In Artifactory, I have added a REMOTE repository, with the following settings: Package Type: NuGet Repository Key: chocolatey-remote URL: https://chocolatey.org/ Test: Successfully connected to server Repository Layout: nuget-default Include Patterns: **/* NuGet Download Context Path: api/v2/package NuGet Feed Context Path: api/v2 NuGet v3 Feed URL: (empty) Screenshots: On the host, I have configured Chocolatey sources: choco

问题 I have a fresh installation of Artifactory 7.2.1(docker based)which is working fine, but I want to access it via nginx proxy, and that's not working. my artifactory is running under http://192.168.211.207:8082/ Custom base URL is set to: http://192.168.211.207:8081/artifactory ->which is redirecting me to http://192.168.211.207:8082/ Now, I have an nginx server which is running on the same server, also via docker. When I try to access: http://192.168.211.207 -> redirects me to https://192.168

问题 I have a fresh installation of Artifactory 7.2.1(docker based)which is working fine, but I want to access it via nginx proxy, and that's not working. my artifactory is running under http://192.168.211.207:8082/ Custom base URL is set to: http://192.168.211.207:8081/artifactory ->which is redirecting me to http://192.168.211.207:8082/ Now, I have an nginx server which is running on the same server, also via docker. When I try to access: http://192.168.211.207 -> redirects me to https://192.168

问题 In an environment where multiple builds (release candidate packages) can be created daily but only one a month gets promoted to production, I think storing every build in Git would be wasteful but there should be a short term location that the last few builds are published. I'm currently publishing these to a shared directory. I have see IVY used for this sort of binary publishing in the past. Git seems like overkill as it would bloat due to it's model of never delete anything. Is there an

问题 In an environment where multiple builds (release candidate packages) can be created daily but only one a month gets promoted to production, I think storing every build in Git would be wasteful but there should be a short term location that the last few builds are published. I'm currently publishing these to a shared directory. I have see IVY used for this sort of binary publishing in the past. Git seems like overkill as it would bloat due to it's model of never delete anything. Is there an