[
https://issues.apache.org/jira/browse/CASSANDRA-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17997:
------------------------------------------
Fix Version/s: 3.0.30
3.11.16
4.0.11
4.1.3
5.0
(was: 3.0.x)
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
Source Control Link:
https://github.com/apache/cassandra/commit/8d3c30dde4b615835073089594003ca40a730992
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Improve git branch handling for CircleCI generate.sh
> ----------------------------------------------------
>
> Key: CASSANDRA-17997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17997
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
> Reporter: Derek Chen-Becker
> Assignee: Derek Chen-Becker
> Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.11, 4.1.3, 5.0
>
>
> The generate.sh script assumes a base git branch that is local and named
> after the official repo branch (e.g. `cassandra-3.11`). This may not be a
> local branch if the developer has recently cloned the repo and is creating a
> work branch, and will lead to the git commands in generate.sh failing:
>
> ```
> fatal: ambiguous argument 'cassandra-3.11...HEAD': unknown revision or path
> not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git <command> [<revision>...] -- [<file>...]'
> ```
> We should be able to make some sanity checks to better guide or warn the
> developer if things aren't set up properly to check against git.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
