dsavenko / agnostic Goto Github PK

ag build down should perform a downstream build.

Hi,

$ ag build
Component not found
$

It's really not obvious from this error message that the command (and other similar commands like test) wants ag build <component>. Especially when you just started to learn the tool and probably don't know the concept of component. :)

It would be nice to output something like Usage: ag build <component> along with the error message.

Thanks,
Alexey

It is now:

Repository: REPO (git/hg)

It is not convenient (hard to select REPO manually because of that git/hg tail).

Consider using vfork and _exit.
Even with fork it is wrong to call exit since buffered data would then be flushed twice.

Cleans build data.
ag clean 'this//component-list/all/up/down/up-constrained/down-constrained'

Allow to clone by URL of the project file.

If ssh (via git/hg) asks for fingerprint confirmation (e.g. github.com is not known yet), 'ag clone' doesn't work

ag build should about with proper return code, if build fails.

Currently, aliases there are not recognized by command like 'ag build'

Say, that some have the project file inside of a repo of some of its components (you need to keep it somewhere) and wants to symlink it to the parent directory. In this case, everything works fine except for the component, which holds the original project file. For this component, ag thinks that its folder is the root.

When ag clone <url> is implemented, one may have two identical project files without symlinks.

In any case, the project file from the parent directory should be preferred.

Provide a "Getting Started" tutorial.

Need a way to specify, which components not to touch (exclude list) for ag-script family (ag build/clean/test/etc).

Need to write proper commands help (and keep it up-to-date afterwards).

clone command should gently skip already cloned components.

Build all components.

ag diff - for the current component, or full project

A new feature for the project file: component templates. Template allows to specify any properties, which may be shared between multiple components, like build and integrate scripts. Components then may inherit templates.

Currently, it fails with segmentation fault.

ag build up <name/alias> should do upstream build from the current component to the given component by every branch, which could reach to it, but no other branches, and do not build anything further up from the given component in the affected branches.

Coloured output for commands like proj, comp.

ag version to get/set components versions.

Make a cmd to remove the project (undo ag clone).

To skip it in collective builds.

Make sure, everything works as expected

ag build down <name/alias> should do downstream build from the current component to the given component by every branch, which could reach to it, but no other branches, and do not build anything further down from the given component in the affected branches.

Fail with error, if it isn't.

Sometimes (mostly for mvn builds) 'ag' waits for a couple of seconds after the build is finished.