Differential D910

No need to expose port 5008 in swh-scheduler-worker's Dockerfile
ClosedPublic
Actions

Authored by douardda on Jan 10 2019, 1:53 PM.

Tags

None

Subscribers

None

Details

Reviewers

Group Reviewers

Commits

rDENV8deedeb75ae8: No need to expose port 5008 in swh-scheduler-worker's Dockerfile
rCDFD8deedeb75ae8: No need to expose port 5008 in swh-scheduler-worker's Dockerfile

Summary

depends on D909

Diff Detail

Repository

rCDFD Dockerfiles for developers

Lint

Automatic diff as part of commit; lint not applicable.

Unit

Automatic diff as part of commit; unit tests not applicable.

Event Timeline

douardda created this revision.Jan 10 2019, 1:53 PM

Herald added a reviewer: Reviewers. · View Herald TranscriptJan 10 2019, 1:53 PM

Harbormaster completed remote builds in B3352: Diff 2879.Jan 10 2019, 1:53 PM

douardda added a child revision: D911: Try to rationalize a bit ports published on the host.Jan 10 2019, 1:54 PM

ardumont accepted this revision.Jan 10 2019, 1:58 PM

This revision is now accepted and ready to land.Jan 10 2019, 1:58 PM

Closed by commit rCDFD8deedeb75ae8: No need to expose port 5008 in swh-scheduler-worker's Dockerfile (authored by douardda). · Explain WhyJan 10 2019, 4:03 PM

This revision was automatically updated to reflect the committed changes.

douardda added a commit: rDENV8deedeb75ae8: No need to expose port 5008 in swh-scheduler-worker's Dockerfile.Nov 26 2019, 1:34 PM

Revision Contents
Changeset List

Path

Size

dockerfiles/

swh-scheduler-worker/

2 lines

Diff 2907

dockerfiles/swh-scheduler-worker/Dockerfile

Loading...