tool version for CI runs and nix dev setup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 21
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
While I was debugging flash_controller I noticed that CI doesn't run the same tool version than what we were using locally through the nix package.
I think it would be nice to:
- report the toolversion of xcelium and VCS in the nightly/weekly runs (e.g. here
XCELIUM-23.09.002instead of justXCELIUM) - align the version of nix and CI
@machshev @mkj121
I'm not sure if we are allowed to publish the exact tool version. If not, is there a way to make this information available internally?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the tool versions used in the nix package with those used by the nightly and weekly CI runs, then inspect the generated reports linked in the issue. Done means the CI reports identify the Xcelium and VCS versions, the nix and CI versions are aligned, and the publication or internal-visibility decision is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100