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

ClearCase plugin may set baseline on wrong code

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • clearcase-plugin
    • None

      I think it is impossible to be certain that the code that is baselined by the ClearCase plugin is the same code that was built by Hudson. Even when using the "Lock" feature, the sequence used by the plugin is as follows:

      • Create the snapshot view
      • Lock the stream
      • Create the baseline
      • Build
      • Set promotion level
      • Recommend baseline
      • Unlock the stream

      I think the locking is not set correctly: It is still possible to deliver sources to the stream while the snapshot view is being created, before the lock is set. If this happens, Hudson will build a different codebase than the one that is baselined.

      I suggest the following order:

      • Lock the stream
      • Create the snapshot view
      • Create the baseline
      • Unlock the stream
      • Build
      • Set promotion level
      • Recommend baseline

      Note that the lock is set earlier, but also released earlier - when using a snapshot view, there is no need to keep the stream locked while building.

          [JENKINS-8356] ClearCase plugin may set baseline on wrong code

          Romain Seguy added a comment -

          Removed the clearcase-ucm-baseline plugin from the components, the issue is not related to it.

          Romain Seguy added a comment - Removed the clearcase-ucm-baseline plugin from the components, the issue is not related to it.

            Unassigned Unassigned
            atroq atroq
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: