You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Konstantin Kolinko (Commented) (JIRA)" <ge...@gump.apache.org> on 2012/02/19 23:28:37 UTC

[jira] [Commented] (GUMP-147) Complain if a project does not provide all the outputs it states

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

Konstantin Kolinko commented on GUMP-147:
-----------------------------------------

I think it is already implemented.
The "lucene-java" project recently had the issue of missing outputs and that caused the project to be marked as failed. So this check is working.

Notification email contains [1] (search for "lucene-java"):
[[[
The current state of this project is 'Failed', with reason 'Missing Build Outputs'.
]]]

The issue in lucene-java was [2] that their build configuration was changed and jars were produced in a different place. The built was successful (and link to build output was green), but the whole project was in the failed state.  So this check actually works.

I do not know whether the check iterates over all outputs, as lucene-java project has only one jar.

For reference:
[1] http://marc.info/?l=gump&m=132938480323353&w=2
[2] http://svn.apache.org/viewvc?view=revision&revision=1290917
                
> Complain if a project does not provide all the outputs it states
> ----------------------------------------------------------------
>
>                 Key: GUMP-147
>                 URL: https://issues.apache.org/jira/browse/GUMP-147
>             Project: Gump
>          Issue Type: New Feature
>          Components: Python-based Gump
>    Affects Versions: Gump3-alpha-7
>            Reporter: Leo Simons
>             Fix For: Gump3-alpha-7
>
>
> We should have a post-processing plugin (maybe one-per-output-type) that looks for successfully built projects, then goes and peeks if each and every of the outputs it specifies now actually exists (probably os.exists() and sometimes os.isfile() and os.isdir() if appropriate). If not, the plugin should mark the failure on the output.
> The logreporter should be modified to include this information with each project (this is probably a METADATA FAILURE), eg loop over all outputs for all projects and check_failure on each of them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org