[
https://issues.apache.org/jira/browse/CASSANDRA-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017663#comment-18017663
]
Stefan Miklosovic commented on CASSANDRA-20875:
-----------------------------------------------
I ve done
{code}
~/dev/cassandra/cassandra-instaclustr/cassandra [trunk L|⚑ 171]
14:58 $ .build/run-ci -b mck/20875/5.0 -r
https://github.com/thelastpickle/cassandra.git -p packaging
Enter Jenkins password:
Build number: 80
Jenkins UI at
http://pre-ci.cassandra.apache.org/job/cassandra/80/pipeline-overview/
Waiting for build to complete… 00:59 |
{code}
while I was on my "trunk" branch (
~/dev/cassandra/cassandra-instaclustr/cassandra [trunk L ...)
> 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
> Components: CI
> 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: [email protected]
For additional commands, e-mail: [email protected]
