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
Currently the builder api client in the habitat binary only has 1 means for checking job status: hab bldr job status <GROUP_ID>|| --<ORIGIN>
This is fine if you know the group id and largely we put these into the UI for users to check. However, it would be nice to make these jobs/groups discoverable via the CLI. Ideally it would be really great to be a able to get all of the jobs/groups associated with a single top level package.
It's also possible we have a need for refactoring the current UX around hab bldr job status though that may be a side effect of this work.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
Currently the builder api client in the habitat binary only has 1 means for checking job status:
hab bldr job status <GROUP_ID>|| --<ORIGIN>
This is fine if you know the group id and largely we put these into the UI for users to check. However, it would be nice to make these jobs/groups discoverable via the CLI. Ideally it would be really great to be a able to get all of the jobs/groups associated with a single top level package.
It's also possible we have a need for refactoring the current UX around
hab bldr job status
though that may be a side effect of this work.The text was updated successfully, but these errors were encountered: