3 ms·
Encapsulates this era as the battleground of silo'd "as a service" vs "can be done" For example I can have jenkins email build fails to slack in, oh, probably
by VLM 10y ago
Encapsulates this era as the battleground of silo'd "as a service" vs "can be done"
For example I can have jenkins email build fails to slack in, oh, probably less than two minutes, I've done it before. From memory I make a custom email addrs in slack and tell slack which channel to feed it into, and then add that address to my jenkins that already sent buildSpam.
In IRC I could do it... google implies there's a ZenIRCBot project on github and probably many others. Probably there are bots and tools that google didn't immediately find.
Its not rocket surgery to use fetchmail and some kind of Perl IRC library to simply POP everything out of a mailbox into a directory /tmp/wtf and probably about 3 lines of perl to read all the files in /tmp/wtf, connect to irc on some channel, output what it found, and if successful delete the emails from /tmp/wtf. Then put fetchmail and the 3 line perl script into cron and away we go.
Looks like Zapier is kinda in between "I could do it" and "AAS"
- jasonjayr 10y agoJenkins has a IRC plugin, already in the stock distribution. Jenkins bot idles in channel, and logs all sorts of failures or successes, or whatever. With the irc server + channels setup, this also takes less than 2 minutes.
- anonymoushn 10y agoYou can have Jenkins send IRC messages using a single invocation of netcat. This should take less than two minutes.