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

Missing option "Add timestamps to the Console Output" (Build Environment)

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • None
    • Jenkins 1.460
      Build Flow 0.3
      TimeStamper 1.2.2
      Red Hat Enterprise Linux 5.5 64 bit
      Sun Java 1.6.0_20

      It would be useful to support the TimeStamper plugin in Flow jobs.
      We can see what time each job is triggered / completes in a central place
      (because this info is available elsewhere in Jenkins, priority is set to Trivial)

          [JENKINS-13523] Missing option "Add timestamps to the Console Output" (Build Environment)

          Ben Golding created issue -
          Steven G Brown made changes -
          Component/s New: timestamper [ 15749 ]

          Richard Cross added a comment - - edited

          Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activities.

          Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority?

          Richard Cross added a comment - - edited Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activities. Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority?
          Ben Golding made changes -
          Priority Original: Trivial [ 5 ] New: Major [ 3 ]

          Ben Golding added a comment -

          Richard: changed priority to 'Major'

          Ben Golding added a comment - Richard: changed priority to 'Major'

          dan russell added a comment -

          Being groovy can always add your own, though would be nice if the option was supported

          println "job scheduled at" + new Date()
          build("job")
          println "job completed at" + new Date()

          dan russell added a comment - Being groovy can always add your own, though would be nice if the option was supported println "job scheduled at" + new Date() build("job") println "job completed at" + new Date()

          It seems that the timestamp is fully compatible with the Build Flow plugin, but it cannot be enabled through the UI due to Build Flow job types not having a "Build Environment" section.

          As a quick PoC, I tried added the timestamper wrapper config to the job's config.xml directly. After doing this the subsequent builds displayed timestamps as if it had been enabled normally. The downside is that as soon as the project's configuration is changed through the UI, the manual addition is removed

          Jim Carrothers added a comment - It seems that the timestamp is fully compatible with the Build Flow plugin, but it cannot be enabled through the UI due to Build Flow job types not having a "Build Environment" section. As a quick PoC, I tried added the timestamper wrapper config to the job's config.xml directly. After doing this the subsequent builds displayed timestamps as if it had been enabled normally. The downside is that as soon as the project's configuration is changed through the UI, the manual addition is removed
          Baptiste Mathus made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ] New: Damien Nozay [ dnozay ]
          Damien Nozay made changes -
          Assignee Original: Damien Nozay [ dnozay ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 143989 ] New: JNJira + In-Review [ 176054 ]

            Unassigned Unassigned
            bgolding Ben Golding
            Votes:
            7 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: