|
2 | 2 | oneAPI Specifications |
3 | 3 | ===================== |
4 | 4 |
|
| 5 | +.. image:: https://github.com/oneapi-src/oneapi-spec/workflows/CI/badge.svg |
| 6 | + :target: https://github.com/oneapi-src/oneapi-spec/actions?query=workflow%3ACI |
| 7 | + |
5 | 8 | This repo contains the sources for the `oneAPI Specification`_ |
6 | 9 |
|
7 | 10 | The document is built with `Sphinx`_ using a theme provided by `Read |
@@ -122,28 +125,19 @@ You can run a docker container with:: |
122 | 125 | CI |
123 | 126 | -- |
124 | 127 |
|
125 | | -We are currently using gitlab CI inside the intel firewall. We expect |
126 | | -all the sources to be in this repo by the 3/26/2020 release, and will |
127 | | -move the CI system to a public service. |
128 | | - |
129 | | -See .gitlab-ci.yml for the CI configuration. The CI monitors and |
130 | | -builds 2 repo's inside Intel. oneapi-spec-mirror is a mirror of the |
131 | | -repo on github. Turnaround for testing depends on the interval between |
132 | | -mirroring updates, which appears to be ~30 minutes. For quick |
133 | | -turnaround, you can push your branch to the oneapi-spec-test repo, |
134 | | -which will be built immmediately. |
| 128 | +We use Github actions. See .github/workflows/main.yml |
135 | 129 |
|
136 | 130 | On every commit, the CI system builds and publishes the document to |
137 | | -the staging server. To see the URL, look at the end of the log in the |
138 | | -CI system. |
| 131 | +the staging server. To see the URL, look at the end of the log for the |
| 132 | +build step in the CI system. The staging server is an s3 bucket, and |
| 133 | +the access keys are managed as github action secrets. PR's based on |
| 134 | +forks do not have access to the keys and will not publish on the |
| 135 | +staging server. |
139 | 136 |
|
140 | 137 | For commits to the publish branch, the document is staged inside a |
141 | 138 | full copy of the spec.oneapi.com site, which includes redirects and |
142 | 139 | older versions of the doc. To see the URL, look at the end of the log |
143 | | -in the CI system. |
144 | | - |
145 | | -To push to S3, the CI system configuration sets AWS_ACCESS_KEY_ID and |
146 | | -AWS_SECRET_ACCESS_KEY environment variables. |
| 140 | +for the build step in the CI system. |
147 | 141 |
|
148 | 142 | ---------- |
149 | 143 | Publishing |
|
0 commit comments