www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbert Duerr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5490) Allow project specific buildbot change_source property
Date Mon, 19 Nov 2012 07:46:58 GMT

    [ https://issues.apache.org/jira/browse/INFRA-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500075#comment-13500075

Herbert Duerr commented on INFRA-5490:

The most confusing thing about the global change_source is that the revision reported in "got_revision"
is very often outside of our project. We rename our build-output using that revision as part
of the result-name and if the revision is off this is confusing.

The unrelated change messages in the waterfall display are another confusing aspect of this

For the buildbot status mails there is the problem that build.getSourceStamp() usually returns
an unrelated revision or changed_by and getResponsibleUsers() returns a way too extensive
list, so they both are less valuable info than they would be otherwise.

And with a change_source matching to our project one could also think of running schedulers
such as the SingleBranchScheduler for critical branches. But maybe we could workaround the
general problem by using a ChangeFilter from buildbot.changes.filter.

Anyway, all these are more annoyances than critical problems, but since every project that
uses the functionality runs into them, this multiplies with the number of projects. Just tracking+evaluating
these problems here and collecting ideas for workarounds until the root cause will be solved
is a good idea I think.
> 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

View raw message