Expertiza Continuous Integration - Revision history

Pmocampo: /* Benefits */

2013-04-17T19:55:00Z

Benefits

← Older revision		Revision as of 19:55, 17 April 2013
Line 8:		Line 8:
	* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].		* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].
	* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.		* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.
	[[Screen_Shot_2013-04-17_at_3.38.47_PM.png]]		[[File:Screen_Shot_2013-04-17_at_3.38.47_PM.png]]
	* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code		* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code
	* Allows Expertiza contributors to catch a build failure and roll back a commit.		* Allows Expertiza contributors to catch a build failure and roll back a commit.

Pmocampo: /* Benefits */

2013-04-17T19:54:45Z

Benefits

← Older revision		Revision as of 19:54, 17 April 2013
Line 8:		Line 8:
	* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].		* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].
	* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.		* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.
	[[~~http://wiki.expertiza.ncsu.edu/index.php/File:~~Screen_Shot_2013-04-17_at_3.38.47_PM.png]]		[[Screen_Shot_2013-04-17_at_3.38.47_PM.png]]
	* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code		* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code
	* Allows Expertiza contributors to catch a build failure and roll back a commit.		* Allows Expertiza contributors to catch a build failure and roll back a commit.

Pmocampo: /* Benefits */

2013-04-17T19:54:31Z

Benefits

← Older revision		Revision as of 19:54, 17 April 2013
Line 8:		Line 8:
	* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].		* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].
	* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.		* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.
			[[http://wiki.expertiza.ncsu.edu/index.php/File:Screen_Shot_2013-04-17_at_3.38.47_PM.png]]
	* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code		* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code
	* Allows Expertiza contributors to catch a build failure and roll back a commit.		* Allows Expertiza contributors to catch a build failure and roll back a commit.

	== Travis CI Build Configuration ==		== Travis CI Build Configuration ==
	The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza.		The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza.

Pmocampo: /* Travis CI Build Configuration */

2013-04-17T19:52:40Z

Travis CI Build Configuration

← Older revision		Revision as of 19:52, 17 April 2013
Line 12:		Line 12:
	== Travis CI Build Configuration ==		== Travis CI Build Configuration ==
	The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza.		The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza.
	Configuration changes are done by modifying the .travis.yml configuration file in the root of the repository and committing to the master and/or production branch.		Configuration changes are done by modifying the [[https://github.com/expertiza/expertiza/blob/master/.travis.yml .travis.yml]] configuration file in the root of the repository and committing to the master and/or production branch.

			* Additional branches can be included in build inspections by adding their names to the list under <i>branches</i>
			* Email notifications can be modified by including additional recipients or changing the [[http://about.travis-ci.org/docs/user/notifications/#Email-notifications frequency of notifications]]
			* To include rspec tests into the build inspection, we must add the following line of code in the <i>script</i> block
			<code>- "export DISPLAY=:99.0 && bundle exec rspec spec/"</code>
			* A specific cucumber formatter for Travis exists and it can be modified by editing the <i>travis</i> profile in [[https://github.com/expertiza/expertiza/blob/master/config/cucumber.yml cucumber.yml]]

Pmocampo at 19:44, 17 April 2013

2013-04-17T19:44:08Z

← Older revision		Revision as of 19:44, 17 April 2013
Line 2:		Line 2:
	You can see the current status of the project using the [[https://travis-ci.org/expertiza/expertiza Expertiza Travis Dashboard]]		You can see the current status of the project using the [[https://travis-ci.org/expertiza/expertiza Expertiza Travis Dashboard]]
	== Continuous Integration ==		== Continuous Integration ==
			Travis CI automatically builds the Expertiza project to make sure that no failures are introduced into the existing test suites after new code is committed.
			As of April 18th, 2013, the Travis CI configuration for Expertiza only builds and checks the cucumber test suite for failures on the master and production branches.
	== Benefits ==		== Benefits ==
			* Notifies the Expertiza Support List of test failures or changes in a build (previously failing tests passing after a build).
			* Build status indicator on the Expertiza [[https://github.com/expertiza/expertiza/blob/master/README.md Github readme]].
			* Pass/Fail indicator on pull requests and a link to a Travis summary specific to that build request.
			* Allows Expertiza contributors to determine whether a pull request is admissible before merging the code
			* Allows Expertiza contributors to catch a build failure and roll back a commit.
	== Travis CI Build Configuration ==		== Travis CI Build Configuration ==
			The [[http://about.travis-ci.org/docs/user/build-configuration/ configuration documentation]] for Travis is very extensive but there are some things to note in regards to Expertiza.
			Configuration changes are done by modifying the .travis.yml configuration file in the root of the repository and committing to the master and/or production branch.

Pmocampo: Created page with "The build status for the Expertiza project is tracked by the http://about.travis-ci.org/blog/ Travis Continuous Integration tool. You can see the current status of the projec..."

2013-04-17T19:31:57Z

Created page with "The build status for the Expertiza project is tracked by the http://about.travis-ci.org/blog/ Travis Continuous Integration tool. You can see the current status of the projec..."

New page

The build status for the Expertiza project is tracked by the [[http://about.travis-ci.org/blog/ Travis Continuous Integration]] tool.
You can see the current status of the project using the [[https://travis-ci.org/expertiza/expertiza Expertiza Travis Dashboard]]
== Continuous Integration ==
== Benefits ==
== Travis CI Build Configuration ==