[
https://issues.apache.org/jira/browse/CASSANDRA-18699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747882#comment-17747882
]
Michael Semb Wever commented on CASSANDRA-18699:
------------------------------------------------
This is a consequence of separate stage jobs, and these jobs themselves
re-cloning the git branch and building from scratch.
The in-tree scripts solve (remove) the re-cloning problem. CASSANDRA-18133
The standalone jenkinsfile will remove (inline) the stage jobs, allowing us to
stash and unstash the build directory from the initial build step in the
pipeline. CASSANDRA-18594
> Python dtests upgrade tests mixed SHA runs
> ------------------------------------------
>
> Key: CASSANDRA-18699
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18699
> Project: Cassandra
> Issue Type: Bug
> Reporter: Berenguer Blasi
> Priority: Normal
>
> Hi adding a bug I noticed in jenkins:
> A- Commit SHA1
> B- Jenkins starts a test run and eventually starts python dtests
> C- Before B completes commit SHA2 comes in
> Python dtests in B will run mixed SHA1 and SHA2 versions of trunk. An example
> [https://ci-cassandra.apache.org/job/Cassandra-trunk-dtest-upgrade/1213/jdk=jdk_11_latest,label=cassandra-dtest,split=11/consoleFull|http://example.com]
> where both 2a458ba01dae3b35b62ad2ef361e1acb567c97f0 and the later
> a565711056c859398d0b26081b46e71d2076de1d get mixed up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
