Merge pull request #816 from DomT4/httpsbot

various: update CI links.

Library/Homebrew/test/test_integration_cmds.rb

@@ -773,7 +773,7 @@ class IntegrationCommandTests < Homebrew::TestCase
     end
 
     assert_match "Testing URLs require `--bottle`!",
-      cmd_fail("pull", "http://bot.brew.sh/job/Homebrew\%20Testing/1028/")
+      cmd_fail("pull", "https://bot.brew.sh/job/Homebrew\%20Testing/1028/")
     assert_match "Current branch is new-branch",
       cmd_fail("pull", "1")
     assert_match "No changed formulae found to bump",

share/doc/homebrew/Brew-Test-Bot-For-Core-Contributors.md

@@ -3,11 +3,11 @@ If a build has run and passed on `brew test-bot` then it can be used to quickly
 
 There are two types of Jenkins jobs you will interact with:
 
-## [Homebrew Pull Requests](http://bot.brew.sh/job/Homebrew%20Core%20Pull%20Requests/)
+## [Homebrew Pull Requests](https://bot.brew.sh/job/Homebrew%20Core%20Pull%20Requests/)
 This job automatically builds any pull requests submitted to Homebrew/homebrew-core. On success or failure it updates the pull request status (see more details on the [main Brew Test Bot wiki page](Brew-Test-Bot.md)). On a successful build it automatically uploads bottles.
 
-## [Homebrew Testing](http://bot.brew.sh/job/Homebrew%20Testing/)
-This job is manually triggered to run [`brew test-bot`](https://github.com/Homebrew/brew/blob/master/Library/Homebrew/cmd/test-bot.rb) with user-specified parameters. On a successful build it automatically uploads bottles.
+## [Homebrew Testing](https://bot.brew.sh/job/Homebrew%20Testing/)
+This job is manually triggered to run [`brew test-bot`](https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/test-bot.rb) with user-specified parameters. On a successful build it automatically uploads bottles.
 
 You can manually start this job with parameters to run [`brew test-bot`](https://github.com/Homebrew/brew/blob/master/Library/Homebrew/cmd/test-bot.rb) with the same parameters. It's often useful to pass a pull request URL, a commit URL, a commit SHA-1 and/or formula names to have `brew-test-bot` test them, report the results and produce bottles.
 
@@ -21,5 +21,5 @@ To pull and bottle a pull request with `brew pull`:
 To bottle a test build :
 
 1. Ensure the job has already completed successfully.
-2. Run `brew pull --bottle http://bot.brew.sh/job/Homebrew%20Testing/1234/` where `http://bot.brew.sh/job/Homebrew%20Testing/1234/` is the testing build URL in Jenkins.
+2. Run `brew pull --bottle https://bot.brew.sh/job/Homebrew%20Testing/1234/` where `https://bot.brew.sh/job/Homebrew%20Testing/1234/` is the testing build URL in Jenkins.
 3. Run `git push` to push the commits.

share/doc/homebrew/Brew-Test-Bot.md

@@ -3,7 +3,7 @@
 by [our Kickstarter in 2013](https://www.kickstarter.com/projects/homebrew/brew-test-bot).
 
 It comprises of four Mac Minis running in a data centre in England which host
-[a Jenkins instance at http://bot.brew.sh](http://bot.brew.sh) and run the
+[a Jenkins instance at https://bot.brew.sh](https://bot.brew.sh) and run the
 [`brew test-bot.rb`](https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/test-bot.rb)
 Ruby script to perform automated testing of commits to the master branch, pull
 requests and custom builds requested by maintainers.
@@ -55,7 +55,7 @@ A failed build looks like this:
 ---
 
 You can click the test results link
-(e.g. `brew-test-bot.Homebrew/homebrew/pull/22183-3c17deb.install embree`) to
+(e.g. `brew-test-bot.el_capitan.install openssl`) to
 view the failed test output:
 
 ![Failed Test](images/brew-test-bot-failed-test.png)

share/doc/homebrew/New-Maintainer-Checklist.md

@@ -38,8 +38,8 @@ If they accept, follow a few steps to get them set up:
 
 - [x] Invite them to the [**@Homebrew/maintainers** team](https://github.com/orgs/Homebrew/teams/maintainers) to give them write access to all repositories (but don't make them owners yet)
 - [x] Ask them to sign up for a [Bintray](https://bintray.com) account and invite them to [Bintray's Homebrew organisation](https://bintray.com/homebrew/organization/edit/members) as a member (but not administrator access yet) so they can publish new bottles
-- [x] Add them to the [Jenkins' GitHub Authorization Settings admin user names](http://bot.brew.sh/configureSecurity/) so they can adjust settings and restart jobs
-- [x] Add them to the [Jenkins' GitHub Pull Request Builder admin list](http://bot.brew.sh/configure) to enable `@BrewTestBot test this please` for them
+- [x] Add them to the [Jenkins' GitHub Authorization Settings admin user names](https://bot.brew.sh/configureSecurity/) so they can adjust settings and restart jobs
+- [x] Add them to the [Jenkins' GitHub Pull Request Builder admin list](https://bot.brew.sh/configure) to enable `@BrewTestBot test this please` for them
 - [x] Invite them to the [`homebrew-dev` private maintainers mailing list](https://groups.google.com/forum/#!managemembers/homebrew-dev/invite)
 - [x] Invite them to the [`machomebrew` private maintainers Slack](https://machomebrew.slack.com/admin/invites)
 - [x] Add them to [Homebrew's README](https://github.com/Homebrew/brew/edit/master/README.md)