One thing I install parallel to every OneDev setup is a docker registry. So maybe this is a point.

Beside something written in Java could you think of bundling a registry executable with OneDev?
Like this: https://github.com/distribution/distribution

I tend to implement a Java based docker registry if possible. Just shipping a registry executable with OneDev complicates bare-metal installation, and does not provide much value I think. In that case I'd like to leave it to users to install their own.

Also I'd like to integrate OneDev with docker registry tightly to do things such as authenticating against same user base, associating docker image with build record, managing docker image from OneDev UI, etc.

I am not sure how difficult it will be to implement a docker registry in Java though...

@robin Maybe you could take a look at https://github.com/sonatype/nexus-public which is Java also and EPL 1.0 Licensed. Maybe even some code might be reused, as EPL and MIT are compatible.

Thanks for the info. Definitely will look into this when I start to implement this feature.

May I give my 2 cents? I guess most of us users switched to OneDev because:

1. it is a gorgeous project
2. Robin is amazing
3. the installation process is easy and well documented
4. OneDev is (relatively) light

Adding features that are readily available elsewhere (in that case: docker registry v2) might not be the best idea: who among us has not struggled with a self-hosted GitLab? Meaning: please keep OneDev mean and lean!

I would love to have that option or at least some documentation how to achieve this with Docker. I get some network issues when I deploy the registry in a separat container.

@stsinc I think you are missing the point here. All of what OneDev delivers is "readily available" in other, separate projects. Strength and value of OneDev comes from fact that it neatly integrates it under one tool, and need for container registry is so common requirement that it would be great thing to include it inside OneDev.

This and visual representation of pipelines as graphs are 2 main components missing in current releases.

Visual pipeline already available in dev branch. It visualizes job dependencies both at define time, and at runtime. This feature will be released in OneDev 7.

That's excellent news:)

@robin in light of Gitea having released a registry for various media, will this be coming soon? I’m trying to decide whether it’s worth standing something like Harbour up as I don’t want to stand up if this feature will come

This may not come very soon, and I hope to get it into OneDev in year 2023. Right now I am working on custom dashboard which is early requested by my own company.

Ok, no worries

@robin is there an issue tracking the custom dashboard work? This sounds interesting

Issue #377 covers this request. It basically provides dashboard so that different role in the team can start work more easily. For instance, customer can see projects with latest release and change log, while QA sees test builds with issues to be tested etc.

Personally I think OneDev should not bundle a docker registry. If OneDev fails for whatever reason, not only your code is inaccessible but also all already built, immutable docker image artifacts stored in that registry. Also a registry is pretty stable and does not have many releases. Yet you would constantly restart it if you upgrade OneDev regularly. If you start depending on the bundled registry then it is regularly not available for some time. This might be mitigated for EE edition and a clustered OneDev but then the registry must be consistent all the time across OneDev nodes.

Security could also be a thing if we assume that OneDev runs in a development network and the final application runs in a production network. Instead of connecting both networks directly it might be better to have a third network connected to both that only contains the registry that OneDev can push to and the production cluster can pull from.

@robin What happened to https://code.onedev.io/onedev/server/~issues/1193#IssueComment-4110??

@markkrj I changed the mind, as I hope to get financial support via enterprise version so that I can work on this product full time (currently far from that yet).

Also want to mention that being an enterprise feature, the package integration will be much more powerful than other products, including the ability to query/subsribe packages, package storage high availability, generate changelog automatically, link builds with packages so that you can see published packages directly from build, etc.

While I understand the decision to focus certain features on enterprise, it's a little sad. I still hope you will get enough users to work full-time on this.

Nevertheless, if feasible, could you enhance the documentation to guide users in adding a basic Docker registry? This would be helpful for those interested in integration, even if it's not part of the core features.

Nevertheless, if feasible, could you enhance the documentation to guide users in adding a basic Docker registry

Just use a third party docker registry in this case, for instance the harbor.

State changed as code fixing the issue is committed (aff60f2a)

State changed as build #4330 is successful