I suggest you ...

Pre-processing controls during a file check in.

Need a way to do pre file check in proceessing for things like source code formatting or not allowing a commit if the file doesn't compile or junit tetss don't pass. An MPX control can psuedo do this but it come after the fact the check in is comitted.

Or give use the abiility to create a custom APE for the checkin in dialog.

16 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jason Aderhold shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    We have already started on StarTeam 16.1. As of now, we wouldn’t be able to add it to 16.1 without taking something away that has already been committed. Should anything change, we’ll consider it. Otherwise, I have it on the roadmap for the next release following 16.1

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        We have many XML files checked in and much of the difference is in XML whitespace formatting or fields we don't care about. It would be nice to be able to "format" the XML on check in to reduce the number of false positives for differences.

      • Pedro Garcia commented  ·   ·  Flag as inappropriate

        I think a interesting thing would be to have a sandbox like for every user so the user would know that his file is in the server, but this file would not be promoted to the view if the pre-processing control indicate any thinkg. This way both the user and the team would be safe that the version on server is ok and that all files, even the boken ones are in the server.

      Feedback and Knowledge Base