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

No description recorded after release

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: release-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      This plugin prior to version 1.1 used to record a description (ex: Release# 1.0)
      after a release is made for a job.

      This functionality is missing from the latest version. Could you please
      re-introduce it?

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : petehayes
          Path:
          trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseWrapper.java
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/ReleaseBuildBadgeAction/badge.jelly
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/config.jelly
          trunk/hudson/plugins/release/src/main/webapp/help-releaseVersionTemplate.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=21248
          Log:
          JENKINS-4022 Changed approach so that build parameters do not have to be aware of the release plugin in order to be used. In this implementation the user specifies a release version template that can include references to configured build and release parameters, i.e. Release: ${releaseVersion}

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : petehayes Path: trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseWrapper.java trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/ReleaseBuildBadgeAction/badge.jelly trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/config.jelly trunk/hudson/plugins/release/src/main/webapp/help-releaseVersionTemplate.html http://fisheye4.cenqua.com/changelog/hudson/?cs=21248 Log: JENKINS-4022 Changed approach so that build parameters do not have to be aware of the release plugin in order to be used. In this implementation the user specifies a release version template that can include references to configured build and release parameters, i.e. Release: ${releaseVersion}
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : petehayes
          Path:
          trunk/hudson/plugins/release/pom.xml
          trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseStringParameterDefinition.java
          trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseStringParameterValue.java
          trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseVersionValue.java
          trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseWrapper.java
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterDefinition/config.jelly
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterDefinition/index.jelly
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterValue/value.jelly
          trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/ReleaseAction/index.jelly
          trunk/hudson/plugins/release/src/main/webapp/help-releaseParameter.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=21222
          Log:
          JENKINS-4022 Plugin now scans parameters configured for release and if any implement ReleaseVersionValue then that parameter's value is used as the release version. The release plugin also now contributes a new string parameter called Release String Parameter that is identical to the existing String Parameter but implements the ReleaseVersionValue.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : petehayes Path: trunk/hudson/plugins/release/pom.xml trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseStringParameterDefinition.java trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseStringParameterValue.java trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseVersionValue.java trunk/hudson/plugins/release/src/main/java/hudson/plugins/release/ReleaseWrapper.java trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterDefinition/config.jelly trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterDefinition/index.jelly trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseStringParameterValue/value.jelly trunk/hudson/plugins/release/src/main/resources/hudson/plugins/release/ReleaseWrapper/ReleaseAction/index.jelly trunk/hudson/plugins/release/src/main/webapp/help-releaseParameter.html http://fisheye4.cenqua.com/changelog/hudson/?cs=21222 Log: JENKINS-4022 Plugin now scans parameters configured for release and if any implement ReleaseVersionValue then that parameter's value is used as the release version. The release plugin also now contributes a new string parameter called Release String Parameter that is identical to the existing String Parameter but implements the ReleaseVersionValue.
          Hide
          petehayes Peter Hayes added a comment -

          This feature has been implemented in the 1.6 version of the release plugin. You
          will need to use the new Release String Parameter as the parameter that defines
          the release version in order for the plugin to pick up the release version and
          set it as the description.

          Show
          petehayes Peter Hayes added a comment - This feature has been implemented in the 1.6 version of the release plugin. You will need to use the new Release String Parameter as the parameter that defines the release version in order for the plugin to pick up the release version and set it as the description.
          Hide
          petehayes Peter Hayes added a comment -

          OK. I will look into adding this checkbox.

          Show
          petehayes Peter Hayes added a comment - OK. I will look into adding this checkbox.
          Hide
          shibug shibug added a comment -

          In order to maintain the compatibility with earlier release, it would make sense
          if you provide the checkbox option. Since this plugin is used for release,
          there is bound to be a parameter which contains the release version.

          I cannot think of any other way to determine the Release version other than
          searching through the log but that may be inconsistent

          Show
          shibug shibug added a comment - In order to maintain the compatibility with earlier release, it would make sense if you provide the checkbox option. Since this plugin is used for release, there is bound to be a parameter which contains the release version. I cannot think of any other way to determine the Release version other than searching through the log but that may be inconsistent
          Hide
          petehayes Peter Hayes added a comment -

          Yes this was removed. Since I modified the release plugin to be configured with
          arbitrary parameters, it does not know which of the parameters it should use as
          a description. I could introduce a checkbox on each parameter to indicate that
          it should be set as the description, but I don't particularly like this but I
          can add it to maintain the original support. Do you have other thoughts on how
          this can be achieved?

          As a side note, I thought I had been hearing that Hudson might be able to
          determine the "version" of the build. This would be generally better as it
          would work for all builds, not just for release builds.

          Show
          petehayes Peter Hayes added a comment - Yes this was removed. Since I modified the release plugin to be configured with arbitrary parameters, it does not know which of the parameters it should use as a description. I could introduce a checkbox on each parameter to indicate that it should be set as the description, but I don't particularly like this but I can add it to maintain the original support. Do you have other thoughts on how this can be achieved? As a side note, I thought I had been hearing that Hudson might be able to determine the "version" of the build. This would be generally better as it would work for all builds, not just for release builds.

            People

            • Assignee:
              petehayes Peter Hayes
              Reporter:
              shibug shibug
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: