www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12735) [Buildbot] Setup a buildbot job to build the Apache Flex Site
Date Mon, 10 Oct 2016 08:11:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561614#comment-15561614

Christofer Dutz commented on INFRA-12735:

Well gitpubsub takes care of the syncing of HTML content (Am I correct?) 
Currently I have the Website content in an orphan branch "maven-site" and I setup the maven-site-plugin
to produce the content for the site into the "asf-site" branch of the samt git repo (This
is working nicely on my machine as I have setup the GIT credentials).
On Jenkins the pushing of the update "asf-site" repo fails because of missing credentials.
I was told that on buildbot these credentials are setup so I should be able to do a simple
"git push".

So what I'm hoping to do is setup a buildbot job to chekout the "maven-site" branch and do
a "mvn site-deploy".

> [Buildbot] Setup a buildbot job to build the Apache Flex Site
> -------------------------------------------------------------
>                 Key: INFRA-12735
>                 URL: https://issues.apache.org/jira/browse/INFRA-12735
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot
>            Reporter: Christofer Dutz
>            Assignee: Gavin
> Hi,
> I just finished a (hopefully) working version of the Maven Site generation for the Apache
Flex project. I would now like to setup (or have setup) a build job, that:
> 1. Checks out: https://git-wip-us.apache.org/repos/asf/flex-site.git
> 2. Checksout the "maven-site" branch
> 3. Runs a Maven "mvn clean site-deploy"
> That should update the "asf-site" branch with new content. For now this asf-site should
NOT be used by gitpubsub. We are currently working on migrating content from the Apache CMS
to this new site generation and want so switch some time in the future when all are happy
with the content.

This message was sent by Atlassian JIRA

View raw message