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

["#asfinfra Bot (JIRA)" <ji...@apache.org>]

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

#asfinfra Bot closed INFRA-7738.
--------------------------------
    Resolution: Won't Fix  (was: Unresolved)

Hi, 

This issue has been in state 'Pending Closed' for at least 5 days, and was previously waiting for at least 3 days for waiting for updates. 
  
We are closing this issue automatically, feel free to reopen the issue or open a new one should you need further help.


-- 
Cheers,
Apache Infrastructure Team

> 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)