You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Dionysios Logothetis (JIRA)" <ji...@apache.org> on 2018/05/17 06:33:00 UTC
[jira] [Commented] (GIRAPH-1179) Apache Hudson CI integration tries
to build with a JRE instead of JDK
[ https://issues.apache.org/jira/browse/GIRAPH-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478613#comment-16478613 ]
Dionysios Logothetis commented on GIRAPH-1179:
----------------------------------------------
This is now fixed: https://builds.apache.org/view/E-G/view/Giraph/job/Giraph-trunk-Commit/
> Apache Hudson CI integration tries to build with a JRE instead of JDK
> ---------------------------------------------------------------------
>
> Key: GIRAPH-1179
> URL: https://issues.apache.org/jira/browse/GIRAPH-1179
> Project: Giraph
> Issue Type: Bug
> Components: build
> Affects Versions: 1.3.0
> Reporter: Adam Kennedy
> Priority: Major
>
> The continuous integration testing is broken for Giraph. The hooks all seem to be in place, but the Jenkins jobs appear to be set up incorrectly and try to use a JRE to build Giraph instead of a JDK.
> I assume this has been broken for a long time, since the Jenkins repo describes Giraph as Apache Incubating Giraph. To get the project back to a place where we can release regularly again, we should fix this.
> Do we have any idea who would need to fix this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)