artifactory

Gradle artifactory plugin saying “Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'…”

孤街浪徒 提交于 2019-12-03 22:08:27
Here's the configuration to get the artifactory plugin: buildscript { repositories { mavenCentral() 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' apply plugin:'ivy-publish' ...some publish spec stuff... I run gradle (2.3) and I get: > Failed to apply plugin [id 'com.jfrog.artifactory'] > Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention@6b6c7be4' with class 'org.jfrog.gradle.plugin.artifactory.dsl

Return Code 401 with Maven 3 uploading SNAPSHOT to Artifactory

霸气de小男生 提交于 2019-12-03 21:47:14
I am running the following: Apache Maven 3.0.5, Artifactory(Open-Source) 3.1.0 No Jenkins/Hudson, just the default Artifactory setup. Excerpt from pom.xml: <distributionManagement> <repository> <id>ServerA2</id> <name>ServerA2-releases</name> <url>http://192.168.1.16:8081/artifactory/libs-release-local</url> </repository> <snapshotRepository> <id>ServerA2</id> <name>ServerA2-snapshots</name> <url>http://192.168.1.16:8081/artifactory/libs-snapshot-local</url> </snapshotRepository> </distributionManagement> Excerpt from settings.xml: <?xml version="1.0" encoding="UTF-8"?> <settings xsi

Should we use Nexus or Artifactory for a Maven Repo?

半城伤御伤魂 提交于 2019-12-03 17:54:00
问题 We are using Maven for a large build process (> 100 modules). We have been storing our external dependencies in source control, and using that to update a local repo. However, we are ready to graduate to a local repo that can cache central so that we don't have to proactively download all 3rd parties (but we can still have a local repo to pull from). In addition we want to publish our internal build artifacts from a nightly build so that developers don't have to build the world. We are

How to publish builds to Artifactory from GitLab CI?

别等时光非礼了梦想. 提交于 2019-12-03 17:12:47
问题 I am looking for an easy and clean way to publish artefacts build with GitLab CI onto Artifactory. I was able to spot https://gitlab.com/gitlab-org/omnibus/blob/af8af9552966348a15dc1bf488efb29a8ca27111/lib/omnibus/publishers/artifactory_publisher.rb but I wasnt able to find any documentation regarding how I am supposed to configure it to make it work. Note: I am looking for a gitlab_ci.yaml approach, not as in implementing it externally. 回答1: At a basic level, this can be done with the JFrog

How to upload an artifact to Artifactory / consume it in a build system (Gradle Maven Ant) where the artifact does not have an extension

偶尔善良 提交于 2019-12-03 14:57:33
I have the following files which I would like to upload to Artifactory as a 9.8.0 versioned artifact. NOTE : The first two files DO NOT have an extension (they are executable files i.e. if you open them/cat on it, you'll see junk characters). Folder/files of a given version 9.8.0 in CVS is like: com.company.project/gigaproject/v9.8.0/linux/gigainstall com.company.project/gigaproject/v9.8.0/solaris/gigainstall com.company.project/gigaproject/v9.8.0/win32/gigainstall.exe com.company.project/gigaproject/v9.8.0/gigafile.dtd com.company.project/gigaproject/v9.8.0/gigaanotherfile.dtd com.company

NPM lockfiles/shrinkwrap get random “dl” parameter tacked on to the “resolved” URL

安稳与你 提交于 2019-12-03 12:16:09
问题 Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity): https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz ?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz Then, from pull request to

Can Nexus or Artifactory store simple tar.gz artifacts?

心不动则不痛 提交于 2019-12-03 09:35:07
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 software artifact. Now, I work on the operations side. I don't care about doing builds, or managing software

What is the correct way to configure grails maven authentication to Artifactory?

ⅰ亾dé卋堺 提交于 2019-12-03 07:36:50
What is the correct way to configure authentication to Artifactory using the Maven resolver? Currently I'm using: grails.project.ivy.authentication = { repositories { mavenRepo "http://SERVER:8081/artifactory/remote-repos" } credentials { realm = "Artifactory Realm" host = "SERVER" username = "USER" password = "PASSWORD" } } grails.project.dependency.resolver = "maven" // or ivy grails.project.dependency.resolution = { // inherit Grails' default dependencies inherits("global") { // specify dependency exclusions here; for example, uncomment this to disable ehcache: // excludes 'ehcache' } log

How to configure Maven2 to publish to Artifactory?

若如初见. 提交于 2019-12-03 07:08:12
问题 Currently I have a Maven2 project that builds a JAR when you run: mvn clean package I need to now tweak the pom.xml to publish this JAR ( myapp.jar ) to an Artifactory server running at: http://myartifactory/artifactory/simple/myorg/myapp/0.1 I tried adding a <repositories> element to my pom.xml but nothing is being published with this config: <repositories> <repository> <id>myartifactory</id> <url>http://myartifactory/artifactory/simple/</url> </repository> </repositories> Any ideas as to

Accessing an Artifactory/Maven Repo that requires basic-auth

跟風遠走 提交于 2019-12-03 06:51:31
问题 I have an Artifactory repo that sits behind basic authentication. How would I configure the settings.xml to allow access? <mirrors> <mirror> <id>artifactory</id> <mirrorOf>*</mirrorOf> <url>https://myserver.example.com/artifactory/repo</url> <name>Artifactory</name> </mirror> </mirrors> <servers> <!-- This server configuration gives your personal username/password for artifactory. Note that the server id must match that given in the mirrors section. --> <server> <id>Artifactory</id> <username