Add Slack notifications to Travis CI

[nacin]

Using ​https://travis-ci.org/aaronjorbin/develop.wordpress for now.

The reformatting was the result of the travis CLI client, which was used to encrypt the credentials.

[nacin]

In 30963:

Add Slack notifications to Travis CI config. fixes #30755.

[jorbin]

In 31352:

Update Travis-ci Slack notification token

see #30755

[jorbin]

In 31353:

Travis hates tabs.

Related [31352]

see #30755

[netweb]

I setup my own testing instance of Slack and this worked for me:

For the Travis CI Slack channel #core get the Travis CI token from the correct service integration:

• Slack Integrations e.g. https://wordpress.slack.com/services
• Token e.g. AbCdEfGh12JkLm34PqRs56Tu

In a terminal prompt of a local clone of ​https://github.com/aaronjorbin/develop.wordpress running the following will automatically update the existing value in .travis.yml

• travis encrypt "wordpress:AbCdEfGh12JkLm34PqRs56Tu" --add notifications.slack

Note: wordpress in the above command is the Slack instance/organisation name and not the channel name.

[ocean90]

Any news on this? :heart:

[netweb]

I've a new repo, ​WordPress & Travis CI Playground for testing the new Travis CI Docker/Ubuntu 14.04 provisioning.

To be performed by a WordPress Slack Administrator:

1. Open ​https://wordpress.slack.com/messages/core/

2. Click #core dropdown and click Add a service interaction...

3. You should now have be in a new tab with a URL similar to https://wordpress.slack.com/services/new?channel_id=A02BCDEFG

4. Scroll down to Travis CI and click View

5. In the Post to Channel dropdown select #core and click Add Travis CI interaction

6. You should now be at https://wordpress.slack.com/services/1234567890?added=1

7. Copy and paste the code from the Encrypting your credentials section e.g. travis encrypt "wordpress:AbCdEfGh12JkLm34PqRs56Tu" --add notifications.slack to Jorbin via Slack DM

To be performed by Jorbin in a local checkout of https://github.com/aaronjorbin/develop.wordpress

1. In a terminal prompt go to the above checkout

2. sudo gem install travis

3. Copy and paste the code sent by Slack DM e.g travis encrypt "wordpress:AbCdEfGh12JkLm34PqRs56Tu" --add notifications.slack

4. Accept the prompt Detected repository as aaronjorbin/develop.wordpress, is this correct? |yes| by pressing enter

5. Commit the change to .travis.yml e.g. ​https://github.com/ntwb/wordpress-travis/commit/87d4bf71dc6e06c3881ae408ff19a77c31f69549

6. The result ​https://travis-ci.org/ntwb/wordpress-travis/builds/72964977

[ocean90]

Would be nice to have. ¯\_(ツ)_/¯

[jorbin]

In 34555:

Add Travis Notifications to the #core channel on Slack

This is hopefully the final attempt at adding notifications to the #core channel on Slack. By default, Travis spams the channel. In order to cut that down a bit, notifications are set as follows:

• On Failure: Always (If the tests fail, the world needs to know)
• On Success: Change (this means that the first green run after a red run aka, the world is happy again)
• On Start: Never (Travis runs every time there is a commit. No need for a notification)

Props Netweb, samuelsidler
Fixes #30755

[jorbin]

this didn't work :( Going to try something else.

[jorbin]

In 34567:

Move travis secure token under rooms

Travis lint says it is dropping the secure token, hence not actually pinging slack. According to ​http://docs.travis-ci.com/user/notifications/#Slack-notifications what we encrypt *should* be usable under rooms. Will this work? I don't know, but YOLO.

Fixes #30755

[johnbillion]

In 40277:

Build/Test tools: Update .travis.yml to include latest improvements from trunk.

• Explicitly use PHPUnit 5.7 for the PHP 7 builds on Travis.
• On Travis CI install and use the node version which is specified in package.json.
• Add some more debugging to Travis and bring the format of the Xdebug fix inline with branches.
• Get Travis builds working on HHVM again.
• In addition, brings the Slack notification settings up to date.

Merges [40255], [40257], [40258], [40259], [40269], and [40271] to the 4.3 branch.

See #35105, #40100, #30755

[ocean90]

In 40282:

Build/Test Tools: Update .travis.yml to include latest improvements from trunk.

• Explicitly use PHPUnit 5.7 for the PHP 7 builds on Travis.
• On Travis CI install and use the node version which is specified in package.json.
• Add some more debugging to Travis and bring the format of the Xdebug fix inline with branches.
• Get Travis builds working on HHVM again.
• In addition, brings the Slack notification settings up to date and allows Travis CI to cache the node_modules directory.

Merge of [40255], [40257-40259], [40269], and [40271] to the 4.2 branch.

See #35105, #40100, #30755, #36291, #36490.

[ocean90]

In 40286:

Build/Test Tools: Update .travis.yml to include latest improvements from trunk.

• On Travis CI install and use node version 0.10.48 to ensure correct node-sass builds.
• Explicitly use PHPUnit 5.7 for the PHP 7 builds on Travis.
• Add some more debugging to Travis and bring the format of the Xdebug fix inline with branches.
• Get Travis builds working on HHVM again.
• In addition, brings the Slack notification settings up to date and allows Travis CI to cache the node_modules directory.

Merge of [40255], [40257],[40259], [40269], and [40271] to the 4.1 branch.

See #35105, #40100, #30755, #36291, #36490.

[ocean90]

In 40288:

Build/Test Tools: Update .travis.yml to include latest improvements from trunk.

• On Travis CI install and use node version 0.10.48 to ensure correct node-sass builds.
• Explicitly use PHPUnit 5.7 for the PHP 7 builds on Travis.
• Add some more debugging to Travis and bring the format of the Xdebug fix inline with branches.
• Get Travis builds working on HHVM again.
• In addition, brings the Slack notification settings up to date and allows Travis CI to cache the node_modules directory.

Merge of [40255], [40257],[40259], [40269], and [40271] to the 4.0 branch.

See #35105, #40100, #30755, #36291, #36490.