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

timestamps() randomly not recognized as a valid option

    XMLWordPrintable

Details

    • pipeline-model-definition 1.3.3

    Description

      timestamp() is not recognised as a valid option when job is triggered because of cron (If job is triggered manually issue it is not reproducible):

      org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
      WorkflowScript: 8: Invalid option type "timestamps". Valid option types: [authorizationMatrix, buildDiscarder, disableConcurrentBuilds, overrideIndexTriggers, skipDefaultCheckout]
      

      I am using the plugin in a Declarative pipeline like that:

      pipeline {
          agent { label 'foo' }
      
          options {
              buildDiscarder(logRotator(daysToKeepStr: '20', numToKeepStr: '100'))
              timestamps()
          }
         
         ...
          
          triggers {
              parameterizedCron('''
                  0 7 * * 1-5 % ENVIRONMENT=bar
              ''')
          }
      
          ...    
      }
      
      

      Attachments

        Issue Links

          Activity

            mrjoshwoodcock Josh Woodcock added a comment -

            We are on version 1.3.4.1 now. Is this resolved and released? 

            mrjoshwoodcock Josh Woodcock added a comment - We are on version 1.3.4.1 now. Is this resolved and released? 

            +1 still waiting for the fix as we are intermittently seeing this issue.

            historus Matthias Schulz added a comment - +1 still waiting for the fix as we are intermittently seeing this issue.

            any news?

            das999 Anatoliy Nenashev added a comment - any news?
            dnusbaum Devin Nusbaum added a comment -

            The fix discussed in earlier comments was released in Pipeline: Declarative 1.33, but I have seen reports from users still experiencing the problem even after that fix, so there are probably other similar problems in the codebase somewhere.

            dnusbaum Devin Nusbaum added a comment - The fix discussed in earlier comments was released in Pipeline: Declarative 1.33, but I have seen reports from users still experiencing the problem even after that fix, so there are probably other similar problems in the codebase somewhere.
            varun7447 Varun Reddy added a comment -

            We are still facing same issue with Jenkins 2.176.2. Is there anything that we need to do? Weird thing in a multibranch one of my development branch options {timestamps()} it works fine. but same repo with a new branch created from the clone of development branch it is failing. 

            varun7447 Varun Reddy added a comment - We are still facing same issue with Jenkins 2.176.2. Is there anything that we need to do? Weird thing in a multibranch one of my development branch options {timestamps()} it works fine. but same repo with a new branch created from the clone of development branch it is failing. 

            People

              Unassigned Unassigned
              kupas Victor Pascual
              Votes:
              18 Vote for this issue
              Watchers:
              41 Start watching this issue

              Dates

                Created:
                Updated: