Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Failed builds

Naci,

It is possible to layer the build so that each step is smaller and easier to diagnose?

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/


Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx

12/07/2004 11:22 AM

Please respond to
wtp-dev
To
wtp-dev@xxxxxxxxxxx
cc
Subject
Re: [wtp-dev] Failed builds





Chuck,

We have been looking into ways of displaying as much information about the build as possible.  But there are a few challenges:
  • The ant build log xml is currently about 20MB for each build.
  • We tried to filter a reasonable set from this that is dispalyed in the XML Log tab using and xsl:
  • e.g: http://eteration.dyndns.org:8080/cruisecontrol/buildresults/wtp?tab=xmlLogFile&log=log20041207151748  (look at the end)
  • However, when abuild fails this log only have as much information about the failure as the ant task provides. Currently PDE tasks do not provide too much info.  They dump it into workspace .log (Can also be in the range of a few 10s of MB)
  • We typically look ath the XML Log from the reporting app, which you also have access, and learned a few patterns.  For example when it fails in generating build scripts complaining about not finding a plugin, the problem is one of:
    • plugin names have changed or inconsistent across plugin.xml/feature.xml
    • plugin versions have changed or inconsistent acrossplugin.xml/feature.xml
    • plugin is not registered in feature.xml
    • plugin is not in .map file
    • plugin is not in CVS So maybe we can include a simple "text" about the reason for a failure and have a build Troubleshooting FAQ.
      Any other ideas?

      At 04:55 PM 12/7/2004, you wrote:
    The current build notification doesn't give us any clue whats going wrong.  Unless the results are published to the wtp download site.  

    So we are forced to do local builds here to diagnose.

    Can we improve this?

    Thanks - Chuck

    Rational J2EE Tooling Team Lead
    IBM Software Lab - Research Triangle Park, NC
    Email:  cbridgha@xxxxxxxxxx
    Phone: 919-254-1848 (T/L: 444)



    Naci Dai <naci.dai@xxxxxxxxxxxxx>
    Sent by: wtp-dev-admin@xxxxxxxxxxx

    12/07/2004 04:47 AM

    Please respond to
    wtp-dev


    To

    wtp-dev@xxxxxxxxxxx

    cc
    Subject

    [wtp-dev] Failed builds




    Component owners,

    The reason for the build failures is the internet component renaming (i.e.
    plugin.xml ).  Please review your plugins.

                   Currently, wst.*.wsi.* plugins and probably some others have dependencies.
    Naci Dai,
    Managing Director

    eteration a.s.
    Inonu cad. Sumer sok. Zitas D1-15
    Kozyatagi, Istanbul 81090
    +90 (532) 573 7783 (cell)
    +90 (216) 361 5434 (phone)
    +90 (216) 361 2034 (fax)
    http://www.eteration.com
    mailto:nacidai@xxxxxxx
    mailto:naci@xxxxxxxxxxxxx



    _______________________________________________
    wtp-dev mailing list
    wtp-dev@xxxxxxxxxxx
    http://dev.eclipse.org/mailman/listinfo/wtp-dev

    Naci Dai,
    Managing Director

    eteration a.s.
    Inonu cad. Sumer sok. Zitas D1-15
    Kozyatagi, Istanbul 81090
    +90 (532) 573 7783 (cell)
    +90 (216) 361 5434 (phone)
    +90 (216) 361 2034 (fax)
    http://www.eteration.com
    mailto:nacidai@xxxxxxx
    mailto:naci@xxxxxxxxxxxxx

Back to the top