www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7738) Need openjpa docs buildbot enhanced to support new 2.3.x stream
Date Fri, 16 May 2014 19:40:34 GMT

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

Gavin commented on INFRA-7738:
------------------------------

Feel free to update the openjpa.conf file (update your wc first)

Note that to get the buildbot config to pass I commented out a chunk of code in your file
that needs to be investigated further.

> 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
>          Components: Buildbot
>            Reporter: Kevin Sutter
>            Assignee: Gavin
>              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.2#6252)

Mime
View raw message