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

🔍 Dataverse + Azure Integration: Choosing Between Synapse Link and Microsoft Fabric

  Managing large-scale data in Microsoft Dataverse ? You're likely choosing between Azure Synapse Link and the newer Microsoft Fabric Link . Both unlock powerful analytics and reporting options—but with different trade-offs in performance, setup, and long-term cost. Let’s break it down 👇 📊 Power BI and Dataverse: Great, But With Limits Power BI uses TDS (Tabular Data Stream) to connect directly to Dataverse tables. Real-time querying works well for smaller datasets (tens of thousands of records). However, complex queries and relationships may cause timeouts after 5 minutes , making it unreliable for enterprise-scale analytics. 🔗 Azure Synapse Link: Power + Complexity ✅ Strengths: Designed for large datasets , converting Dataverse tables to CSV format for efficient querying and reporting. Highly customizable with Synapse Studio , Azure Data Lake , and Data Factory for deeper ETL/ELT capabilities. ⚠️ Watchouts: Requires technical setup : Azur...
Read more

⚡ Example: Rate Limiting in Azure API Management

  Scenario: You have a public API and want to limit each user to 5 calls per minute to prevent abuse or accidental overload. 🛡️ What is Rate Limiting? Rate limiting controls how many requests a client can make to your API within a specific time window . It helps: Prevent API abuse Protect backend systems Fairly distribute API usage 💡 Using the rate-limit-by-key Policy Azure APIM uses a policy called rate-limit-by-key . It limits requests based on a unique identifier — usually the caller's subscription key or IP address. 🔧 Example Policy (XML) Here’s how you can add this to your inbound policy : < inbound > < base /> < rate-limit-by-key calls = "5" renewal-period = "60" counter-key = "@(context.Subscription?.Key)" /> </ inbound > Explanation: Attribute Meaning calls="5" Maximum 5 calls allowed renewal-period="60" Time window of 60 seconds (1 minute...
Read more

👤 Anonymous Role in Power Pages – What It Is and When to Use It

  When building public-facing websites with Power Pages , not every visitor will be a logged-in user. Some might just be browsing, some might want to ask a question, and others might be using your portal for the very first time. So how do we allow unregistered users to interact with our portal safely ? That’s where the Anonymous Users role comes in. 🚪 Who Are Anonymous Users? Anonymous users are visitors who haven’t logged in to your Power Pages portal. They: Have not signed in May not have an account Might be visiting for the first time And here’s the best part — Power Pages automatically assigns them the “Anonymous Users” web role. You don’t have to do anything special to give it. 🔐 What Can They Do? By default, anonymous users can see pages marked as "anonymous access allowed" , but they can't create or edit data unless you let them . To let anonymous users interact with your data (e.g., submit a form), you need to: Create table permissi...
Read more