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

Please add support for variables for page names

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      Jenkins ver. 1.424.1
      confluence-publisher 1.3
      Atlassian Confluence 3.5.9
    • Similar Issues:

      Description

      We have a parameterized job that we would like to post results on different pages depending on the parameters. Please allow the plugin to resolve variable names for the Page names.

        Attachments

          Activity

          rmyung Roger Myung created issue -
          jhansche Joe Hansche made changes -
          Field Original Value New Value
          Assignee sirot [ sirot ] Joe Hansche [ jhansche ]
          Hide
          jhansche Joe Hansche added a comment -

          The problem I have with this is that I try to do as much auto-detection up front as I can, which is why you see the ajax checks while entering the Space Name and Page Name fields. If using a parameter value in that field, the ajax check will fail, and the job itself will fail if you enter something invalid when initially building the job.

          That said, if there's an error, I agree it's not my problem and caused by the person configuring the job. The goal was just to be helpful up front while configuring it.

          As a last resort, I can just replace the current error with a warning if it detects a "$" in the space or page name. That just means it'll have to be up to you to make sure the parameter is formatted properly when kicking off a build.

          Show
          jhansche Joe Hansche added a comment - The problem I have with this is that I try to do as much auto-detection up front as I can, which is why you see the ajax checks while entering the Space Name and Page Name fields. If using a parameter value in that field, the ajax check will fail, and the job itself will fail if you enter something invalid when initially building the job. That said, if there's an error, I agree it's not my problem and caused by the person configuring the job. The goal was just to be helpful up front while configuring it. As a last resort, I can just replace the current error with a warning if it detects a "$" in the space or page name. That just means it'll have to be up to you to make sure the parameter is formatted properly when kicking off a build.
          Hide
          jhansche Joe Hansche added a comment -

          Implemented in the next release (1.4).

          Show
          jhansche Joe Hansche added a comment - Implemented in the next release (1.4).
          jhansche Joe Hansche made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Hide
          jhansche Joe Hansche added a comment -

          Released in version 1.4. It might take a bit for the repository to update.

          Show
          jhansche Joe Hansche added a comment - Released in version 1.4. It might take a bit for the repository to update.
          jhansche Joe Hansche made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 142576 ] JNJira + In-Review [ 205576 ]

            People

            • Assignee:
              jhansche Joe Hansche
              Reporter:
              rmyung Roger Myung
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: