| commit | 4daa9055beffa17ed47a71d52e7af219acc38e29 | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Mon, 2 Nov 2020 13:09:23 +0000 (2 13:09 +0000) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Tue, 10 Nov 2020 07:51:30 +0000 (10 08:51 +0100) | ||
| tree | 58668a51704318b7b298690f0bf511412273e5ea | treesnapshot (tar.gz zip) |
| parent | 2deca810d8c2b8d0c56782ef8d9f4bfbfcacd261 | commitdiff |
gitlab: publish the docs built during CI
Most of the build jobs will create the sphinx documentation. If we
expose this as an artifact of a "pages" job in a "public" directory, it
will get published using GitLab Pages. This means a user can push a
branch with docs changes to GitLab and view the results at
https://yourusername.gitlab.io/qemu/
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20201102130926.161183-2-berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Most of the build jobs will create the sphinx documentation. If we
expose this as an artifact of a "pages" job in a "public" directory, it
will get published using GitLab Pages. This means a user can push a
branch with docs changes to GitLab and view the results at
https://yourusername.gitlab.io/qemu/
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20201102130926.161183-2-berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| .gitlab-ci.yml | diffblobblamehistory |