Michael Semb Wever created CASSANDRA-19536:
----------------------------------------------
Summary: Persist parameter defaults between builds in Jenkinsfile
Key: CASSANDRA-19536
URL: https://issues.apache.org/jira/browse/CASSANDRA-19536
Project: Cassandra
Issue Type: Task
Components: CI
Reporter: Michael Semb Wever
Assignee: Michael Semb Wever
When the Jenkinsfile is being used in a job that was created by dsl and
intended to be triggered by scm polling, e.g. post-commit, that dsl will want
to set alternative defaults for the Jenkinsfile parameters.
By default each build of the Jenkinsfile will restore the job's default
parameters (i.e. changing the defaults for the next build).
This is described in more detail here
[https://www.linkedin.com/pulse/build-jenkins-job-default-parameters-using-bipin-kumar-chaurasia/]
and summarised in a quick answer here
[https://stackoverflow.com/questions/57745451/how-can-i-override-a-jenkinsfiles-default-parameters]
Patch for this is here:
[https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/jenkinsfile-persist-parameters]
I'm waiting on INFRA-25694 to see if there are any other problems/changes in
the Jenkinsfile when it's running in ci-cassandra.a.o
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
