| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | # Brew Test Bot
 | 
					
						
							| 
									
										
										
										
											2017-01-04 16:16:00 -06:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | `brew test-bot` is the name for the automated review and testing system funded | 
					
						
							| 
									
										
										
										
											2015-01-04 04:27:16 +01:00
										 |  |  | by [our Kickstarter in 2013](https://www.kickstarter.com/projects/homebrew/brew-test-bot). | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | It comprises of four Mac Minis running in a data centre in England which host | 
					
						
							| 
									
										
										
										
											2016-08-26 01:40:10 +01:00
										 |  |  | [a Jenkins instance at https://bot.brew.sh](https://bot.brew.sh) and run the | 
					
						
							| 
									
										
										
										
											2016-08-17 16:23:02 -07:00
										 |  |  | [`brew test-bot.rb`](https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/test-bot.rb) | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | Ruby script to perform automated testing of commits to the master branch, pull | 
					
						
							|  |  |  | requests and custom builds requested by maintainers. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ## Pull Requests
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | The bot automatically builds pull requests and updates their status depending | 
					
						
							|  |  |  | on the result of the job. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | For example, a job which has been queued but not yet started will have a | 
					
						
							|  |  |  | section in the pull-request that looks like this: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | A failed build looks like this: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | A passed build looks like this: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | On failed or passed builds you can click the "Details" link to view the result | 
					
						
							|  |  |  | in Jenkins. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | When you click this you'll see the results. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | A passed build looks like this: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | A failed build looks like this: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | You can click the test results link | 
					
						
							| 
									
										
										
										
											2016-08-26 01:40:10 +01:00
										 |  |  | (e.g. `brew-test-bot.el_capitan.install openssl`) to | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | view the failed test output: | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-20 06:45:38 +01:00
										 |  |  |  | 
					
						
							| 
									
										
										
										
											2014-10-26 14:54:36 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | --- |