You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Ian Dickinson (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 15:01:42 UTC
[jira] [Created] (INFRA-4148) Publish from staging to public with
Apache CMS not working
Publish from staging to public with Apache CMS not working
----------------------------------------------------------
Key: INFRA-4148
URL: https://issues.apache.org/jira/browse/INFRA-4148
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: CMS
Reporter: Ian Dickinson
I've updating our staging area on the CMS, and twice now tried to publish staging to external. Neither commit seems to have been noticed by buildbot, so the public web site is still not in sync with staging.
The relevant commits are:
Author: ijd
Date: Wed Nov 23 11:43:04 2011
New Revision: 799158
Log:
Pushing JENA-167
Author: ijd
Date: Wed Nov 23 12:38:01 2011
New Revision: 799160
Log:
Trying again to push staging to public to resolve JENA-167
This is a recent change: Yesterday, publishing from staging was working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4148) Publish from staging to public with
Apache CMS not working
Posted by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-4148.
-------------------------------
Seems to be working properly again.
> Publish from staging to public with Apache CMS not working
> ----------------------------------------------------------
>
> Key: INFRA-4148
> URL: https://issues.apache.org/jira/browse/INFRA-4148
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
>
> I've updating our staging area on the CMS, and twice now tried to publish staging to external. Neither commit seems to have been noticed by buildbot, so the public web site is still not in sync with staging.
> The relevant commits are:
> Author: ijd
> Date: Wed Nov 23 11:43:04 2011
> New Revision: 799158
> Log:
> Pushing JENA-167
> Author: ijd
> Date: Wed Nov 23 12:38:01 2011
> New Revision: 799160
> Log:
> Trying again to push staging to public to resolve JENA-167
> This is a recent change: Yesterday, publishing from staging was working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (INFRA-4148) Publish from staging to public with
Apache CMS not working
Posted by "Ian Dickinson (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Dickinson resolved INFRA-4148.
----------------------------------
Resolution: Invalid
Published web site is building OK now
> Publish from staging to public with Apache CMS not working
> ----------------------------------------------------------
>
> Key: INFRA-4148
> URL: https://issues.apache.org/jira/browse/INFRA-4148
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
>
> I've updating our staging area on the CMS, and twice now tried to publish staging to external. Neither commit seems to have been noticed by buildbot, so the public web site is still not in sync with staging.
> The relevant commits are:
> Author: ijd
> Date: Wed Nov 23 11:43:04 2011
> New Revision: 799158
> Log:
> Pushing JENA-167
> Author: ijd
> Date: Wed Nov 23 12:38:01 2011
> New Revision: 799160
> Log:
> Trying again to push staging to public to resolve JENA-167
> This is a recent change: Yesterday, publishing from staging was working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4148) Publish from staging to public with
Apache CMS not working
Posted by "Ian Dickinson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157111#comment-13157111 ]
Ian Dickinson commented on INFRA-4148:
--------------------------------------
I'm still experiencing this behaviour - have performed a commit to production, no response as yet from buildbot:
Author: ijd
Date: Fri Nov 25 11:45:53 2011
New Revision: 799243
Log:
Another attempt to publish staging to external
Modified:
websites/production/jena/ (props changed)
websites/production/jena/content/jena/getting_involved/index.html
> Publish from staging to public with Apache CMS not working
> ----------------------------------------------------------
>
> Key: INFRA-4148
> URL: https://issues.apache.org/jira/browse/INFRA-4148
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
>
> I've updating our staging area on the CMS, and twice now tried to publish staging to external. Neither commit seems to have been noticed by buildbot, so the public web site is still not in sync with staging.
> The relevant commits are:
> Author: ijd
> Date: Wed Nov 23 11:43:04 2011
> New Revision: 799158
> Log:
> Pushing JENA-167
> Author: ijd
> Date: Wed Nov 23 12:38:01 2011
> New Revision: 799160
> Log:
> Trying again to push staging to public to resolve JENA-167
> This is a recent change: Yesterday, publishing from staging was working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira