[
https://issues.apache.org/jira/browse/CASSANDRA-18665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773186#comment-17773186
]
Michael Semb Wever edited comment on CASSANDRA-18665 at 10/9/23 8:35 AM:
-------------------------------------------------------------------------
quick replies, more (mostly code changes) to come for the others…
bq. There's a non-trivial burden associated with us carrying these scripts,
support, and artifacts along.
Keep in mind the cassandra-builds scripts will be deprecated and remain
for-the-most-part static and archived.
The in-tree scripts are bound to the branch's version, and can (and will) be
keep minimal to what that branch is compatible against.
bq. Why are we testing on python3.6?
Legacy. in-tree won't. Like most cassandra_job_dsl_seed.groovy it will not be
fixed/improved, just archived as everything moves over to in-tree and
standalone jenkinsfile.
bq. So the {1..11}seq for ccm creation - what's the failure rate and reason
look like there? Why 11 attempts?
That's downloading each patch version, not retries.
bq. Why do this at docker image compile time rather than runtime
Moving us towards dependency pinning, and permanently reproducible builds. But
at the end of the day we cannot pin everything.
bq. What's the story with the df and mount debugging on cluster install_dir?
just debug to figure out the current bug that's blocking me.
was (Author: michaelsembwever):
quick replies, more (mostly code changes) to come for the others…
bq. There's a non-trivial burden associated with us carrying these scripts,
support, and artifacts along.
Keep in mind the cassandra-builds scripts will be deprecated and remain
for-the-most-part static and archived.
The in-tree scripts are bound to the branch's version, and can (and will) be
keep minimal to what that branch is compatible against.
bq. Why are we testing on python3.6?
Legacy. in-tree won't. Like most cassandra_job_dsl_seed.groovy it will not be
fixed/improved, just archived as everything moves over to in-tree and
standalone jenkinsfile.
bq. So the {1..11}seq for ccm creation - what's the failure rate and reason look
like there? Why 11 attempts?
That's downloading each patch version, not retries.
bq. Why do this at docker image compile time rather than runtime
Moving us towards dependency pinning, and permanently reproducible builds. But
at the end of the day we cannot pin everything.
bq. What's the story with the df and mount debugging on cluster install_dir?
just debug to figure out the current bug that's blocking me.
> Update jenkins groovy dsl to use in-tree scripts
> ------------------------------------------------
>
> Key: CASSANDRA-18665
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18665
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
