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

ci: how to setup custom testing machine #1471

Merged

Conversation

praiskup
Copy link
Member

SSIA

@praiskup praiskup added no-release-notes no-ci-builds No need to run CI automation (Packit, Copr builds, Testing Farm, ...) labels Sep 27, 2024
@praiskup praiskup force-pushed the praiskup-ec2-preparation branch 2 times, most recently from 6ff1092 to 51080ad Compare September 27, 2024 10:34
@praiskup praiskup force-pushed the praiskup-ec2-preparation branch from 51080ad to 0a3a9dd Compare September 27, 2024 11:33
Copy link
Member

@xsuchy xsuchy left a comment

Choose a reason for hiding this comment

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

Aaaaaah. Submodules. Run away!

Please, please no. No submodules.

@praiskup
Copy link
Member Author

There's nothing wrong with git submodules, huh? :-)

Anyway, I'm not doing anything with the status quo, just updating to a new hash (and documenting).

@xsuchy
Copy link
Member

xsuchy commented Oct 9, 2024

/me pulling a long stick and hitting merge button. But I do not want to touch this with a bare hand. :)

@xsuchy xsuchy merged commit 0516f5a into rpm-software-management:main Oct 9, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-ci-builds No need to run CI automation (Packit, Copr builds, Testing Farm, ...) no-release-notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants