1
我试图发布到Artifactory使用项目的Gradle包装和凭据键入用户的gradle.properties。使用Grail的gradlew和用户的gradle.properties文件发布到Artifactory
在我build.gradle
文件,我有以下的代码片段发布到Artifactory
:
artifactory {
contextUrl = "https://path.to/artifactory"
publish {
repository {
repoKey = 'plugins-release-local'
username = ${artifactory_user}
password = ${artifactory_password}
maven = true
}
defaults {
publications ('mavenJava')
}
}
}
publishing {
publications {
mavenJava(MavenPublication) {
from components.java
}
}
}
这里是我的gradle.properties
文件的内容:
[email protected] ~/.gradle
$ cat gradle.properties
artifactory_user=xxx
artifactory_password=yyy
的用户名和密码硬编码build.gradle
,这个作品:
./gradlew artifactoryPublish
在尝试试图通过CLI传递凭据从~/.gradle/gradle.properties
./gradlew artifactoryPublish
HTTP response code: 502. HTTP response message: Bad Gateway
读:
./gradlew -Dartifactory_user=xxx -Dartifactory_password=yyy artifactoryPublish
HTTP response code: 401. HTTP response message: Unauthorized
更新#每@RaGe的build.gradle的1
更新:
artifactory {
contextUrl = "https://path/to/artifactory"
publish {
repository {
repoKey = 'plugins-release-local'
username = artifactory_user
password = artifactory_password
maven = true
}
defaults {
publications ('mavenJava')
}
}
}
publishing {
publications {
mavenJava(MavenPublication) {
from components.java
}
}
}
结果:得到一个401而不是502的使用:
- ./gradlew artifactoryPublish
- ./gradlew -Dartifactory_user = XXX -Dartifactory_password = YYY artifactoryPublish
更新#2
Artifactory在通过Apache 2.2上的反向代理访问的Tomcat8/Java8上运行。
更新#3
注到解决方案:在Cygwin下,确保编辑正确的gradle.properties,位于C:\用户\ username.gradle \ gradle.properties
我一直在来回走,确认了我的gradle.properties文件中的凭据,并对我的build.gradle中的值进行了硬编码。当我对这些值进行硬编码时,它始终都能正常工作。否则,我得到了401. – TekiusFanatikus
你尝试了我建议的语法吗? – RaGe
是的,请参阅更新#1和#2 – TekiusFanatikus