infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Piotrowski (Sujan) (JIRA)" <>
Subject [jira] [Commented] (INFRA-17030) Azure Pipelines as CI tool
Date Mon, 01 Oct 2018 12:29:00 GMT


Jan Piotrowski (Sujan) commented on INFRA-17030:

Nice [~pitrou].

In our PR adding the configuration, 2 program managers from Microsoft have said hello. Kayla
Ngan explicitly offered help and answers around permissions and similar topics. Probably not
on JIRA (yet), but feel free to abuse our PR to contact if needed.

> Azure Pipelines as CI tool
> --------------------------
>                 Key: INFRA-17030
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: CI, Github
>            Reporter: Jan Piotrowski (Sujan)
>            Priority: Major
>              Labels: Azure
> Microsoft recently rebranded Visual Studio Team Services (VSTS) as Azure DevOps, which
includes a CI tool called "Azure Pipelines":
> This especially piqued our interest:
> > Starting today, Azure Pipelines provides unlimited CI/CD minutes and 10 parallel
jobs to every open source project for free.
> We have a project that could _really_ use the 10x parallelism with `cordova-lib` and
would like to try Azure Pipelines as an additional CI tool.
> We tested our configuration in a fork, which worked pretty well:
> We also created a PR for cordova-lib that adds this configuration to our repository already:
> Azure Pipelines is best installed via the Github App from the Github Marketplace:

> (Configuring via Azure DevOps itself works as well, but requires additional configuration
until it really works with the GitHub repository and adds a lot of additional tools we don't
need by default).
> An empty `apache-cordova` organization in Azure Devops exists, where I could invite any
user that will do the Github app and permission stuff:
But of course you could also create an Apache account if you prefer to do it that way - no
idea about the requirements here.

This message was sent by Atlassian JIRA

View raw message