|.onedev-buildspec.yml||Loading last commit info...|
NOTE: We develop OneDev at code.onedev.io for sake of dogfooding. All issues and pull requests should be submitted there
Self-hosted Git Server with Kanban and CI/CD
Of course IDE is good at doing this, but often we need to search in old commits (investigate issues in release versions etc), and switching commits in IDE can be troublesome and slow.
You can also jump to symbol definition in diff while reviewing commits or pull requests.
You may switch to any commit, and search code with regular expression. OneDev under the hood indexes the code with Lucene incrementally. At search time, literal tri-grams in the regular expression are extracted for a coarse search, followed by exact match in the result. This makes the regex search blazing fast, even for large repositories like Linux.
Of course this can be done by many third party applications at GitHub, however they display the result on their own applications, and this makes review activities such as adding comment over analysis result difficult. Not to mention that you need to pay for these services.
The simple open/close state of GitHub/GitLab issues does not work well for many workflows. Considering issues submitted by customers:
- If developer closes issue upon committing the code, customer will be notified and may ask for the release fixing the issue.
- If developer closes the issue at release time, QA might be confused at what issues to test as they all remain open at test time.
With customizable issue states, we may address the issue with four states: open, committed, test ready and released:
- When code is committed, issue transits to committed state automatically
- When a test build is created and deployed, the issue transits to test ready state automatically. QA will be notified and can check issue detail to know which environment the test build is deployed into.
- When test passes, and a release build is created, customers submitting the issue will be notified and they can check issue detail to see which release contains the fix.
Service desk allows your users to submit tickets via email without the need to have a OneDev account. These tickets can then be created in desired projects, and assigned to appropriate members in your team. All further discussions over the tickets can take place completely in email, with discussion contents posted to ticket as comments. User will also get notifications when there are any ticket activities, for instance, when a relevant release is created or deployed
Thanks to ANTLR again, OneDev ships sophisticated query languages for projects, commits, issues, builds, and pull requests, with intuitive auto-completions and hints. For instance, it enables our customers finding fixed issues between their running release and latest release, and enables us to find all commits submitted by someone touching specified modules, etc.
Queries can be saved and subscribed, so that you won't miss anything interested.
OneDev ships with GUI to generate CI/CD Yaml. No need to google around for Yaml grammars. A one-liner docker command to start OneDev server and you have a local CI/CD runner automatically. Concerns about server capability to run massive jobs? Another one-liner to connect self-updating agent from any machine. Want auto-scale CI/CD farm? A helm one-liner to deploy OneDev into k8s cluster.
Build pipeline, matrix jobs, typed parameters, parameter chaining, step templates, build promotions… too many neat features to elaborate…
Specify pull request review policy based on author, branch, and changed files. OneDev can leverage git change history to suggest most appropriate reviewers for pull requests touching certain files.
Comment on any part of code or diff to start a lightweight review without opening pull request. Review comments live through code modification and even file rename to serve as documentation.
Each discussion is threaded so that you can easily know discussions with new comments/updates.
Press cmd/ctrl-k to bring up command palette from anywhere. Search projects, files, issues, pull requests, builds, and various settings and jump to them without leaving your keyboard
When embedding an image in a markdown file in GitHub/GitLab, you need to upload the image in a separate page, and then figure out the relative path to reference that image. With OneDev, you simply upload the image to desired folder in same editor, and the link will be generated automatically.
OneDev tracks your cursor in edit window and scrolls the preview window as necessary so that you can always preview what you are typing.
OneDev inspects git history of main branch to calculate trend of source lines of code by language efficiently.
Organization is ideal for public service. However for self-hosted internal use, we feel that a hierarchical structure is more practical to organize projects. Child projects can inherit settings from parent project and can selectively override some of them if necessary. This reduces a lot of overhead to manage a lot of projects in the company.
OneDev is carefully designed with performance in mind. With a 2 core 2GB box, you will get all features above for medium sized projects.
It has been intensively used for more than 5 years, with battle-proven reliability. Fixing bugs is our highest priority, and there is
normally few to no known bugs in the wild.
YourKit supports this project by providing a free open source license of their excellent Java profiler