Skip to content

[JENKINS-1035] "Latest Artifacts" should read "Latest successful Artifacts" #24037

Closed

Description

@jenkins-infra-bot

If a job fails its artifacts are not saved by hudosn. I think this is the
intended behavior for building some kind of software.

We use use hudson to run tests and those jobs produce log files which we need if
a test has failed. Currently I have to dig into the workspace view in order to
find logs of a failed test. It would be better if hudson would collect the
artifacts of such a failed build and show these on the "Build artifacts" page.

In the job configuration page, under "Post-build Actions" > "Archive the
artifacts" > "Advanced..." could be a switch labelled "Archive artifacts even if
build failed".


Originally reported by gradopado, imported from: "Latest Artifacts" should read "Latest successful Artifacts"
  • status: Closed
  • priority: Major
  • component(s): other
  • resolution: Fixed
  • resolved: 2007-11-30T07:19:36+00:00
  • votes: 0
  • watchers: 0
  • imported: 2025-12-08
Raw content of original issue

If a job fails its artifacts are not saved by hudosn. I think this is the intended behavior for building some kind of software.

We use use hudson to run tests and those jobs produce log files which we need if a test has failed. Currently I have to dig into the workspace view in order to find logs of a failed test. It would be better if hudson would collect the artifacts of such a failed build and show these on the "Build artifacts" page.

In the job configuration page, under "Post-build Actions" > "Archive the artifacts" > "Advanced..." could be a switch labelled "Archive artifacts even if build failed".

  • environment: Platform: All, OS: All

Activity

  1. jenkins-infra-bot commented on Nov 29, 2007

    @jenkins-infra-bot
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment:

      Artifact archiver has no such logic in it. It will archive artifacts regardless of whether the build failed or succeeded.

      Maybe you are complaining about the "last successful artifacts" link in the project top page — perhaps you are saying that you want this to be just "last artifacts" in your case?

    Artifact archiver has no such logic in it. It will archive artifacts regardless
    of whether the build failed or succeeded.

    Maybe you are complaining about the "last successful artifacts" link in the
    project top page — perhaps you are saying that you want this to be just "last
    artifacts" in your case?

  2. jenkins-infra-bot commented on Nov 29, 2007

    @jenkins-infra-bot
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment:

      If that's the case, please reopen with appropriate title.

    If that's the case, please reopen with appropriate title.

  3. jenkins-infra-bot commented on Nov 30, 2007

    @jenkins-infra-bot
    Author
    gradopado:
    • Original comment link
    • Raw content of original comment:

      changed old summary "Archive the artifacts" allow for collecting artifacts of failed builds"

      Yes, you're right Kohsuke, the link on the top page has a misleading label. It is okay to present just the latest good build results. It's okay go to a build's page for accessing its logs.

      So please change the label and I'll be fine with it.

    changed old summary "Archive the artifacts" allow for collecting artifacts of
    failed builds"

    Yes, you're right Kohsuke, the link on the top page has a misleading label. It
    is okay to present just the latest good build results. It's okay go to a build's
    page for accessing its logs.

    So please change the label and I'll be fine with it.

  4. jenkins-infra-bot commented on Nov 30, 2007

    @jenkins-infra-bot
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment:

      Fixed as suggested in 1.160.

    Fixed as suggested in 1.160.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions