Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: other
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      Seems that the usual way how jobs work on hudson is that there is one job for
      building a project and then if I want to have a subsequent job to run all unit
      tests, that job needs to download artifacts produced by that build job from
      Hudson. As a consequence, people usually add separate targets to their build
      scripts for running unit tests from hudson which download the build artifacts
      from the network.
      I think it would be nice if things could work the way how users would do it when
      running tests locally - i.e. use usual targets for building and then simply run
      a target for unit tests in the same workspace. This could be achieved by
      providing the subsequent jobs an exact snapshot of the workspace at the time
      when the parent job finished running.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                mmatula mmatula
              • Votes:
                42 Vote for this issue
                Watchers:
                30 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: