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.

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

new column "distro" in butido db jobs output #48

Closed
christophprokop opened this issue Nov 16, 2022 · 1 comment
Closed

new column "distro" in butido db jobs output #48

christophprokop opened this issue Nov 16, 2022 · 1 comment
Assignees
Labels
good first issue Good for newcomers prio Issues with a higher priority

Comments

@christophprokop
Copy link
Collaborator

$ butido db jobs -L 1
│ Submit │ Job │ Time │ Endpoint │ Success │ Package │ Version │
│ 40c0be74-0b77-457c-86a0-a1cd4f4cd1a9 │ ed855e87-0537-4b34-a45e-a7725e8b8e26 │ 2022-11-14 10:34:46 │ host1 │ yes │ demo-app │ 1.2.3│

butido db jobs does not list linux distro short name (e.g. "rh8", "sles15", ...)
location for the new column: far right (after "package" and "version")

@matthiasbeyer
Copy link
Contributor

Related to #49

@christophprokop christophprokop added the good first issue Good for newcomers label Nov 17, 2022
@primeos-work primeos-work added the prio Issues with a higher priority label Nov 30, 2022
primeos-work added a commit to primeos-work/butido that referenced this issue Mar 2, 2023
This changes the `images` configuration setting so that shorter names
can be assigned to container images. This is done in preparation of
adding an additional column to the `butido db jobs` output that shows
the image that was used for the build (science-computing#48). The full image names are
often too long so it should be possible to specify shorter names as
aliases. The `compatibility` setting is bumped since this is a breaking
change that requires updating the configuration files (side note: we
should probably use a normal number for the `compatibility` setting as
it shouldn't depend on the butido version).

Fix science-computing#101.

Signed-off-by: Michael Weiss <michael.weiss@atos.net>
bors bot added a commit that referenced this issue Mar 7, 2023
178: Implement support for short image names and the distro column r=christophprokop a=primeos-work

This implements the necessary changes for #48 and #101.
It also contains the first preparations for the next butido release.


Co-authored-by: Michael Weiss <michael.weiss@atos.net>
@bors bors bot closed this as completed in cc17274 Mar 7, 2023
ammernico pushed a commit to ammernico/butido that referenced this issue Mar 28, 2023
This changes the `images` configuration setting so that shorter names
can be assigned to container images. This is done in preparation of
adding an additional column to the `butido db jobs` output that shows
the image that was used for the build (science-computing#48). The full image names are
often too long so it should be possible to specify shorter names as
aliases. The `compatibility` setting is bumped since this is a breaking
change that requires updating the configuration files (side note: we
should probably use a normal number for the `compatibility` setting as
it shouldn't depend on the butido version).

Fix science-computing#101.

Signed-off-by: Michael Weiss <michael.weiss@atos.net>
ammernico pushed a commit to ammernico/butido that referenced this issue Mar 28, 2023
The openSoftware developers build packages for multiple distributions
and requested an additional column in the `butido db jobs` output to
show for which distro the job was built (without having to perform a
separate/manual lookup for each entry). This feature should of course be
useful in general. The distro information is based on the name of the
container image. Some of our image names are quite long so we decided to
change the format of the `images` configuration setting (108eecc) so
that users can specify a short name that will be used to shorten the
output/column of the `db jobs` command.
The full/long image name, that is stored in the DB, will be used as a
fallback if there is no corresponding entry in the configuration (e.g.,
because the image was dropped in the meantime).

This resolves science-computing#48.

Signed-off-by: Michael Weiss <michael.weiss@atos.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers prio Issues with a higher priority
Projects
None yet
Development

No branches or pull requests

4 participants