Fix Markdown lint warnings (MD029)
MD029 - Ordered list item prefix
This commit is contained in:
@@ -1556,13 +1556,13 @@ This section is for behavioral changes to the models that were not due to a bug
|
||||
|
||||
You can now make examples and tests be built in ns-3 in two ways.
|
||||
|
||||
1. Using `build.py` when ns-3 is built for the first time:
|
||||
* Using `build.py` when ns-3 is built for the first time:
|
||||
|
||||
```shell
|
||||
./build.py --enable-examples --enable-tests
|
||||
```
|
||||
|
||||
2. Using `waf` once ns-3 has been built:
|
||||
* Using `waf` once ns-3 has been built:
|
||||
|
||||
```shell
|
||||
./waf configure --enable-examples --enable-tests
|
||||
|
||||
@@ -68,9 +68,9 @@ When you fork ns-3-dev on Gitlab, you get access to some free hours of execution
|
||||
To customize the path:
|
||||
|
||||
1. Go to the project's **Settings > CI / CD**.
|
||||
2. Expand the **General pipelines** section.
|
||||
3. Provide `utils/tests/gitlab-ci.yml` as a value in the **Custom CI configuration path** field.
|
||||
4. Click **Save changes**.
|
||||
1. Expand the **General pipelines** section.
|
||||
1. Provide `utils/tests/gitlab-ci.yml` as a value in the **Custom CI configuration path** field.
|
||||
1. Click **Save changes**.
|
||||
|
||||
To perform a deeper test, you can manually run the daily or the weekly test. Go to the Gitlab interface, then enter in the CI/CD menu and select Pipelines. On the top, you can manually run a pipeline: select the branch, and add a variable `RELEASE` set to `daily` or `weekly` following your need, and then run it.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user