-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error publishing build info using Gradle Artifactory plugin #476
Comments
@e88z4, |
Where can I get the latest release (4.24.0) of Gradle Artifactory Plugin? https://bintray.com/jfrog/jfrog-jars/build-info-extractor-gradle says the latest version is 4.21.0 |
I have the same error with |
@e88z4 Did you ever resolve this? I have the same issue. I suspect that our maven repository does not allow publishing I would also be happy to turn off build info completely with artifactory {
contextUrl = 'http://repo.myorg.com/artifactory' //The base Artifactory URL if not overridden by the publisher/resolver
publish {
contextUrl = 'http://repo.myorg.com/artifactory' //The base Artifactory URL for the publisher
//A closure defining publishing information
repository {
...
ivy {
....
}
}
defaults {
...
publishBuildInfo = false //Publish build-info to Artifactory (true by default)
publishArtifacts = true //Publish artifacts to Artifactory (true by default)
publishPom = true //Publish generated POM files to Artifactory (true by default).
publishIvy = true //Publish generated Ivy descriptor files to Artifactory (true by default).
}
} However this doesn't seem to be supported in the Gradle Kotlin DSL. There is |
@e88z4 & @raptium bintray is deprecated and there you will not found any new version. |
Describe the bug
When publishing build information after publishing the artifact in our pipeline, we encountered the following error.
build.gradle publishing content
To Reproduce
Declarative pipeline step executing the gradle script execution:
Expected behavior
Build info is being published correctly to Artifactory.
Versions
The text was updated successfully, but these errors were encountered: