Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1570

Prototype deployment of an incremental release to UC without use of Maven index

    Details

    • Similar Issues:
    • Epic Link:

      Description

      Allow a plugin developer to publish binaries to the regular update center without using maven-release-plugin at all (and without needing an entry in repository-permissions-updater): after pushing master changes that are successfully deployed to Incrementals, file a pull request against backend-update-center2 patching some simple text file to include the specified incremental release. In this scenario the plugin could even specify something like

      <revision>1</revision>
      

      so that the only interesting portion of the observed plugin version is the rev count. (Currently the Maven extension does not have an option to drop the -rc prefix; if it did, revision could be dropped altogether, which would look cleaner.)

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            The JEP mentions that a PR builder for this could run some sanity checks about the repository state (for example, that plugins are not requesting incompatible dependencies); but it could go further and inspect what is being changed in this PR:

            • The PR author is listed in repository-permissions-updater as being permitted to release this plugin. (Note that we would need a mapping between LDAP usernames and GitHub usernames. Which we are sorely missing anyway.)
            • The selected commit is an ancestor of the plugin’s current master head.
            Show
            jglick Jesse Glick added a comment - The JEP mentions that a PR builder for this could run some sanity checks about the repository state (for example, that plugins are not requesting incompatible dependencies); but it could go further and inspect what is being changed in this PR: The PR author is listed in repository-permissions-updater as being permitted to release this plugin. (Note that we would need a mapping between LDAP usernames and GitHub usernames. Which we are sorely missing anyway.) The selected commit is an ancestor of the plugin’s current master head.
            Hide
            jglick Jesse Glick added a comment -

            Note that this differs from the draft JEP for CD in that it proposes using a GitOps flow for publishing releases, rather than continuing to rely on the nondeterminism inherent in update-center2’s Artifactory scan.

            Show
            jglick Jesse Glick added a comment - Note that this differs from the draft JEP for CD in that it proposes using a GitOps flow for publishing releases, rather than continuing to rely on the nondeterminism inherent in update-center2 ’s Artifactory scan.

              People

              • Assignee:
                Unassigned
                Reporter:
                jglick Jesse Glick
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: