You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/03/03 05:39:18 UTC

[jira] [Updated] (INFRA-7738) Need openjpa docs buildbot enhanced to support new 2.3.x stream

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

Chris Lambertus updated INFRA-7738:
-----------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

This is 2+ years old. Is this still an ongoing problem?

> Need openjpa docs buildbot enhanced to support new 2.3.x stream
> ---------------------------------------------------------------
>
>                 Key: INFRA-7738
>                 URL: https://issues.apache.org/jira/browse/INFRA-7738
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>            Reporter: Kevin Sutter
>              Labels: openjpa
>
> We have a new service stream (branch) for OpenJPA called 2.3.x.  We need to perform the doc builds like we have for the other streams.  The team member (Albert) that originally set this up with Infra is no longer on the team, so I'm trying to figure out the process.
> It looks like I have access to the openjpa.conf file.  So, should I go ahead and make the necessary update?  Here's all that I was planning to do (adding '2.3.x'):
> ojpa_branches = ['trunk' , '2.3.x' , '2.2.1.x' , '2.2.x' , '2.1.x' , '2.0.x' , '1.3.x' , '1.2.x' , '1.0.x']
> The thing I'm not sure about is how to go about testing this change.  I like to do the test-then-commit process...  :-)  Thanks for any assistance.
> I was also having some issues with IRC and the #openjpa-bot channel last night, but I'll keep experimenting with that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)