Skip to content
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

Open
nucatus opened this issue Sep 19, 2016 · 5 comments

Comments

@nucatus
Copy link

nucatus commented Sep 19, 2016

Since version 4.4.2 (inclusive) of the build-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 the build-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

screen_shot_2016-09-19_at_1_33_29_pm

screen_shot_2016-09-19_at_1_32_49_pm

@nucatus nucatus changed the title Artifact published only once, all the consequent publishing retries are void Artifact published only once, all the subsequent publishing retries are void - since version 4.4.2 Sep 19, 2016
@eyalbe4
Copy link
Contributor

eyalbe4 commented Sep 27, 2016

Thank you for reporting this @nucatus,
We've just committed that fixes this issue and created a snapshot version of the plugin with the fix.
Will you be able to try out the snapshot and let us know if it resolves the issue?
You can install the snapshot as follows:

buildscript {
    repositories {  
        maven() {
            url 'https://oss.jfrog.org/artifactory/oss-snapshot-local'
        }               
    }
    dependencies {
        classpath "org.jfrog.buildinfo:build-info-extractor-gradle:4.4.x-SNAPSHOT"
    }
}

Thanks.

@nucatus
Copy link
Author

nucatus commented Oct 7, 2016

Well, it seems it is fixed in the snapshot. Are these changes in the 4.4.5 release?

@eyalbe4
Copy link
Contributor

eyalbe4 commented Oct 7, 2016

No @nucatus, the changes will be included in the next release.

@romangurevitch
Copy link
Contributor

@nucatus, Artifactory gradle plugin version that fixes the issue was released, release version 4.4.6.

@nucatus
Copy link
Author

nucatus commented Oct 9, 2016

Thanks @romangurevitch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants