www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf (äñ§€¥£¢) (JIRA) <j...@apache.org>
Subject [jira] [Updated] (INFRA-5490) buildbot: Narrow down blamelist and revision numbers to those of the ^/${project} tree
Date Wed, 28 Nov 2012 06:16:58 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Shahaf (äñ§€¥£¢) updated INFRA-5490:
-------------------------------------------

    Summary: buildbot: Narrow down blamelist and revision numbers to those of the ^/${project}
tree  (was: Allow project specific buildbot change_source property)

Tweaking the issue title to describe the problem, rather than the solution. (This isn't implying
an opinion on the suggested solution(s))
                
> buildbot: Narrow down blamelist and revision numbers to those of the ^/${project} tree
> --------------------------------------------------------------------------------------
>
>                 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

Mime
View raw message