Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-11813

beam-sdks-java-google-cloud-platform-bom files ends up in two nexus repositories

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P0
    • Resolution: Fixed
    • Affects Version/s: 2.28.0
    • Fix Version/s: 2.28.0
    • Component/s: build-system, sdk-java-core
    • Labels:
      None

      Description

      When building the Beam 2.28.0 RC1 I noticed that "beam-sdks-java-google-cloud-platform-bom-2.28.0" modules related files end up in two different Apache nexus staging repositories.

       

      (1) beam-sdks-java-google-cloud-platform-bom-2.28.0.pom in it's own repository

      (2) Everything else including signature/checksum files for above ends up in the regular nexus staging repository

      Seems like this module was recently added in https://github.com/apache/beam/pull/13737

      Not sure why this is happening but I suspect a mis-configuration somewhere.

      I believe this blocks release validation.

       

        Attachments

        1. repo1.png
          821 kB
          Chamikara Madhusanka Jayalath
        2. repo1-contents.png
          1.10 MB
          Chamikara Madhusanka Jayalath
        3. repo2.png
          807 kB
          Chamikara Madhusanka Jayalath
        4. repo2-contents.png
          768 kB
          Chamikara Madhusanka Jayalath
        5. Screen Shot 2021-02-16 at 14.49.26.png
          1016 kB
          Tomo Suzuki

          Activity

            People

            • Assignee:
              kileys Kiley Sok
              Reporter:
              chamikara Chamikara Madhusanka Jayalath
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: