concourse / concourse/pool-resource
Getting two environments at a time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Twice recently, the Opsman pipeline has claimed TWO environments. It only actually uses one of them, and then only unclaims one of them. This leaves one of the environments in limbo, until a human notices and manually unclaims it.
This is what it looks like in the pipeline.
Is there any additional information I can give you next time this happens to help you diagnose?
Contributor guide
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 reproducing the Opsman pipeline behavior described in the issue and tracing how pool-resource handles claiming and unclaiming environments. Use the attached pipeline image as context; done means a run that claims two environments releases both, leaving neither in limbo.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100