bisq/.travis.yml

language: java
jdk: oraclejdk8
notifications:
  slack:
    on_success: change
    on_failure: always
    secure: EzlqWTBuhb3FCfApjUXaShWgsWOVDwMXI7ISMiVBkcl2VFISYs/lc/7Qjr7rdy4iqQOQXMcUPHdwMUp0diX+GxiSjLARjUpKIvNOPswZWBL+3Z1h28jyOwtHRviZbM1EU0BZROrr+ODyTNz2lf+L1iXTkpSvk50o5JAnAkumsPw=
added code to fix travis build 2017-07-06 22:38:23 +02:00			`language: java`
Polish .travis.yml formatting 2017-08-09 09:49:35 +02:00			`jdk: oraclejdk8`
Send Travis CI notifications to Slack (#898) Per instructions at https://docs.travis-ci.com/user/notifications#Configuring-slack-notifications 2017-08-09 09:49:44 +02:00			`notifications:`
			`slack:`
Reduce Travis CI Slack notification frequency Per https://docs.travis-ci.com/user/notifications/#Configuring-Slack-notifications the default setting for Travis Slack notifications is to send a message on every successful build. This commit changes this frequency, such that notifications are always sent when builds fail and only sent when builds succeed after a previous failure. 2018-03-15 08:44:19 +01:00			`on_success: change`
			`on_failure: always`
Update Travis CI Slack notification config The configuration was still set up to send notifications to #bisq-core. Now it will send them to #bisq-desktop. 2018-03-10 22:05:38 +01:00			`secure: EzlqWTBuhb3FCfApjUXaShWgsWOVDwMXI7ISMiVBkcl2VFISYs/lc/7Qjr7rdy4iqQOQXMcUPHdwMUp0diX+GxiSjLARjUpKIvNOPswZWBL+3Z1h28jyOwtHRviZbM1EU0BZROrr+ODyTNz2lf+L1iXTkpSvk50o5JAnAkumsPw=`