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

Using description setter plugin causes non-parametrized build to become parametrized

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Tomcat 7.0

      I've recently updated mu installation and noticed that now when I rebuild anything that has description set I get an extra parameter named "DESCRIPTION_SETTER_DESCRIPTION".

      This makes no sense to me. Why would I want to pre-set description of a build. It MUST be automatically set for most of the jobs we have (e.g. with application version that was built). If I wanted a build parameter like that I would add it manually.

      Please change this behavior. It's annoying and confusing for our staff.

          [JENKINS-32472] Using description setter plugin causes non-parametrized build to become parametrized

          Maciej Jaros added a comment -

          I've temporarily resolved the situation by downgrading to 1.9. After downgrade it is required to build jobs that were build with 1.10 version. Required if you want rebuild to work correctly (i.e. don't show "DESCRIPTION_SETTER_DESCRIPTION" parameter).

          Maciej Jaros added a comment - I've temporarily resolved the situation by downgrading to 1.9. After downgrade it is required to build jobs that were build with 1.10 version. Required if you want rebuild to work correctly (i.e. don't show "DESCRIPTION_SETTER_DESCRIPTION" parameter).

          This behaviour is ridiculous. Please fix.
          Exposing the description as env variable by default, which is then passed as -D option in case of some build step types, is a no-go as well. Causes build to fail on many occasions.

          Tomasz Przybysz added a comment - This behaviour is ridiculous. Please fix. Exposing the description as env variable by default, which is then passed as -D option in case of some build step types, is a no-go as well. Causes build to fail on many occasions.

          zhh205 added a comment -

          Warings in log:

          WARNUNG: Skipped parameter `DESCRIPTION_SETTER_DESCRIPTION` as it is undefined on `ReleaseCandidate`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach
          

          although the job ReleaseCandidate ist not parameterized.
          According to https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170, this feature (JENKINS-17461) should be considered as not secure. IMO this feature can be achived otherwise, or at least the implementation is too intrusive.

          zhh205 added a comment - Warings in log: WARNUNG: Skipped parameter `DESCRIPTION_SETTER_DESCRIPTION` as it is undefined on `ReleaseCandidate`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters= true ` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach although the job ReleaseCandidate ist not parameterized. According to https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 , this feature ( JENKINS-17461 ) should be considered as not secure. IMO this feature can be achived otherwise, or at least the implementation is too intrusive.

            huybrechts huybrechts
            nux Maciej Jaros
            Votes:
            13 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: