Jenkins

 Jenkins in Azure DevOps refers to integrating Jenkins, a popular open-source automation server, into your Azure DevOps ecosystem to manage builds, tests, and deployments.

While Azure DevOps already includes its own CI/CD system (Azure Pipelines), Jenkins can be used:

  • instead of Azure Pipelines (if you're already using Jenkins)

  • alongside Azure DevOps (e.g., source code in Azure Repos, build in Jenkins)

🧩 What is Jenkins?

Jenkins is a widely-used automation server that enables:

  • Continuous Integration (CI)

  • Continuous Delivery/Deployment (CD)

  • Automated builds, tests, packaging, and deployments

It supports many plugins and can integrate with most tools in the DevOps lifecycle.

🔄 Why Integrate Jenkins with Azure DevOps?

You may want to:

  • Use Azure Repos as the source code repo for Jenkins builds.

  • Trigger Jenkins builds from Azure DevOps Pipelines or Releases.

  • Report Jenkins build results back to Azure DevOps (e.g., PR checks).

  • Use Jenkins to deploy artifacts created in Azure DevOps.

🔧 Common Integration Scenarios

1. Azure Repos → Jenkins

Use Azure DevOps Git repository as the code source in a Jenkins job.

How:

  • Use a webhook from Azure DevOps to trigger a Jenkins job on code push.

  • Install the Jenkins Azure DevOps plugin for deeper integration.

2. Jenkins → Azure DevOps Pipeline

Run a Jenkins job from within an Azure DevOps pipeline (as a build step).

yaml
- task: JenkinsQueueJob@2
  inputs:
    serverEndpoint: 'MyJenkinsConnection'
    jobName: 'my-jenkins-job'
    captureConsole: true

3. Jenkins Build Status in Azure DevOps

Display Jenkins build results (pass/fail) in:

  • Azure Repos pull requests (as status checks)

  • Azure Boards work items (via service hooks)

4. Publish Artifacts from Jenkins to Azure

Use Jenkins to push build artifacts to:

  • Azure Artifacts (NuGet/npm packages)

  • Azure Storage or App Services

  • Azure Container Registry

Comments

Post a Comment

Popular posts from this blog

🤖 Copilot vs Microsoft Copilot vs Copilot Studio: What’s the Difference?

Microsoft’s AI-powered tools are transforming the way we work, create, and collaborate. But with all the buzz around “Copilot,” “Microsoft Copilot,” and “Copilot Studio,” it’s easy to get confused. Let’s break down what each of these really means—and when to use them. 🚀 What Is “Copilot”? “ Copilot ” is Microsoft’s umbrella term for AI assistants built into its tools. Whether you’re in Word, Excel, or Teams, Copilot helps you do things faster —like generating text, summarizing information, analyzing data, or writing emails. Think of it like an intelligent assistant sitting next to you, helping with routine and creative tasks. 🔍 Example Copilots: Copilot in Word – Drafts documents, rewrites text, summarizes long reports. Copilot in Excel – Generates formulas, explains complex data, creates dashboards. Copilot in Teams – Summarizes meetings, drafts responses, manages tasks. 👉 It’s not a separate product—it’s a built-in experience across Microsoft tools. 🧠 What Is Micro...
Read more

Automating Unique Number Generation in Dynamics 365 Using Plugins

Introduction When working with Dynamics 365, generating unique and sequential numbers for records such as invoices, quotes, or orders is a common requirement. Instead of manually assigning these numbers, we can use an Auto-Numbering Plugin to automate the process. In this blog, we’ll break down a C# plugin that implements this functionality in an easy-to-understand way. Why Do We Need Auto-Numbering? Manual numbering is prone to errors, duplication, and inefficiency. Automating this ensures: Unique numbering for each record Improved data consistency A structured format (e.g., INV-1001, INV-1002 ) How Does the Plugin Work? The plugin follows a structured approach to generate and assign unique numbers: Retrieve the Auto-Number Configuration Record Lock the record to prevent conflicts Increment the current number and update it Assign the new number to the created entity Let’s break down the code into simple steps. Understanding the Code Complete C# Code for Auto-Numbering Plugin...
Read more

In-Process vs Isolated Process Azure Functions: What’s the Difference?

 When building Azure Functions using .NET, one of the most important architectural choices you’ll face is deciding between In-Process and Isolated Process (Out-of-Process) hosting models. This decision impacts everything from startup time to dependency control and middleware capabilities. So let’s break it down. What is In-Process (InProc) Hosting? In the In-Process model: Your function code runs inside the same process as the Azure Functions runtime. It uses the same AppDomain and host environment . Benefits: Better performance (lower cold start time). Full access to features in the Microsoft.Azure.WebJobs SDK (like bindings, triggers, and logging). Easier to use existing .NET libraries and tools. Limitations: Tightly coupled to the Azure Functions runtime version. Less flexibility in middleware and custom startup configuration. Potential for dependency conflicts if runtime and your code use different versions of libraries. What is ...
Read more