Convert travis-ci/appveyor to github actions#951
Conversation
|
I'm seeing that common_timeout fails, should be marked with |
|
@ygj6 great job! how long does it takes now on github actions? |
|
About 15min in my morning (maybe your evening), but it is very slow and easy to fail in the evening. Just my personal feeling. |
.github/workflows/doxygen.yml
Outdated
|
|
||
| - name: Deploy Documentation | ||
| env: | ||
| LIBEVENT_DEPLOY_PRI: ${{ secrets.LIBEVENT_DEPLOY_PRI }} |
There was a problem hiding this comment.
A was talking about this variable, is it available for PRs? (I couldn't find anything in documentation)
There was a problem hiding this comment.
#951 (comment)
‘secrets.LIBEVENT_DEPLOY_PRI’ is defined by myself.
There was a problem hiding this comment.
Indeed, the libevent repo will need the same, and my question is will these secrete variable will be available to the PRs?
For example, in travis-ci encrypted variables a not available to the PRs:
Encrypted environment variables are not available to pull requests from forks due to the security risk of exposing such information to unknown code.
There was a problem hiding this comment.
doxygen workflow is not applicable for PRs. And the workflow runs only on push events, not pull_request events.
on:
push:
branches:
- master
The workflow will be triggered if PR is merged.
I also test this in a example.
There was a problem hiding this comment.
doxygen workflow is not applicable for PRs.
Ok, just out of curiosity do you know if user-defined secrets available for the PRs?
There was a problem hiding this comment.
I'm not sure. I will keep track of this issue, maybe I am missing something now.
|
I made some modifications:
Parallel testing is still likely to fail, so I deleted several |
|
@ygj6 any other known issues? or ready for merge? |
f3c1ac4 to
6611f45
Compare
I added some codes like |
d9af6a3 to
8aa973f
Compare
|
In the last force-push, I deleted the branch |
|
Ok, are you ok with my push (maybe --force) into your TODO branch? |
But this will retry all tests, while we need only few |
|
My topic branch against your PR is github-actions |
OK, no problem. |
* github-actions: Update badges (drop travis-ci and appveyor) Drop travis-ci CI Drop appveyor CI github actions: test and coverage github actions: doxygen Ignore truthy in yamllint (for github-actions) test: mark common_timeout as retriable cmake: set rpath for libraries on linux test-export: compatible with all versions of visual studio coverage: 'lcov --remove' need full path
* github-actions: Update badges (drop travis-ci and appveyor) Drop travis-ci CI Drop appveyor CI github actions: test and coverage github actions: doxygen Ignore truthy in yamllint (for github-actions) test: mark common_timeout as retriable cmake: set rpath for libraries on linux test-export: compatible with all versions of visual studio coverage: 'lcov --remove' need full path
* github-actions-v2: travis: disable doxygen and coveralls, in favor of github actions github actions: test and coverage github actions: doxygen Ignore truthy in yamllint (for github-actions) test: mark common_timeout as retriable cmake: set rpath for libraries on linux test-export: compatible with all versions of visual studio coverage: 'lcov --remove' need full path
|
@ygj6 merged (thanks a lot for looking into this!) P.S. I decided to leave the travis-ci (with disabled coveralls/doxygem)/appveyor for awhile |
Actually right now github's VMs is better then travis/appveyor.
Fixes: 28eb0d9 ("github actions looks good - drop travis/appveyor (libevent#951)")
Closes: #945
CMAKE_C_COMPILER_IDisAppleClangon mac. The commandmake verify_coveragewill fail unless you change line 78 incmake/CodeCoverage.cmake.Checking
CMAKE_BUILD_TYPEon lines 83-85 is redundant because it is already done on lines 186-188 in CMakeLists.txt, and it cause a warning whenCMAKE_BUILD_TYPEis set to 'debug'.The command
lcov --removealways treats the output as an absolute path, so we need pass it a full path.Supports all versions of Visual Studio.
Before setting rpath:
After setting rpath:
We need do some settings for libevent/libevent and libevent/doc:
First, generate the keys:
ssh-keygen -f libevent-deploy-key # will generate libevent-deploy-key and libevent-deploy-key.pubOpen
https://github.com/libevent/libevent/settings/secrets->Add new secretsNameinputLIBEVENT_DEPLOY_PRIValueinput content of libevent-deploy-keyOpen
https://github.com/libevent/doc/settings/keys->Add deploy keyTitleinputLIBEVENT_DEPLOY_PUBKeyinput content of libevent-deploy-key.pub