Hello Jacek,

Well done, you're process is the right one.

Here are the three required steps :

1. install Qserv from git with eupspkg (cf. README-devel.txt, which 
seems right) : this is a eups standard and works for all LSST packages.
2. configure Qserv (cf. README.txt)
3. run integration tests (cf. README.txt)

4. A new step could be added to explain how to rebuild and install an 
updated version of a git repos.
We should ask Mario to get the right answer about it.

I have no idea about how to simplify, because I think it's good that 
developper understand the three previous steps.
We may discuss this during out next Qserv meeting ?

Maybe a script a bit like the one ised with "git bisect" :
tests/tools/run-tests.sh
could be OK ?

Some more details :

1. Please note that the zookeeper data and mysql data aren't removed : 
they're still available with in your previous Qserv instance installdir.
2. Note also that the above part can be a bit simplified :

---
setup qserv <the new version>

# this basically wipes out everything: zookeeper data, mysql data...
# but if I don't do that, I won't have scripts from admin/bin
# for starting/stopping qserv, so I can't skip it. This really
# needs to be fixed...
cd $QSERV_DIR/admin
scons

# if I want to run integration tests, it looks like this is needed too:
setup qserv_testdata
cd $QSERV_DIR/admin
scons client

# and then I need to start services
qserv-start.sh
---

with :

---
setup qserv <the new version>
# if I want to run integration tests, it looks like this is needed too:
setup qserv_testdata

# this basically wipes out everything: zookeeper data, mysql data...
# but if I don't do that, I won't have scripts from admin/bin
# for starting/stopping qserv, so I can't skip it. This really
# needs to be fixed...
cd $QSERV_DIR/admin
scons

# and then I need to start services
qserv-start.sh
---

Cheers,

Fabrice

On 05/24/2014 08:46 AM, Jacek Becla wrote:
> I am playing with switching branches in my local qserv.
> It is actually quite a process! Here is what I found
> so far:
>
>
> # I won't have access to the PIDs for already
> # running services, so better to stop them now.
> # That is because things are run from a place that
> # looks like:
> # ~/stack/Linux64/qserv/master-ga7082f1e02/,
> # and we will switch to something like:
> # ~/stack/Linux64/qserv/tickets.DM-630-gb26efd78da
> qserv-stop.sh
>
> # switch branch
> cd ~/repo/qserv
> git checkout tickets/DM-630
>
> # build, install
> eupspkg -er build
> eupspkg -er install
>
> # this is only needed if it is the very first time
> # I work with a given version of the branch
> eupspkg -er decl
>
> setup qserv <the new version>
>
> # this basically wipes out everything: zookeeper data, mysql data...
> # but if I don't do that, I won't have scripts from admin/bin
> # for starting/stopping qserv, so I can't skip it. This really
> # needs to be fixed...
> cd $QSERV_DIR/admin
> scons
>
> # if I want to run integration tests, it looks like this is needed too:
> setup qserv_testdata
> cd $QSERV_DIR/admin
> scons client
>
> # and then I need to start services
> qserv-start.sh
>
> then qserv-testdata.py should work
>
> This is quite complex and error prone and easy to get wrong.
> Could we possibly simplify it?
>
> Jacek
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the QSERV-L list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1