artifactory

All, Currently all of our services uses different other internal services and their dependency is resolved by directly giving Bitbucket repository path of the services in the build config file (package.json). We want to setup a local artificatory where all the internal modules will be made available and dependencies can be resolved from their than from Bitbucket directly. Can someone give me some pointers how can I do this? What are the various steps involved? I would set up this for production environment so what factors should I keep in mind while installation. I recommend you to follow this

So we are currently working on the migration of ant building/publishing scripts for Android projects to the new Android Gradle build system. Our projects generally relies on both internal and third-party libraries. The internal libraries have been published on Artifactory repositories and now I'm struggling to resolve the dependencies over them. buildscript { repositories { maven { url 'http://repo1.maven.org/maven2' } maven{ url 'http://dl.bintray.com/jfrog/jfrog-jars' } } dependencies { classpath 'com.android.tools.build:gradle:0.4' classpath(group: 'org.jfrog.buildinfo', name: 'build-info

Is there a way to download an artifact using AQL? I have a query sent with: curl -u user:pass \ -X POST https://artifactoryURL/artifactory/api/search/aql \ -H 'content-type: text/plain' \ -T query.aql And my query.aql : items.find( { "repo":{"$eq":"repo"}, "$and": [ { "path": { "$match": "path/*"}, "name": { "$match": "*.rpm"} } ] } ) .sort({ "$desc": ["modified"] }) .limit(1) Now that I know it returns what I want, Is there a way to change the request from api/search/aql to something like api/download/aql and get those items? EDIT: I had also tried doing this with the jfrog cli but they don't

I have setup Artifactory according to the instructions given here, http://www.jfrog.com/confluence/display/RTF/Npm+Repositories , but on publishing a package the following is displayed: npm http PUT http://localhost:8083/artifactory/api/npm/npm-local/UIBase npm http 400 http://localhost:8083/artifactory/api/npm/npm-local/UIBase npm ERR! registry error parsing json npm ERR! publish Failed PUT response 400 npm ERR! SyntaxError: Unexpected token M npm ERR! Missing attachments with tarball data, aborting upload for: 'UIBase' npm ERR! at Object.parse (native) npm ERR! at RegClient.<anonymous> (/usr

I tried setup deploy to local repository: -- settings.xml -- <server> <id>myrepo</id> <username>deployer</username> <password>123456</password> </server> -- pom.xml --- <repositories> <repository> <id>myrepo</id> <url>http://myserver.com/artifactory/libs-release-local</url> <releases> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </releases> <snapshots> <enabled>false</enabled> <updatePolicy>always</updatePolicy> </snapshots> </repository> </repositories> when I execute "mvn deploy" I got error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:

The version-numbers for our jars have to be longer them x.x.x. We would rather need x.x.x.x to integrate some old-fashioned self-made mechanism. This is, because we tag our software with x.x.x and as soon as we have a delivery to a customer one specific jar has to be build exactly at this point of time to fit to another backend, which communicates with our program. For that reason this one jar has the version 2.3.4.1, when generated and in next delivery of the same Version it is build and named 2.3.4.2. Now artifactory cannot handle this an doesn't save more than x.x.x.2 in some cases. So we