Re: [fossil-users] Email notification on ticket creation or modification

[Stephan Beal]

On Thu, Jul 31, 2014 at 10:36 PM, Ross Berteig  wrote:

> This leaves out the -limit option, but alludes to it with "LIMIT is
> the...". That should probably read:
> The same issue exists in the help text for the /timeline.rss webpage.


Thanks - the change has been made locally and will be pushed soon.


-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Ross Berteig]

I hadn't noticed the rss command before. Looks useful if I ever want to 
consume an RSS feed manually. I do notice that it has a small issue in 
its documentation, which reads in part (rewrapped because I give up on 
forcing thunderbird to let me have a long line today):


> -type|y FLAG
>may be: all (default), ci (show checkins only), t (show tickets
>only), w (show wiki only). LIMIT is the number of items to show.

This leaves out the -limit option, but alludes to it with "LIMIT is 
the...". That should probably read:


> -type|y FLAG
>may be: all (default), ci (show checkins only), t (show tickets
>only), w (show wiki only).
>
> -limit|n LIMIT
>the maximum number of items to show.

The same issue exists in the help text for the /timeline.rss webpage.

--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Thomas Bilk]

This can be achieved even easier as I discovered just recently. There is
a rss command option for fossil that generates rss files. I use this
bash script with a cron to generate all rss files to a public directory:

#!/usr/bin/env bash
for fos in `ls /var/repos/*.fossil`; do
  rss=`echo $fos | sed 's/\/var\/repos\/\(.*\)\.fossil/\1/'`;
  /usr/local/bin/fossil rss -R $fos --url https://repos.com/$rss >
/var/public/rss/$rss.rss;
done

Am 31.07.2014 18:40, schrieb Stephan Beal:
> On Thu, Jul 31, 2014 at 5:49 PM, James Bremner  > wrote:
> 
> On 28/07/2014 2:24 PM, Ross Berteig wrote:
> 
> all the RSS-based services I could find could not do authentication
> 
> 
> How about a cron job which uses wget::
> 
> wget http://me:mypassword@myrepo/timeline.rss -O thefeed.rss
> 
> and maybe then feed that feed file to your non-auth-capable reader?
> 
> -- 
> - stephan beal
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Stephan Beal]

On Thu, Jul 31, 2014 at 5:49 PM, James Bremner 
wrote:

> On 28/07/2014 2:24 PM, Ross Berteig wrote:
>
>> all the RSS-based services I could find could not do authentication
>>
>
How about a cron job which uses wget::

wget http://me:mypassword@myrepo/timeline.rss -O thefeed.rss

and maybe then feed that feed file to your non-auth-capable reader?

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[James Bremner]

On 28/07/2014 2:24 PM, Ross Berteig wrote:

all the RSS-based services I could find could not do authentication


Did you look at "RSS Live links" 
https://chrome.google.com/webstore/detail/foxish-live-rss/jpgagcapnkccceppgljfpoadahaopjdb?hl=en


This is a chrome plugin, so as long as you log in to the fossil repo 
using chrome, the RSS reader can access the fossil RSS feed without any 
more authentication steps.  In practice, it just works.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Ross Berteig]

On 7/28/2014 12:02 PM, Andreas Kupries wrote:

On Mon, Jul 28, 2014 at 11:24 AM, Ross Berteig  wrote:

We had a similar need here for a project that unfortunately could not have a
public-facing server,


There is also FX, the Fossil eXtension project, see
 http://core.tcl.tk/akupries/fx/index


That looks quite interesting. When I can harvest some spare cycles to 
polish local infrastructure again, I'll see if I can make it work for 
me. Thanks!


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Andreas Kupries]

On Mon, Jul 28, 2014 at 11:24 AM, Ross Berteig  wrote:
> We had a similar need here for a project that unfortunately could not have a
> public-facing server,

There is also FX, the Fossil eXtension project, see
http://core.tcl.tk/akupries/fx/index

Regarding notification services see the examples at

http://core.tcl.tk/akupries/fx/doc/trunk/embedded/www/doc/files/fx_example_tkt_local.html

