You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2015/01/31 13:51:35 UTC
[jira] [Closed] (BUILDS-48) Changes to buildbot configuration not
effective
[ https://issues.apache.org/jira/browse/BUILDS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed BUILDS-48.
-----------------------
Resolution: Fixed
Everything looks good now. Likley was affected by other projects having an incorrect config and blocking the update.
> Changes to buildbot configuration not effective
> -----------------------------------------------
>
> Key: BUILDS-48
> URL: https://issues.apache.org/jira/browse/BUILDS-48
> Project: Infra Build Platform
> Issue Type: Bug
> Components: Buildbot
> Reporter: Michael Dürig
> Assignee: Gavin
>
> About a day ago I did changes to the Jackrabbit buildbot configuration \[1] changing the command line to
> {code}
> "mvn", "clean", "install" , "-PintegrationTesting", "-Dns-fixtures=", "-DBUILD_NAME=buildbot-linux-oak-trunk"
> {code}
> Looking at the output of a recent build \[2] I still see the old command line from before my change:
> {code}
> mvn clean install -PintegrationTesting -Dns-fixtures=
> {code}
> Is it normal for the changes to need more than a day to take effect? Or did I miss a step in the process?
> \[1] https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/jackrabbit.conf
> \[2] http://ci.apache.org/builders/oak-trunk/builds/921/steps/compile/logs/stdio
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)