Answers: <p>I would love to get some clarity too maybe from a more authoritative source than myself (I'm sure I'm guilty of FUD too).</p>
  
  <p>I've been looking to deploy to Azure using Kubernetes.  I am similarly confused but I think that is because there isn't one clear path.  I can't speak for Microsoft but their attitude to cloud seems to be they are happy to become "<em>all things to all men</em>".  If you are using Azure, Microsoft don't seem to have a strong opinion on how you get there. </p>
  
  <p>Microsoft are actively trying to evolve; e.g. 
  <a href="https://www.zdnet.com/article/linux-now-dominates-azure/" rel="noreferrer">Linux now dominates Azure</a></p>
  
  <hr>
  
  <p>Clearly <strong>Azure DevOps</strong> deployment pipeline does exactly what Jenkins can do - so in that sense it is a competitor.  There is also that slightly off-putting upfront Azure DevOps pricing for parallel pipelines.</p>
  
  <p>On the one hand, Azure DevOps appears to be a re-branding of Visual Studio Team Services.  So it will be familiar to people already within the traditional Microsoft development ecosystem.  At the same time Microsoft are making great efforts to embrace technologies that are not traditionally Microsoft (<a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/index?view=vsts" rel="noreferrer">Go, Java, Node.js, Python, Ruby, PHP</a> etc).</p>
  
  <p>It is early days - but it is not a surprise that Azure DevOps pipelines should prefer the Microsoft Git properties of Azure Repos and GitHub.  In the same way that <a href="https://bitbucket.org/product/features/pipelines" rel="noreferrer">BitBucket pipelines</a> prefers BitBucket and <a href="https://docs.gitlab.com/ee/ci/pipelines.html" rel="noreferrer">GitLab pipelines</a> prefer GitLab.</p>
  
  <hr>
  
  <p><strong><em>Meanwhile;</em></strong></p>
  
  <p>The Azure Marketplace offers a <a href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps/azure-oss.jenkins" rel="noreferrer">Jenkins deployment</a> that comes with Azure deployment plugins out of the box.</p>
  
  <p>Many Jenkins plugins have been developed by the <a href="https://plugins.jenkins.io/?q=azure%20devops%20team" rel="noreferrer">Azure DevOps team</a>.</p>
  
  <hr>
  
  <p><strong><em>in addition;</em></strong></p>
  
  <p>Microsoft have put their backing behind Kubernetes related projects <a href="https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm" rel="noreferrer">Helm</a> and <a href="https://docs.microsoft.com/en-us/azure/aks/kubernetes-draft" rel="noreferrer">Draft</a>.  Helm is a package manager for Kubernetes.  You can even use Helm to deploy a Jenkins installation into Kubernetes.</p>
  
  <p>--</p>
  
  <p>It would be interesting to see someone weigh up the benefits, <a href="https://azure.microsoft.com/en-us/pricing/calculator" rel="noreferrer">costs</a> and effort of running your own Jenkins in Azure verses using Azure DevOps pipelines.</p>
  
  <p>... and then there is <a href="https://jenkins-x.io/" rel="noreferrer">Jenkins-X</a>.</p>
  
  <p>So it would seem we have many options and decisions to make.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-01-18T10:48:09.237Z
Answers: 2019-01-18T11:23:06.137Z
Answers: 2019-01-18T11:23:06.137Z
Answers: Mark McLaren
Answers: <ol>
  <li><p>Yes, because Azure Pipelines can do what Jenkins does.  However, you don't have to throw the baby out with the bathwater.  Microsoft continues to position their platforms such that integrations can occur with existing installations of just about anything.  Many orgs have huge investments in tooling that is difficult to change.  Rather than taking an all-or-nothing stance, Microsoft is embracing standards and a bring-your-own mentality, giving you ultimate choice as to how you want to implement the tools.</p></li>
  <li><p>The agents technically are your pipeline as the tasks execute on the agents targeted within the pipeline.  All you are configuring within the portal are the steps the pipeline will execute.  The agents download tools/extensions necessary to execute the tasks.  In addition, with the new YAML pipelines, the pipelines are defined within your code repos.  As far as hosting is concerned, you can host Azure DevOps Server entirely on premise, within any cloud provider, or a combination of Azure VMs and Azure SQL.</p></li>
  <li><p>Generic Git repositories are <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/?view=azure-devops" rel="nofollow noreferrer">supported in Azure DevOps Services using the classic editor or both YAML and classic editor if using Azure DevOps Server</a> (on-prem) at the moment.  You can add <a href="https://marketplace.visualstudio.com/items?itemName=onlyutkarsh.gitlab-integration" rel="nofollow noreferrer">GitLab repository integration</a> by installing the extension.</p></li>
  </ol>
  
Answers: CC BY-SA 4.0
Answers: 2019-03-27T17:38:48.890Z
Answers: 2019-03-27T17:38:48.890Z
Answers: Sumo
Answers: <p>In answer to part 2 (maybe), it does seem like they're pitching it as an alternative to Jenkins, although there's plenty of documentation suggesting that it can all be <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/release/integrate-jenkins-pipelines-cicd?view=azure-devops&amp;tabs=yaml" rel="nofollow noreferrer">used together</a> (and <a href="https://www.dragonspears.com/blog/ci-cd-with-jenkins-and-azure-devops-services" rel="nofollow noreferrer">here</a>). When used with Jenkins though, it does seem to be more focussed on a deployment bridge. I was hoping that I could use it as a build agent with Jenkins as an orchestrator, like I could do with Jenkins &amp; AWS CodeBuild.
  I haven't <em>seen</em> anything to suggest I could do so yet, but maybe...
  Multi-cloud deployments is very intriguing though...</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-03-08T11:33:49.690Z
Answers: 2019-03-08T11:39:27.377Z
Answers: 2019-03-08T11:39:27.377Z
Answers: phedro
Body: <p>I've been doing some research on the Azure DevOps solution that <a href="https://azure.microsoft.com/en-us/blog/introducing-azure-devops/" rel="noreferrer">Microsoft recently unveiled</a>.</p>
  
  <p>Some background, I've been using Jenkins for years, and recently started exploring the containerisation rabbit hole (Docker, Kubernetes, etc),</p>
  
  <p>I'm unsure about some of the aspects of Azure DevOps Pipelines, and it'd be awesome to get some feedback and clarity.  </p>
  
  <h2>TL;DR</h2>
  
  <ol>
  <li>Is Azure DevOps now competing with Jenkins, where they previously <a href="https://www.youtube.com/watch?v=buQNF1sekq8" rel="noreferrer">supported the Jenkins community via open source plugins</a> for Jenkins? </li>
  <li>Is it possible for me to host Azure DevOps Pipelines completely on premise, not just agents? </li>
  <li>Is it possible to use a self hosted git solution (like GitLab on-premise) with Azure DevOps Pipelines? </li>
  </ol>
  
  <h2>Longer version</h2>
  
  <ol>
  <li>Microsoft has developed various open-source plugins for Jenkins, such as the <a href="https://docs.microsoft.com/en-us/azure/jenkins/deploy-jenkins-app-service-plugin" rel="noreferrer">Azure App Service Jenkins plugin</a>. There are many examples. To me it seems like the Azure DevOps (specifically Pipelines) solution is now competing directly with Jenkins, or am I missing something?</li>
  <li>To me it seems that there is no way to host the Azure Pipelines solution on premise, or in a cloud provider of my choice. Yes, I can <a href="https://azure.microsoft.com/en-us/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/" rel="noreferrer">host my own agents</a> where the bulk of the work is performed, but the actual execution of the pipeline logic happens on Microsoft's servers. And then I have to <a href="https://azure.microsoft.com/en-us/pricing/details/devops/azure-pipelines/" rel="noreferrer">pay for parallel jobs</a>. I'm comparing this to an on-premise (or cloud provider of choice) hosted Jenkins instance, where no payment is required, and no 3rd party is even aware that our pipelines are running. Am I missing something? </li>
  <li>From what I can tell, Azure Pipelines has no support for self hosted repositories, I either put my code <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-yaml?view=vsts" rel="noreferrer">on GitHub or on Azure repos</a>, nothing else. Thus, I can't even use this Pipelines solution if I have a privately hosted GitLab instance? </li>
  </ol>
  
  <p>Thanks for any input. </p>
  
Comments: CC BY-SA 4.0
Comments: 2018-10-20T06:04:18.650Z
Comments: Could I suggest splitting this question up into separate ones? The question as it stands seems more like an invitation to discuss opinions. If you could separate them into individual questions, they could be better answered.
Comments: Bruce Becker
Comments: CC BY-SA 4.0
Comments: 2018-11-12T12:38:18.847Z
Comments: Hi Have you got any answers for any of these questions?
Comments: user10804
Comments: CC BY-SA 4.0
Comments: 2018-12-03T16:52:57.833Z
Comments: Azure Devops cant be hosted on premise, but TFS can which is essentially the same thing but gets its updates slightly more slowly. We use TFS 2018 on prem and its great
Comments: Rich
Comments: CC BY-SA 4.0
Comments: 2019-01-15T13:04:56.240Z
Comments: Is this a real question? To me it looks like FUD with no actual research.
Comments: Carles Company
Comments: CC BY-SA 4.0
Comments: 2019-01-17T10:25:40.433Z
Comments: Great question! Have you reached any answer to your questions? If so, please write it so that the community can benefit from it too.
Comments: rodrigogq
Tags: <jenkins><azure-pipelines>
Title: Jenkins vs Azure DevOps Pipelines
UserDisplayName: Anrich
ThreadText: # Jenkins vs Azure DevOps Pipelines
  
  (Asked by: username_0 on 2018-10-10)
  
  I've been doing some research on the Azure DevOps solution that [Microsoft recently unveiled](https://azure.microsoft.com/en-us/blog/introducing-azure-devops/).
  
  Some background, I've been using Jenkins for years, and recently started exploring the containerisation rabbit hole (Docker, Kubernetes, etc),
  
  I'm unsure about some of the aspects of Azure DevOps Pipelines, and it'd be awesome to get some feedback and clarity.
  
  ## TL;DR
  
  1. Is Azure DevOps now competing with Jenkins, where they previously [supported the Jenkins community via open source plugins](https://www.youtube.com/watch?v=buQNF1sekq8) for Jenkins?
  2. Is it possible for me to host Azure DevOps Pipelines completely on premise, not just agents?
  3. Is it possible to use a self hosted git solution (like GitLab on-premise) with Azure DevOps Pipelines?
  
  ## Longer version
  
  1. Microsoft has developed various open-source plugins for Jenkins, such as the [Azure App Service Jenkins plugin](https://docs.microsoft.com/en-us/azure/jenkins/deploy-jenkins-app-service-plugin). There are many examples. To me it seems like the Azure DevOps (specifically Pipelines) solution is now competing directly with Jenkins, or am I missing something?
  2. To me it seems that there is no way to host the Azure Pipelines solution on premise, or in a cloud provider of my choice. Yes, I can [host my own agents](https://azure.microsoft.com/en-us/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/) where the bulk of the work is performed, but the actual execution of the pipeline logic happens on Microsoft's servers. And then I have to [pay for parallel jobs](https://azure.microsoft.com/en-us/pricing/details/devops/azure-pipelines/). I'm comparing this to an on-premise (or cloud provider of choice) hosted Jenkins instance, where no payment is required, and no 3rd party is even aware that our pipelines are running. Am I missing something?
  3. From what I can tell, Azure Pipelines has no support for self hosted repositories, I either put my code [on GitHub or on Azure repos](https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-yaml?view=vsts), nothing else. Thus, I can't even use this Pipelines solution if I have a privately hosted GitLab instance?
  
  Thanks for any input.
  
  **Tags:** jenkins, azure-pipelines
  
  > **Comments:**
  > **username_1**: Could I suggest splitting this question up into separate ones? The question as it stands seems more like an invitation to discuss opinions. If you could separate them into individual questions, they could be better answered.  
  > **username_2**: Hi Have you got any answers for any of these questions?  
  > **username_3**: Azure Devops cant be hosted on premise, but TFS can which is essentially the same thing but gets its updates slightly more slowly. We use TFS 2018 on prem and its great  
  > **username_4**: Is this a real question? To me it looks like FUD with no actual research.  
  > **username_5**: Great question! Have you reached any answer to your questions? If so, please write it so that the community can benefit from it too.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_6 on 2019-01-18. Score: 5
  
  I would love to get some clarity too maybe from a more authoritative source than myself (I'm sure I'm guilty of FUD too).
  
  I've been looking to deploy to Azure using Kubernetes. I am similarly confused but I think that is because there isn't one clear path. I can't speak for Microsoft but their attitude to cloud seems to be they are happy to become "*all things to all men*". If you are using Azure, Microsoft don't seem to have a strong opinion on how you get there.
  
  Microsoft are actively trying to evolve; e.g.
  [Linux now dominates Azure](https://www.zdnet.com/article/linux-now-dominates-azure/)
  
  ---
  
  Clearly **Azure DevOps** deployment pipeline does exactly what Jenkins can do - so in that sense it is a competitor. There is also that slightly off-putting upfront Azure DevOps pricing for parallel pipelines.
  
  On the one hand, Azure DevOps appears to be a re-branding of Visual Studio Team Services. So it will be familiar to people already within the traditional Microsoft development ecosystem. At the same time Microsoft are making great efforts to embrace technologies that are not traditionally Microsoft ([Go, Java, Node.js, Python, Ruby, PHP](https://docs.microsoft.com/en-us/azure/devops/pipelines/index?view=vsts) etc).
  
  It is early days - but it is not a surprise that Azure DevOps pipelines should prefer the Microsoft Git properties of Azure Repos and GitHub. In the same way that [BitBucket pipelines](https://bitbucket.org/product/features/pipelines) prefers BitBucket and [GitLab pipelines](https://docs.gitlab.com/ee/ci/pipelines.html) prefer GitLab.
  
  ---
  
  ***Meanwhile;***
  
  The Azure Marketplace offers a [Jenkins deployment](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/azure-oss.jenkins) that comes with Azure deployment plugins out of the box.
  
  Many Jenkins plugins have been developed by the [Azure DevOps team](https://plugins.jenkins.io/?q=azure%20devops%20team).
  
  ---
  
  ***in addition;***
  
  Microsoft have put their backing behind Kubernetes related projects [Helm](https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm) and [Draft](https://docs.microsoft.com/en-us/azure/aks/kubernetes-draft). Helm is a package manager for Kubernetes. You can even use Helm to deploy a Jenkins installation into Kubernetes.
  
  --
  
  It would be interesting to see someone weigh up the benefits, [costs](https://azure.microsoft.com/en-us/pricing/calculator) and effort of running your own Jenkins in Azure verses using Azure DevOps pipelines.
  
  ... and then there is [Jenkins-X](https://jenkins-x.io/).
  
  So it would seem we have many options and decisions to make.
  
  
  ---
  
  ### Answer by username_7 on 2019-03-27. Score: 2
  
  1. Yes, because Azure Pipelines can do what Jenkins does. However, you don't have to throw the baby out with the bathwater. Microsoft continues to position their platforms such that integrations can occur with existing installations of just about anything. Many orgs have huge investments in tooling that is difficult to change. Rather than taking an all-or-nothing stance, Microsoft is embracing standards and a bring-your-own mentality, giving you ultimate choice as to how you want to implement the tools.
  2. The agents technically are your pipeline as the tasks execute on the agents targeted within the pipeline. All you are configuring within the portal are the steps the pipeline will execute. The agents download tools/extensions necessary to execute the tasks. In addition, with the new YAML pipelines, the pipelines are defined within your code repos. As far as hosting is concerned, you can host Azure DevOps Server entirely on premise, within any cloud provider, or a combination of Azure VMs and Azure SQL.
  3. Generic Git repositories are [supported in Azure DevOps Services using the classic editor or both YAML and classic editor if using Azure DevOps Server](https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/?view=azure-devops) (on-prem) at the moment. You can add [GitLab repository integration](https://marketplace.visualstudio.com/items?itemName=onlyutkarsh.gitlab-integration) by installing the extension.
  
  
  ---
  
  ### Answer by username_8 on 2019-03-08. Score: 2
  
  In answer to part 2 (maybe), it does seem like they're pitching it as an alternative to Jenkins, although there's plenty of documentation suggesting that it can all be [used together](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/integrate-jenkins-pipelines-cicd?view=azure-devops&tabs=yaml) (and [here](https://www.dragonspears.com/blog/ci-cd-with-jenkins-and-azure-devops-services)). When used with Jenkins though, it does seem to be more focussed on a deployment bridge. I was hoping that I could use it as a build agent with Jenkins as an orchestrator, like I could do with Jenkins & AWS CodeBuild.
  I haven't *seen* anything to suggest I could do so yet, but maybe...
  Multi-cloud deployments is very intriguing though...
  
  
  ---
  
  