-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of tools #4
List of tools #4
Comments
Just got an idea. We could make install.sh create and update a tools list. And for all nightly and tag releases, the list would be fetched by a exegol-docs pipeline 🤷 I'd like to avoid having to maintain a list of hundreds of tools manually. Why not also find a way to have the following values for each tool added to the list:
|
Main idea
|
Data will be produced in the image and will then probably be extracted by a pipeline (either on exegol-images or exegol-docs) and be pushed to the exegol-docs repo. I'd like to publish a list of tools for each version of each image variant. |
Let's move forward with the following pseudo structure for now: function install_whatevertool() {
# install commands
# aliases, history, test commands
add-to-list "toolname,https://linkToTool/"
}
function add-to-list() {
echo $1 >> "/.exegol/installed_tools"
} The |
Done : ThePorgs/Exegol-images#125 |
We now need to code the parser on the doc side. |
It may be necessary that during the build of an image (Exegol-images) a step be added in order to recover the list "/.exegol/installed_tools" and from there, parse then push them on the docs repository with the right format. |
Also, the changes should be a pull request and not directly pushed to main from the docs repo to avoid issues. |
Let's do something like this. In my opinion, the best way to do this is to edit the pipeline of exegol-images. We can add a step between the (1) valid: in the first iteration of this iteration, we can simply check the number of columns in the file (number or |
I got an initial working setup https://github.com/ThePorgs/Exegol-images/actions/runs/5618467445/job/15224175922 It produces what follows It's a start. I now need to do some testing, but I'm pretty happy with the result, we're close to a v1 ! |
Regarding the nightly tag, i don't thin we need archive for each commit, it will be too much, regarding nightly we only keep the latest nightly version and archive for the stable releases only imo. |
Agreed. I pushed the new pipelines steps on production. We'll have to keep an eye on it on the next iterations of the pipelines. |
We're good to go. Pipelines are in prod. |
Re-opening, need to improve the pipeline |
Should be alright now, closing |
We need to document the tools installed in exegol. In my opinion, it should end up in the Exegol images section.
The text was updated successfully, but these errors were encountered: