infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-16737) CMS changes not triggering a staging build
Date Mon, 09 Jul 2018 19:37:00 GMT

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

Mark Thomas resolved INFRA-16737.
---------------------------------
    Resolution: Fixed

This will have been the same issue as the tomcat-build - ci.apache.org not resolving correctly
on svn-master.a.o

> CMS changes not triggering a staging build
> ------------------------------------------
>
>                 Key: INFRA-16737
>                 URL: https://issues.apache.org/jira/browse/INFRA-16737
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS
>            Reporter: Mark Thomas
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>
> This morning I made this change:
> http://svn.apache.org/r1835400
> It did not trigger a staging build here:
> https://ci.apache.org/builders/www-site-staging
> I've looked but can't figure out where that builder and the associated scheduler is defined
so I am unable to debug this further.
> I note that the slave went off-line over the weekend. That may or may not be relevant.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message