-
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
Artifact published only once, all the subsequent publishing retries are void - since version 4.4.2 #98
Comments
Thank you for reporting this @nucatus,
Thanks. |
Well, it seems it is fixed in the snapshot. Are these changes in the 4.4.5 release? |
No @nucatus, the changes will be included in the next release. |
@nucatus, Artifactory gradle plugin version that fixes the issue was released, release version 4.4.6. |
Thanks @romangurevitch |
Since version
4.4.2
(inclusive) of thebuild-info-extractor-gradle
plugin, the artifacts are not published to the repository. It works only once, after the gradle cache is purged, and all the consequent publish commands are void, unless you purge the gradle cache again (NOT entirely, but thebuild-info-extractor-gradle
jar). In this case, only a build descriptor is published. (see the attached screenshots)This happens only with gradle 3.0 though. When gradle 2.14.1 is used, the artifacts are correctly published IF gradle is not ran as daemon. If gradle is running as daemon, the SAME behavior is observed regardless of which gradle version is used.
I tried this with a fresh clone of your example repository. This uses the 4.4.0 version of the plugin, but when using latests versions (4.4.2, 4.4.3, 4.4.4), the defect is observed.
The repository version we are using is Artifactory OSS, 4.7.5 rev 40176
The text was updated successfully, but these errors were encountered: