Differences

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

--- development:testing:continuous_integration [2016/12/21 16:40] – [Install Testing Tools] demiankatz
+++ development:testing:continuous_integration [2021/05/06 11:30] (current) – [Travis CI] demiankatz
@@ Line 16: / Line 16: @@
   * [[http://jenkins-ci.org/|Jenkins Home Page]]
   * [[http://toptopic.wordpress.com/2009/02/26/php-and-hudson/|PHP + Hudson Article]]
-  * [[http://jenkins-php.org/|Template for Jenkins Jobs for PHP Projects]]
+  * [[http://vufind.org/jenkins|VuFind's Jenkins Server]]
-  * [[http://vufind.org/hudson|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 ====
@@ Line 35: / Line 34: @@
 ==== Mink / Selenium ====
-We use Mink (a browser automation abstraction library) with Selenium (a browser automation library) for building automated browser-based tests.  This is useful for integration testing, although complex tests can sometimes take a very long time to execute. See [[development:testing:unit_tests#browser_automation_tests_with_mink|this wiki page]] for more details.
+We use Mink (a browser automation abstraction library) with either Chrome in headless mode or Selenium (a browser automation library) for building automated browser-based tests.  This is useful for integration testing, although complex tests can sometimes take a very long time to execute. See [[development:testing:unit_tests#browser_automation_tests_with_mink|this wiki page]] for more details.
 Resources:
@@ Line 136: / Line 135: @@
   * Build triggers:
     * [x] Build when a change is pushed to GitHub (note that you need to configure the hooks: https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin#GitHubPlugin-TriggerabuildwhenachangeispushedtoGitHub)
+  * Execute shell [this must run BEFORE Phing]:
+    * composer install
   * Build / Invoke Phing targets:
+    * Phing version: Be sure to set up a custom Phing installation in Manage Jenkins / Configure System. This should have a PHP Command setting of "$WORKSPACE/vendor/bin/phing" to run the version of Phing installed by Composer.
     * Targets: main
     * If you need to customize the build file, click Advanced... and enter your custom build file name in "Phing Build File"
@@ Line 149: / Line 151: @@
 ---- struct data ----
+properties.Page Owner :
 ----