Release

[BenFradet]

No description provided.

[BenFradet]

@wiktorolko mmh weird, this is what's getting published: https://bintray.com/snowplow/snowplow-maven/java-referer-parser#files/com/snowplowanalytics/java-referer-parser/build_7a78zkkfwr9j2dlg28ai6p06m$_run_closure3$_closure9@5c48b72c

the travis logs are here: https://travis-ci.org/snowplow-referer-parser/java-referer-parser/jobs/455483041#L618

[wiktorolko]

@BenFradet I'll have a look at it in the evening or tomorrow morning and I'll let you know what are my findings.

[wiktorolko]

The version element should be inside the pkg element like here:

pkg {
    version {
        ...
    }
}

currently it's at the same level. I'm sorry, I haven't noticed it as I've been developing it.

[BenFradet]

No worries 👍 , I published the first rc to bintray: https://bintray.com/snowplow/snowplow-maven/java-referer-parser.

I asked for the mirroring to jcenter which is required to mirror to central, this usually takes around a day.

[BenFradet]

the sync to central seems to fail https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds/456857476#L832

[wiktorolko]

Did you have a change to check why the sync to central fails? If it's the build.gradle and plugin config to blame, then my first guess would be replacing:

name = archivesBaseName (line 31)
groupId group (line 90)
version version (line 92)

with strings:

name = 'java-referer-parser' (line 31)
groupId 'com.snowplowanalytics' (line 90)
version '0.4.0-rc2' (line 92)

[BenFradet]

actually it seems we've gone one step backwards as it's not even published to bintray anymore https://bintray.com/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc2

[wiktorolko]

Are you able to identify the rc-1 build that got into the bintray? The page
https://bintray.com/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc1 says that it got updated Updated Nov 16, 2018, but all the rc-1 builds (https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds: #18, #21, #22) were failing exactly the same as the latest one.

Maven Central: HTTP/1.1 400 Bad Request might mean that we are missing some obligatory description/author/signing/whatever. Looking at the .jar are you able to identify what's missing?

[BenFradet]

I don't know what's missing, as far as files are concerned they all seem to be there https://bintray.com/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc1#files/com%2Fsnowplowanalytics%2Fjava-referer-parser%2F0.4.0-rc1

[wiktorolko]

I disagree with the statement that we've gone one step backwards as it's not even published to bintray anymore. I had a look at the builds history and the task: bintrayUpload was successful and bintrayPublish failed for both builds: #22 (rc1), #28 (rc2). The only difference is that the first one failed with 403, the other with 400.

build #22 (0.4.0-rc1) Nov, 16 (https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds/455923652). bintrayUpload task succeeded, bintrayPublish task FAILED (403), however, it's visible in bintray.

Task :bintrayUpload
Uploading to https://api.bintray.com/content/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc1/com/snowplowanalytics/java-referer-parser/0.4.0-rc1/java-referer-parser-0.4.0-rc1-sources.jar...
Uploaded to 'https://api.bintray.com/content/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc1/com/snowplowanalytics/java-referer-parser/0.4.0-rc1/java-referer-parser-0.4.0-rc1-sources.jar'.
...
> Task :bintrayPublish FAILED

* What went wrong:
Execution failed for task ':bintrayPublish'.
> Could not sync 'snowplow/snowplow-maven/java-referer-parser/0.4.0-rc1' to Maven Central: HTTP/1.1 403 Forbidden [message:In order to sync to Maven Central your package must be included in the JCenter repository]

build #28 (0.4.0-rc2) Nov, 19 (https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds/456857476). bintrayUpload task succeeded, bintrayPublish task FAILED (400), however, it's NOT visible in bintray.

Task ':bintrayUpload' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Gradle Bintray Plugin version: 1.8.4
Version 'snowplow/snowplow-maven/java-referer-parser/0.4.0-rc2' does not exist. Attempting to create it...
Created version '0.4.0-rc2'.
Uploading to https://api.bintray.com/content/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc2/com/snowplowanalytics/java-referer-parser/0.4.0-rc2/java-referer-parser-0.4.0-rc2-sources.jar...
Uploaded to 'https://api.bintray.com/content/snowplow/snowplow-maven/java-referer-parser/0.4.0-rc2/com/snowplowanalytics/java-referer-parser/0.4.0-rc2/java-referer-parser-0.4.0-rc2-sources.jar'.
...
:bintrayUpload (Thread[main,5,main]) completed. Took 5.241 secs.

:bintrayPublish (Thread[main,5,main]) started.
> Task :bintrayPublish FAILED
Task ':bintrayPublish' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Signed version '0.4.0-rc2'.
:bintrayPublish (Thread[main,5,main]) completed. Took 2.063 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':bintrayPublish'.
> Could not sync 'snowplow/snowplow-maven/java-referer-parser/0.4.0-rc2' to Maven Central: HTTP/1.1 400 Bad Request [status:Sync Failed, messages:[Problem extracting files to sync. Please try again in a bit.]]

I've googled for the "Problem extracting files to sync" and found some evidence that it's a temporary issue which happens when maven central has some problems:

• Around Nov,20th Sonatype had problems with full disk - see: https://twitter.com/sonatype_ops/status/1064900622703648768

Some threads where the issue got resolved after some time:

• Webjar for babel-runtime version 5.8.24 fails webjars/webjars#1231
• Issue deploying files to webjars webjars/webjars#1526
• Prepare for release snowplow/iab-spiders-and-robots-java-client#7
• https://stackoverflow.com/questions/40972473/unnable-to-sync-jcenter-to-maven-central

@BenFradet I know that you've retried on Nov, 30th (https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds/461792099) and it also failed with 400 Problem extracting files to sync., but how about giving it another try?

[BenFradet]

Thanks for the thorough investigation, I'll give it another shot no worries.

[BenFradet]

Turned on logging but that doesn't help much https://travis-ci.org/snowplow-referer-parser/java-referer-parser/builds/476815397#L1877

@mhadam have you seen this in the past with the java tracker?

[BenFradet]

I'm going to contact bintray support and see what they have to say

[wiktorolko]

Thanks for trying a few more times. Now we can be almost sure that the issue is on our end.

Could not sync 'snowplow/snowplow-maven/java-referer-parser/0.4.0-rc3' to Maven Central: HTTP/1.1 400 Bad Request [status:Sync Failed, messages:[Problem extracting files to sync. Please try again in a bit.

Maven Central complains that it's unable to extract files which we send in the request. In .travis.yml file I can see that there are three identical keys named secure under global (lines 15-17). How are they read? Can we verify it somehow they are not confused? Were they generated for this specific project or they are reused?

[BenFradet]

They're encrypted for this specific project through travis encrypt: https://docs.travis-ci.com/user/encryption-keys/

We've been using that for every project without issues.

Anyways I've asked bintray to help us out here, we'll see what they have to say.

[wiktorolko]

Did you get any feedback from the Bintray support?

[BenFradet]

yes, sorry was on holidays for the past two weeks, I'll try their suggestions at the end of the week 👍

[wiktorolko]

Did you have a chance to try their suggestions?

[BenFradet]

yes I just did and it didn't work: https://travis-ci.org/snowplow-referer-parser/java-referer-parser/jobs/495462843#L1892 ...