Page MenuHomePhabricator

[services] Blob - Fix Dockerfile
ClosedPublic

Authored by karol on Aug 22 2022, 6:10 AM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 27 2024, 5:58 AM
Unknown Object (File)
Oct 21 2024, 6:12 AM
Unknown Object (File)
Sep 27 2024, 4:58 PM
Unknown Object (File)
Sep 27 2024, 4:58 PM
Unknown Object (File)
Sep 27 2024, 4:58 PM
Unknown Object (File)
Sep 27 2024, 4:53 PM
Unknown Object (File)
Sep 24 2024, 3:41 PM
Unknown Object (File)
Sep 24 2024, 3:41 PM

Details

Summary

D4493 ruined building blob service using yarn scripts.

@jon Please, take a look here and let me know if this is a nix-friendly change.

Test Plan
cd services
yar run-backup-service-in-sandbox

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

karol edited the test plan for this revision. (Show Details)
karol added reviewers: jon, marcin, tomek.
karol added a subscriber: jon.
This revision is now accepted and ready to land.Aug 22 2022, 6:33 AM
This revision now requires review to proceed.Aug 22 2022, 7:14 PM

@jon Please, take a look here and let me know if this is a nix-friendly change.

Non-docker workflows (nix is just one) don't use docker, so I don't have an opinion. But the code looks fine.

D4493 ruined building blob service using yarn scripts.

We should probably have CI reflect this if it's the canonical way to build blob.

This revision is now accepted and ready to land.Aug 23 2022, 8:40 AM

This also needs to be done for backup

$ yarn run-backup-service-in-sandbox
...
services-backup-server-1  | /bin/sh: 1: scripts/run_service.sh: not found
services-backup-server-1 exited with code 127
Done in 270.49s.

But that's a separate issue, and this still fixes a workflow.

This revision was automatically updated to reflect the committed changes.

@jon, please don't ever point out an issue without creating or linking a task for it.

@karol, please don't ever land a diff where somebody has pointed out an issue without creating or linking a task or diff for it. Can you please do that now?

@jon, please don't ever point out an issue without creating or linking a task for it.

I'm actually not sure who should have ownership of doing this. It was in the test plan, so everyone should have stumbled upon it.