-
Notifications
You must be signed in to change notification settings - Fork 74
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: move to self-hosted action runner #618
Conversation
4eceffe
to
db482f2
Compare
fd78fa8
to
68b4474
Compare
68b4474
to
0b24e29
Compare
Signed-off-by: Kiefer Chang <kiefer.chang@suse.com>
Signed-off-by: Kiefer Chang <kiefer.chang@suse.com>
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.
LGTM. Also, it seems to work, given it says "all checks passed" :-)
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.
LGTM, thanks for this improvement!
@Mergifyio backport v1.2, v1.1 |
❌ No backport have been created
GitHub error:
|
@Mergifyio backport v1.2 |
🟠 Pending
|
@Mergifyio backport v1.2 |
✅ Backports have been created
|
While Jenkins instance worked in the past, I propose we move the vagrant installation CI to GitHub self-hosted action runner for
Note: The drone CI part doesn't change. We still rely on it to build ISO and publish to the release server.