Azure DevOps
🔗 Descripción general de la integración
Delivery teams run their whole workflow through Azure DevOps: code, work items, pipelines, test plans, and packages. Microsoft protects the platform and its own service continuity, but it does not restore what your team deletes by mistake. HYCU for Azure DevOps gives you an independent, offsite copy and lets you:
- Back up Azure DevOps data including:
- Repos (branches, tags, pull requests, wikis)
- Boards (work items, backlogs, sprints, process schema)
- Pipelines (build and release definitions, variable groups, environments)
- Test Plans (plans, suites, cases, results)
- Artifacts (NuGet, npm, Maven, PyPI, Cargo, Universal feeds)
- Organization and project settings
- Assign backup policies by project or organization, with control over frequency, retention, and data residency.
- Back up and recover data to offsite, customer-managed cloud storage, locked immutable if you choose.
- Recover only what you need:
- Full project or organization
- A single repository, with branches and policies intact
- A single work item, with fields, comments, and attachments
- A single pipeline or variable group
With HYCU for Azure DevOps, one failure stays one failure. Restore what broke without standing down the whole delivery organization.
📦 Objetos de copia de seguridad y recuperación
Full mirrors of every Git repository, including all branches, tags, and pull requests, plus YAML and classic pipeline definitions, build and release history, variable groups, and environments.
Work items with fields, comments, attachments, and revision history. Queries, backlogs, teams, and delivery plans. Test plans, suites, cases, and runs with results and code coverage.
Package binaries across NuGet, npm, Maven, PyPI, Cargo, and Universal feeds, plus process templates, security ACLs, users and groups, service hooks, and areas and iterations.
Project and code wikis, plus team dashboards, backed up alongside the projects and teams they belong to.
Restore a whole project after an accidental deletion, or a repository with its branches, tags, and policies intact, even after a force push destroys history.
Restore a single work item with its fields, comments, and attachments, or a saved query and query folder, without rebuilding either from memory.
Restore a pipeline definition, variable group, service hook, team, or delivery plan in place, without disturbing anything still running.
Restore a project or code wiki on its own, without restoring the whole project around it.