Feature #21595
closedShow "Static Query" in Job invocations overview
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1505932
Description of problem:
Running the same job against different targets results in a confusing overview page. Adding the "Static Query" would give at least a hint of the targets of historic jobs.
Version-Release number of selected component (if applicable):
Satellite 6.2.12
How reproducible:
always
Steps to Reproduce:
1. Run a job against "name = hosta"
2. Run a job against "name = hostb"
Actual results:
Both jobs look identical on the "Job invocations" list https://satellite/job_invocations
Expected results:
Additional column shows target of the jobs.
Additional info:
Updated by Adam Ruzicka over 6 years ago
- Category set to Foreman
- Target version set to 113
- Difficulty set to easy
Updated by Aditi Puntambekar over 5 years ago
- Assignee set to Aditi Puntambekar
- Triaged set to No
Updated by Aditi Puntambekar over 5 years ago
Hello Adam!
Here, while adding the new column, should we write a new helper method for getting the host name in the index.html of job_invocations ?
Updated by Adam Ruzicka over 5 years ago
Most likely yes. While you're doing this, please bear in mind that there may be many hosts per job invocation and some kind of truncation might be needed.
Updated by Aditi Puntambekar over 5 years ago
Okay. How about handling it directly in view ?
<td> <%= trunc_with_tooltip(invocation&.targeting&.search_query, 15) %> </td>
This can render the value for us directly without helper method.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/394 added
Updated by Aditi Puntambekar over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|8f0ba81e3634c2f015814ee77e1b303f77ef3faa.
Updated by Adam Ruzicka over 5 years ago
- Fixed in Releases foreman_remote_execution 1.6.6 (Foreman 1.20) added
Updated by Ondřej Ezr almost 3 years ago
- Related to Bug #32794: N+1 on targeting on index page added