You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data/tool_pages/platform/2in_00_the_ocaml_infrastructure.md
+29-31Lines changed: 29 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ The OCaml ecosystem is supported by a [robust infrastructure built around OCurre
16
16
17
17
The OCaml infrastructure services can be grouped into three main categories: Community infrastructure services, services for individual projects, and infrastructure operation services. Here we present a brief overview of the major services from the first two categories.
18
18
19
-
### Community Infrastructure Services
19
+
### Services for Individual Projects
20
20
21
-
These services power the broader OCaml ecosystem, supporting package repositories, documentation, and other essential community resources:
21
+
These services used for your own projects to help with reproducible builds, testing, benchmarking, and continuous integration:
22
22
23
23
#### Docker Base Images
24
24
@@ -29,35 +29,6 @@ This service builds the official `ocaml/opam` Docker images for various Linux di
29
29
30
30
**Using the pre-built OCaml Docker images:** You can view the available [pre-built Docker images for various OCaml configurations at DockerHub](https://hub.docker.com/r/ocaml/opam).
Tests package submissions to the opam repository. When you submit a pull request to opam-repository, this service verifies that your package builds correctly and also tests all dependent packages to ensure compatibility.
38
-
39
-
**Publishing a package to opam-repository:** After creating a GitHub release and opening an opam-repository PR with `dune-release`, monitor your opam-repository PR to ensure all tests pass.
Builds documentation for all packages in the opam repository, with correct cross-package linking. Generated documentation is published to the OCaml.org website.
47
-
48
-
**Package documentation on OCaml.org:** After publishing your package to opam-repository, the documentation will automatically be built and integrated with the [OCaml.org website's package area](https://ocaml.org/packages).
Regularly tests that all packages in the opam repository still build correctly. This service is used by OCaml compiler developers when preparing major changes like new OCaml compiler releases.
56
-
57
-
### Services for Individual Projects
58
-
59
-
These services can be enabled for your own GitHub repositories to help with testing, benchmarking, and continuous integration:
@@ -85,6 +56,33 @@ Tests OCaml projects against multicore OCaml versions - particularly useful if y
85
56
86
57
**How to enable OCaml-Multicore-CI on your GitHub project:** Check out the [OCaml-Multicore-CI README on GitHub](https://github.com/ocurrent/ocaml-multicore-ci).
87
58
59
+
### Community Infrastructure Services
60
+
61
+
These services power the broader OCaml ecosystem, supporting package repositories, documentation, and other essential community resources:
Tests package submissions to the opam repository. When you submit a pull request to opam-repository, this service verifies that your package builds correctly and also tests all dependent packages to ensure compatibility.
69
+
70
+
**Maintaining compatibility for packages in the opam-repository:** After publishing a package by creating a GitHub release and opening an opam-repository PR (e.g. by [using `dune-release`](/publishing-packages-w-dune)), monitor your opam-repository PR to ensure all tests pass.
Builds **documentation for all packages in the opam repository**, with correct cross-package linking. After publishing your package to opam-repository, the documentation will automatically be built and published to the [OCaml.org website's package area](https://ocaml.org/packages).
Regularly tests that all packages in the opam repository still build correctly. This service is used by OCaml compiler developers when preparing major changes like new OCaml compiler releases.
85
+
88
86
## Platform Support
89
87
90
88
The OCaml infrastructure supports building and testing on multiple platforms:
0 commit comments