also email notification is an option so we could include scons-dev on build notifications, but direct email notifications can't filter on branch. A web server receiving a webhook notification could how ever instead send emails to scons-dev with such a filter.
On Tue, Dec 5, 2017 at 10:47 PM, Daniel Moody <[email protected]> wrote: > The web server could filter what results would actually get posted > > On Tue, Dec 5, 2017 at 10:42 PM, Jonathon Reinhart < > [email protected]> wrote: > >> Is @SConsProject the Twitter account you're referring to? >> >> Does SCons really want to post Tweets when a build fails? I've never seen >> this before. To me, Twitter is used by open-source projects for things like >> announcing new releases, bugfixes, special events, etc. and not posting to >> the world when some Joe's feature branch failed to build. >> >> Cheers, >> Jonathon >> >> >> On Tue, Dec 5, 2017 at 10:34 PM, Daniel Moody <[email protected]> >> wrote: >> >>> Writing tweets to twitter will require private API keys, which implies a >>> private server is needed. >>> >>> Is there any private server scons has that could run a small web server >>> to receive the webhook notification from travis and write the tweet to >>> twitter? >>> >>> For the web server, I was thinking of using a python web server to >>> receive the notification and twython package to write the tweet. >>> >>> >>> >>> >>> >>> On Tue, Dec 5, 2017 at 1:22 PM, Bill Deegan <[email protected]> >>> wrote: >>> >>>> Great! >>>> That's all I can think of at the moment. >>>> >>>> Thanks, >>>> -Bill >>>> >>>> On Tue, Dec 5, 2017 at 10:19 AM, Daniel Moody <[email protected]> >>>> wrote: >>>> >>>>> https://docs.travis-ci.com/user/notifications/ >>>>> >>>>> IRC is covered. Webhook seems open ended to setup for any site so >>>>> seems possible for Twitter messages with some setup. >>>>> >>>>> Any other notification types we are interested in? >>>>> >>>>> I'll take a look and submit a PR. >>>>> >>>>> On Dec 5, 2017 12:55 PM, "Bill Deegan" <[email protected]> >>>>> wrote: >>>>> >>>>>> Should be enabled now. >>>>>> Just merged one of your pull requests.. >>>>>> I'll keep an eye on it. >>>>>> Can we get the results to post on twitter? and/or IRC? >>>>>> >>>>>> On Sun, Dec 3, 2017 at 9:08 PM, Bill Deegan < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Yes. I'll get to it in the next week or so. >>>>>>> We do have buildbot doing similar at : buildbot.scons.org >>>>>>> >>>>>>> -Bill >>>>>>> >>>>>>> On Sun, Dec 3, 2017 at 2:02 PM, Daniel Moody <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> In this pull request: >>>>>>>> https://github.com/SCons/scons/pull/17 >>>>>>>> >>>>>>>> SCons got a Travis CI script added to the repo. Travis CI is a free >>>>>>>> service for running each new commit to github against a testing script >>>>>>>> (.travis.yml). This takes place on Travis's servers and builds are >>>>>>>> recorded >>>>>>>> and accessible via links. Below is an example: >>>>>>>> >>>>>>>> https://travis-ci.org/dmoody256/scons/builds/311007377 >>>>>>>> >>>>>>>> The also add a nifty little check next to the commit if the commit >>>>>>>> passed the test: >>>>>>>> [image: Inline image 2] >>>>>>>> >>>>>>>> I was wondering if someone who has access could enable the service >>>>>>>> for the SCons project? >>>>>>>> >>>>>>>> Below are some instructions on how to do it from the Github web >>>>>>>> interface >>>>>>>> >>>>>>>> In order to utilize the script you need to add Travis CI as a >>>>>>>> service, below are some basic instructions from Github: >>>>>>>> >>>>>>>> 1. Navigate to the repository you want to connect to Travis. >>>>>>>> 2. In the right sidebar, click Settings. >>>>>>>> 3. In the left sidebar, click Webhooks & Services. >>>>>>>> 4. In the Services box, click Add service. >>>>>>>> 5. Select "Travis CI". >>>>>>>> 6. For public projects leave the configuration fields empty >>>>>>>> 7. Click Add service. >>>>>>>> 8. Go to https://travis-ci.org/profile >>>>>>>> 9. Turn Automatic CI on for the project you want to run builds >>>>>>>> for >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Scons-dev mailing list >>>>>>>> [email protected] >>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Scons-dev mailing list >>>>>> [email protected] >>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Scons-dev mailing list >>>>> [email protected] >>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Scons-dev mailing list >>>> [email protected] >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>> >>>> >>> >>> _______________________________________________ >>> Scons-dev mailing list >>> [email protected] >>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>> >>> >> >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
