Menu

#19 Monitor Multiple Source Control Directories

Next Release
open
8
2004-08-13
2003-12-01
Melly
No

I would also like to see token based check-ins. Also,
the ability to monitor multiple directories. If either of
the ones I've mentioned have been worked please feel
free to let me know. Thanks.

Discussion

  • Ryan Cromwell

    Ryan Cromwell - 2004-04-22

    Logged In: YES
    user_id=858689

    I very much second this. The only reason we will be most
    likely selecting CC.Net is because of the inibility to provoke a
    build when references have changed.

     
  • Michael Ferrante

    • priority: 5 --> 7
    • assigned_to: nobody --> michaelferrante
    • summary: Two Features --> Monitor Multiple Source Control Directories
     
  • Michael Ferrante

    Logged In: YES
    user_id=956382

    The feature for monitoring multiple source control directories
    has been partially implemented, only for Visual SourceSafe.

     
  • Michael Ferrante

    • priority: 7 --> 9
     
  • Michael Ferrante

    • priority: 9 --> 8
     
  • Klaus Oberhofer

    Klaus Oberhofer - 2004-10-20

    Logged In: YES
    user_id=653977

    It would be nice if monitoring and getting could be split
    into two separate tasks, because I want to:

    1. Draco monitors two VSS directories ($/project and $/build)
    2. Draco detects changes
    3. Draco gets the $/build directory and calls a Nant script
    4. The nant script labels the $/build directory
    5. The nant script gets the $/build directory at the
    labelled moment
    6. The nant script does the build

    If I could disable the get within Draco for one of the
    monitored repositories, I could spare one unnecessary get
    operation .
    I would also prever to split "monitoring" and "building"
    within the Draco buildconfig file into two separate XML
    elements, even it would mean to loose backward compatibility.

     

Log in to post a comment.