#740: Changecommentlink/revlink should take project/repo into consideration
--------------------+-------------------------------------------------------
Reporter:  marcusl  |        Owner:  marcusl
    Type:  defect   |       Status:  closed 
Priority:  major    |    Milestone:  0.8.0  
 Version:  master   |   Resolution:  fixed  
Keywords:  jinja    |  
--------------------+-------------------------------------------------------
Changes (by marcusl):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 (In [b466c5d4bccbe13ea2d6d94169d452526a3404bc]):

 WebStatus: Add support for project and repository in
 changecommentlink/revlink

  * These WebStatus args can now be callables, dicts or (as before) a
  single string/tuple
  * Added projectlink/repolink that adds URLs to repo/project main pages
  * Changed jinja change_macro to take a change as arg (cleaner code)
  * Changed some support classes in console to take a single
  build/sourcestamp arg instead of picking every necessary variable
  * The revlink/shortrev/changecomment filters now take a parameter, the
  repo or project to which the revision/comment belongs.
  * Shorten all revs to 40 chars in html rather than in python.
  * Add unit test for jinja link filters

 Comments belong to projects as they usually refer to ticket ids. So
 project == ticket db.

-- 
Ticket URL: <http://buildbot.net/trac/ticket/740#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits

Reply via email to