Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 16 additions & 11 deletions .mise/README.md → .ci/mise/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ of Bazel and CodeChecker.
Files
-----

File | Description
------------------ | -----------
.mise/config.toml | Mise configuration, contains tools and tasks
.mise/init.sh | Source this script to install and init mise
.mise/run.sh | Run this script to run mise tasks from CI
.mise/print-env.sh | Utility script to show current versions of tools
File | Description
--------------------- | -----------
.ci/mise/config.toml | Mise configuration, contains tools and tasks
.ci/mise/init.sh | Source this script to install and init mise
.ci/mise/run.sh | Run this script to run mise tasks from CI
.ci/mise/print-env.sh | Utility script to show current versions of tools


How to use
Expand All @@ -26,15 +26,20 @@ How to use

To install and initialize mise just run the following:
```bash
source .mise/init.sh
source .ci/mise/init.sh
```

This script automatically downloads, installs, and runs `mise install`
to install all default tools.

> [!IMPORTANT]
> You must source the `init.sh` script (not just execute it) as it sets the
> `MISE_CONFIG_FILE` environment variable to point to the custom config location
> at `.ci/mise/config.toml`.

Note that once installed in your local environment mise and tools will
remain in the cache (`~/.local/share/mise/`), so next time if you run
`source .mise/init.sh` again it will take no time.
`source .ci/mise/init.sh` again it will take no time.

### After installation

Expand All @@ -49,18 +54,18 @@ And execute tasks and tests in the environment controlled by mise.

### Run tests

In `.mise` directory you can find `config.toml` file which describes
In `.ci/mise` directory you can find `config.toml` file which describes
all default tools and some test tasks - you can run them manually.
Or use wrapper script which basically runs initialization and then
executes `mise run` command.

For example, you can run unit tests with Bazel 7 and CodeChecker 6.25
using `pytest` with maximum verbosity:
```bash
.mise/run.sh test:7-25 test/unit -vvv
.ci/mise/run.sh test:7-25 test/unit -vvv
```

Note that `.mise/run.sh` script is just a convenience for CI (Continuous Integration).
Note that `.ci/mise/run.sh` script is just a convenience for CI (Continuous Integration).

### Uninstall

Expand Down
2 changes: 1 addition & 1 deletion .mise/config.toml → .ci/mise/config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ experimental = true


[vars]
run = ".mise/print-env.sh -vvv && pytest"
run = ".ci/mise/print-env.sh -vvv && pytest"


[tasks."install:bazel-6"]
Expand Down
1 change: 1 addition & 0 deletions .mise/init.sh → .ci/mise/init.sh
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ fi
mise trust --quiet
mise version
export MISE_CONDA_CONCURRENCY=1
export MISE_CONFIG_FILE=".ci/mise/config.toml"
mise install || mise install
mise reshim

Expand Down
File renamed without changes.
File renamed without changes.
6 changes: 3 additions & 3 deletions .github/workflows/mise.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -60,12 +60,12 @@ jobs:

- name: Install and init mise
run: |
source .mise/init.sh
source .ci/mise/init.sh

- name: Install all versions
run: |
.mise/run.sh install
.ci/mise/run.sh install

- name: Run Mise tests
run: |
.mise/run.sh ${{ inputs.arguments }}
.ci/mise/run.sh ${{ inputs.arguments }}