 |
 |
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