Skip to content

[Bioc-devel] RSS package feeds not updated

6 messages · Dan Tenenbaum, Stephanie M. Gogarten, Kevin Rue-Albrecht

Original
Dan Tenenbaum
# 
----- Original Message -----
Thanks for the report. I've had a look. I've changed the system so it doesn't try to be smart about not updating feeds for packages that do not have issues. 
This means all package feeds will be updated daily, whether there is an issue or not. Not sure if this will be annoying to feed users; we can revisit it if it's an issue. 

Thanks,
Dan
Stephanie M. Gogarten
#
On 12/2/14 8:17 AM, Dan Tenenbaum wrote:
I have to say, I liked the old system better.  I have a feed for each of 
my packages in the bottom of my email program, so I could see at a 
glance if there was a problem with one of the packages (new message in 
the feed).  Failure messages are a lot more noticeable if they're not 
buried among lots of "nothing to see here" messages.

Stephanie
Dan Tenenbaum
# 
----- Original Message -----
OK, I will re-re-visit this and see what can be done.
Dan
Kevin Rue-Albrecht
# 
Hi Stephanie,

I am using rss2email (
http://www.allthingsrss.com/rss2email/getting-started-with-rss2email/), a
script that I installed to track my package feed, and that is run by my
Windows task scheduler every day, to send me the RSS news in an email (not
as an RSS feed per se)

Now, just like you I get the good and the bad news following the nightly
build. But since I get them as emails, I just set up a filter to mark good
emails as read and I move them directly in a separate email folder (you
could also delete them).
This way, only the bad news show up as unread messages which catch my
attention.

Took a bit of time to set up, but then it ran seamlessly ever since.
No extra work for Dan, and developers who might want to log the successful
builds can do so.

Hope that helps.
Kevin


On 3 December 2014 at 00:19, Stephanie M. Gogarten <
sdmorris at u.washington.edu> wrote:

            

      
      
      
    

        

      
      
    

        

      
      
    

        

      
      
    

        

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Dan Tenenbaum
    

    

      
      #
    

  


  

      
----- Original Message -----

            

      
      
      
    

        
(incidentally written by the late Aaron Swartz)

            

      
      
      
    

        
I don't consider it 'extra work' to restore a feature that was there and used to work. I do think 'no news is good news' is a good feature (I think it's also good to be notified when the build has returned to normal, so the system should only notify when build status changes) but it needs to work properly, so I'll try and figure out why it wasn't working and restore it. Then I'll let you know so you can remove your filter if you want.

Dan

            

      
      
      
    

        

      
      
    

  
  


  


      

    

    

      
      

        


  

        

      Dan Tenenbaum
    

    

      
      #
    

  


  

      
----- Original Message -----

            

      
      
      
    

        
OK, I have overhauled the logic that decides when to update the rss feeds. So we should be back to "no news is good news" (it may take a cycle or two to actually get there). The logic is a bit different than it was before. I think before you would only get an "everything is fine" notification if the rss file did not exist. But now you get notifications every time the build status changes, but not when it was the same as yesterday. So if your package has an error, you'll get one notification, and when the problem is fixed you will get another notification saying everything is ok with the package. This is in line with continuous integration systems such as Jenkins which notify you on error and notify you again when the build has returned to normal.  

Thanks to all for the feedback, it's helpful to know whether and how people are using this feature. Let me know if you discover further issues.

Dan