OneDev
Sign In

Blogs

OneDev 16.5: AI-Powered CI Fixes and a Smoother Developer Experience

OneDev 16.5 brings AI deeper into the development loop. You can now ask an AI user to fix a failed build on demand. AI users can also step in automatically when a human-submitted pull request hits a CI/CD failure or merge conflict.

This release also smooths everyday development and administration with mobile-friendly workspace terminals, SSO-only login, private Git identities, durable redirects for moved issues, and more control over rebuilds and Renovate project selection.

Fix CI/CD Failures with AI on Demand

OneDev already supports automatic CI/CD failure handling. A post-build action can create an issue when a build fails and assign it to an AI user. The AI user then investigates the failure and works on a fix.

If you have not set up that automation, you can now use the Fix action on the build detail page whenever an AI user is available. There is no need to collect logs, create an issue, or explain the failure manually.

Selecting Fix opens the AI assistant with the failed build already in context. The AI creates a fix issue, assigns it to itself, and follows the normal OneDev workflow. The fix remains visible and traceable, and the resulting code changes still go through your regular review and CI/CD process.

Let AI Repair Human-Submitted Pull Requests

AI users can now take responsibility for pull requests opened by people, not only those created by AI.

When you assign an AI user to a pull request, you can configure it to:

  • Fix failed CI/CD builds
  • Resolve merge conflicts
  • Review and merge the pull request when it is acceptable

If a relevant build fails or the pull request develops a conflict, OneDev can automatically start the assigned AI user with the pull request, build, and current commit in context. The AI works on the existing branch and submits its fix to the same review loop. These responsibilities are configured for each AI user, keeping the automation aligned with its intended role.

Together, these features give teams two ways to repair failures: invoke AI on demand from a failed build, or assign an AI user to a pull request in advance for automatic assistance.

Use Workspace Terminals on Mobile

Workspace terminals are now easier to use on phones and other touch devices. An on-screen key bar provides keys that are awkward or unavailable on a mobile keyboard. The terminal also follows the visual viewport as the browser UI and keyboard change the available screen area.

That makes it practical to inspect a workspace, run a quick command, or respond to an urgent problem without switching to a desktop.

Run OneDev with SSO-Only Login

Administrators can now disable the internal password login form in security settings, making SSO the only sign-in path.

OneDev adapts the login flow to the configured providers:

  • With one SSO provider, users are redirected to it immediately.
  • With multiple SSO providers, users choose a provider without seeing the internal login form.
  • With no SSO provider, OneDev keeps the internal form available to avoid an accidental lockout.

If an SSO configuration problem locks administrators out, run bin/enable-internal-login on the server to restore internal login.

OneDev can also sign users out at the SSO provider when the provider supports it. OpenID Connect providers with an end-session endpoint can close the upstream session and return the user to OneDev. Providers without that capability keep the existing local sign-out behavior.

Keep Personal Email Addresses out of Git History

Git identities are now simpler and more privacy-friendly. Users can keep their email addresses private by having OneDev use a generated address such as [email protected] for Git operations. AI and service users follow the same predictable noreply convention.

Administrators can customize the noreply domain in system settings, so generated Git identities match the organization rather than using a fixed domain.

Move Issues without Breaking Old Links

Issues can now be moved directly from the issue detail page. OneDev leaves a permanent redirect at the original project and issue number.

Old URLs, bookmarks, and references in issues, pull requests, comments, and commit messages continue to work after the move. The original number stays reserved, so it can never point to an unrelated issue. This redirect behavior applies whether the move starts from the detail page or the issue list.

Get More Control over CI/CD Rebuilds

Each job now has independent options to include upstream and downstream jobs in a rebuild. Include upstream jobs when dependencies need to be regenerated, downstream jobs when dependents need to be refreshed, or both to reconstruct a wider pipeline path.

Both options are disabled by default, preserving the existing targeted rebuild behavior until a job opts in.

Select Renovate Projects Recursively

The Update Dependencies via Renovate step can now select projects recursively. Selecting a parent project includes descendants at every depth, so newly added repositories deep in the hierarchy are picked up without repeatedly editing the step configuration.

See the Full OneDev 16.5 Changelog

These are the highlights of OneDev 16.5. See the complete changelog for all improvements and bug fixes.