[
https://issues.apache.org/jira/browse/CASSANDRA-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738296#comment-17738296
]
Michael Semb Wever commented on CASSANDRA-18594:
------------------------------------------------
bq. stage jobs don't always running on the same SHA as the pipeline's run,
Stage jobs run against the HEAD of their corresponding branch (each stage job
exists for each branch). When the stage job's build starts, it just tests
against HEAD, so that any commit that have landed on the branch after the
pipeline has started will be included.
There is logging of what SHA each stage build split runs on is and in the
pipeline summary there's checking between all the SHAs matching.
This does not apply to the devbranch, as the pipeline and each stage job is
parameterised by fork+branch of cassandra and cassandra-dtest repos.
> Standalone Jenkinsfile
> ----------------------
>
> Key: CASSANDRA-18594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18594
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 5.x
>
>
> Spin off CASSANDRA-18133
> Once all build and test scripts are in-tree, dockerised with their images
> in-tree too, the {{.jenkins/Jenkinsfile}} can be rewritten to be standalone.
> Today its inner stage jobs refer to already defined jobs by cassandra-builds'
> groovy dsl.
>
> This addresses the epic's stated existing problems:
> - mixture of jenkins dsl groovy, declarative and scripting pipeline.
> - different pre-commit and post-commit jenkins pipelines are used.
> In addition it addresses:
> - stage jobs don't always running on the same SHA as the pipeline's run,
> - a more readable Jenkinsfile
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
