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

          Hide
          mdonohue mdonohue added a comment -

          I'm not sure what you're asking for. Could you clarify? Giving an example would
          help.

          Show
          mdonohue mdonohue added a comment - I'm not sure what you're asking for. Could you clarify? Giving an example would help.
          Hide
          schmidtfx schmidtfx added a comment -

          we configured our build job as following

          • trigger each 10 minutes for scm changes
          • if there are changes -> start the build process
          • otherwise do nothing

          in our apache log file a svn request appears every 10 minutes
          so far so good
          but this request appears twice. first the hudson master asks the svn for updates
          and then the build client (other physical machine).

          in my opinion one svn update request should be enough.

          i hope this was more helpfull

          Show
          schmidtfx schmidtfx added a comment - we configured our build job as following trigger each 10 minutes for scm changes if there are changes -> start the build process otherwise do nothing in our apache log file a svn request appears every 10 minutes so far so good but this request appears twice. first the hudson master asks the svn for updates and then the build client (other physical machine). in my opinion one svn update request should be enough. i hope this was more helpfull
          Hide
          jamesdumay James Dumay added a comment -

          There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem with the latest version of Jenkins and the subversion plugin, reopen and comment with reproduction instructions.

          Show
          jamesdumay James Dumay added a comment - There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem with the latest version of Jenkins and the subversion plugin, reopen and comment with reproduction instructions.

            People

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

              Dates

              Created:
              Updated:
              Resolved: