Pipeline durability in GitHub Organization Project

[Jan Kosecki]

Hi, 

I've got a GitHub Organization Project that loads all requested repositories of the organization and builds them using Jenkinsfiles inside each repository. 
I've read this article https://jenkins.io/blog/2018/02/22/cheetah/ and I'm tempted to set dev builds to use "PERFORMANCE_OPTIMIZED" and only release builds to use "MAX_SURVIVABILITY". 
I tried to use "options { durabilityHint('PERFORMANCE_OPTIMIZED') }" like in article but it gets rejected by jenkins.

Invalid option type "durabilityHint". Valid option types: [ansiColor, catchError, checkoutToSubdirectory, lock, retry, script, skipDefaultCheckout, timeout, timestamps, waitUntil, warnError, withAWS, withContext, withCredentials, withEnv, ws] @ line 94, column 11.
             durabilityHint('MAX_SURVIVABILITY')

How can I set durability for different builds in GitHub Organization Project?

[Mark Waite]

The durabilityHint symbol is provided by the workflow-job plugin.  Do you have that plugin installed?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/da1bc51c-91b4-4e5f-885a-1396fe1f8e0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Jan Kosecki]

Yes, I do.

From what I see, "workflow-job" ID references "Pipeline: Job" plug-in chuj I have installed. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtELM1WQF0W4hdKG610d5-_tiC-nvX6A3WdzKUPgp06-%3DA%40mail.gmail.com.

[Mark Waite]

Are you running the most recent releases of the Pipeline plugins?  That symbol was first included in workflow job plugin version 2.17.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BroAGMPMqAnw7iojpJ%2BNDN%3DdUOWc_cNZJcv9jAPxpX2SwRGrA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Jan Kosecki]

Yes, I'm using version 2.33.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE4apO_cBhBh2XeF81z_ubiYd9itYNitO_aoAk52pnnJw%40mail.gmail.com.

[Devin Nusbaum]

You might be running into https://issues.jenkins-ci.org/browse/JENKINS-48556, where Declarative is intermittently unable to recognize valid option types. Some things that could cause that issue were fixed in Pipeline: Declarative 1.3.3, but I have seen reports from users on newer versions as well, so I think there are still some problems.

If you have any way to consistently reproduce the issue, or see any patterns on when it occurs, that would be helpful.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BroAGOFv-1bfViu0z1mP1jj0Mq1e%3Dqf7FahV%3DZ3-zjHTyYfdg%40mail.gmail.com.