Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Show container resolution and actual used container in job-info page #16588

Closed
bgruening opened this issue Aug 24, 2023 · 1 comment · Fixed by #18579
Closed

Show container resolution and actual used container in job-info page #16588

bgruening opened this issue Aug 24, 2023 · 1 comment · Fixed by #18579
Assignees
@mvdbeek
Labels
area/admin area/backend area/UI-UX

Comments

@bgruening
Copy link
Member

xref: #13037 (comment)

One major problem is that only the dependency resolution is shown on that page currently, not the container resolution. Additionally, I am pretty sure that you're seeing the dependency as it resolves presently, not the dependency that was necessarily used when the job ran.

And I think @mvdbeek suggested running it as a metric plugin.
@bgruening bgruening mentioned this issue Aug 24, 2023
Merged
@bgruening
Copy link
Member Author

It would be also nice if more complicated cases, like a mixed conda/container resolver would be able to get displayed in the job-info page. E.g. run in centos:7 container but using samtools, bowtie2 conda packages mounted from host system.

@mvdbeek mvdbeek self-assigned this Nov 7, 2023
@mvdbeek mvdbeek moved this from Triage/Discuss to Todo in Backend Working Group - weeklies Nov 7, 2023
mvdbeek added a commit to mvdbeek/galaxy that referenced this issue Jul 20, 2024
@mvdbeek
Record container id and type in core job metrics
7385b93 
Closes galaxyproject#16588.
Not sure if we want to do this versus a separate but always loaded
plugin vs a regular relationship in the database.

Seems unlikely that we'd do anything beyond reporting, so maybe this is
fine for now ?
@mvdbeek mvdbeek mentioned this issue Jul 20, 2024
Merged
4 tasks
mvdbeek added a commit to mvdbeek/galaxy that referenced this issue Jul 26, 2024
@mvdbeek
Record container id and type in core job metrics
9587f59 
Closes galaxyproject#16588.
Not sure if we want to do this versus a separate but always loaded
plugin vs a regular relationship in the database.

Seems unlikely that we'd do anything beyond reporting, so maybe this is
fine for now ?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mvdbeek mvdbeek

Labels
area/admin area/backend area/UI-UX
Projects
Backend Working Group - weeklies
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Record container id and type in core job metrics mvdbeek/galaxy
2 participants
@bgruening @mvdbeek