• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • clearcase-plugin
    • None
    • Platform: All, OS: All

      The way the plug-in is implemented makes it impossible to recommend baselines if
      locked builds is used. While the stream is locked no modifications are allowed
      which means that the baseline can’t be recommended since it in fact modifies the
      streams. I think the lock should be released at the beginning of ‘perform’ in
      the publisher. By then the baseline has been created and the view rebased and
      it’s ok to unlock the stream. The publisher could go on and promote/demote and
      finally recommend the baseline.

      I think that the current solution could never work. I’ll be happy to fix this if
      someone with commit-status could make sure that it ends up in the svn-repo.

      I've been told at the mailing-list that the workaround is to exclude the
      build-user from the lock but I believe that it needs to be fixed in the plugin.

          [JENKINS-3305] Incorrect handling of locked builds

          sunfire added a comment -

          Feel free to fix this.

          sunfire added a comment - Feel free to fix this.

            sunfire sunfire
            henrikreinhold henrikreinhold
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: