[jboss-jira] [JBoss JIRA] (DROOLS-662) Autopublish drools-website, optaplanner-website and jbpm-website through travis

Geoffrey De Smet (JIRA) issues at jboss.org
Wed Jan 6 08:02:00 EST 2016


    [ https://issues.jboss.org/browse/DROOLS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145405#comment-13145405 ] 

Geoffrey De Smet commented on DROOLS-662:
-----------------------------------------

Current state: the travis jobs exist, but they don't publish yet. We need them to publish too.

> Autopublish drools-website, optaplanner-website and jbpm-website through travis
> -------------------------------------------------------------------------------
>
>                 Key: DROOLS-662
>                 URL: https://issues.jboss.org/browse/DROOLS-662
>             Project: Drools
>          Issue Type: Task
>            Reporter: Geoffrey De Smet
>            Assignee: Michael Biarnes Kiefer
>
> The jboss-tools guys already auto publish their awestruct website. xcoulon on irc #awestruct told me how they do this at Devoxx. 
> Travis is like Jenkins, but works really well for ruby stuff (such as awestruct websites). It can publish our websites automatically if we push a commit. Here's how to set it up:
> - Add a .travis.yml file, look at this one for inspiration: https://github.com/jbosstools/jbosstools-website/blob/master/.travis.yml
> - Get a secret token to be able to publish a website on jboss.org filemanagement server. Then encrypt that secret token with Travis's public key (so only Travis can decrypt it). Write the encrypted secret token in the travis.yml file. Remove all knowledge of the actual secret token, so it can't leak.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list