cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andres de la Peña (Jira) <>
Subject [jira] [Commented] (CASSANDRA-16989) Add environment variables to CircleCI config generation script
Date Mon, 27 Sep 2021 11:47:00 GMT


Andres de la Peña commented on CASSANDRA-16989:

[~bereng] thanks for the input, I have tried to address those problems in the last commits:
{quote}This seems wrong
./ -a
ERROR: Cannot use option -a with options -l, -m, -h or -e
That was due to a problem with how the boolean where managed and a couple of typos, it should
be fixed by [this commit|].
{quote}Also using -l, -m or -h will always display the help at the end no matter what.
I don't see that one, help is only printed when there are no arguments or when there is an
error on them. Are you still seeing that problem with the last changes?
{quote}Run -m and file is generated. Run -l with an invalid env var and file is overwritten
with the -l one instead of erroring out {{./ -m; ./ -l -e pepe=CASSANDRA-pepe}}
Good catch, I have moved the env vars validation to do it before the file generation, [here|].
{quote}Seems sed is not working?
Setting environment variable DTEST_BRANCH: CASSANDRA-pepe
sed: can't read s|- DTEST_BRANCH:.*|- DTEST_BRANCH: CASSANDRA-pepe|: No such file or directory
That's due to differences between versions of sed, it should work with [this change|].

> Add environment variables to CircleCI config generation script
> --------------------------------------------------------------
>                 Key: CASSANDRA-16989
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Normal
>          Time Spent: 10m
>  Remaining Estimate: 0h
> The purpose of this ticket is adding arguments to the CircleCI config generation script
allowing to set the values specific environment variables such as {{DTEST_REPO}} or {{DTEST_BRANCH}}
in the generated {{.circleci/config.yml}} file. For example, we could generate a CircleCI
config file with MIDRES specifying a dtest repo and branch by running:
> {code}
> -m \
>   -e DTEST_REPO=git:// \
> {code}
> Or we could set the test multiplexer for repeating a specific test with HIGHRES:
> {code}
> -h \
>   -e REPEATED_UTEST_TARGET=testsome \
>   -e REPEATED_UTEST_CLASS=org.apache.cassandra.cql3.ViewTest \
>   -e REPEATED_UTEST_METHODS=testCompoundPartitionKey,testStaticTable \
> {code}
> This can be useful on its own so we don't have to manually edit the {{config-2_1.yml}}/{{config.yml}},
and it can also be useful for automation scripts manipulating these files.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message