You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2020/11/04 05:14:00 UTC

[jira] [Resolved] (BIGTOP-3409) Move bigtop website off from CMS: staging

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

Kengo Seki resolved BIGTOP-3409.
--------------------------------
    Resolution: Fixed

Our website has already been migrated to the staging mechanism using .asf.yaml. Thanks a lot [~oflebbe]!

> Move bigtop website off from CMS: staging
> -----------------------------------------
>
>                 Key: BIGTOP-3409
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3409
>             Project: Bigtop
>          Issue Type: Task
>          Components: website
>    Affects Versions: 1.4.0
>            Reporter: Olaf Flebbe
>            Assignee: Olaf Flebbe
>            Priority: Major
>             Fix For: 1.5.0
>
>
> First step:
> Try a staging website 
> I created a job for pushing the website to the asf-staging branch at
> https://ci-builds.apache.org/job/BigTop/job/site/
> According to https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features we need to create {{.asf.yaml}} file for uploading to final destination.
> The content should be
> {code}
> staging:
>   profile: ~
>   whoami:  asf-staging
>  {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)