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

Remove the clearcase view when user reconfigures job to change view name or remove clearcase support

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • clearcase-plugin
    • None
    • Platform: All, OS: All

      2 cases where Hudson can leave a "lost" view on the build server:

      1. User configures the job and changes the view name
      2. User disables clearcase support in the job

          [JENKINS-3507] Remove the clearcase view when user reconfigures job to change view name or remove clearcase support

          Peter Hayes created issue -

          Andrew Bayer added a comment -

          Taking issue.

          Andrew Bayer added a comment - Taking issue.

          Andrew Bayer added a comment -

          Remarking this as an enhancement request. It's not likely to be implemented any
          time soon, regrettably - there's no way for the ClearCase plugin to know when a
          job's SCM is changed away from ClearCase, nor to know that there's actually been
          a change to the view name. Both of those would require some sort of mechanism in
          Hudson core for firing actions when configurations change, but that does not
          exist currently.

          Andrew Bayer added a comment - Remarking this as an enhancement request. It's not likely to be implemented any time soon, regrettably - there's no way for the ClearCase plugin to know when a job's SCM is changed away from ClearCase, nor to know that there's actually been a change to the view name. Both of those would require some sort of mechanism in Hudson core for firing actions when configurations change, but that does not exist currently.

          Vincent Latombe added a comment -

          Case 1. should be handled correctly now (in trunk).

          I would add a new case : when workspace is changed (using custom workspace in free style project)

          Vincent Latombe added a comment - Case 1. should be handled correctly now (in trunk). I would add a new case : when workspace is changed (using custom workspace in free style project)

          Vincent Latombe added a comment -

          Workaround is to clean the workspace before modifying either :

          • view name
          • SCM
          • workspace location

          Vincent Latombe added a comment - Workaround is to clean the workspace before modifying either : view name SCM workspace location
          Vincent Latombe made changes -
          Assignee Original: Andrew Bayer [ abayer ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 133580 ] New: JNJira + In-Review [ 174050 ]

            Unassigned Unassigned
            petehayes Peter Hayes
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: