Detect previously applied steps to skip, speeding up later runs for troubleshooting or update

Open
#49 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
powershell
Domain
devops, tooling

Research direction

The issue does not name files, tests, or an entry point. Start by tracing how configuration items are applied during a rerun and determine how their versions or changesets can be recorded and checked. Done means reruns skip items already present at the latest changeset while still applying new or updated functionality.

Written by the indexing model from the issue text.

Description

Image

As an idempotent system, having to rerun to correct failures or perform updates should be fast.

It appears that reruns are attempting to run all items over again. To reduce time and friction, it would be a good idea to store a version/release number to check for new functionality or updates to existing, and run a check for the configuration before attempting to apply it, then skip those that are present and on the latest changeset.

Dominant language
PowerShell
Stars
2.2k
Forks
168
Avg merge
5h 14m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/WindowsDeveloperConfig

All issues in microsoft/WindowsDeveloperConfig

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.