.github: Add documentation workflow and Containerfile - #2114
Conversation
|
@bia1708 with https://github.com/adi-innersource/ghdl/pull/379 merged, this should be merged too. |
| - uses: actions/checkout@v7 | ||
| - name: Ensure SDKs | ||
| run: | | ||
| [[ -f "$SOURCE_AMD_XILINX" ]] && echo "vivado=true" >> $GITHUB_ENV || : |
There was a problem hiding this comment.
why not fail this step if vivado isn't in the PATH and prevent it getting to the Build Libraries step?
There was a problem hiding this comment.
I want to keep it functional on fallback ubuntu-latest without any SDK, the documentation will be incomplete, but still builds. This way, forks of the repository remain functional.
| github.event_name == 'pull_request' || | ||
| github.ref_type == 'tag' | ||
|
|
||
| steps: |
There was a problem hiding this comment.
Shouldn't this be skipped for PRs?
| push: | ||
| branches: | ||
| - main | ||
| pull_request: |
There was a problem hiding this comment.
If we build docs for PRs to any branch, shouldn't we also build them for pushes to release branches as well?
There was a problem hiding this comment.
I will run on tag created instead of branch
4070e13 to
be81918
Compare
| push: | ||
| branches: | ||
| - main | ||
| pull_request: |
There was a problem hiding this comment.
I will run on tag created instead of branch
| - uses: actions/checkout@v7 | ||
| - name: Ensure SDKs | ||
| run: | | ||
| [[ -f "$SOURCE_AMD_XILINX" ]] && echo "vivado=true" >> $GITHUB_ENV || : |
There was a problem hiding this comment.
I want to keep it functional on fallback ubuntu-latest without any SDK, the documentation will be incomplete, but still builds. This way, forks of the repository remain functional.
| github.event_name == 'pull_request' || | ||
| github.ref_type == 'tag' | ||
|
|
||
| steps: |
Add minimal Containerfile with the dependencies for the SDK AMD Xilinx (vitis, vivado). Signed-off-by: Jorge Marques <jorge.marques@analog.com>
If SOURCE_AMD_XILINX exists, source it and use to build the libraries, since the component.xml IP-XACT data is used to verify the documentation. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
The ZynqMP guides was split into multiple pages: - adrv9009 quickstart zynqmp + adrv9009 quickstart zcu102 + adrv9009 quickstart zc706 + adrv9009 quickstart kcu105 + adrv9009 quickstart a10gx + adrv9009 quickstart a10soc Link quickstart pages instead. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
e873b7d to
87d173b
Compare

PR Description
Add documentation build on GitHub Actions
Adds full featured documentation builds to GitHub Actions, including building the IP cores with AMD Xilinx tools to generate the IP-XACT metadata.
The IP-XACT is used to verify and complete the documentation, for example, generate the IP block SVG, enrich the parameters and ports tables.
If AMD Xilinx tools are not available (detect by settings64.sh missing), gracefully skip building the libs.
Currently does not checkouts external dependencies, causing:
Future improvements:
Solves: 'hidden' documentation builds.
PR Type
PR Checklist