-
Notifications
You must be signed in to change notification settings - Fork 26
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
Convert Linux Tests on Travis to Tests on Github Actions #83
Comments
Dave Cramer, I read the Travis file travis.yml, and based on what I read, I made a Github Actions file .github/workflows/build.yml. Using the new build.yml file and Github Actions, I successfully built and tested plr with versions of PostgreSQL from 9.5 through 13. In the file ".github/workflows/build.yml" only some minor changes were done.
In Travis, the build-test runs under "travis". In Travis, $HOME may be volatile. In Travis, to use "setfacl", elevated privileges are not needed.
to
In Travis, the first former case works. Changed This was not required. This minimized the number of processes. It looks cleaner. Here is the commit Here is the build result. Here is the PostgreSQL 13 run result. What do you think? Do you think that build-tests, using Github Actions, may become a permanent part of "postgres-plr? |
Well the simplest solution would be to move to travis-ci.com, but I prefer github actions. So I'd be up for this. Can you create a PR for it |
A message is received every time, that a login occurs to Travis (https://travis-ci.org/). ``` Please be aware travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information. I am aware that plr uses Travis to "test a build". ``` plr can also use another CI to also "test a build", for example, in the case that Travis actually, does stop serving open source projects. To see the "Github Actions" test result, one may navigate to the Github repository web page tab "Actions". Alternately, one may browse to the page: https://github.com/postgres-plr/plr/actions Fixes postgres-plr#83
A message is received every time, that a login occurs to Travis (https://travis-ci.org/). ``` Please be aware travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information. ``` I am aware that plr uses Travis to "test a build". plr can also use another CI to also "test a build", for example, in the case that Travis actually, does stop serving open source projects. To see the "Github Actions" test result, one may navigate to the Github repository web page tab "Actions". Alternately, one may browse to the page: https://github.com/postgres-plr/plr/actions Fixes postgres-plr#83
A message is received every time, that a login occurs to Travis (https://travis-ci.org/). ``` Please be aware travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information. ``` I am aware that plr uses Travis to "test a build". plr can also use another CI to also "test a build", for example, in the case that Travis actually, does stop serving open source projects. To see the "Github Actions" test result, one may navigate to the Github repository web page tab "Actions". Alternately, one may browse to the page: https://github.com/postgres-plr/plr/actions Fixes #83
Dave Cramer,
I am receiving this message everytime, that I login to Travis (https://travis-ci.org/).
I am aware that plr uses Travis to "test a build".
Perhaps, plr can also use another CI to also "test a build", for example, in the case that Travis actually, does stop serving open source projects.
One possible CI, is Github Actions.
The text was updated successfully, but these errors were encountered: