ci: auto deploy the GitHub pages/docs on releases

[evelikov]

This adds a workflow, that triggers on GitHub releases, building/deploying the docs only when needed.

For example:

• release 2.17.0 - deployed
• release 2.18.0 - deployed
• release 2.17.1 - skipped

Notes:

• with this merged, the gh-pages branch can be removed ... we should also remove va_win and revert-583-HierarchyInfo
• this requires two small changes in the project settings
  • Settings -> Pages -> Build and deployment -> Source -> GitHub Actions
  • Settings -> Environment -> github-pages -> Add deployment branch rule -> Add "[0-9].[0-9][0-9].[0-9]" -> Add rule

This MR builds upon and supersedes #642. Notable changes:

• NOTE: fetches the complete history, without this the tag sorting/selection is broken
• uses the official github actions
• builds the minimal set of libva and only as needed
• pretty UI and URL in the Action

[dvrogozh]

@evelikov : thank you for working on this change. Really appreciate. To which degree you have tested the PR? I wonder, did you try real deployment in your fork copy? If yes - can you post a link?

[evelikov]

It was quite a hit and miss, until I got it right to be honest. Ultimately I removed everything, since my fork became a complete mess.

Please try the instructions in your fork and let me know if you hit any issues.

[evelikov]

Here is an illustrative example:

• the original commit ci: add github pages workflow was released as 2.18.0, which triggered CI and deployed
• the extra commit (genuine fix) meson: docs: use libva_version over project_version()was released as 2.17.1, which triggered CI and did not deploy it (check the log - everything is skipped)

[evelikov]

The FreeBSD failure seems unrelated.

[evelikov]

@dvrogozh is the above example and execution outline helpful? Is there anything I can do to move this forward?

[evelikov]

@XinfengZhang @dvrogozh humble ping?

[evelikov]

@dvrogozh @XinfengZhang is there anything more I can do here?

[XinfengZhang]

LGTM, but have questions:

1. from the comments https://github.com/intel/libva/pull/642/files#r999197827, looks @jangsc0000 met some problem with official https://github.com/actions/deploy-pages.
2. after merging this PR, the actions only take effect with new tag generated? or with a new commit merged? expect the first one without duplicated deployment.

[evelikov]

1. from the comments https://github.com/intel/libva/pull/642/files#r999197827, looks @jangsc0000 met some problem with official https://github.com/actions/deploy-pages.

Their comment does not say what the problem is, so I have no idea. It just works in my testing.

2. after merging this PR, the actions only take effect with new tag generated? or with a new commit merged? expect the first one without duplicated deployment.

I think you meant to say except instead of expect, correct?

The action will trigger only when a new release is made - either via the web UI aka https://github.com/intel/libva/releases/new or the CLI tools.

[XinfengZhang]

I am expecting "the actions only take effect with new tag generated" (first option in this sentence) , sorry for confusing.

[evelikov]

I am expecting "the actions only take effect with new tag generated" (first option in this sentence) , sorry for confusing.

@XinfengZhang the English in the above sentence is a bit broken, so I am not sure what you mean.

Are you aiming to correct your previous statement? Are you asking for the PR to be reworked? Something else?

[XinfengZhang]

I am expecting "the actions only take effect with new tag generated" (first option in this sentence) , sorry for confusing.

@XinfengZhang the English in the above sentence is a bit broken, so I am not sure what you mean.

Are you aiming to correct your previous statement? Are you asking for the PR to be reworked? Something else?

no, you already answered my question:

"The action will trigger only when a new release is made - either via the web UI aka https://github.com/intel/libva/releases/new or the CLI tools."

it is my expectation. thanks

[evelikov]

Glad to hear. Anything else I can do to have this merged?

[evelikov]

@XinfengZhang @dvrogozh humble poke - anything I can do to move this forward?