I have been working since last year with julia, and I developed several packages for internal use in my company. Up to now, these developments were my own and did not require much input from other developers. I am mostly versioning them using git repos on a NAS and created a private registry on tha…

Invenia has like everything setup on gitlab for our internal stuff. From autoscaling CI, to documentation hosting, to code coverage hosting. Automatic tagging and releases when you merge. I will poke our devs in the direction of this thread. I know some parts are TagBotGitlab and LocalRegistry.j…

Recent thread: [image] Package on gitlab not github General Usage Hi Gitlab is perfectly fine to use for Julia packages, and so is any other git host. Github is used as the most common example because it is the most popular one and widely used within the Julia community …

Thanks ! It seems that PkgTemplates defines a lot of stuff to help create new packages will all the configuration baked-in. However, I have the feeling that this requires configuration at a higher level than package (e.g. registry …), and that seems out of the scope of PkgTemplates, is it ?

Hey, I’m a dev at Invenia (co-worker of @oxinabox ), and this is an overview of our CI setup. Test pipeline Every Julia package we have lives in its own GitLab repo. Each has a .gitlab-ci.yml file which defines the pipeline for that repo. The one you linked to is a good starting point .gitlab-ci.…

The setup at my company is less complex and correspondingly less ambitious in most, but not all, aspects. Packages Normally one per GitLab project (i.e. repository). Some projects contain dual Julia and Python packages, making use of the Pkg subdir functionality to point to the julia subdirectory…

Thanks @ArnaudHenry and @GunnarFarneback for all the precious info. So to sum up: At the registry level The registry can be created as for any other local registry using LocalRegistry.create_registry on the dedicated bare repo. The registry should have a CI test job using RegistryCI.test in or…

[image] BambOoxX: The registry should have a CI test job using RegistryCI.test in order to verify its integrity any time a package or a new version of a package is registered. It’s a sound thing to do but to be honest I’ve never seen it fail. Then again, should I happen to introduce a bad eno…

[image] GunnarFarneback: Not at all, it’s just a quality of life improvement if your organization struggles with GitLab credentials or have less technically inclined users who find adding a registry URL with Julia’s package manager to be an obscure thing to do. Assuming the registry to be pub…

[image] BambOoxX: Assuming the registry to be public (inside my organization) could the package server bypass the Gitlab safeties, e.g. if a user does not have access to a package repo, could he install it through the package server ? That looks like some sort of a backdoor if it’s the case ^^. …

My solution was to make a JuliaPkgs group where every user has at least read access. All registered packages are in this group.

Julia and Gitlab self-hosted : a state-of-the-art?

General Usage

jd-foster September 3, 2022, 7:36am 3

Recent thread:

Topic		Replies	Views
Registering a package hosted on a public self-hosted gitlab instance New to Julia	13	1352	September 6, 2022
Using Opensource hosting repo instead of GitHub Offtopic	15	2143	January 24, 2021
JuliaRegistries setup for air gapped network General Usage packages , registry	28	2033	March 8, 2023
Package on gitlab not github General Usage	10	1357	September 1, 2022
Easy workflow file for setting up GitHub Actions CI for your Julia package Tooling ci , github-actions	77	10469	September 18, 2021

Julia and Gitlab self-hosted : a state-of-the-art?

Related topics