Figure out update strategy for MicroBuild and SignTool infrastructure
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
The signing infrastructure uses checked-in versions of MicroBuild and SignTool. We should figure out if we need to auto-update them, and how.
If we separate out the signing build pipeline from the Go pipeline, it makes auto-updates easier: https://github.com/microsoft/go/issues/13.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the checked-in MicroBuild and SignTool versions and the linked microsoft/go#13 discussion about separating the signing build pipeline from the Go pipeline. Define whether automatic updates are needed and what pipeline arrangement would support them; done means an agreed update strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100