Gump
  1. Gump
  2. GUMP-147

Complain if a project does not provide all the outputs it states

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Gump3-alpha-7
    • Fix Version/s: None
    • Component/s: Python-based Gump
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Konstantin Kolinko added a comment -

        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

        Show
        Konstantin Kolinko added a comment - 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

          People

          • Assignee:
            Unassigned
            Reporter:
            Leo Simons
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development