Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Engineering] Create Azure DevOps .yaml pipeline for main CI #2331

Closed
3 tasks done
stevengum opened this issue Jun 10, 2020 · 4 comments
Closed
3 tasks done

[Engineering] Create Azure DevOps .yaml pipeline for main CI #2331

stevengum opened this issue Jun 10, 2020 · 4 comments
Assignees
@BruceHaley
Labels
BF Agility For Issues or Feature Requests that impact the SDK Team's agility P0 Must Fix. Release-blocker R10 Release 10 - August 17th, 2020
Milestone
R10

Comments

@stevengum
Copy link
Member

stevengum commented Jun 10, 2020 •
edited by BruceHaley
Loading

We should stop using Azure DevOps Classic Pipelines and switch to .yaml-based pipelines.

  • Create .yaml based pipeline
  • Refactor pipeline to more closely follow dotnet factoring (where applicable)
  • Create separate stages for runtime compatibility

@BruceHaley FYI
@stevengum stevengum added P0 Must Fix. Release-blocker Engineering R10 Release 10 - August 17th, 2020 BF Agility For Issues or Feature Requests that impact the SDK Team's agility labels Jun 10, 2020
@stevengum stevengum self-assigned this Jun 10, 2020
@munozemilio munozemilio added this to the R10 milestone Jul 1, 2020
@stevengum stevengum assigned BruceHaley and unassigned stevengum Jul 1, 2020
@BruceHaley BruceHaley mentioned this issue Jul 6, 2020
Merged
@BruceHaley
Copy link
Contributor

Splitting the pipeline into multiple .yml files makes sense once we have 2 or more yaml pipelines that can share them.

@BruceHaley
Copy link
Contributor

Should BotBuilder-JS-master-CI-node12 be converted as part of this issue?

@stevengum
Copy link
Member Author

Yes please 😄

The build steps I think should be separated out for reusability as well. The input to the build stage should include the Node.js runtime.

@BruceHaley BruceHaley mentioned this issue Jul 7, 2020
Merged
@stevengum
Copy link
Member Author

Closing via #2487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BruceHaley BruceHaley

Labels
BF Agility For Issues or Feature Requests that impact the SDK Team's agility P0 Must Fix. Release-blocker R10 Release 10 - August 17th, 2020
Projects
None yet
Milestone
R10
Development

No branches or pull requests
3 participants
@BruceHaley @stevengum @munozemilio