ci: switch from jenkins to github actions #594
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tiagolobocastro
requested review from
Abhinandan-Purkait,
niladrih and
dsharma-dc
tiagolobocastro
force-pushed
the
ci
branch
3 times, most recently
from
7d945dc to
9965628
Compare
Abhinandan-Purkait
approved these changes
Jan 8, 2025
tiagolobocastro
force-pushed
the
ci
branch
2 times, most recently
from
c2656b3 to
016b50d
Compare
|
bors try |
tryBuild succeeded: |
niladrih
approved these changes
Jan 8, 2025
|
bors merge |
bors-openebs-mayastor bot
pushed a commit
that referenced
this pull request
Jan 8, 2025
594: ci: switch from jenkins to github actions r=tiagolobocastro a=tiagolobocastro Jenkins has become troublesome to maintain and makes it harder for users to see and test output without adding new users. We could probably spend some time improving that, but the current Jenkins is also setup on systems managed by the sponsoring company so it makes sense to move away from that at least. In order to run the CI tests we need a relatively powerful CI system so we are making use of the ubuntu-latest-16-cores runners. The tests seem to run slower than on Jenkins. Part of it may be explained because the dependencies are not pre-cache and also the pre-requisites which take time to install. Co-authored-by: Tiago Castro <[email protected]>
|
bors cancel |
|
Canceled. |
Jenkins has become troublesome to maintain and makes it harder for users to see and test output without adding new users. We could probably spend some time improving that, but the current Jenkins is also setup on systems managed by the sponsoring company so it makes sense to move away from that at least. In order to run the CI tests we need a relatively powerful CI system so we are making use of the ubuntu-latest-16-cores runners. The tests seem to run slower than on Jenkins. Part of it may be explained because the dependencies are not pre-cache and also the pre-requisites which take time to install. Signed-off-by: Tiago Castro <[email protected]>
|
bors merge |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jenkins has become troublesome to maintain and makes it harder for users to see and test output without adding new users.
We could probably spend some time improving that, but the current Jenkins is also setup on systems managed by the sponsoring company so it makes sense to move away from that at least.
In order to run the CI tests we need a relatively powerful CI system so we are making use of the ubuntu-latest-16-cores runners.
The tests seem to run slower than on Jenkins. Part of it may be explained because the dependencies are not pre-cache and also the pre-requisites which take time to install.