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

Last deployed/published/finished column

    Details

    • Similar Issues:

      Description

      Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end of the build (start-time + duration).

      Usually artifacts are only published on successful builds. Therefore it would be most useful if only stable builds was considered (optionally configurable?).

      It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last (successful) job finished.

      Extra points if the name of the column is configurable.
      More extra points if the build-status is selectable (last stable, last unstable, last aborted, etc).

        Attachments

          Activity

          per_bohlin Per Böhlin created issue -
          per_bohlin Per Böhlin made changes -
          Field Original Value New Value
          Description Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was available, approximated by the end-time (start-time + duration).

          It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last job finished.

          Extra points if the name of the column is configurable.
          Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end of the build (start-time + duration).

          It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last job finished.

          Extra points if the name of the column is configurable.
          per_bohlin Per Böhlin made changes -
          Description Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end of the build (start-time + duration).

          It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last job finished.

          Extra points if the name of the column is configurable.
          Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end of the build (start-time + duration).

          Usually artifacts are only published on successful builds. Therefore it would be most useful if only stable builds was considered (optionally configurable?).

          It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last (successful) job finished.

          Extra points if the name of the column is configurable.
          More extra points if the build-status is selectable (last stable, last unstable, last aborted, etc).
          fredg Fred G made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          fredg Fred G made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              fredg Fred G
              Reporter:
              per_bohlin Per Böhlin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: