• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Blocker Blocker
    • clearcase-plugin
    • None
    • Hudson 1.353
      ClearCase Plugin 1.1.1

      I believe hudson tries to do the scm polling on the machine of the last successful build. We have an dynamic environment where an slave can't be exists next day. So an scm poll failed and clearcase plugin reports no changes. This job runs no more automatically.

      If this scenario happend, the clearcase plugin must run the scm poll on master or an available node.

        1. mylyn-context.zip
          5 kB
        2. patch.txt
          1 kB
        3. patchWithTests.txt
          8 kB

          [JENKINS-6184] SCM poll must run on master

          Hi,

          I started thinking on this issue, and I'm not quite satisfied with the patch you provided :

          • if all slaves the job has runned on are offline, it will always trigger the build even if no change occured. I don't think this is what you want to happen.

          Vincent Latombe added a comment - Hi, I started thinking on this issue, and I'm not quite satisfied with the patch you provided : if all slaves the job has runned on are offline, it will always trigger the build even if no change occured. I don't think this is what you want to happen.

          My current patch, based on kumi's

          Vincent Latombe added a comment - My current patch, based on kumi's

          If the problem is still valid, it should be handled by core rather than a specific scm implementation.

          Vincent Latombe added a comment - If the problem is still valid, it should be handled by core rather than a specific scm implementation.

          Craig Ringer added a comment -

          Poll git only on master

          Craig Ringer added a comment - Poll git only on master

            Unassigned Unassigned
            kumi kumi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: