Michal Mocnak wrote:
> It's first preview and the flow is from my mind, actually if you
> think that something should be implemented differently, please tell
> it
Some random ideas for features that may or may not be useful:
1. Use the IDE's Diff view to show all source code changes made in a
build. (Means you need some way to map the VCS repository used by Hudson
to local sources, unless you can run diffs straight from the server.)
2. Add an action to a build to display its build log in the IDE's Output
Window (including live output, for a running build); hyperlink any
errors to local sources (again needs VCS mapping).
3. For those users without proper commit triggers set up, permit a
project build to be scheduled automatically after committing changes
from certain sources in the IDE. In principle the module could figure
out the association automatically, for CVS and Subversion at least.
4. Browse the Hudson workspace as a remote r/o filesystem, e.g. for
diagnosis of strange build failures. (Could also be integrated with #2.)
5. Add an action to the context menu of an IDE project (Ant- or
Maven-based) to create a Hudson project which builds it.
-J.
--
[hidden email] netbeans.org ant.apache.org hudson.dev.java.net
http://google.com/search?q=e%5E%28pi*i%29%2B1---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]