-
Notifications
You must be signed in to change notification settings - Fork 25
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
Test deployment locally with tmt (from packit branch) #581
Conversation
[test] |
Build failed. ✔️ pre-commit SUCCESS in 1m 44s |
5a17873
to
a76a467
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 45s |
a76a467
to
a2677c7
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 40s |
a2677c7
to
88d08b0
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 37s |
88d08b0
to
07e4cd0
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 45s |
07e4cd0
to
b84b896
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 51s |
b84b896
to
eb5653c
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 37s |
b232a4c
to
385b341
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 52s |
b0b87a1
to
b6d1528
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
b6d1528
to
1be22b2
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 37s |
check |
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
1ac6e50
to
081086c
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 44s |
081086c
to
64f0e4b
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 38s |
64f0e4b
to
e8ac4bf
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 42s |
e8ac4bf
to
84c97d9
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 43s |
269609b
to
5b9a555
Compare
Co-authored-by: Laura Barcziová <[email protected]> Co-authored-by: Matej Focko <[email protected]>
Tokman is no longer used. The github-app-private-key is now used directly by the service and the workers.
cd4deb9
to
e906d88
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 40s |
Build failed. ✔️ pre-commit SUCCESS in 1m 36s |
Co-authored-by: Matej Focko <[email protected]>
f250568
to
49425a1
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 41s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Schedule test on Testing Farm / tests (pull_request) Successful in 36m
🥳 🥳 🥳
great job Maja!
as for the Zuul deployment-tests
, can we remove them right now or in a follow-up PR? We should then also configure the new check to be required to pass for merging (in the repo settings).
Now we are using testing farm for it.
Build succeeded. ✔️ pre-commit SUCCESS in 1m 40s |
I have disabled deployment test from zuul. |
@majamassarini I meant just changing the branch protection rules to require |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Yes, it is preferred. Though having no (red) CI right now is IMO bit worse, and you have the GH Action ready 🤷 flakey > nothing IMO |
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 37s |
To be able to access secrets and test ansible scripts using github secrets in the testing farm github action I need to create a PR from the packit repo itself (and not from a fork).
This is the reason why the PR is duplicated at the moment.
Should fix #562 #563 #564 #565