giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-377) Jenkins not happy
Date Wed, 31 Oct 2012 16:29:12 GMT

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

Nitay Joffe commented on GIRAPH-377:
------------------------------------

Ok. What is the info under reporting test results? Presumably there is some option that specifies
where Hudson is looking for it's test results. It is probably set to something like <top-level>/target/foo
when it should be <top-level>/giraph/target/foo. Well really we should include the stuff
in giraph-formats-contrib/target/foo as well.

Also we probably want to cleanup the builds, namely remove giraph-formats-contrib (should
be built by everything now), and update the builds to match the profiles we currently have?
                
> Jenkins not happy
> -----------------
>
>                 Key: GIRAPH-377
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-377
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Nitay Joffe
>            Assignee: Nitay Joffe
>            Priority: Minor
>
> https://builds.apache.org/job/Giraph-trunk-Commit/
> The butler is not happy since the top-level-pom change.
> Code is building fine, but some final reporting step is making it register as failed.
> In other words, I forgot to tip the butler.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message