Closed Bug 1927736 Opened 1 year ago Closed 1 year ago

every time push to try via lando fails it leaves behind changes in try_task_config.json, old push to try did not do that

Categories

(Developer Infrastructure :: Try, defect, P3)

Product:
Developer Infrastructure
Component:
Try
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: tnikkel, Unassigned)

References

(Blocks 1 open bug)

Details

Try pushing to try and get an error (a good way to do that is have an mq applied), it will leave behind changes in try_task_config.json which is annoying to clean up.

This is because the code path that removes the try_task_config.json is also the code path which is causing failure due to mq. We use hg prune from evolve to safely remove the temporary try commit.

Severity: -- → S3
Component: Lando → Try
Priority: -- → P3
Product: Conduit → Developer Infrastructure

Naive question: can we inject try_task_config.json into the payload sent to Lando with it ever existing on disk?

Sorry but we don't support mq. Its usage at Mozilla has been deprecated for more than 10 years now.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX

Pushing to try fails for other reasons, like network reasons.

You need to log in before you can comment on or make changes to this bug.