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

Patrick Hunt edited comment on ZOOKEEPER-1963 at 12/16/14 7:01 PM:
-------------------------------------------------------------------

I updated jenkins to enable this change:

1) updated all the trunk jbs to be jdk7 or later, in a couple cases I got rid 
of jobs that no longer made sense (ibm6 and jdk7 trunk jobs, now that trunk 
itself is jdk7 we don't need a duplicate job for that
2) the 3.5.x job is already just jdk7, so I think we're good there.

[~gkesavan] - can you look at these two jobs? I updated them to be jdk7 as the 
java version in the job, but the scripts that they are running (nightly) are 
pulling in jenkins tools latest, which I believe is jdk6 (verified via the 
console).
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/

Giri - should we continue to use the nightly scripts, or should we move off 
that and just put the content of the scripts into the job itself? (seems hadoop 
has done this?) Could you make these changes? I don't have access to the 
jenkins hosts so I'm not sure how all the environment vars should be set.


Otw I think we are good to go from a jenkins perspective.


was (Author: phunt):
I updated jenkins to enable this change:

1) updated all the trunk jbs to be jdk7 or later, in a couple cases I got rid 
of jobs that no longer made sense (ibm6 and jdk7 trunk jobs, now that trunk 
itself is jdk7 we don't need a duplicate job for that
2) the 3.5.x job is already just jdk7, so I think we're good there.

[~gkesavan] - can you look at these two jobs? I updated them to be jdk7 as the 
java version in the job, but the scripts that they are running (nightly) are 
pulling in jenkins tools latest, which I believe is jdk6 (verified via the 
console).

Giri - should we continue to use the nightly scripts, or should we move off 
that and just put the content of the scripts into the job itself? (seems hadoop 
has done this?) Could you make these changes? I don't have access to the 
jenkins hosts so I'm not sure how all the environment vars should be set.


Otw I think we are good to go from a jenkins perspective.

> Make JDK 7 the minimum requirement for Zookeeper
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-1963
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1963
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.5.0
>            Reporter: Edward Carter
>            Assignee: Hongchao Deng
>             Fix For: 3.5.1
>
>         Attachments: ZOOKEEPER-1963-v2.patch, ZOOKEEPER-1963.patch
>
>
> JDK 6 stopped receiving public updates in early 2013:
> http://www.oracle.com/technetwork/java/eol-135779.html
> I propose making JDK 7 the minimum for Zookeeper going forward.  One patch 
> that I've personally submitted already would have been a good fit for Java 
> 7's try-with-resources statement, and another pending patch fails to build on 
> versions of Java prior to 7 because a unit test in it uses 
> InetAddress.getLoopbackAddress(), which would be awkward to replace.  I'm 
> sure there are many other examples.



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

Reply via email to