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

CC UCM Baseline plugin fails to pull down data when subcomponents of a composite component reside in different pvobs.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • None
    • Using CC plugin 1.3.3 and CC UCM Baseline Plugin 1.7.1 (W2K3)

      Using CC plugin 1.3.3 and CC UCM Baseline Plugin 1.7.1 (W2K3)

      Is anyone else seeing issue with Composite Baselines whose sub componets are located in other pvobs?

      i.e

      MyCompositeComponent (PVOB_A)

      SubComponent1 (PVOB_A)

      SubComponent2 (PVOB_A)

      SubComponent3 (PVOB_B) <--- Fails to load b/c it tries to look for its baseline in PVOB_A and not PVOB_B

      This issue sounds alot like http://issues.hudson-ci.org/browse/HUDSON-7014

          [JENKINS-8695] CC UCM Baseline plugin fails to pull down data when subcomponents of a composite component reside in different pvobs.

          Romain Seguy added a comment -

          Hi Elias,

          I've attached a version of clearcase-ucp-baseline.hpi with a fix. As I don't have multi-pvobs samples, may you please confirm it fixes the issue?

          Thanks

          Romain Seguy added a comment - Hi Elias, I've attached a version of clearcase-ucp-baseline.hpi with a fix. As I don't have multi-pvobs samples, may you please confirm it fixes the issue? Thanks

          Elias Mata added a comment -

          Can i test this on Hudson or does it have to be Jenkins?
          Is this fix applied to both Hudson and Jenkisn or just Jenkins?

          Elias Mata added a comment - Can i test this on Hudson or does it have to be Jenkins? Is this fix applied to both Hudson and Jenkisn or just Jenkins?

          Romain Seguy added a comment -

          It will work on both because it's compiled against an "old" version of Hudson (1.375).

          Romain Seguy added a comment - It will work on both because it's compiled against an "old" version of Hudson (1.375).

          Elias Mata added a comment -

          But if it works as expected then the fix will only be "packaged" with future jenkins releases and not hudson releases correct?

          Elias Mata added a comment - But if it works as expected then the fix will only be "packaged" with future jenkins releases and not hudson releases correct?

          Romain Seguy added a comment -

          No, it will be packaged for Hudson 1.375 and, as long Hudson and Jenkins have the same APIs, it will work on both.

          Romain Seguy added a comment - No, it will be packaged for Hudson 1.375 and, as long Hudson and Jenkins have the same APIs, it will work on both.

          Elias Mata added a comment -

          So the fix worked!!
          Thanks for the quick turnaround.

          Is it safe to say that no matter where someone submits an issue/defect to http://issues.jenkins-ci.org or http://issues.hudson-ci.org it will be shared across both hudson and jenkins eventhough they have forked?

          That seems to be the case since i opened the same defect in both sites yet the hudson one was closed stating it was a duplicate from the one in jenkins.

          If they are sharing fixes then has this truly forked?

          Elias Mata added a comment - So the fix worked!! Thanks for the quick turnaround. Is it safe to say that no matter where someone submits an issue/defect to http://issues.jenkins-ci.org or http://issues.hudson-ci.org it will be shared across both hudson and jenkins eventhough they have forked? That seems to be the case since i opened the same defect in both sites yet the hudson one was closed stating it was a duplicate from the one in jenkins. If they are sharing fixes then has this truly forked?

          Romain Seguy added a comment -

          It's safe to say "no matter when someone submits etc.", I for the moment check issues on both trackers. I will be like that for the months to come.

          Notice that I've not made any decision on my plugin regarding its use on Hudson or Jenkins, for the moment it runs on both servers and I'll try to go as-is as long as possible.

          Romain Seguy added a comment - It's safe to say "no matter when someone submits etc.", I for the moment check issues on both trackers. I will be like that for the months to come. Notice that I've not made any decision on my plugin regarding its use on Hudson or Jenkins, for the moment it runs on both servers and I'll try to go as-is as long as possible.

          Elias Mata added a comment -

          Has this fix made it into any of the new Hudson of Jenkins releases?
          I don't see it in there change logs.

          -Eli

          Elias Mata added a comment - Has this fix made it into any of the new Hudson of Jenkins releases? I don't see it in there change logs. -Eli

          Romain Seguy added a comment -

          I've made a release yesterday evening, French-time, on Jenkins side. I've not checked if the plugin gets displayed in the update center. The binary is available on Jenkins' Maven repo: http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/clearcase-ucm-baseline/1.7.3/

          Romain Seguy added a comment - I've made a release yesterday evening, French-time, on Jenkins side. I've not checked if the plugin gets displayed in the update center. The binary is available on Jenkins' Maven repo: http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/clearcase-ucm-baseline/1.7.3/

          Romain Seguy added a comment -

          Fixed in 1.7.3

          Romain Seguy added a comment - Fixed in 1.7.3

            rseguy Romain Seguy
            out2000_98 Elias Mata
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: