About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:testing:continuous_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
development:testing:continuous_integration [2021/02/17 18:14] – [Mink / Selenium] demiankatzdevelopment:testing:continuous_integration [2021/05/06 11:30] (current) – [Travis CI] demiankatz
Line 18: Line 18:
   * [[http://vufind.org/jenkins|VuFind's Jenkins Server]]   * [[http://vufind.org/jenkins|VuFind's Jenkins Server]]
  
-==== Travis CI ====+==== GitHub Actions / Travis CI ====
  
-[[http://travis-ci.org|Travis CI]] is a hosted continuous integration service with strong GitHub integration. While VuFind uses Jenkins for its primary CI functionality due to richer reporting capabilities, it also uses Travis as a first line of defense for detecting test breaks and style problems in pull requests.+[[https://github.com/features/actions|GitHub Actions]] and [[http://travis-ci.org|Travis CI]] are hosted continuous integration services with strong GitHub integration. While VuFind uses Jenkins for its primary CI functionality due to richer reporting capabilities, it also uses GitHub Actions or Travis as a first line of defense for detecting test breaks and style problems in pull requests. (VuFind used Travis for many years, but switched to GitHub Actions when Travis reduced its support for open source development).
 ==== Phing ==== ==== Phing ====
  
Line 151: Line 151:
    
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
development/testing/continuous_integration.1613585695.txt.gz · Last modified: 2021/02/17 18:14 by demiankatz