You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2025/09/01 11:16:00 UTC

[jira] [Assigned] (CASSANDRA-20875) fix resolution of Cassandra main branch upon job determination in .build/run-ci

     [ https://issues.apache.org/jira/browse/CASSANDRA-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Semb Wever reassigned CASSANDRA-20875:
----------------------------------------------

    Assignee: Michael Semb Wever

> fix resolution of Cassandra main branch upon job determination in .build/run-ci
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20875
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20875
>             Project: Apache Cassandra
>          Issue Type: Bug
>            Reporter: Stefan Miklosovic
>            Assignee: Michael Semb Wever
>            Priority: Normal
>
> We are currently resolving the job name by looking into "build.xml" and parsing the version from there. This works until we use "-b" option on ".build/run-ci" script which says which branch we want to use.
> Basically, we could be on "trunk" while specifying a branch via "-b" which is in fact a branch from cassandra-5.0. In that case we would run CI against "cassandra" / trunk job instead of "cassandra-5.0" job. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org