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

Client and Server triggers for SCM changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: Linux
    • Similar Issues:

      Description

      In our system there is a Hudson master and a client.
      The build will be triggered by SCM (Subversion) changes.

      In our Apache Logfile we can see that the master triggers for updates. Also the
      client checks the SCM for changes, although there are no changes.

      In my opinion it should be adequate that only one instance checks the SCM for
      updates.

      Thanks

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            schmidtfx schmidtfx
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: