Skip to content

[TSPS-519] Add version number to pipeline run history page #5341

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

Merged
merged 4 commits into from
Jun 12, 2025

Conversation

MatthewBemis
Copy link
Member

Jira Ticket: https://broadworkbench.atlassian.net/browse/519

There are some small backend changes required to return the pipeline version number, which I'll PR shortly. In the meantime, this UI change is resilient to the missing field so we can merge the PRs in any order without breakage.

Summary of changes:

What

  • Adds the version number next to the pipeline name in the job history page
    screencapture-localhost-3000-2025-06-10-12_52_35

Why

Testing strategy

@@ -32,6 +32,7 @@ export interface UserPipelineQuotaDetails {
export interface PipelineRun {
jobId: string;
pipelineName: string;
pipelineVersion?: number;
Copy link
Member Author

@MatthewBemis MatthewBemis Jun 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

depending on merge order w/ the backend code, this will eventually be required. i'll clean it up accordingly, but for the sake of iteration speed and backwards compatibility, it can merge like this (IMO)

Copy link

@MatthewBemis
Copy link
Member Author

merging this - the related failures are due to gcp outage and this is going into a feature branch anyway

@MatthewBemis MatthewBemis merged commit 155f751 into tsps_imputation_ui_feature_branch Jun 12, 2025
5 of 8 checks passed
@MatthewBemis MatthewBemis deleted the mb-tsps-519 branch June 12, 2025 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants