Closed Bug 1961373 Opened 11 months ago Closed 11 months ago

upload semanticdb-kotlinc 0.5.0 to maven.mozilla.org

Categories

(Release Engineering :: General, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jcristau, Assigned: jcristau)

References

Details

Per https://phabricator.services.mozilla.com/D245420#8482992 we'd like to have this on maven.mozilla.org rather than a new repository.

I got upload credentials, and started uploading files to stage to check how it's going: https://maven-default.stage.mozaws.net/?prefix=maven2/com/github/mozsearch/semanticdb-kotlinc/v0.5.0/

Unfortunately the v0.5.0 breaks assumptions in the code we use to populate maven-metadata.xml:
https://github.com/mozilla-releng/maven-lambda/blob/3e61c01612899811ae15634c02f660997cbca515/maven_lambda/metadata.py#L227
https://github.com/mozilla-releng/mozilla-version/blob/2773f44195743699af9445b90ce75a020efe156f/mozilla_version/maven.py#L22-L29

[ERROR] ValueError: "maven2/com/github/mozsearch/semanticdb-kotlinc/v0.5.0/semanticdb-kotlinc-v0.5.0.pom" does not contain a valid version. See root error.
Traceback (most recent call last):
  File "/var/task/metadata.py", line 51, in lambda_handler
    uploaded_metadata_files = craft_and_upload_maven_metadata(
  File "/var/task/metadata.py", line 107, in craft_and_upload_maven_metadata
    metadata = metadata_function(bucket_name, pom_files)
  File "/var/task/metadata.py", line 128, in generate_release_maven_metadata
    latest_version = get_latest_version(versions_per_path)
  File "/var/task/metadata.py", line 209, in get_latest_version
    maven_versions = [
  File "/var/task/metadata.py", line 210, in <listcomp>
    _parse_version(version, path)
  File "/var/task/metadata.py", line 227, in _parse_version
    raise ValueError(

I see https://github.com/mozsearch/semanticdb-kotlinc/commit/b23c09f0ed57067600f08c828cf56f1ee3007f3e removed some code from build.gradle.kts that used to strip out the v prefix from the tag to populate the version number. Nicolas, I don't suppose you can make the next releases without that prefix?

Flags: needinfo?(nicolas.guichard)

I removed that code because Jitpack just uses whatever Git tags we set. I've pushed a plain 0.5.0 tag and deleted the v0.5.0 tag. The artifacts are now available at https://jitpack.io/com/github/mozsearch/semanticdb-kotlinc/0.5.0/ .

Flags: needinfo?(nicolas.guichard)
Summary: upload semanticdb-kotlinc to maven.mozilla.org → upload semanticdb-kotlinc 0.5.0 to maven.mozilla.org

Alright this is up now:
https://maven.mozilla.org/?prefix=maven2/com/github/mozsearch/semanticdb-kotlinc/

Thanks for the patience as I figured out the logistics, and let me know if that works / reopen if it doesn't :)

Assignee: nobody → jcristau
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED

As a followup (and reminder for next time): I missed a few checksum files in the initial upload, and the nexus proxy complains if it can't validate md5/sha1 for files that are requested, returning 404 to the client.

Blocks: 1973889
Blocks: 1988302
No longer blocks: 1988302
See Also: → 1988302
You need to log in before you can comment on or make changes to this bug.