You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/developing/custom-production-image.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This included the ability for users of ldmx-sw to manually launch the workflow t
25
25
#### Steps
26
26
2. Add `omarmoreno` as a [collaborator](https://docs.docker.com/docker-hub/repos/#collaborators-and-their-role) on the new repository you created
27
27
(This is the username that will be pushing any generated production images to DockerHub).
28
-
3. Go to the [Build Production Image]([200~https://github.com/LDMX-Software/ldmx-sw/actions/workflows/build_production_image.yml) workflow on the "Actions" page.
28
+
3. Go to the [Build Production Image](https://github.com/LDMX-Software/ldmx-sw/actions/workflows/build_production_image.yml) workflow on the "Actions" page.
29
29
4. Select "Run Workflow" and input your values for the three parameters. Leave the drop down menu to the value `trunk` - that is the branch on which the workflow is run.
30
30
-`repo`: **required** DockerHub repository that you want the image to be pushed to (same as repo you created earlier - e.g. `tomeichlersmith/eat`)
31
31
-`branch`: (optional) name of branch you want to be compiled into the production image (e.g. `iss420-my-cool-devs`, default is `trunk`)
@@ -90,5 +90,5 @@ A lot of different submission scripts have been written in `bash` and `python`,
90
90
3. Submit the job script using the submission program (e.g. `bsub` or `condor`) however many times
0 commit comments