简体   繁体   English

Gradle发布到Artifactory的特定回购

[英]Gradle publish to the specific repo of the Artifactory

I am trying to setup the artifacts (APK/aar files) build process with gradle similar to how I am used to with maven. 我正在尝试使用gradle设置工件(APK / aar文件)构建过程,类似于我习惯使用maven。

mvn release:prepare (Adjusts version, checks into SVN, creates the tag) 
mvn release:perform -Dgoals=deploy (Pushes the artifact to http://artifactory.XXX.local/artifactory/libs-releases-local/)

I want to be able to run the gradle commands and achieve similar results. 我希望能够运行gradle命令并获得类似的结果。 I am using https://github.com/researchgate/gradle-release plugin for the release management (which works fine so I am good with release). 我正在使用https://github.com/researchgate/gradle-release插件进行发布管理(工作正常,因此我对发布很好)。 But when I run the command gradlew artifactoryPublish the artifact is deployed at some other location (as if it's not respecting the repoKey in the gradle file) 但是当我运行命令gradlew artifactoryPublish ,工件被部署在其他位置(就好像它不尊重gradle文件中的repoKey)

D:\\my-lib-android-0.0.2>gradlew artifactoryPublish ... ... [buildinfo] Not using buildInfo properties file for this build. D:\\ my-lib-android-0.0.2> gradlew artifactoryPublish ...... [buildinfo]不使用buildInfo属性文件进行此构建。 :artifactoryPublish Deploying build descriptor to: http://artifactory.XXX.local/artifactory/api/build Build successfully deployed. :artifactoryPublish将构建描述符部署到: http://artifactory.XXX.local/artifactory/api/build构建成功部署。 Browse it in Artifactory under http://artifactory.XXX.local/artifactory/webapp/builds/my-lib-android-0.0.2/1449880830949 > http://artifactory.XXX.local/artifactory/webapp/builds/my-lib-android-0.0.2/1449880830949下的Artifactory中浏览它>

BUILD SUCCESSFUL 建立成功

Total time: 9.692 secs 总时间:9.692秒

So my question is how can I fix my setup so that the artifact is pushed to a URL similar to this: 所以我的问题是如何修复我的设置,以便将工件推送到类似于此的URL:

http://artifactory.XXX.local/artifactory/libs-releases-local/com/example/my-lib-android/0.0.2/my-lib-android-0.0.2.aar

build.gradle File: build.gradle文件:

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.3.0'
        classpath(group: 'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '3.1.2')
        classpath 'net.researchgate:gradle-release:2.3.4'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}
plugins {
    id 'net.researchgate.release' version '2.3.4'
}

apply plugin: "com.jfrog.artifactory"
apply plugin: 'maven-publish'
apply plugin: 'net.researchgate.release'

allprojects {
    repositories {
        jcenter()
        maven {
            url 'http://artifactory.XXX.local/artifactory/libs-releases-local'
        }
    }
}

artifactory {
    contextUrl = "${artifactory_contextUrl}"
    //The base Artifactory URL if not overridden by the publisher/resolver
    publish {       
        repository {
            repoKey = "libs-releases-local"
            username = "${artifactory_user}"
            password = "${artifactory_password}"
            maven = true

        }
    }
}

release {
    revertOnFail = false
}
task build{

}

gradle.properties File: gradle.properties文件:

version=my-lib-android-0.0.3-SNAPSHOT
artifactory_user=myUserName
artifactory_password=myPasssword
artifactory_contextUrl=http://artifactory.XXX.local/artifactory

Using android-maven plugin: 使用android-maven插件:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.9.2'
        classpath 'com.github.dcendents:android-maven-plugin:1.0'
        classpath 'org.jfrog.buildinfo:build-info-extractor-gradle:3.2.0'
    }
}

apply plugin: 'android-library'
apply plugin: 'com.jfrog.artifactory-upload'
apply plugin: 'android-maven'


configurations {
  published
}

task sourceJar(type: Jar) {
    from android.sourceSets.main.java
    classifier "sources"
}

artifactoryPublish {
    dependsOn sourceJar
}

artifacts {
    published sourceJar
}

artifactory {
    contextUrl = "${artifactory_contextUrl}"
    publish {
        repository {
            repoKey = "libs-releases-local"
            username = "${artifactory_user}"
            password = "${artifactory_password}"
        }
        defaults {
            publishConfigs('archives', 'published')
            publishPom = true //Publish generated POM files to Artifactory (true by default)
            publishIvy = false //Publish generated Ivy descriptor files to Artifactory (true by default)
        }
    }
}

I usually do it with the mavenDeployer-plugin like this. 我通常使用像这样的mavenDeployer-plugin。 Don't know if it matches your case, but I'll just leave it here. 不知道它是否符合你的情况,但我会把它留在这里。

apply plugin: 'maven'
uploadArchives {
    repositories {
        mavenDeployer {
            repository(url: 'http://arandom.nexus.com:8081/nexus/content/repositories/releases') {
                authentication(userName: NEXUS_USERNAME, password: NEXUS_PASSWORD);
            }
            snapshotRepository(url: 'http://arandom.nexus.com:8081/nexus/content/repositories/snapshots') {
                authentication(userName: NEXUS_USERNAME, password: NEXUS_PASSWORD);
            }
            pom.groupId = "groupId"
            pom.artifactId = "artifactId"
            pom.version = "${versionMajor}.${versionMinor}.${versionPatch}"
        }
    }
}

some further reading for local repos here 在这里进一步阅读本地回购

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM