Details

    • Type: Publishing Support
    • Status: Closed
    • Priority: Major
    • Resolution: Automatically Closed
    • Group Id:
      null
    • Publishing Hostname:
      oss.sonatype.org
    • Modify publishing permissions?:
      No

      Description

      Hi!

      We (Elasticsearch) use oss.sonatype.org. Thanks very much for providing the service!

      Right now, we're trying to create some automation that can make the release process for us a little bit less painful. Right now, after a build is done locally and pushed up to the staging repo on oss.sonatype.org, a developer needs to log in and manually promote those builds to the public repo.

      In my reading, I've come across two main approaches for dealing with this problem. It seems that for v2 of the Nexus Repo manager, that the recommended approach is to use the Nexus Maven plugin. Is that correct? It also seems that for v3, it's possible to call the API directly in order to handling promoting builds from staging into the public repo.

      It's our preference not to have to use a plugin and to avoid modifying the project POM if we can help it. If we can call an API and have Jenkins promote the build for us, that would be ideal.

      So, two questions - is this workflow (without a plugin) possible with oss.sonatype.org right now? If it does indeed require v3 as I suspect it may, are there any plans to upgrade oss.sonatype.org?

      Any help or advice would be most appreciated!

      Cheers,

      -Mike Place

      mike.place@elastic.co

        Attachments

          Activity

            People

            Assignee:
            central-ossrh Bot Central-OSSRH
            Reporter:
            cachedout Mike Place
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title