Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53164

Rebrand from Essentials to Evergreen the "essentials jenkins plugin"

    XMLWordPrintable

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      Evergreen - Milestone 1

      Description

      Essentials Jenkins plugin =>

      • rename the plugin display name
      • change the artifactId (we generally do not do this, but I think in this case we should because it's 1) still early stage and 2) nobody is ever supposed to install this plugin manually anyway
      • rename the repo
      • rename the JIRA component

        Attachments

          Issue Links

          is blocked by

          Task - A task that needs to be done. INFRA-1753 Rename https://github.com/jenkinsci/essentials-plugin/ to evergreen-plugin

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            batmat Baptiste Mathus added a comment -
            Show
            batmat Baptiste Mathus added a comment - Rename of text and artifactId done through https://github.com/jenkinsci/essentials-plugin/pull/13 JIRA component renamed using the IRC bot GitHub repo to be done through INFRA-1753 as the IRC bot requires one being an admin to rename a github repo
            Hide
            Permalink
            batmat Baptiste Mathus added a comment -

            Good feedback on the PR to update evergreen about the cohabitation of the two artifactIds:

            • we should tombstone the essentials artifact anyway to avoid issues
            • we do not support yet removing things like plugins. @rtyler rightly says it might then be a good idea to do it now.

            => Tombstoning allows us to move forward right away by having the two plugins together. Then we can remove the essentials plugin from the disk later on by implementing deletions.

            Show
            batmat Baptiste Mathus added a comment - Good feedback on the PR to update evergreen about the cohabitation of the two artifactIds: we should tombstone the essentials artifact anyway to avoid issues we do not support yet removing things like plugins. @rtyler rightly says it might then be a good idea to do it now. => Tombstoning allows us to move forward right away by having the two plugins together. Then we can remove the essentials plugin from the disk later on by implementing deletions.

              People

              Assignee:
              batmat Baptiste Mathus
              Reporter:
              batmat Baptiste Mathus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: