You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2015/01/04 21:55:34 UTC

[jira] [Created] (INFRA-8979) Update to cms.conf not picked up

Sebb created INFRA-8979:
---------------------------

             Summary: Update to cms.conf not picked up
                 Key: INFRA-8979
                 URL: https://issues.apache.org/jira/browse/INFRA-8979
             Project: Infrastructure
          Issue Type: Bug
          Components: Buildbot
            Reporter: Sebb


See BUILDS-43 and INFRA-8866

I updated cms.conf to change where the commons buildbot sends its notifications. The (only) commons entry is currently:

cms_staging_build(project='commons', buildtype='maven', commitlist='notifications@commons.apache.org', branch='commons/cms-site')

However, I just did an update and the message was sent to the commits list instead.

Here is a snippet of the commit message:

===========
Subject: svn commit: r935046 - in /websites/staging/commons/trunk/content: ./
 downloads/ gsoc/ gsoc/2010/ releases/
Date: Sun, 04 Jan 2015 20:33:39 -0000
To: commits@commons.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20...@hades.apache.org>

Author: buildbot
Date: Sun Jan  4 20:33:38 2015
New Revision: 935046

Log:
Staging update by buildbot for commons

Modified:
===========

It looks like the cms.conf file I editted has not been picked up by the Buildbot instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)