GitLab’s built-in Continuous Integration (CI) tools are some of the best in the industry. Onyx Point, LLC. has been continuing our efforts to improve GitLab’s CI security. Continue reading to learn more about integrating GitLab CI with high-performance computing (HPC) resource schedulers.
This post follows up on the previous SetUID Runners article by taking a deeper look at code and rationale for specific features. In the previous post we outlined our goals and process for the first phase of ongoing work to improve security and functionality of GitLab CI Runners at the Department of Energy’s (DoE) High Performance Computing (HPC) labs. If you haven’t seen it, you can read it here
GitLab’s built in continuous integration (CI) tools are some of the best in the industry. Onyx Point has been leading an effort to improve GitLab’s CI security. Continue reading to learn more about how Onyx Point has implemented more secure job access controls in high-performance computing infrastructures.
Energy science hinges on High Performance Computing (HPC), and U.S. Department of Energy (DOE) scientists write
millions of lines of scientific simulation code every year to drive new discoveries. Simulations need to be tested and kept up to
date, and the demand among scientists for robust continuous integration (CI) is growing.
Several feature requests have been opened for various types of
Many of our customers do not have regular Internet access and many of them,
being highly regulated, cannot install local copies of GitLab to be able to run
against the provided API.