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

Jenkinsfile: WAIT FOR UPGRADE VERSION #910

Merged

Conversation

ebattat
Copy link
Collaborator

@ebattat ebattat commented Sep 30, 2024

Type of change

Note: Fill x in []

  • bug
  • enhancement
  • documentation
  • dependencies

Description

Currently, the stage 'WORKLOADS Verifications' runs until the stage 'OpenShift Upgrade AND Verifications' is complete. Change it to use WAIT_FOR_UPGRADE_VERSION inside the stage 'WORKLOADS Verifications', so that it runs the Windows verification in a single job loop.

For security reasons, all pull requests need to be approved first before running any automated CI

@ebattat ebattat added the enhancement New feature or request label Sep 30, 2024
@ebattat ebattat self-assigned this Sep 30, 2024
Copy link
Member

@RobertKrawitz RobertKrawitz left a comment

Choose a reason for hiding this comment

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

My comment isn't about the changes per se, but I want to determine whether the podman run should have its status checked before setting success to true.

@@ -264,14 +258,12 @@ END
} else {
echo "Reached maximum retry attempts for workload ${workload}. Moving to the next workload..."
}
}
Copy link
Member

Choose a reason for hiding this comment

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

Above here, do you need to check that the sudo podman run succeeds before success = true?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I dont think it necessary

Copy link
Member

Choose a reason for hiding this comment

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

Why? It's a simple check, and things can go wrong.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Its only on failure

Copy link
Member

Choose a reason for hiding this comment

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

It looks like you're relying on something raising an excception if something goes wrong, but what if the podman run simply fails? Shouldn't that be treated as a failure?

Copy link
Collaborator Author

@ebattat ebattat Oct 1, 2024

Choose a reason for hiding this comment

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

It is more for failure inside the container, If podman run will fail, I prefer that all the run the will fail and not continue.

Copy link
Member

Choose a reason for hiding this comment

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

Right, but that's why you should check whether the podman run fails -- if it fails, then you fail the entire run.

@ebattat ebattat changed the title WAIT FOR UPGRADE VERSION Jenkinsfile: WAIT FOR UPGRADE VERSION Oct 6, 2024
@ebattat ebattat merged commit 9946954 into redhat-performance:main Oct 8, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants