[Paraview-developers] New git repo: reporting changed repo after only pull

[Moreland, Kenneth]

I tried adding your execute_process after my call to ctest_update, but I don't think it's quite working.  The problem is that the submodule update command does not get run until after the ctest_update call returns, and by that time CTest has already determined that the update has failed.

Where exactly should I be putting the execute_process?

-Ken


On 4/20/10 7:07 AM, "Dave Partyka" <dave.partyka at kitware.com> wrote:

You're going to want to add something like this in your script for initial checkout:

  execute_process(
    COMMAND \"${CTEST_GIT_COMMAND}\" submodule init
    WORKING_DIRECTORY \"${CTEST_SOURCE_DIRECTORY}\"
    )

And for each update you'll want:

  execute_process(
    COMMAND \"${CTEST_GIT_COMMAND}\" submodule update --recursive --
    WORKING_DIRECTORY \"${CTEST_SOURCE_DIRECTORY}\"
    )

Also this will be handy:

# Look for a GIT command-line client.
if(NOT DEFINED CTEST_GIT_COMMAND)
find_program(CTEST_GIT_COMMAND NAMES git git.cmd)
endif()

On Mon, Apr 19, 2010 at 7:16 PM, Dave Partyka <dave.partyka at kitware.com> wrote:
I do not know if ctest knows how to update submodules automatically. I have it on my todo list to talk to Brad King about this for the same reason for updating the ParaView dashboards here at Kitware. I'll share what I find out.


On Mon, Apr 19, 2010 at 7:13 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
Yes.  That seems to fix the problem.  However, is there a way to get ctest to run that after pulling?  Otherwise we'll still get a bunch of errors in the dashboard.

-Ken



On 4/19/10 5:09 PM, "Dave Partyka" <dave.partyka at kitware.com <http://dave.partyka@kitware.com> > wrote:

does 'git submodule update' help?

On Mon, Apr 19, 2010 at 7:02 PM, Moreland, Kenneth <kmorel at sandia.gov <http://kmorel@sandia.gov> > wrote:
I noticed something odd when converting to the new git repositories today.  After only cloning the repository, setting up the modules, and then pulling (using the --rebase flag as described on the Wiki), status reports that I have made a change in my repository even though I have not.  Here is a terminal capture of a newly cloned ParaView repository (after modules and hooks are set up).

kmorel2 0> git status                                /Users/kmorel/src/ParaView
# On branch master
nothing to commit (working directory clean)
kmorel2 1> git pull --rebase                         /Users/kmorel/src/ParaView
remote: Counting objects: 44, done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 26 (delta 20), reused 0 (delta 0)
Unpacking objects: 100% (26/26), done.