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

Detect older configuration and auto-reconfigure job

XMLWordPrintable

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

      Since the 1.0 version of the plugin requires the user to separate out the load
      rules from the config spec, it takes a potentially large amount of work to
      manually do this. It would be better for users of the plugin if the plugin
      itself could detect that the configuration is out of date and automatically
      configure the separate rules by parsing the config spec.

          [JENKINS-4455] Detect older configuration and auto-reconfigure job

          Peter Hayes created issue -

          Andrew Bayer added a comment -

          I thought about this, but it wasn't quite as trivial as it seems at first
          glance. Remember, all base ClearCase configurations now need load rules -
          previously, only snapshot views did, so anyone using dynamic views wouldn't get
          anything out of this. In addition, the load rules for snapshot views in <1.0
          could be incompatible with what we need for load rules in >=1.0 (view paths
          could be included, etc), or could be in include files, etc... Yes, not doing
          anything automatically does require work, but I believe it's better to require
          work than to tell users it's being updated automatically and then not have the
          update work properly in many cases, without any way of notifying users of that.

          Andrew Bayer added a comment - I thought about this, but it wasn't quite as trivial as it seems at first glance. Remember, all base ClearCase configurations now need load rules - previously, only snapshot views did, so anyone using dynamic views wouldn't get anything out of this. In addition, the load rules for snapshot views in <1.0 could be incompatible with what we need for load rules in >=1.0 (view paths could be included, etc), or could be in include files, etc... Yes, not doing anything automatically does require work, but I believe it's better to require work than to tell users it's being updated automatically and then not have the update work properly in many cases, without any way of notifying users of that.

          Peter Hayes added a comment -

          Could this be optional then? In our case we have about 100 jobs that require
          updating and all of them use snapshot views with simple "load /..." settings at
          the bottom of the config specs. This setting wouldn't even have to be present
          in the UI, maybe just a system property that people can set to take advantage of
          this?

          Peter Hayes added a comment - Could this be optional then? In our case we have about 100 jobs that require updating and all of them use snapshot views with simple "load /..." settings at the bottom of the config specs. This setting wouldn't even have to be present in the UI, maybe just a system property that people can set to take advantage of this?
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 134528 ] New: JNJira + In-Review [ 174163 ]
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]

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

              Created:
              Updated: