[jira] [Assigned] (GUMP-148) Clean up entire codebase and add documentation
[ https://issues.apache.org/jira/browse/GUMP-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leo Simons reassigned GUMP-148: --- Assignee: (was: Leo Simons) Clean up entire codebase and add documentation -- Key: GUMP-148 URL: https://issues.apache.org/jira/browse/GUMP-148 Project: Gump Issue Type: Task Components: Python-based Gump Affects Versions: Gump3-alpha-7 Reporter: Leo Simons Fix For: Gump3-alpha-7 It'd be nice if the gump codebase could get some time to stabilize after this milestone. To be confident we don't get too much bit rot, its important to take a big stroll through the codebase, adding javadocs, rolling up unrolled algorithms, getting rid of code duplication, standardizing method names, etc etc. Let's use this issue for code review reporting. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] Assigned: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ] Leo Simons reassigned GUMP-146: --- Assign To: Leo Simons (was: Adam Jack) Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ] Leo Simons resolved GUMP-146: - Resolution: Fixed Implemented in SVN revision 333089. Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (GUMP-82) Keep only the jars from the last successful build
[ http://issues.apache.org/jira/browse/GUMP-82?page=all ] Leo Simons resolved GUMP-82: Resolution: Fixed Assign To: Leo Simons Implemented as part of SVN revision 333089. Keep only the jars from the last successful build - Key: GUMP-82 URL: http://issues.apache.org/jira/browse/GUMP-82 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump2-2.4 Reporter: Stefano Mazzocchi Assignee: Leo Simons Fix For: Gump3-alpha-5 Currently, gump saves all jars and then a cron job removes them after a week. I think it's a waste of space since what we really need is just the latest one that was built. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (GUMP-105) design a way to build against the last-successful-dependency-build
[ http://issues.apache.org/jira/browse/GUMP-105?page=all ] Leo Simons resolved GUMP-105: - Resolution: Fixed Implemented fully after SVN revision 333089. Still a very experimental feature but it seems to be holding up in basic testing. Good enough for now. design a way to build against the last-successful-dependency-build -- Key: GUMP-105 URL: http://issues.apache.org/jira/browse/GUMP-105 Project: Gump Type: Task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 The first algorithm to get right is GUMP-104, where we bail out of building at all if a dependency dies. The next step to tackle is to build against the last version of the dependency that /was/ built successfully. This requires gump to become time-aware beyond a single build run, saving off previous successes into a repository and knowing about them. It requires a significant extension of the model where, for example class BuildFailureRecoveryPlugin(AbstractPlugin): visit_project(p): if p.state = FAILED: successful_p = historyutil.lookup_last_successful_build(p) modelutil.replace(p, succesful_p) p.failed_project = p p.state == RECOVERED stages are inserted to keep most of the plugins blissfully unaware of the intelligence going on. If we get this right that'll be where the staged plugin model will really start to shine, as the graph theory people can design smart new algorithms (As long as they're compatible with the basic topsort we're doing in some way), and the build tool people can just, well, build stuff. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=all ] Leo Simons updated GUMP-29: --- Fix Version: Gump3-alpha-6 (was: Gump3-alpha-5) Description: New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. was: New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. Version: Gump3-alpha-6 (was: Gump3-alpha-5) (was: Gump3-alpha-4) Environment: bump. new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=comments#action_12357532 ] Leo Simons commented on GUMP-29: Grr. This issue keeps lying around mostly because our doc editing / publishing process isn't good enough. We have a variety of tools at the ASF and all are either painful to use or buggy or have a variety of other limitations (like being a wiki). Bumping this up a version. new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-91) testcases for gump.engine.loader.Loader
[ http://issues.apache.org/jira/browse/GUMP-91?page=all ] Leo Simons closed GUMP-91: -- Resolution: Won't Fix I don't think it'll happen. testcases for gump.engine.loader.Loader --- Key: GUMP-91 URL: http://issues.apache.org/jira/browse/GUMP-91 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-93) testcases for gump.engine.objectifier.Objectifier
[ http://issues.apache.org/jira/browse/GUMP-93?page=all ] Leo Simons closed GUMP-93: -- Resolution: Won't Fix I don't think it'll happen. testcases for gump.engine.objectifier.Objectifier - Key: GUMP-93 URL: http://issues.apache.org/jira/browse/GUMP-93 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-92) testcases for gump.engine.normalizer.Normalizer
[ http://issues.apache.org/jira/browse/GUMP-92?page=all ] Leo Simons closed GUMP-92: -- Resolution: Won't Fix I don't think it'll happen. testcases for gump.engine.normalizer.Normalizer --- Key: GUMP-92 URL: http://issues.apache.org/jira/browse/GUMP-92 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-31) cvs dirs should be cleaned every month (or so)
[ http://issues.apache.org/jira/browse/GUMP-31?page=all ] Leo Simons updated GUMP-31: --- Fix Version: Gump3-alpha-6 (was: Gump3-alpha-7) Description: cvs hackery corrupts cvs trees. We should shield gump against this: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=672035 was: cvs hackery corrupts cvs trees. We should shield gump against this: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=672035 Version: Gump3-alpha-6 (was: Gump3-alpha-7) Environment: Assign To: Leo Simons cvs dirs should be cleaned every month (or so) -- Key: GUMP-31 URL: http://issues.apache.org/jira/browse/GUMP-31 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-6 cvs hackery corrupts cvs trees. We should shield gump against this: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=672035 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-31) cvs dirs should be cleaned every month (or so)
[ http://issues.apache.org/jira/browse/GUMP-31?page=all ] Leo Simons closed GUMP-31: -- Resolution: Fixed cvs dirs should be cleaned every month (or so) -- Key: GUMP-31 URL: http://issues.apache.org/jira/browse/GUMP-31 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-6 cvs hackery corrupts cvs trees. We should shield gump against this: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=672035 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-31) cvs dirs should be cleaned every month (or so)
[ http://issues.apache.org/jira/browse/GUMP-31?page=comments#action_12357537 ] Leo Simons commented on GUMP-31: Detection of changes can now be done by introspecting three properties set on the model: module.update_log module.update_exit_status module.update_type these are set by updater.py. The new sync.py has support for cleaning out directories, and the updater now uses that support. By passing the '--do-repo-clean' commandline option, all the repositories and modules for the projects that are being built are cleaned out and a new checkout is done. Setting the cronjob to add that option every now and then should suffice. cvs dirs should be cleaned every month (or so) -- Key: GUMP-31 URL: http://issues.apache.org/jira/browse/GUMP-31 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-6 cvs hackery corrupts cvs trees. We should shield gump against this: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=672035 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-157) Gump builds fail on Windows when projects include maven / tags
[ http://issues.apache.org/jira/browse/GUMP-157?page=comments#action_12356952 ] Leo Simons commented on GUMP-157: - Hi bill! Patch looks fine. As an ASF committer you should have write access to the gump codebase. Feel free to commit the patch yourself! Gump builds fail on Windows when projects include maven / tags Key: GUMP-157 URL: http://issues.apache.org/jira/browse/GUMP-157 Project: Gump Type: Bug Components: Python-based Gump Environment: Windows Reporter: Bill Barker Priority: Minor Attachments: maven.diff Currently, any Gump project with a maven / tag fails when running on a Windows platform. The underlying reason is that Maven (or at least v1.0.2) is too brain-dead to parse 'project.properties' other than by using j.u.Properties. As a result, the standard Windows File.separator of \ is considered to be a quote character, and is dropped from the jarpath of the dependancies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-147) Complain if a project does not provide all the outputs it states
Complain if a project does not provide all the outputs it states Key: GUMP-147 URL: http://issues.apache.org/jira/browse/GUMP-147 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 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 contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-148) Clean up entire codebase and add documentation
Clean up entire codebase and add documentation -- Key: GUMP-148 URL: http://issues.apache.org/jira/browse/GUMP-148 Project: Gump Type: Task Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Assigned to: Leo Simons Fix For: Gump3-alpha-6 It'd be nice if the gump codebase could get some time to stabilize after this milestone. To be confident we don't get too much bit rot, its important to take a big stroll through the codebase, adding javadocs, rolling up unrolled algorithms, getting rid of code duplication, standardizing method names, etc etc. Let's use this issue for code review reporting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-84) Packages defined in built modules are shown as green but they should be blue
[ http://issues.apache.org/jira/browse/GUMP-84?page=all ] Leo Simons closed GUMP-84: -- Resolution: Fixed Assign To: Leo Simons Fixed in revision 215990. Packages defined in built modules are shown as green but they should be blue Key: GUMP-84 URL: http://issues.apache.org/jira/browse/GUMP-84 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2-2.4 Reporter: Stefano Mazzocchi Assignee: Leo Simons Fix For: Gump3-alpha-5 packages are colored blue when they are not built by gump. Modules are allowed to have their own internal packages, wrapping some of the jars they contain in their repository. Gump should treat those the same as packages, but currently it does not and it misleads the statistics. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-36) Generate source diff report on build failure
[ http://issues.apache.org/jira/browse/GUMP-36?page=all ] Leo Simons updated GUMP-36: --- Fix Version: Gump3-alpha-6 (was: Gump3-alpha-5) Version: Gump3-alpha-6 (was: Gump2-2.4) Generate source diff report on build failure Key: GUMP-36 URL: http://issues.apache.org/jira/browse/GUMP-36 Project: Gump Type: New Feature Components: Dynagump Versions: Gump3-alpha-6 Reporter: Vincent Massol Fix For: Gump3-alpha-6 When a project fails to build, generate a report containing the following information: - CVS source diff on the project itself between the last success build and the current checked out sources - CVS source diffs on the project first level dependencies between the last success build and the current checked out sources - CVS source diff on Gump project files between the last success build and the current checked out sources. The idea is to help devlopers of the failed project in indentifying the reason of the failure. See http://blogs.codehaus.org/people/vmassol/archives/000644_diffing_continuous_build_results.html for more details. Thanks -Vincent -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-94) testcases for gump.engine.verifier.Verifier
[ http://issues.apache.org/jira/browse/GUMP-94?page=all ] Leo Simons closed GUMP-94: -- Resolution: Fixed Assign To: Leo Simons fixed in revision 216018 testcases for gump.engine.verifier.Verifier --- Key: GUMP-94 URL: http://issues.apache.org/jira/browse/GUMP-94 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ] Leo Simons reassigned GUMP-146: --- Assign To: Adam Jack Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-139) module project fails, it needs to be module project module
[ http://issues.apache.org/jira/browse/GUMP-139?page=all ] Leo Simons closed GUMP-139: --- Fix Version: Gump3-alpha-4 Resolution: Fixed module project fails, it needs to be module project module --- Key: GUMP-139 URL: http://issues.apache.org/jira/browse/GUMP-139 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-4 This might be considered support for 0.4 metadata. Normalizer:_get_list_merged_by_name returns cloned nodes --- and those nodes are w/o a parent. As such Normalizer:_find_module_containing_node fails when looking for the parent module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-137) A missing href (e.g. typo of file/URL not found) causes Gump to crash
[ http://issues.apache.org/jira/browse/GUMP-137?page=all ] Leo Simons closed GUMP-137: --- Fix Version: Gump3-alpha-4 Resolution: Fixed Assign To: Leo Simons It seems this was fixed a while back but I forgot to close the issue. A missing href (e.g. typo of file/URL not found) causes Gump to crash - Key: GUMP-137 URL: http://issues.apache.org/jira/browse/GUMP-137 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-4 A missing href (e.g. typo of file/URL not found) causes Gump to crash: Find module starting with DOM Element: module at 0x11c4120 Found! 16:44:13 WARNINGDropping module '' because of href resolution error! 16:44:13 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 21 4, in run (domtree, dropped_nodes) = self.workspace_loader.get_workspace_tree(self.wor kspace) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\loader.py, line 186, in get_workspace_tree _resolve_hrefs_in_children(ws, dropped_nodes, [], self.get_as_stream, self.h andle_error) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\loader.py, line 67, in _resolve_hrefs_in_children _resolve_hrefs_in_children(child, dropped_nodes, found_hrefs[:], download_fu nc, error_func) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\loader.py, line 61, in _resolve_hrefs_in_children _resolve_href(child, dropped_nodes, found_hrefs, download_func, error_func) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\loader.py, line 89, in _resolve_href error_func(href, node, dropped_nodes) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\loader.py, line 225, in handle_error _do_drop(project, dropped_nodes) File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\modeller.py, line 47 , in _do_drop node_to_remove_element_from = to_remove.parentNode AttributeError: 'NoneType' object has no attribute 'parentNode' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=all ] Leo Simons closed GUMP-138: --- Fix Version: Gump3-alpha-4 (was: Gump3-alpha-3) Resolution: Fixed Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-4 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-131) Build fails with build timed out
[ http://issues.apache.org/jira/browse/GUMP-131?page=all ] Leo Simons updated GUMP-131: Fix Version: Gump2-2.4 Description: While compiling a make on a very large (compile time 2 hours or more) C/C++ project, the build is reported as failed with the reason build timed out. The build log shows that the build has been stopped half way through the build. There is no obvious evidence that the build has hung in any way. If an attempt is made to cd to the build directory and type make, the build completes normally. There is no obvious timeout setting that can change this - if there is can the build timed out message be replaced with a message that says build timed out - increase option ZZZ and try again. was: While compiling a make on a very large (compile time 2 hours or more) C/C++ project, the build is reported as failed with the reason build timed out. The build log shows that the build has been stopped half way through the build. There is no obvious evidence that the build has hung in any way. If an attempt is made to cd to the build directory and type make, the build completes normally. There is no obvious timeout setting that can change this - if there is can the build timed out message be replaced with a message that says build timed out - increase option ZZZ and try again. Version: Gump2-2.4 Assign To: Adam Jack Build fails with build timed out -- Key: GUMP-131 URL: http://issues.apache.org/jira/browse/GUMP-131 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2-2.4 Environment: Solaris v2.8, Gump SVN trunk (Python 2.4.1) Reporter: Graham Leggett Assignee: Adam Jack Fix For: Gump2-2.4 While compiling a make on a very large (compile time 2 hours or more) C/C++ project, the build is reported as failed with the reason build timed out. The build log shows that the build has been stopped half way through the build. There is no obvious evidence that the build has hung in any way. If an attempt is made to cd to the build directory and type make, the build completes normally. There is no obvious timeout setting that can change this - if there is can the build timed out message be replaced with a message that says build timed out - increase option ZZZ and try again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-132) http://vmgump.apache.org/ needs a landing page
[ http://issues.apache.org/jira/browse/GUMP-132?page=all ] Leo Simons closed GUMP-132: --- Resolution: Fixed Assign To: Adam Jack http://vmgump.apache.org/ needs a landing page -- Key: GUMP-132 URL: http://issues.apache.org/jira/browse/GUMP-132 Project: Gump Type: Task Components: Infrastructure Reporter: Adam Jack Assignee: Adam Jack Priority: Minor http://vmgump.apache.org/ needs a landing page, like Brutus used to have. Was that page saved? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-115) Make gump result pages link to LXR-generated content
[ http://issues.apache.org/jira/browse/GUMP-115?page=all ] Leo Simons updated GUMP-115: Component: Dynagump (was: Python-based Gump) Fix Version: Gump3-alpha-6 Version: Gump3-alpha-6 Environment: Make gump result pages link to LXR-generated content Key: GUMP-115 URL: http://issues.apache.org/jira/browse/GUMP-115 Project: Gump Type: New Feature Components: Dynagump Versions: Gump3-alpha-6 Reporter: Leo Simons Priority: Minor Fix For: Gump3-alpha-6 Once GUMP-114 is set up, we could provide links to the cross-referenced stuff from the gump build results pages. It would be esp. cool to parse build outputs for filenames and line numbers and transform those into links into the cross referenced source. This would mean that a whole lot of debugging could take place by clicking around the gump site, without developers having to check out the matching version of code they wish to examine from version control. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-113) Set up dynagump installation and proxypass from main gump site
[ http://issues.apache.org/jira/browse/GUMP-113?page=comments#action_12315261 ] Leo Simons commented on GUMP-113: - The new dynagump is at http://vmgump.apache.org:8080/ started from the crontab of the 'gump' user. Set up dynagump installation and proxypass from main gump site -- Key: GUMP-113 URL: http://issues.apache.org/jira/browse/GUMP-113 Project: Gump Type: Task Components: Infrastructure Versions: Gump3-alpha-4 Environment: brutus.apache.org, minotaur.apache.org, or perhaps a new vhost on loki or helios Reporter: Leo Simons Priority: Minor We should actively start using the cool new interface dynagump provides us for our documentation needs. This requires a webapp set up, and the gump.apache.org vhost should be proxypassing it for security, performance and url management reasons. For now I suggest we simply hide the actual dynagump features in development, and link only to the documentation that's in there. This should not be started before the whole infrastructure dust cloud settles a little and the plans for the apache hardware become more definitive. We should also take care not to confuse users; for now we don't want them doing anything with Gump3 whatsoever :-D -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-117) gump.plugins.java.ClasspathPlugin component for setting (BUILD|SYS|*)CLASSPATH properties on java-based projects
[ http://issues.apache.org/jira/browse/GUMP-117?page=all ] Leo Simons closed GUMP-117: --- Resolution: Fixed Assign To: Leo Simons (was: Adam Jack) Fixed in SVN revision 209309. gump.plugins.java.ClasspathPlugin component for setting (BUILD|SYS|*)CLASSPATH properties on java-based projects Key: GUMP-117 URL: http://issues.apache.org/jira/browse/GUMP-117 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 Java-based projects require a properly set up classpath to compile. A plugin should be created that understands how java does classpath management, and it should then create the relevant classpath settings based on the dependencies specified for a project, annotating the model with that info. Ideally most of this functionality can be pushed into a helper module as its likely we'll need to reuse bits elsewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-90) testcases for gump.engine
[ http://issues.apache.org/jira/browse/GUMP-90?page=all ] Leo Simons closed GUMP-90: -- Resolution: Won't Fix Assign To: Leo Simons It's not very likely that this is going to happen properly -- the code is simply too hard to completely verify through unit tests. We've resorted to using integration testing which has led to reasonable code coverage. Its not optimal, but hey, unit testing in python isn't, either. testcases for gump.engine - Key: GUMP-90 URL: http://issues.apache.org/jira/browse/GUMP-90 Project: Gump Type: Test Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 The modeller code is large, complex and vital to the functionality of gump. It really does need quite extensive unit testing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-91) testcases for gump.engine.loader.Loader
[ http://issues.apache.org/jira/browse/GUMP-91?page=all ] Leo Simons updated GUMP-91: --- Fix Version: Gump3-alpha-5 (was: Gump3-alpha-4) Description: Version: Gump3-alpha-5 (was: Gump3-alpha-4) Environment: testcases for gump.engine.loader.Loader --- Key: GUMP-91 URL: http://issues.apache.org/jira/browse/GUMP-91 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-92) testcases for gump.engine.normalizer.Normalizer
[ http://issues.apache.org/jira/browse/GUMP-92?page=all ] Leo Simons updated GUMP-92: --- Fix Version: Gump3-alpha-5 (was: Gump3-alpha-4) Description: Version: Gump3-alpha-5 (was: Gump3-alpha-4) Environment: testcases for gump.engine.normalizer.Normalizer --- Key: GUMP-92 URL: http://issues.apache.org/jira/browse/GUMP-92 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-93) testcases for gump.engine.objectifier.Objectifier
[ http://issues.apache.org/jira/browse/GUMP-93?page=all ] Leo Simons updated GUMP-93: --- Fix Version: Gump3-alpha-5 (was: Gump3-alpha-4) Description: Version: Gump3-alpha-5 (was: Gump3-alpha-4) Environment: testcases for gump.engine.objectifier.Objectifier - Key: GUMP-93 URL: http://issues.apache.org/jira/browse/GUMP-93 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-94) testcases for gump.engine.verifier.Verifier
[ http://issues.apache.org/jira/browse/GUMP-94?page=all ] Leo Simons updated GUMP-94: --- Fix Version: Gump3-alpha-5 (was: Gump3-alpha-4) Description: Version: Gump3-alpha-5 (was: Gump3-alpha-4) Environment: testcases for gump.engine.verifier.Verifier --- Key: GUMP-94 URL: http://issues.apache.org/jira/browse/GUMP-94 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-120) gump.engine.modeller.Objectifier support for ant/ elements
[ http://issues.apache.org/jira/browse/GUMP-120?page=all ] Leo Simons closed GUMP-120: --- Resolution: Fixed gump.engine.modeller.Objectifier support for ant/ elements Key: GUMP-120 URL: http://issues.apache.org/jira/browse/GUMP-120 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-4 The objectifier should recognize ant/ elements and create the relevant model elements on encountering them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-130) Comprehensive integration test fixture
[ http://issues.apache.org/jira/browse/GUMP-130?page=all ] Leo Simons closed GUMP-130: --- Resolution: Fixed Assign To: Leo Simons Comprehensive integration test fixture -- Key: GUMP-130 URL: http://issues.apache.org/jira/browse/GUMP-130 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 Gump3 currently has a rather small giraffe.xml profile in its metadata/ directory. This basis should be expanded to a sizeable profile that exercises a significant part of gump's features. We should split the profile up into multiple xml files, create small quick-to-compile dummy projects instead of using live ones, and provide the documentation neccessary for joe developer to add to that fixture. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-141) Automate navigation generation for Dynagump
Automate navigation generation for Dynagump --- Key: GUMP-141 URL: http://issues.apache.org/jira/browse/GUMP-141 Project: Gump Type: Improvement Components: Dynagump Versions: Gump3-alpha-4 Reporter: Leo Simons Currently dynagump has some navigational elements (like the page trail at the top) which are generated manually from its xml files. It would be nice if this could be automated in some way, for example somewhat like forrest (http://forrest.apache.org/) or maven (http://maven.apache.org/) auto-create navigation elements on their pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-142) Add some documentation on how to add functionality to Dynagump
Add some documentation on how to add functionality to Dynagump -- Key: GUMP-142 URL: http://issues.apache.org/jira/browse/GUMP-142 Project: Gump Type: Improvement Components: Dynagump Versions: Gump3-alpha-4 Reporter: Leo Simons Adding new functionality to Dynagump involves something like - create an xsp page - maybe use some sql stuff on that xsp page - maybe add some cocoon components/blocks for use with the xsp - maybe modify the cocoon sitemap to make those components available to that page - link to that page from elsewhere in the webapp structure - commit everything It would be great to have a basic Howto (either on the wiki or inside the dynagump source itself) describing these steps in some detail, if possible with references to the relevant cocoon documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-143) Create init script for Dynagump
Create init script for Dynagump --- Key: GUMP-143 URL: http://issues.apache.org/jira/browse/GUMP-143 Project: Gump Type: Improvement Components: Dynagump Versions: Gump3-alpha-4 Reporter: Leo Simons Currently dynagump is only set up for starting it directly from the command line. We need some basic daemon functionality. We need a shell script which can be linked into /etc/init.d on unix systems (eg that accepts start, stop, restart, etc) so that we can install dynagump as a service on our servers. There is probably already a script + some code that does this for Jetty, we just need to get that inside our SVN tree with paths set up right and the like (eg pointing to somewhere inside GUMP_HOME, probably, and setting GUMP_HOME to a sensible default, or whatever). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-144) Design and document sensible URL scheme for gump data
Design and document sensible URL scheme for gump data - Key: GUMP-144 URL: http://issues.apache.org/jira/browse/GUMP-144 Project: Gump Type: New Feature Components: Dynagump Versions: Gump3-alpha-4 Reporter: Leo Simons We should have permanent URLs for accessing gump data and think of proper url space management. For example (and just as an example), we might want to have http://gump.apache.org/results/vmgump.apache.org/public/2005/06/30/12:34/project-summaries/xml-xerces.html result in the results summary for the xml-xerces project for the public gump run on vmgump.apache.org on 2005-06-30 that started at 12:34am. This URL should still be the same 3 years from now. We might also want something like http://gump.apache.org/results/all-runs/last/project-summaries/xml-xerces.html to get the most recent of those summaries for all runs of all profiles on all known servers. Or whatever. URL management requires some up-front planning, so we should do it :-). A nice example of good permanent URLs is mod_mbox. Ie the url http://mail-archives.apache.org/mod_mbox/gump-general/200311.mbox/[EMAIL PROTECTED] is still going to return the same information 5 years from now. Gump2 is not a good example at all :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-145) Apache HTTPD config snippet for Dynagump
Apache HTTPD config snippet for Dynagump Key: GUMP-145 URL: http://issues.apache.org/jira/browse/GUMP-145 Project: Gump Type: Task Components: Dynagump Versions: Gump3-alpha-4 Reporter: Leo Simons We want to configure http://gump.apache.org/ (which is static pages served up by apache) to proxypass certain bits of its url space to Dynagump instances running elsewhere. We might also want to configure the httpds running on other machines (eg vmgump, gump.zones) to proxy pass bits of their url space to dynagump, and serve up some static content (images, stylesheets) directly without going through Jetty. We need example httpd.conf stuff and documentation for how that is set up. The actual config for gump.apache.org lives in Infrastructure SVN. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-139) module project fails, it needs to be module project module
[ http://issues.apache.org/jira/browse/GUMP-139?page=comments#action_12313867 ] Leo Simons commented on GUMP-139: - I've got a fix for this locally. module project fails, it needs to be module project module --- Key: GUMP-139 URL: http://issues.apache.org/jira/browse/GUMP-139 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons This might be considered support for 0.4 metadata. Normalizer:_get_list_merged_by_name returns cloned nodes --- and those nodes are w/o a parent. As such Normalizer:_find_module_containing_node fails when looking for the parent module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=comments#action_12313856 ] Leo Simons commented on GUMP-138: - Potential fix committed in r190983. I can't reproduce the above stack trace (ie I don't have the above workspace definitions) so I'm not too confident. Adam, could you try again? Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Fix For: Gump3-alpha-3 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-136) Bad XML causes Gump3 to crash
[ http://issues.apache.org/jira/browse/GUMP-136?page=all ] Leo Simons closed GUMP-136: --- Fix Version: Gump3-alpha-4 Resolution: Fixed Assign To: Leo Simons Fixed with svn commit 190980. Bad XML causes Gump3 to crash - Key: GUMP-136 URL: http://issues.apache.org/jira/browse/GUMP-136 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-4 If any included (via 'href') XML is bad, Gump exits with an XML parser exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=all ] Leo Simons reassigned GUMP-138: --- Assign To: Adam Jack Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Adam Jack Fix For: Gump3-alpha-3 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Leo Simons reassigned GUMP-122: --- Assign To: Adam Jack Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=all ] Leo Simons reassigned GUMP-138: --- Assign To: Leo Simons (was: Adam Jack) Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-3 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-139) module project fails, it needs to be module project module
[ http://issues.apache.org/jira/browse/GUMP-139?page=all ] Leo Simons reassigned GUMP-139: --- Assign To: Leo Simons module project fails, it needs to be module project module --- Key: GUMP-139 URL: http://issues.apache.org/jira/browse/GUMP-139 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons This might be considered support for 0.4 metadata. Normalizer:_get_list_merged_by_name returns cloned nodes --- and those nodes are w/o a parent. As such Normalizer:_find_module_containing_node fails when looking for the parent module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-110) document the gump3 graph algebra language and explain it
[ http://issues.apache.org/jira/browse/GUMP-110?page=all ] Leo Simons reassigned GUMP-110: --- Assign To: Leo Simons document the gump3 graph algebra language and explain it Key: GUMP-110 URL: http://issues.apache.org/jira/browse/GUMP-110 Project: Gump Type: Sub-task Components: Documentation Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-110) document the gump3 graph algebra language and explain it
[ http://issues.apache.org/jira/browse/GUMP-110?page=all ] Leo Simons closed GUMP-110: --- Resolution: Fixed The powerpoint file contains as much of an explanation as can comfortably be expressed in English. document the gump3 graph algebra language and explain it Key: GUMP-110 URL: http://issues.apache.org/jira/browse/GUMP-110 Project: Gump Type: Sub-task Components: Documentation Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-107) Document gump3 algorithm design
[ http://issues.apache.org/jira/browse/GUMP-107?page=all ] Leo Simons reassigned GUMP-107: --- Assign To: Leo Simons Document gump3 algorithm design --- Key: GUMP-107 URL: http://issues.apache.org/jira/browse/GUMP-107 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 Stefano and Leo whiteboarded an algorithm a while ago that describes a way to be a lot more certain about what change caused what problem where than the current algorithms as design in Gump1 and Gump2. A scan of the algorithm is drifting around somewhere, and part of it has been transformed into a powerpoint presentation. The entire thing needs to be properly documented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-107) Document gump3 algorithm design
[ http://issues.apache.org/jira/browse/GUMP-107?page=all ] Leo Simons closed GUMP-107: --- Resolution: Fixed Document gump3 algorithm design --- Key: GUMP-107 URL: http://issues.apache.org/jira/browse/GUMP-107 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 Stefano and Leo whiteboarded an algorithm a while ago that describes a way to be a lot more certain about what change caused what problem where than the current algorithms as design in Gump1 and Gump2. A scan of the algorithm is drifting around somewhere, and part of it has been transformed into a powerpoint presentation. The entire thing needs to be properly documented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-129) Create pretty color-coded and easy-to-read CLI output
[ http://issues.apache.org/jira/browse/GUMP-129?page=all ] Leo Simons closed GUMP-129: --- Resolution: Fixed fixed in revision r168384. Create pretty color-coded and easy-to-read CLI output - Key: GUMP-129 URL: http://issues.apache.org/jira/browse/GUMP-129 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Priority: Minor Fix For: Gump3-alpha-4 Gump's output needs to be as readable and intuitive as possible, using colors, and two simple default modes (--debug and no --debug). The output needs to be a good reflection of gump its activity, ie it preferably shouldn't go completely silent for long periods of time. It should fit in no more than a few screenfuls if possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-130) Comprehensive integration test fixture
Comprehensive integration test fixture -- Key: GUMP-130 URL: http://issues.apache.org/jira/browse/GUMP-130 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Fix For: Gump3-alpha-4 Gump3 currently has a rather small giraffe.xml profile in its metadata/ directory. This basis should be expanded to a sizeable profile that exercises a significant part of gump's features. We should split the profile up into multiple xml files, create small quick-to-compile dummy projects instead of using live ones, and provide the documentation neccessary for joe developer to add to that fixture. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-124) Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm
Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm - Key: GUMP-124 URL: http://issues.apache.org/jira/browse/GUMP-124 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assigned to: Leo Simons Fix For: Gump3-alpha-4 It turns out that the visitor provided to the Walker class is the right place to implement all kinds of smarter gump algorithms. Scattering an algorithm between several plugins is hard if not impossible: it is often necessary to skip a project if its dependencies fail, which would mean severe breakage of a lot of gump.model assumptions to make it work. On the other hand, modifying the visitor to make those decisions there is easy. It seems there is a seperation between intelligence and plugin which can be encapsulated. This should probably move into the gump.engine package so plugin authors need not worry about it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-123) Refactor gump.engine.modeller into smaller bits
Refactor gump.engine.modeller into smaller bits --- Key: GUMP-123 URL: http://issues.apache.org/jira/browse/GUMP-123 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assigned to: Leo Simons Fix For: Gump3-alpha-4 modeller.py is a bit of a mess, hard to read, hard to test. It should be broken up into multiple files and some of its classes should be broken up into multiple smaller classes, or, more likely, functions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-125) Flexible way to configure gump in modern unix-like fashion
Flexible way to configure gump in modern unix-like fashion -- Key: GUMP-125 URL: http://issues.apache.org/jira/browse/GUMP-125 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 Gump2 is configured in the workspace/ just like Java-Gump was. Gump3 is currently configured through environment variables and the command line (sourcing a shell script for custom settings). We should provide a logical and modern way to configure gump through /etc/gump3 and $HOME/.gump3 directories where you can safely store configuration data related to the machine or the environment (ie, database to use, JAVA_HOME to use, ...). A nice example of an application with flexible configuration support is exim, another one is spamassassin, yet another one is apache2 as provided for debian. Things I would like to see: * conf.d directories to allow spliting config * per-profile config as well as per-machine config * use python's features as much as possible for config features and intelligence * installation of default config files with lots of comments so no RTFM is needed One advantage of the gump3 gump script is that it has no particular trouble firing up jetty (for dynagump) or apache (for webgump). We really need to keep that flexibility, meaning it might make sense to have the configuration parsing set up almost totally seperately from the rest of gump. We could even consider something that reads the environment and the config files and then generates a really-long-commandline or temporary-shell-script. It could be a reusable python tool :-) Or maybe that's a bad idea. We'll see. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-126) Simple scheduling support using a gump run queue
Simple scheduling support using a gump run queue
--
Key: GUMP-126
URL: http://issues.apache.org/jira/browse/GUMP-126
Project: Gump
Type: New Feature
Components: Python-based Gump
Versions: Gump3-alpha-6
Reporter: Leo Simons
Fix For: Gump3-alpha-6
As discussed on the mailing list:
http://mail-archives.apache.org/mod_mbox/gump-general/200504.mbox/[EMAIL
PROTECTED]
Naïve line-based schedule file using simple commands together with cron could
be real nice.
Creating schedules
--
We should have something like
gump schedule-run --profile=public --official
gump schedule-run --profile=public
gump schedule-run --profile=kaffe
Which writes a file $GUMP_HOME/schedule looking like this
gump run --profile=public --official
gump run --profile=public
gump run --profile=kaffe
The code would be along the lines of
schedule_run()
{
local schedulefile=$GUMP_HOME/schedule
echo gump run $* $schedulefile
}
You would also want to schedule runs immediately
gump schedule-run-first --profile=custom --debug
Which would be something like
schedule_run_first()
{
local schedulefile=$GUMP_HOME/schedule
echo gump run $* $schedulefile.new
cat $schedulefile $schedulefile.new
rm $schedulefile
mv $schedulefile.new $schedulefile
}
And of course there's more options like
schedule_run_when_idle()
{
local pidfile=$GUMP_HOME/pygump/pygump.pid
if [[ ! -f $pidfile ]]; then
schedule_run
fi
}
The next bit is to have calls to those schedule-run commands in the
crontab:
# the next run after midnight will be the official one
0 0 * * * . /home/gump/.bash_profile; gump schedule-run-first \
--profile=public --official
0 6 * * * . /home/gump/.bash_profile; gump schedule-run \
--profile=kaffe
0 12 * * * . /home/gump/.bash_profile; gump schedule-run \
--profile=jdk15
0 3,9,15,18 * * * . /home/gump/.bash_profile; gump schedule-run-when-idle \
--profile=public
Keeping schedules
-
And then have something like
gump try-to-invoke-run
Which checks to see if gump is running, and if not, takes a line from
$GUMP_HOME/schedule and executes it. Along the lines of
try_to_invoke_run()
{
local pidfile=$GUMP_HOME/pygump/pygump.pid
if [[ ! -f $pidfile ]]; then
line=remove_first_line_from_schedule
`$line`
fi
}
And we run that real often from the crontab:
60/12 * * * * . /home/gump/.bash_profile; gump try-to-invoke-run
Why
---
This would ensure gump would be running just about continuously, but you
could also easily interrupt using
gump kill
gump schedule-run-first --profile=custom --debug
To manually change the schedule if you wanted to try something.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-128) Support federation of gump instances
Support federation of gump instances Key: GUMP-128 URL: http://issues.apache.org/jira/browse/GUMP-128 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 As discussed on the mailing list http://mail-archives.apache.org/mod_mbox/gump-general/200504.mbox/[EMAIL PROTECTED] (And before that in other threads as well), it could make sense to incorporate features to make multiple gump instances work together and share results. Another source of ideas on this is Vincent Massol's weblog: http://blogs.codehaus.org/people/vmassol/ ie http://blogs.codehaus.org/people/vmassol/archives/001006_distributed_build.html this is a rather big and complex undertaking. The challenge will be to not impact most of the logic and most of the codebase with these changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (GUMP-127) Support for local plugins
Support for local plugins - Key: GUMP-127 URL: http://issues.apache.org/jira/browse/GUMP-127 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 As discussed in http://mail-archives.apache.org/mod_mbox/gump-general/200504.mbox/[EMAIL PROTECTED] it might be nice to be able to install custom plugins locally, ie inside $HOME/.gump/plugins or similar. One application we might want to look at that supports this is maven, another one (which is probably overkill by far) is eclipse, a third one is Chandler. It could be as simple as adding a directory to the python path :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-109) verify gump3 digital algorithm
[ http://issues.apache.org/jira/browse/GUMP-109?page=all ] Leo Simons reassigned GUMP-109: --- Assign To: Leo Simons (was: Stefano Mazzocchi) verify gump3 digital algorithm -- Key: GUMP-109 URL: http://issues.apache.org/jira/browse/GUMP-109 Project: Gump Type: Sub-task Components: Documentation Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-103) design conventions for marking up the gump.model and modifying behaviour
[ http://issues.apache.org/jira/browse/GUMP-103?page=all ] Leo Simons closed GUMP-103: --- Resolution: Fixed IMO looking at the source for the plugins in development currently makes it easy enough to figure out what means what. If we keep up this level of documentation it should be okay for some time to come. design conventions for marking up the gump.model and modifying behaviour Key: GUMP-103 URL: http://issues.apache.org/jira/browse/GUMP-103 Project: Gump Type: Task Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Fix For: Gump3-alpha-4 A whole bunch of plugins will want to execute commands as part of building some project. What should be the workflow inside gump to make that happen? It might make sense to have components like the MkdirPlugin and AntPlugin mark up their commands with the exit code, as well as output log and/or error log. Then there might be a StateDetectionPlugin that looks at the state of all projects after the builder plugins are done, and sets a project failure|success|prereq failure state or something like that on the project itself, in addition perhaps having a blame list pointing at the commands that failed, sorting that in some logical order (if ant failed due to mkdir failing, blame the mkdir, not ant). There could be several StateDetectionPLugins so we can try out different algorithms in dealing with success/failure. The key bit is to keep the builders and the like simple and preferably very linear in their behaviour, with little branching. The less they have to do, the easier it is to add new ones :-D -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-119) gump.model.Ant class for modelling ant/ commands
[ http://issues.apache.org/jira/browse/GUMP-119?page=all ] Leo Simons reassigned GUMP-119: --- Assign To: Adam Jack Adam's working on the ant support gump.model.Ant class for modelling ant/ commands -- Key: GUMP-119 URL: http://issues.apache.org/jira/browse/GUMP-119 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-4 We need to support ant/ commands in the gump3 model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-120) gump.engine.modeller.Objectifier support for ant/ elements
[ http://issues.apache.org/jira/browse/GUMP-120?page=all ] Leo Simons reassigned GUMP-120: --- Assign To: Adam Jack Adam's working on the ant support gump.engine.modeller.Objectifier support for ant/ elements Key: GUMP-120 URL: http://issues.apache.org/jira/browse/GUMP-120 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-4 The objectifier should recognize ant/ elements and create the relevant model elements on encountering them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-124) Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm
[ http://issues.apache.org/jira/browse/GUMP-124?page=all ] Leo Simons closed GUMP-124: --- Resolution: Fixed Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm - Key: GUMP-124 URL: http://issues.apache.org/jira/browse/GUMP-124 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 It turns out that the visitor provided to the Walker class is the right place to implement all kinds of smarter gump algorithms. Scattering an algorithm between several plugins is hard if not impossible: it is often necessary to skip a project if its dependencies fail, which would mean severe breakage of a lot of gump.model assumptions to make it work. On the other hand, modifying the visitor to make those decisions there is easy. It seems there is a seperation between intelligence and plugin which can be encapsulated. This should probably move into the gump.engine package so plugin authors need not worry about it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-124) Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm
[ http://issues.apache.org/jira/browse/GUMP-124?page=comments#action_64211 ] Leo Simons commented on GUMP-124: - Fixed in r165514. Refactor so that gump.plugins.MulticastPlugin and gump.plugins.buildintelligence become gump.engine.algorithm - Key: GUMP-124 URL: http://issues.apache.org/jira/browse/GUMP-124 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 It turns out that the visitor provided to the Walker class is the right place to implement all kinds of smarter gump algorithms. Scattering an algorithm between several plugins is hard if not impossible: it is often necessary to skip a project if its dependencies fail, which would mean severe breakage of a lot of gump.model assumptions to make it work. On the other hand, modifying the visitor to make those decisions there is easy. It seems there is a seperation between intelligence and plugin which can be encapsulated. This should probably move into the gump.engine package so plugin authors need not worry about it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work started: (GUMP-123) Refactor gump.engine.modeller into smaller bits
[ http://issues.apache.org/jira/browse/GUMP-123?page=all ] Work on GUMP-123 started by Leo Simons Refactor gump.engine.modeller into smaller bits --- Key: GUMP-123 URL: http://issues.apache.org/jira/browse/GUMP-123 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 modeller.py is a bit of a mess, hard to read, hard to test. It should be broken up into multiple files and some of its classes should be broken up into multiple smaller classes, or, more likely, functions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work started: (GUMP-123) Refactor gump.engine.modeller into smaller bits
[ http://issues.apache.org/jira/browse/GUMP-123?page=all ] Work on GUMP-123 started by Leo Simons Refactor gump.engine.modeller into smaller bits --- Key: GUMP-123 URL: http://issues.apache.org/jira/browse/GUMP-123 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 modeller.py is a bit of a mess, hard to read, hard to test. It should be broken up into multiple files and some of its classes should be broken up into multiple smaller classes, or, more likely, functions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-123) Refactor gump.engine.modeller into smaller bits
[ http://issues.apache.org/jira/browse/GUMP-123?page=all ] Leo Simons closed GUMP-123: --- Resolution: Fixed Fixed in r165531. Refactor gump.engine.modeller into smaller bits --- Key: GUMP-123 URL: http://issues.apache.org/jira/browse/GUMP-123 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 modeller.py is a bit of a mess, hard to read, hard to test. It should be broken up into multiple files and some of its classes should be broken up into multiple smaller classes, or, more likely, functions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-81) Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames
[ http://issues.apache.org/jira/browse/GUMP-81?page=all ] Leo Simons closed GUMP-81: -- Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames Key: GUMP-81 URL: http://issues.apache.org/jira/browse/GUMP-81 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2-2.4 Reporter: Adam Jack Fix For: Gump2-2.4 A circumstance was found whereby 'resume.xml' (with an e acute) in a module (XOM, FWIIW) was checked out of the repository, but the (Python code) 'sync' to a working directory failed. It failed because Python's os.listdir returned a string for it, not Unicode (although it returned unicode for al lthe plain file). This seems related to the fact that the default filesystem encoding on the platofrm was 'ascii', and this file was not ascii. We need to create a test for such files, then work with Gump to resolve this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-54) wrap corrupts the data
[ http://issues.apache.org/jira/browse/GUMP-54?page=all ] Leo Simons closed GUMP-54: -- wrap corrupts the data -- Key: GUMP-54 URL: http://issues.apache.org/jira/browse/GUMP-54 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2-2.4 Reporter: Adam Jack Priority: Minor Fix For: Gump2-2.4 Line wrap appears to corrupt the data, which make it almost unreadable. [Note: The main build data is no longer wrapped, making this a minor issue.] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-52) Fails to propogate 'config' (no such depends) properly
[ http://issues.apache.org/jira/browse/GUMP-52?page=all ] Leo Simons closed GUMP-52: -- Resolution: Incomplete unclear what this is about. Fails to propogate 'config' (no such depends) properly -- Key: GUMP-52 URL: http://issues.apache.org/jira/browse/GUMP-52 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2-2.4 Reporter: Adam Jack Priority: Minor Fix For: Gump2-2.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work started: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Work on GUMP-122 started by Leo Simons Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Leo Simons reassigned GUMP-122: --- Assign To: Leo Simons Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Leo Simons reassigned GUMP-122: --- Assign To: (was: Leo Simons) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-90) testcases for gump.engine
[ http://issues.apache.org/jira/browse/GUMP-90?page=all ] Leo Simons updated GUMP-90: --- Summary: testcases for gump.engine (was: testcases for gump.engine.modeller) testcases for gump.engine - Key: GUMP-90 URL: http://issues.apache.org/jira/browse/GUMP-90 Project: Gump Type: Test Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Fix For: Gump3-alpha-4 The modeller code is large, complex and vital to the functionality of gump. It really does need quite extensive unit testing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work stopped: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Work on GUMP-122 stopped by Leo Simons Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-94) testcases for gump.engine.verifier.Verifier
[ http://issues.apache.org/jira/browse/GUMP-94?page=all ] Leo Simons updated GUMP-94: --- Summary: testcases for gump.engine.verifier.Verifier (was: testcases for gump.engine.model.Verifier) Description: Environment: testcases for gump.engine.verifier.Verifier --- Key: GUMP-94 URL: http://issues.apache.org/jira/browse/GUMP-94 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Fix For: Gump3-alpha-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-92) testcases for gump.engine.normalizer.Normalizer
[ http://issues.apache.org/jira/browse/GUMP-92?page=all ] Leo Simons updated GUMP-92: --- Summary: testcases for gump.engine.normalizer.Normalizer (was: testcases for gump.engine.model.Normalizer) Description: Environment: testcases for gump.engine.normalizer.Normalizer --- Key: GUMP-92 URL: http://issues.apache.org/jira/browse/GUMP-92 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Fix For: Gump3-alpha-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-91) testcases for gump.engine.loader.Loader
[ http://issues.apache.org/jira/browse/GUMP-91?page=all ] Leo Simons updated GUMP-91: --- Summary: testcases for gump.engine.loader.Loader (was: testcases for gump.engine.model.Loader) testcases for gump.engine.loader.Loader --- Key: GUMP-91 URL: http://issues.apache.org/jira/browse/GUMP-91 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-4 Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-89) support junitreport
[ http://issues.apache.org/jira/browse/GUMP-89?page=all ] Leo Simons updated GUMP-89: --- Version: Gump3-alpha-5 (was: Gump2-2.4) Fix Version: Gump3-alpha-5 (was: Gump2-2.4) support junitreport Key: GUMP-89 URL: http://issues.apache.org/jira/browse/GUMP-89 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 Gump should support junitreport/: http://gump.apache.org/metadata/project.html#junitreport the referenced directories should be published as part of the logs whether or not the project build is successful, and linked to from the gump html pages, probably as part of the Output Artifacts section on the details page of a project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-83) The mkdir element ought be removed, and automated
[ http://issues.apache.org/jira/browse/GUMP-83?page=all ] Leo Simons closed GUMP-83: -- Resolution: Fixed Fix Version: Gump3-alpha-4 (was: Gump2-2.4) (was: GOM-0.4) let's fix this as part of GUMP-117 and not worry about it for gump2. The mkdir element ought be removed, and automated -- Key: GUMP-83 URL: http://issues.apache.org/jira/browse/GUMP-83 Project: Gump Type: Improvement Components: Object Model (GOM), Python-based Gump Versions: Gump2-2.4, GOM-0.4 Reporter: Adam Jack Fix For: Gump3-alpha-4 Gump knows that certain CLASSPATH directories needs to be built prior to the build tool's JVM being started, or they will be dropped. As such the mkdir element was added. This can be removed, and we can automatically do this for all work directories, hence automatic the process and simplifying it for users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-62) Module docs needs to point to fully qualified viewcvs
[ http://issues.apache.org/jira/browse/GUMP-62?page=all ] Leo Simons updated GUMP-62: --- Version: Gump3-alpha-5 (was: Gump2-2.4) Fix Version: Gump3-alpha-5 (was: Gump2-2.4) move to fix in gump3-alpha-5 Module docs needs to point to fully qualified viewcvs - Key: GUMP-62 URL: http://issues.apache.org/jira/browse/GUMP-62 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Adam Jack Priority: Minor Fix For: Gump3-alpha-5 If available allow user to click on a link to view source for a module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work started: (GUMP-91) testcases for gump.engine.model.Loader
[ http://issues.apache.org/jira/browse/GUMP-91?page=all ] Work on GUMP-91 started by Leo Simons testcases for gump.engine.model.Loader -- Key: GUMP-91 URL: http://issues.apache.org/jira/browse/GUMP-91 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-91) testcases for gump.engine.model.Loader
[ http://issues.apache.org/jira/browse/GUMP-91?page=all ] Leo Simons reassigned GUMP-91: -- Assign To: Leo Simons testcases for gump.engine.model.Loader -- Key: GUMP-91 URL: http://issues.apache.org/jira/browse/GUMP-91 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-alpha -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-96) testcases for gump.util.executor
[ http://issues.apache.org/jira/browse/GUMP-96?page=all ] Leo Simons updated GUMP-96: --- Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) testcases for gump.util.executor Key: GUMP-96 URL: http://issues.apache.org/jira/browse/GUMP-96 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-95) gump.util.executor.Executor component for cleaning up processes
[ http://issues.apache.org/jira/browse/GUMP-95?page=all ] Leo Simons updated GUMP-95: --- Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) gump.util.executor.Executor component for cleaning up processes --- Key: GUMP-95 URL: http://issues.apache.org/jira/browse/GUMP-95 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 Gump fires off lots of different processes that may fire off new processes that may in turn create processes that may not be very good at cleaning up after themselves. For simple relatively short-running commands that we trust to clean up after themselves (like self-updating ourselves from svn or grepping a file or whatever), we can trust in the subprocess module that comes with python. For other tasks such as firing up actual builds, we should have something more robust. A skeleton algorithm is provided at: http://mail-archives.apache.org/mod_mbox/gump-general/200503.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-102) gump.plugins.RmdirPlugin component for removing rmdir/ directories
[ http://issues.apache.org/jira/browse/GUMP-102?page=all ] Leo Simons updated GUMP-102: Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) gump.plugins.RmdirPlugin component for removing rmdir/ directories Key: GUMP-102 URL: http://issues.apache.org/jira/browse/GUMP-102 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 A simple plugin that looks for all rmdir | gump.model.Rmdir commands and executes them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-97) basic implementation of gump.util.executor
[ http://issues.apache.org/jira/browse/GUMP-97?page=all ] Leo Simons updated GUMP-97: --- Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) basic implementation of gump.util.executor -- Key: GUMP-97 URL: http://issues.apache.org/jira/browse/GUMP-97 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-101) gump.plugins.MkdirPlugin component for creating mkdir/ directories
[ http://issues.apache.org/jira/browse/GUMP-101?page=all ] Leo Simons updated GUMP-101: Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) gump.plugins.MkdirPlugin component for creating mkdir/ directories Key: GUMP-101 URL: http://issues.apache.org/jira/browse/GUMP-101 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 A simple plugin that looks for all mkdir/ | gump.model.Mkdir commands and executes them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-95) gump.util.executor.Executor component for cleaning up processes
[ http://issues.apache.org/jira/browse/GUMP-95?page=all ] Leo Simons updated GUMP-95: --- Version: Gump3-alpha-3 (was: Gump3-alpha-4) gump.util.executor.Executor component for cleaning up processes --- Key: GUMP-95 URL: http://issues.apache.org/jira/browse/GUMP-95 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 Gump fires off lots of different processes that may fire off new processes that may in turn create processes that may not be very good at cleaning up after themselves. For simple relatively short-running commands that we trust to clean up after themselves (like self-updating ourselves from svn or grepping a file or whatever), we can trust in the subprocess module that comes with python. For other tasks such as firing up actual builds, we should have something more robust. A skeleton algorithm is provided at: http://mail-archives.apache.org/mod_mbox/gump-general/200503.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-19) Support encoding of international characters in nag mail headers
[ http://issues.apache.org/jira/browse/GUMP-19?page=all ] Leo Simons closed GUMP-19: -- Resolution: Fixed fixed long time ago as per Stefan's comment. Support encoding of international characters in nag mail headers Key: GUMP-19 URL: http://issues.apache.org/jira/browse/GUMP-19 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2 Reporter: Stefan Bodewig Fix For: Gump2 As wittnessed by the failing nag mails to log4j. Escaping of non-ASCII characters is well defined, sounds like a rather simple fix that might make a good candidate fix for somebody with a very low working knowledge of Python. Read, I'll look into it unless anybody beats me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-21) FOG factor is misleading and requires improvement
[ http://issues.apache.org/jira/browse/GUMP-21?page=all ] Leo Simons closed GUMP-21: -- Resolution: Fixed FOG factor is misleading and requires improvement - Key: GUMP-21 URL: http://issues.apache.org/jira/browse/GUMP-21 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump2 Reporter: Daniel Savarese Assignee: Adam Jack Fix For: Gump2 FOG is defined right now as: def getFOGFactor(self): return round((float(self.successes) / (float(self.failures) + float(self.prereqs))), 2) This is not helpful. Last month, jakart-oro failed to build by coincidence around the time of a Gump run and the problem was fixed before the next Gump run, yet its FOG factor dropped in half. The responsiveness to resolving build and integration problems is not taken into account. It is likely that it is impossible for FOG to mean anything because the factors that determine a project's health (to borrow the term used by Adam Jack in an email to the commons-dev and gump lists) are largely orthogonal. FOG should probably be a vector and if you really wanted a single number you could use the length of that vector. One of the major problems with the current factor is that a project's FOG factor continues to increase when no changes have been made to the repository. It's not meaningful to count only successful builds towards improving the factor because no changes may have been made to the code base. Ideally, you count only builds that cause no failures after a change to the code base. FOG doesn't factor in how quickly (or slowly) projects recover from build failures, and how often changes to a code base cause failures (either in itself or in other projects). Right now, a project with few code changes (say once a month) that causes a failure 50% (1 every 2 months) of the time the code is changed with a mean time of failure correction of 1 week is deemed more reliable (higher FOG factor) than a project that makes frequent changes (say every day) to its code base and causes a failure 10% of the time (1 every 10 days) with a mean time of failure correction of 1 day. That's because FOG is based almost entirely on consecutive successful Gump builds, which is not useful. Rather than propose a new meaningless way of computing FOG, I suggest FOG stop being used temporarily. It would be more useful to break out and report all of the independently useful metrics and through experience over time determine how each impacts the overall notion of FOG and eventually derive a way of condensing the information (perhaps a FOG factor, perhaps a vector) in a useful manner. Right now the state of affairs is that someone decided FOG was a cool thing, so it's being reported and people see this number and mistakenly think a project with half the FOG factor of another is less dependable and therefore avoid using it. Alternatively an explanation of what FOG is intended to compute and how it is computed should be placed on Gump reports that list FOG so that consumers of the information will not be misled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-16) Support for regexp in nag
[ http://issues.apache.org/jira/browse/GUMP-16?page=all ] Leo Simons closed GUMP-16: -- Resolution: Won't Fix Fix Version: (was: Gump2) The regexp tag is really a poor man's way to define success/failure condition for a project based on log output. Ideally, the ways to define success/failure will become a lot more refined than this in gump 3 (for example act differently based on different exit statuses, do more than just boolean success/failure) and in the new version of the gump object model. There's currently 25 occurrences of regexp in our metadata, which is feasible to fix by hand when the time arises. Support for regexp in nag --- Key: GUMP-16 URL: http://issues.apache.org/jira/browse/GUMP-16 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2 Environment: All Reporter: Adam Jack Gumpy needs to support regexp http://jakarta.apache.org/gump/metadata/project.html#nag -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-17) Failed to 'list .HTML files as work'
[ http://issues.apache.org/jira/browse/GUMP-17?page=all ] Leo Simons closed GUMP-17: -- Resolution: Fixed Forrest is no longer used; listFilesAsWork no longer exists. Failed to 'list .HTML files as work' Key: GUMP-17 URL: http://issues.apache.org/jira/browse/GUMP-17 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump2 Reporter: Adam Jack Priority: Minor Fix For: Gump2 listFilesAsWork generates a sub page, names that page, and displays the contents. This somehow fails when the file is a .html, since it gets a .html.html extension breaks (perhaps in Forrest). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-25) document actual gump installations
[ http://issues.apache.org/jira/browse/GUMP-25?page=all ] Leo Simons closed GUMP-25: -- Resolution: Fixed info on brutus is pretty good (BrutusConfig page on wiki) now. document actual gump installations -- Key: GUMP-25 URL: http://issues.apache.org/jira/browse/GUMP-25 Project: Gump Type: New Feature Components: Documentation Reporter: Leo Simons Priority: Minor Add some docs on the wiki about the actual gump setups on various machines, how they were set up, and how they are being maintained. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-26) keep around build logs
[ http://issues.apache.org/jira/browse/GUMP-26?page=all ] Leo Simons closed GUMP-26: -- Resolution: Won't Fix Fix Version: Gump3-alpha-3 (was: Gump2) Gump3/Dynagump will store historical data in a database. keep around build logs -- Key: GUMP-26 URL: http://issues.apache.org/jira/browse/GUMP-26 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump2 Reporter: Leo Simons Fix For: Gump3-alpha-3 Java gump used to keep around 5 days worth of build reports. We should have something similar in gumpy, with the last five days kept in full, and perhaps the last five weeks, and the last five months (ie your average backup schedule policy). Maybe we can do compression using diffs, but not sure what is the right space/computation tradeoff. We could put the logs in svn :-D -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-28) document gumpy internals
[ http://issues.apache.org/jira/browse/GUMP-28?page=all ] Leo Simons closed GUMP-28: -- Resolution: Fixed Fix Version: Gump3-alpha-3 (was: Gump2) Code documentation for Gump3 is reasonably good and when combined with unit tests should be mostly sufficient. Of course effort must be invested to keep it that way but that hardly qualifies as an issue to track document gumpy internals Key: GUMP-28 URL: http://issues.apache.org/jira/browse/GUMP-28 Project: Gump Type: Improvement Components: Python-based Gump Versions: Gump2 Reporter: Leo Simons Fix For: Gump3-alpha-3 Whilst gump user documentation and model documentation is quite reasonable, gumpy's source is not the easiest to read atm. Some pydoc (is that what it's called?) is in order, along with some high-level architecture info. Some of this stuff is already at http://wiki.apache.org/gump/GumpInternals but more work is to be done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-106) gump.plugins.ScriptPlugin component for executing script/ commands
[ http://issues.apache.org/jira/browse/GUMP-106?page=all ] Leo Simons updated GUMP-106: Fix Version: Gump3-alpha-3 (was: Gump3-alpha-4) gump.plugins.ScriptPlugin component for executing script/ commands Key: GUMP-106 URL: http://issues.apache.org/jira/browse/GUMP-106 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 The script/ | gump.model.Script command is probably the easiest builder command to be written that can be executed and have actually meaningful side effects. It should thus probably be the first real builder to be implemented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-96) testcases for gump.util.executor
[ http://issues.apache.org/jira/browse/GUMP-96?page=all ] Leo Simons updated GUMP-96: --- Version: Gump3-alpha-3 (was: Gump3-alpha-4) testcases for gump.util.executor Key: GUMP-96 URL: http://issues.apache.org/jira/browse/GUMP-96 Project: Gump Type: Sub-task Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Leo Simons Fix For: Gump3-alpha-3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
