We have run into the same issue described in: https://issues.sonatype.org/browse/OSSRH-45673. We have a set of 5 open source projects which all deploy under the org.duracloud groupId. The full maven deployment (using nexus-staging-maven-plugin) is done in Travis CI but currently this results in multiple repositories being created due to Travis using multiple IPs.
The "work around" link in the ticket above points to a comment on another ticket which points to two URLs that both return 404s. My impression is that specifying a <stagingProfileId> in the nexus-staging-maven-plugin configuration will result in all project components being included in a single staging repo, without regard to client IP, thus allowing a deployment to complete properly. Alternatively, it seems that there is a way to "relax the IP address constraint" on the staging profile itself.
I have no problem adding a <stagingProfileId> setting to each of my projects. Given that I'm working with 5 projects that are often released at roughly the same time, would it work best to have 5 staging profiles, or will 1 suffice? I found the docs for creating a staging profile (https://help.sonatype.com/repomanager2/staging-releases/configuring-the-staging-suite), but cannot actually create a profile (this appears to be a pro feature).
1) Is adding a <stagingProfileId> config to the nexus-staging-maven-plugin the recommended way to solve the multiple-IP issue or is making a change to the staging profile itself preferred?
2) If I should use a profile ID, should there be a different one for each project or one ID for all? If it's one for all, will this impact my ability to deploy multiple projects at once?