Infrastructure
  1. Infrastructure
  2. INFRA-4482

Why is my upload to mvn spread across multiple repositories?

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Unresolved
    • Fix Version/s: Initial Clearing
    • Component/s: Nexus
    • Labels:
      None

      Description

      I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?

      I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.

      I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:

      {code}
        <servers>
          <!-- To publish a snapshot of some part of Maven -->
          <server>
            <id>apache.snapshots.https</id>
            <username>stack
            </username>
            <password>XXXX
            </password>
          </server>
          <!-- To publish a website using Maven -->
          <!-- To stage a release of some part of Maven -->
          <server>
            <id>apache.releases.https</id>
            <username>stack
            </username>
            <password>XXXX
            </password>
          </server>
        </servers>
        <profiles>
          <profile>
            <id>apache-release</id>
            <properties>
          <gpg.keyname>00A5F21E</gpg.keyname>
          <gpg.passphrase>XXXX
          </gpg.passphrase>
            </properties>
          </profile>
        </profiles>
      </settings>
      {code}

      My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup

      Thanks for any pointers.

        Activity

        Gavin made changes -
        Fix Version/s Initial Clearing [ 12325964 ]
        Tony Stevenson made changes -
        Workflow jira [ 12654596 ] INFRA Workflow [ 12711588 ]
        Hide
        stack added a comment -
        Workaround was to do upload from home rather than from work.
        Show
        stack added a comment - Workaround was to do upload from home rather than from work.
        Brian Fox made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Brian Fox [ brianf ]
        Resolution Unresolved [ 9 ]
        Hide
        Brian Fox added a comment -
        For now Nexus needs to have a stable ip for inbound deploys, it uses a combination of user agent, ip and user to divine a single stream of artifacts from a build.

        We are rewriting staging, planned for 2.1 in a month or so that will allow a different mode of staging where this won't be an issue.
        Show
        Brian Fox added a comment - For now Nexus needs to have a stable ip for inbound deploys, it uses a combination of user agent, ip and user to divine a single stream of artifacts from a build. We are rewriting staging, planned for 2.1 in a month or so that will allow a different mode of staging where this won't be an issue.
        Hide
        stack added a comment -
        I talked to our ops lads:

        "Yep. That's exactly the case. We have a NAT pool where we use 32 IP addresses for network address translation. Stability of the outgoing IP address is only guaranteed per destination IP address."

        It would seem that I have to find a build server that is inside a network that doesn't NAT pool.... I'll have to go scrounging if so.
        Show
        stack added a comment - I talked to our ops lads: "Yep. That's exactly the case. We have a NAT pool where we use 32 IP addresses for network address translation. Stability of the outgoing IP address is only guaranteed per destination IP address." It would seem that I have to find a build server that is inside a network that doesn't NAT pool.... I'll have to go scrounging if so.
        Hide
        Sebb added a comment -
        Surely the Nexus login should be sufficient to identify the client?

        Why does Nexus take any notice of the IP address?

        If I upload some files to a staging repo one day, but don't close the repo, I would expect to be able to upload to the same staging repo at a later stage even if my ISP gives me a new IP address; and I would expect to be able to upload a different host too.

        Also, a single IP address may be shared between multiple users (e.g. if uploading from a corporate intranet).
        Show
        Sebb added a comment - Surely the Nexus login should be sufficient to identify the client? Why does Nexus take any notice of the IP address? If I upload some files to a staging repo one day, but don't close the repo, I would expect to be able to upload to the same staging repo at a later stage even if my ISP gives me a new IP address; and I would expect to be able to upload a different host too. Also, a single IP address may be shared between multiple users (e.g. if uploading from a corporate intranet).
        Hide
        Brian Demers added a comment -
        It looks like your outbound connection keeps getting a different IP. Can you verify this is how your network is setup?
        Show
        Brian Demers added a comment - It looks like your outbound connection keeps getting a different IP. Can you verify this is how your network is setup?
        Sebb made changes -
        Component/s Nexus [ 12312660 ]
        Hide
        stack added a comment -
        I cannot pubish my staging repos even if I select all because each complains of missing elements. For example:

        {code}

        Staging ruleset evaluation on repository 'org.apache.hbase-049 (u:stack, a:38.99.102.224)' has failed.

        Staging Checksum Validation
            -Missing MD5: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.md5.'

        Staging Signature Validation
            -Missing Signature: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.asc' does not exist for 'hbase-0.92.0.jar'.

        {code}
        Show
        stack added a comment - I cannot pubish my staging repos even if I select all because each complains of missing elements. For example: {code} Staging ruleset evaluation on repository 'org.apache.hbase-049 (u:stack, a:38.99.102.224)' has failed. Staging Checksum Validation     -Missing MD5: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.md5.' Staging Signature Validation     -Missing Signature: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.asc' does not exist for 'hbase-0.92.0.jar'. {code}
        stack made changes -
        Field Original Value New Value
        Attachment Screen Shot 2012-02-23 at 9.50.58 AM.png [ 12515782 ]
        Hide
        stack added a comment -
        Picture of multiple repos for one artifact upload
        Show
        stack added a comment - Picture of multiple repos for one artifact upload
        stack created issue -

          People

          • Assignee:
            Brian Fox
            Reporter:
            stack
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development