You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Herbert Duerr (JIRA)" <ji...@apache.org> on 2012/11/21 09:43:58 UTC
[jira] [Comment Edited] (INFRA-5490) Allow project specific
buildbot change_source property
[ https://issues.apache.org/jira/browse/INFRA-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501769#comment-13501769 ]
Herbert Duerr edited comment on INFRA-5490 at 11/21/12 8:43 AM:
----------------------------------------------------------------
Todays waterfall display blamelist of the svn-buildbots show http://ci.apache.org/changes/70731 to 70752, a collection of changes to tomcat, jackrabbit, cassandra, openejb, ooo, juddi, jmeter, creadur and also svn. This shows that svn land also has exactly the same problem.
was (Author: hdu):
In todays waterfall display's blamelist of the svn-buildbots the changes http://ci.apache.org/changes/70731 to 70752 are listed, which also contains changes to tomcat, jackrabbit, cassandra, openejb, ooo, juddi, jmeter and creadur. This shows that svn land also has exactly the same problem.
> Allow project specific buildbot change_source property
> ------------------------------------------------------
>
> Key: INFRA-5490
> URL: https://issues.apache.org/jira/browse/INFRA-5490
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist
> Reporter: Herbert Duerr
>
> There is a problem e.g. in the buildbot waterfall view that one can see a lot of changes to the whole repository that are outside of the product specific tree. This is confusing, especially as the got_revision property is set to the latest revision in the whole repository whereas the interesting part (e.g. to reproduce a build problem etc,) is the last change to that part of the repository that is used for building a project specific snapshot.
> In master.cfg there is a line c['change_source']=PBChangeSource() that seems to be responsible for doing it globally. My idea is to change our project specific buildbot config (openofficeorg.conf) so that the change source uses the PBChangeSource prefix option to filter out any changes outside of our tree. The question whether this can be fixed locally in a project specific way were answered by Gavin: this is currently not possible because of the way the hooks are set up.
> Please see the mail thread at http://mail-archives.apache.org/mod_mbox/www-builds/201211.mbox/%3C509244DA.5040301%40apache.org%3E for more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira