nanoframework/Home

Change Azure Pipelines yaml to separate build of booter and CLR

Open

#357 opened on Jul 16, 2018

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees) (89 forks)auto 404
Area: Config-and-BuildArea: InterpreterHacktoberfestPriority: LowType: Enhancementup-for-grabs

Repository metrics

Stars
 (936 stars)
PR merge metrics
 (PR metrics pending)

Description

No need to keep building and releasing booter versions when nothing has changed. Currently nanoBooter is always build along with the nanoCLR which is a waste of time and computing resource. Not to mention that is misleading because you actually don't know if there were any changes or not.

Contributor guide

Research direction
Modify the Azure Pipelines YAML to conditionally build booter only when booter source changes.
Tech stack
azure
Domain
devops
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Azure PipelinesYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55