Turn on Github CI #13489
Closed
Turn on Github CI #13489
Conversation
As an interim measure until we work out our longer term CI strategy this PR enables some basic CI tests using the Github CI capability.
|
Note also that some builds are expected to fail. There are some issues in master at the moment. I'm not seeking to resolve them as part of this PR. |
|
+1 |
|
Given the lack of CI testing at the moment - are we ok with classifying this as urgent? Adding that label - sorry should have added it before. Please reconfirm with that label! |
|
Urgent is a good idea. My approval stands. |
|
To be a bit of a pain, any word on issue #13152, since we can't do GitHub CI to that platform. |
openssl-machine
pushed a commit
that referenced
this pull request
Nov 24, 2020
As an interim measure until we work out our longer term CI strategy this PR enables some basic CI tests using the Github CI capability. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from #13489)
|
Pushed. We'll need to try and figure out the fixes for the various failing items. |
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.
As an interim measure until we work out our longer term CI strategy
this PR enables some basic CI tests using the Github CI capability.
You can take a look at a sample of what this looks like here:
mattcaswell/temptest#5
I've just enabled a small number of builds. It is not yet clear to me what the throughput of this service is - and some builds took 1.5 hours to complete, so I don't want to overload things. The objective of this is to just try and get some CI testing back so that we can at least start committing things again.