• Icon: Patch Patch
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Platform: All, OS: All

      Some of our projects check out dozens of top-level CVS modules. So our console
      output often has such meaningful entries as

      $ cvs -q -z9 update -PdC
      $ cvs -q -z9 update -PdC
      P build.xml
      $ cvs -q -z9 update -PdC
      $ cvs -q -z9 update -PdC
      $ cvs -q -z9 update -PdC
      $ cvs -q -z9 update -PdC
      $ cvs -q -z9 update -PdC
      P build.xml
      $ cvs -q -z9 update -PdC

      Hmm, what was it updating now?

      It would be preferable to run CVS update just once, at the top level, which
      would probably be faster and also print more informative paths. But in any case
      it would also be helpful to see what dir a command is being run in. Attaching
      (as yet untested) patch which should give that information succinctly and be
      useful in our case at least.

          [JENKINS-65] Print cwd when running CVS commands

          Jesse Glick created issue -
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: www [ 15484 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 130138 ] New: JNJira + In-Review [ 199541 ]

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: