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

CVS Changes not reported for jobs if using a branch

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      We build from a branch in CVS and the changes are not getting captured in
      Hudson's change log. It does pull the changes out of CVS and builds them, but
      the changes don't get reported with the job status. See the below output from
      Hudson's console output to show that it actually identified one file update and
      one file removal, but when I look at the Changes for the job, it shows no changes.

      I just upgraded to Hudson 1.322. This feature was working on 1.319.

      Building on master
      [workspace] $ cvs -q -z3 update -PdC -r branch_name -D "Wednesday, September 2,
      2009 10:01:00 PM UTC"
      ? .cvsignore
      ? cppcheck-result.xml
      ? idl/sloccount.sc
      ? lib/sloccount.sc
      ? resources/sloccount.sc
      ? unittestutils/sloccount.sc
      ? xml/sloccount.sc
      U devices/sara/SARADevice.cpp
      P resources/testwaveformncw/TestWaveformNcw.cpp
      $ computing changelog

          [JENKINS-4380] CVS Changes not reported for jobs if using a branch

          msb264 added a comment -

          Chiming in to report experiencing this issue as well.

          Using v1.323. I do not recall if it was working for me in previous versions.

          msb264 added a comment - Chiming in to report experiencing this issue as well. Using v1.323. I do not recall if it was working for me in previous versions.

          jmboulos added a comment -

          @msb264
          Thanks for chiming in. I was wondering if anyone was seeing this issue. I had
          to roll back to version 1.319 where it seems to be working, but there are a lot
          of good fixes in 1.320+ that I want, but cannot upgrade till this feature is
          fixed. If I can't tell what is going into a build, it devalues the use of
          Hudson tremendously.

          Since I opened the ticket, I did upgrade to 1.323 and I also saw the problem
          there as you did.

          jmboulos added a comment - @msb264 Thanks for chiming in. I was wondering if anyone was seeing this issue. I had to roll back to version 1.319 where it seems to be working, but there are a lot of good fixes in 1.320+ that I want, but cannot upgrade till this feature is fixed. If I can't tell what is going into a build, it devalues the use of Hudson tremendously. Since I opened the ticket, I did upgrade to 1.323 and I also saw the problem there as you did.

          jimg777 added a comment -

          This seems to be a duplicate of Bug 4324. jmboulos, if you agree, maybe you can
          mark this as a duplicate of that bug and the votes can be combined.

          jimg777 added a comment - This seems to be a duplicate of Bug 4324. jmboulos, if you agree, maybe you can mark this as a duplicate of that bug and the votes can be combined.

          jmboulos added a comment -

          @jimg777
          Great catch, thanks. I didn't catch it in my search. I'll mark it now.

              • This issue has been marked as a duplicate of 4324 ***

          jmboulos added a comment - @jimg777 Great catch, thanks. I didn't catch it in my search. I'll mark it now. This issue has been marked as a duplicate of 4324 ***

            Unassigned Unassigned
            jmboulos jmboulos
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: