Migrate CI from Travis to GitHub Actions

Description

Travis is only free for open source when nobody is paid to work on the project

They are switching off the travis-ci.org June 15th

migrate

  • lucee

  • lucee-docs

to github actions

Attachments

1

Activity

Zac Spitzer 
3 July 2021 at 09:47
(edited)

Added reporting of test results via the testbox junit reporter

6.0 https://github.com/lucee/Lucee/pull/1371

5.3 https://github.com/lucee/Lucee/pull/1372

Zac Spitzer 
24 June 2021 at 13:00

I got the build trigger working, but it’s returning
Could not authorize build request for lucee/lucee-dockerfiles.

https://travis-ci.com/github/lucee/lucee-dockerfiles/requests

https://github.com/lucee/Lucee/runs/2904898911?check_suite_focus=true#step:16:10

Zac Spitzer 
23 June 2021 at 14:21

I have disabled concurrent builds with GHA, any new workflow run cancels the current workflow run, they can manually be triggered. At the moment this is global across all branches.

Once the s3 tests are improved we can make this per branch & (push or pull)

https://luceeserver.atlassian.net/browse/LDEV-3586

Zac Spitzer 
22 June 2021 at 13:25

5.3 now builds, passes and publishes to s3, 5.3.8.187-SNAPSHOT is out

I have also added build and test for most major extensions, which run labelled tests against the 6.0 branch using 6.0.0.95 snapshot

I have created a GitHub action to run Lucee to do this

https://github.com/zspitzer/lucee-script-engine-runner

For example,

here is the mysql GHA https://github.com/lucee/extension-jdbc-mysql/blob/master/.github/workflows/main.yml

here is the lucee docs GHA https://github.com/lucee/lucee-docs/blob/master/.github/workflows/main.yml

Fixed

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Priority

Created 7 June 2021 at 16:39
Updated 17 January 2022 at 18:33
Resolved 17 January 2022 at 18:33