WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 19 months ago

Last modified 7 weeks ago

#30755 closed enhancement (fixed)

Add Slack notifications to Travis CI

Reported by: nacin Owned by: nacin
Milestone: WordPress.org Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

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.

Change History (20)

#1 @nacin
2 years ago

  • Component changed from General to Build/Test Tools
  • Type changed from defect (bug) to enhancement

#2 @nacin
2 years ago

  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from new to closed

In 30963:

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

This ticket was mentioned in Slack in #core by netweb. View the logs.


2 years ago

#4 @jorbin
2 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

#5 @jorbin
2 years ago

In 31352:

Update Travis-ci Slack notification token

see #30755

#6 @jorbin
2 years ago

In 31353:

Travis hates tabs.

Related [31352]

see #30755

#7 @netweb
2 years ago

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.

#8 @ocean90
2 years ago

  • Milestone changed from 4.1 to WordPress.org

This ticket was mentioned in Slack in #core by ocean90. View the logs.


23 months ago

#10 @ocean90
22 months ago

Any news on this? :heart:

#11 @netweb
21 months ago

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/
  1. Click #core dropdown and click Add a service interaction...
  1. You should now have be in a new tab with a URL similar to https://wordpress.slack.com/services/new?channel_id=A02BCDEFG
  1. Scroll down to Travis CI and click View
  1. In the Post to Channel dropdown select #core and click Add Travis CI interaction
  1. You should now be at https://wordpress.slack.com/services/1234567890?added=1
  1. 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
  1. sudo gem install travis
  1. Copy and paste the code sent by Slack DM e.g travis encrypt "wordpress:AbCdEfGh12JkLm34PqRs56Tu" --add notifications.slack
  1. Accept the prompt Detected repository as aaronjorbin/develop.wordpress, is this correct? |yes| by pressing enter
  1. Commit the change to .travis.yml e.g. https://github.com/ntwb/wordpress-travis/commit/87d4bf71dc6e06c3881ae408ff19a77c31f69549
  1. The result https://travis-ci.org/ntwb/wordpress-travis/builds/72964977 https://cldup.com/jirXr_wi7m.png

This ticket was mentioned in Slack in #core-restapi by netweb. View the logs.


21 months ago

#13 @ocean90
19 months ago

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

#14 @jorbin
19 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed

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

#15 @jorbin
19 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

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

#16 @jorbin
19 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed

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

#17 @johnbillion
7 weeks ago

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

#18 @ocean90
7 weeks ago

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.

#19 @ocean90
7 weeks ago

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.

#20 @ocean90
7 weeks ago

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.

Note: See TracTickets for help on using tickets.