Ideas for Improvements to the Build&Test Web Application

  1. Dependencies should be set, by default to 'Build' only
  2. The configuration list on the bottom should be alphabetically sorted
  3. Need simple string search capability on name and version
  4. Creation of modules and configurations should be atomic with respect to the WS
  5. Creation of configurations should allow editing before creation
  6. Main panels should be scrollable
  7. Main panes should be re-sizable (e.g. by using split panels)
  8. When expanding a configuration in the configuration tree, if there's only one platform, it should be automatically expanded
  9. When entering 'edit mode' for commands/properties/environment, entries should be immediately modifiable; the current behaviour requires either double-clicking them or clicking the small button on the right
  10. Wish: keyboard-driven navigation of trees
  11. Sort environment/properties alphabetically
  12. Distinguish between 'normal' properties and '.DEFAULT' properties
  13. ETICS module tree: double click on a tree item is not working properly when item is opened for the first time (and is loaded)
  14. It would be good to have the possibility of submitting a build/test by clicking directly in the platform, so that I don't need to select a given platform
  15. When you submit a job there jobID used to check the status is not displayed
  16. There should be a place where my submissions and job status are displayed
  17. When you click in the dependencies on a Configuration they are displayed on the right, but if I click on the dependency the dependency is not displayed

-- PaoloFabriani - 05 Jun 2007

Added Guillermo's feedback -- MebSter - 25 Jun 2007

Ideas for Improvements to the CLI

etics-build command:

  1. Would it be possible to have either a new option or a real --nodeps behaviour which just recompile the code without connetcing to the ETICS repository and performs several checks anyway? From a developer point of you, 90% of recompilations are done just after having slightly changed the code; in most cases there's absolutely no need to perform any external check /network connection (which is VERY time consuming)

  1. As far as I can see, the rpm produced by a compilation and stored in RPMS directory is not regenerated, unless --force option is specified. I believe this should be the default behaviour, because otherwise it leads to an unconsistent situation (libraries referring to modified code, rpm to old code)

  1. This is quite trivial feature, yet it's often very annoying: would it be possible to issue "etics-build" from the component directory I'm currently working, as in the old ANT build system? Developers always work with few (possibly just one) directories and always have to ChangeDir and specify the module when etics-building.

From Alessandro Maraschini -- MebSter - 25 Jun 2007

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2007-06-25 - MebSter
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ETICS All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback