OpKey CI

This extension provides testing of build and release tasks with OpKey before packaging and publishing. This OpKey Plugin is used for Continuous Integration and Continuous Development of build in Azure DevOps Pipeline. It enables to automate the CI and CD build. It helps you to deliver more value to your users with more frequent deployments of a higher quality.

Need of Azure DevOps Pipeline Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository, as required. Each check-in is then verified by an automated build, allowing teams to detect problems early. OpKey can easily be integrated into Visual Studio Team Services continuous integration systems. It enables users to trigger Builds execution and detect bugs, if any. Implementing CI helps QA team to catch bugs early in the development cycle, which makes them less expensive to get fixed by the developers.

When many developers collaborate on complex software projects, it may not be feasible for them to integrate different parts of code together. However, you can make this process more efficient and more reliable if you build and deploy your project continuously. Visual Studio Team Services simplifies Continuous integration for your applications regardless of what platform you are targeting, or what language you are using.

Azure DevOps Pipeline allows you to Build on any platform (Linux, Mac, and Windows) Run your Build on a hosted or private agent Use multi-platform build agents for Android, iOS, Java, .NET, and other applications Track your builds with real-time build status

Task Included OpKey CI step in build and release step.

How to Use After installing the extension, you can add one(or more) of the tasks to a new or existing build definition or release definition.

Feedback and issues. If you have support or issues, please send an email or file an issue on opkey support.