http://core.tcl.tk/akupries/fx/doc/trunk/embedded/www/doc/files/fx_example_tkt_remote_dev.html

http://core.tcl.tk/akupries/fx/doc/trunk/embedded/www/doc/files/fx_example_tkt_remote_root.html

> The big downside for me is that it requires configuration per user and per
> repository.

The FX configuration (routes) is per-repository.
It can be per-user if a specific user should get all notifications.
FX can pull email addresses out of the tickets, if properly configured
(dynamic routing).

> It isn't easy, for instance, to get emailed when any ticket on
> any of my repositories changes. It also doesn't have a lot of configuration
> for what information to drop in the email, and the resulting emails little
> more than hints to go read the actual ticket.

An example of FX-generated mail is below.
The header and footer elements (See inserted marker (*)) are configurable.

FX currently serves the repositories on http://core.tcl.tk


===
(*) Automated mail by fx, on behalf of akupr...@shaw.ca

Ticket Change [943045d3926100c2a84d8f285e17175c7387b265]
  [Ticket [a6b610f7b77f6c8856cb5c931f4b63f3ac64cc8e|a6b610f7b7] bug in
itk_initialize status still Open with 5 other changes]
  By  anonymous
  For Itk - the [incr Tk] extension
  On  2014-07-04T13:01:05.140
  Details 
http://core.tcl.tk/itk/tinfo?name=943045d3926100c2a84d8f285e17175c7387b265
  Ticket  
http://core.tcl.tk/itk/tktview/a6b610f7b77f6c8856cb5c931f4b63f3ac64cc8e

Changed Fields
  icomment:   The attached program illustrates the bug. In Itk 3.3 (change the
  package require from itk to Itk), output is:

  Before itk_initialize: Initial value  myvar changed to
Initial value
  After itk_initialize: Initial value  After object
creation: Initial
  value

  With itk 4.0.0, output is:

  Before itk_initialize: Initial value  myvar changed to   After
  itk_initialize:   After object creation:
  login:  anonymous
  priority:   Immediate
  resolution: Open

(*) 
(*) EuroTcl 2014, Jul 12-13, Munich/DE:  http://www.eurotcl.tcl3d.org/
(*) Tcl 2014 Con, Nov 10-14, Portland-OR/US:
http://www.tcl.tk/community/tcl2014/
(*) Send your abstracts to: tclconfere...@googlegroups.com, by Sep 8
(*) Registration is open.
(*) 
===

-- 
Andreas Kupries
Senior Tcl Developer
Code to Cloud: Smarter, Safer, Faster™
F: 778.786.1133
andre...@activestate.com
http://www.activestate.com
Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

EuroTcl'2014, July 12-13, Munich, GER -- http://www.eurotcl.tcl3d.org/
21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
http://www.tcl.tk/community/tcl2014/
Send mail to tclconfere...@googlegroups.com, by Sep 8
Registration is open.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Ross Berteig]

On 7/28/2014 5:43 AM, Raghavendra Chary B wrote:

...
There are multiple ways to set up email notification on ticket creation
or modification.

I think simplest of them is using IFTTT approach, but i spent lot of
time before i could find it. Hence I strongly feel this should be
documented in official wiki, given that this such a common requirement

In this approach we use IFTTT service to connect rss feed of Fossil scm
to Gmail channel.


We had a similar need here for a project that unfortunately could not 
have a public-facing server, all the RSS-based services I could find 
could not do authentication, and I didn't want to involve 3rd party 
services in any case. I eventually found rss2email [1] which allowed me 
to set up a similar connection between ticket changes and internal email 
recipients. It happily runs on a Windows PC from a periodic Task Manager 
event and sends the expected emails when it sees new RSS events.


[1]: http://www.allthingsrss.com/rss2email/

The big downside for me is that it requires configuration per user and 
per repository. It isn't easy, for instance, to get emailed when any 
ticket on any of my repositories changes. It also doesn't have a lot of 
configuration for what information to drop in the email, and the 
resulting emails little more than hints to go read the actual ticket.


IFTTT may merit a second look for my projects where I do have a public 
facing server, assuming it can handle the needed authentication.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users