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

"Monitor changes in java.net CVS/SVN repository" does not work for Jesey

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • javanet-plugin
    • None
    • Platform: All, OS: All

      We've tried to set the above option for project Jersey several times. The build
      does not get kicked-off automatically and the option gets unchecked
      automatically for some reason.

          [JENKINS-723] "Monitor changes in java.net CVS/SVN repository" does not work for Jesey

          This is because of the case insensitivity in e-mail address and the fact that
          jersey project uses "Jersey" as the job name, not "jersey."

          I've started making the change to make it work. The fix assumes that you don't
          have multiple jobs that only differ in case (like "FOO" and "foo"), which I
          think is reasonable, and is certainly true with our deployment of Hudson at
          kohsuke.sfbay.

          The fix should be available tomorrow morning when I deploy the new version of
          Hudson.

          Kohsuke Kawaguchi added a comment - This is because of the case insensitivity in e-mail address and the fact that jersey project uses "Jersey" as the job name, not "jersey." I've started making the change to make it work. The fix assumes that you don't have multiple jobs that only differ in case (like "FOO" and "foo"), which I think is reasonable, and is certainly true with our deployment of Hudson at kohsuke.sfbay. The fix should be available tomorrow morning when I deploy the new version of Hudson.

          super_kohsuke added a comment -

          Fix deployed.

          super_kohsuke added a comment - Fix deployed.

          mmatula added a comment -

          Still no change. I checked the "Monitor changes" for Jersey, saved, waited for
          about 1 hour, then made some minor changes in build.xml, committed them, waited,
          no build was triggered.
          So, I unchecked "Monitor changes..." for Jersey, saved, waited for 1 hour,
          checked it again, saved, waited for about 30 minutes, made changes in build.xml,
          committed, no build was triggered.

          mmatula added a comment - Still no change. I checked the "Monitor changes" for Jersey, saved, waited for about 1 hour, then made some minor changes in build.xml, committed them, waited, no build was triggered. So, I unchecked "Monitor changes..." for Jersey, saved, waited for 1 hour, checked it again, saved, waited for about 30 minutes, made changes in build.xml, committed, no build was triggered.

          I made one more follow up change. This seems to be working now.

          Kohsuke Kawaguchi added a comment - I made one more follow up change. This seems to be working now.

          mmatula added a comment -

          Thanks, it really works automatically now, although no Build Trigger seems to be
          checked in the config for Jersey. That's weird - seems like the reality got out
          of sync with the config page.
          Re-opening as a P4.

          mmatula added a comment - Thanks, it really works automatically now, although no Build Trigger seems to be checked in the config for Jersey. That's weird - seems like the reality got out of sync with the config page. Re-opening as a P4.

          huybrechts added a comment -

          Created an attachment (id=156)
          path to delete workspace if locked

          huybrechts added a comment - Created an attachment (id=156) path to delete workspace if locked

          huybrechts added a comment -

          sorry, attached patch to the wrong issue...

          huybrechts added a comment - sorry, attached patch to the wrong issue...

          Alan Harder added a comment -

          can this old item be closed? it actually looks to still be the case that builds
          are triggered but the Jersey config page does not show that option checked.. I
          assume this just means that Hudson is still subscribed to receive the change
          notifications even though the job config doesn't show it anymore. what happens
          if you check it and save the config?

          Alan Harder added a comment - can this old item be closed? it actually looks to still be the case that builds are triggered but the Jersey config page does not show that option checked.. I assume this just means that Hudson is still subscribed to receive the change notifications even though the job config doesn't show it anymore. what happens if you check it and save the config?

          Alan Harder added a comment -

          .

          Alan Harder added a comment - .

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

              Created:
              Updated:
              Resolved: