-
Notifications
You must be signed in to change notification settings - Fork 49
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
AIAP: Shift gates to use AIAP #659
Comments
This change updates the 20_apply_aiap.sh script to utilize the status-checker container to determine if airship-in-a-pod has successfully completed. It also includes a check to fail when the status-checker has detected a failure. Relates-To: #659 Change-Id: I3673de7157f498778154c798878ab20245396c62
This adds a new script to the runner container that is run in the entrypoint which runs the log gathering ansible playbook from inside the runner container. The gate then extracts these logs with a new role. This also updates the image_build script to fix how it changes the container imagePullPolicy Closes: #658 Relates-To: #659 Change-Id: I24d11c66e7b71852256e164343f7bb2f331d1fef
I can see the issue #658 is now completed. I can test log extraction feature and enable voting for aiap zuul gate. can someone assign this issue to me ? |
@sirajyasin Sorry I didn't get this assigned to me, I am already working this as well as #658 |
This related patchset https://review.opendev.org/c/airship/airshipctl/+/824738 The Zuul job was timing out because this directory was not found. With this PS, the AIAP Zuul job no longer times out, but it seems to still fail, so the failures would need to be resolved before shifting the gates over to AIAP. I was using this test PS to log output from the Zuul job (https://review.opendev.org/c/airship/airshipctl/+/823727) |
We need to shift our upstream gates to use AIAP exclusively as the functional testing gate in our Airshipctl Zuul and Jenkins systems, so that we are using the same testing mechanism end to end. This requires #658 to be in place first before this can be implemented.
The text was updated successfully, but these errors were encountered: