Uploaded image for project: 'Product Roadmaps'
  1. Product Roadmaps
  2. MMF-2365

Add Azure Pipelines tutorial for GitHub users

    XMLWordPrintable

    Details

    • Type: MMF
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Labels:
      None

      Description

      WHY

      GitHub is gaining more and more traction among SonarQube users, especially since Microsoft acquired it. Microsoft is creating as many bridges as possible between Azure DevOps and GitHub, allowing users to migrate from the first to the latter. They are pushing for a migration from Azure Repo (Azure DevOps code hosting service) to GitHub. 

      Also, we can see in the community multiple scenarios where users host their code with GitHub and still use Azure Pipelines to build (cf. PB Insights).

      As of today, users hosting their code on GitHub have no guidance about how to analyse their project using Azure Pipelines.

      WHAT

      Use case:

      As a developer hosting my code on GitHub, I want to be guided to add quality analysis to my project analyzed with Azure Pipelines, whatever my build technology (Maven/Gradle/.NET/C-C+/Other).

      Acceptance Criteria:

      • Once their project is created in SonarQube, GitHub users who want to analyze their project on Azure Pipelines should be guided with a tutorial.
      • The tutorial should help them whatever the type of build technology (Maven/Gradle/.NET/C-C+/Other) they use.

      HOW

      The current Azure Pipelines tutorial does not mention the source step of the configuration, since it is so trivial.

      We will add that tutorial to GitHub projects.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tom.howlett Tom Howlett
              Reporter:
              christophe.havard Christophe Havard
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: