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

Should not change promotion level for read only components

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • clearcase-plugin
    • None
    • I am using Hudson 1.351 and ClearCase 7.0.1.0

      When you have read only components in a ClearCase project, after the build, the clearcase plugin attempts to change the promotion level to BUILT and fails as I am not the owner of the baseline. It should not attempt to change promotion level if it did not create a new baseline or at the least, it should recommend the baselines that it created for the modifiable components.

          [JENKINS-6093] Should not change promotion level for read only components

          VladDRussian added a comment -

          I have also ran into this issue. We worked around by using another job to actually recommend if the main build was successful. Since it was a legacy component we are moving it out of the main stream since it doesn't change and not referenced in the build so that we can have the main job deal with the CC opterations.

          VladDRussian added a comment - I have also ran into this issue. We worked around by using another job to actually recommend if the main build was successful. Since it was a legacy component we are moving it out of the main stream since it doesn't change and not referenced in the build so that we can have the main job deal with the CC opterations.

            Unassigned Unassigned
            zzstore zzstore
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: