Difference: TestStrippingLineGit (11 vs. 12)

Revision 122017-12-08 - StefanieReichert

Line: 1 to 1
 
META TOPICPARENT name="LHCbStripping"
-- RicardoVazquezGomez - 2016-09-07

Test a Stripping line with git (work in progress)

Line: 11 to 11
 

Setup the environment

Changed:
<
<
Before you can test a stripping line you need to set up the environment. In order to do that, setup DaVinci as follows (XX, YY and ZZ are placeholders for the correct version of DaVinci to be used for testing which will be announced at the beginning of every campaign by the stripping coordinators)
>
>
Before you can test a stripping line you need to set up the environment. In order to do that, setup DaVinci as follows (XX, YY and ZZ are placeholders for the correct version of DaVinci to be used for testing which will be announced at the beginning of every campaign by the stripping coordinators). If you are unsure, check with the Stripping liaison of your WG.
 
lb-dev DaVinci/vXXrYYpZZ
cd DaVinciDev_vXXrYYpZZ
Line: 21 to 21
 
git lb-use Stripping
Changed:
<
<
then checkout and compile StrippingSelections from the master
>
>
then checkout and compile StrippingSelections from the master or the currently used branch for the development of a certain Stripping campaign (check with liaisons if unsure). In this example, we assume master is the correct branch to use.
 
git lb-checkout Stripping/master Phys/StrippingSelections
make configure
Line: 40 to 40
 
cp <path_of_your_file/StrippingMyCharmDecay.py Phys/StrippingSelections/python/StrippingSelections/StrippingCharm/>
Changed:
<
<
Since this is a new line, it has to be added to Phys/StrippingSelections/python/StrippingSelections/StrippingCharm/__init__.py in the, open the init.py file with your favourite editor and add your line to the end of the "_selections" list at the beginning of the file (omit the .py extension)
>
>
Since this is a new line, it has to be added to Phys/StrippingSelections/python/StrippingSelections/StrippingCharm/__init__.py in the, open the init.py file with your favourite editor and add your line to the end of the "_selections" list at the beginning of the file (omit the .py extension)
 
_selections = [ "StrippingSomeCharm","StrippingSomeOtherCharm", "StrippingMyCharmDecay"]
Line: 103 to 103
 

Before I commit my stripping line

Changed:
<
<
Once you have successfully tested your line inform your WG group liaison about the results of the testing and ask for permission to commit to git. For new lines, please inform also the coordinators before committing the new code.
>
>
Once you have successfully tested your line inform your WG group liaison about the results of the testing and ask for permission to commit to git. For new lines, please inform also the coordinators before committing the new code. Add the results of the tests as comment to the merge request.
 

Commit a new or modified line

Line: 139 to 139
  In the gitlab web page https://gitlab.cern.ch/lhcb/Stripping you can find all of the existing branches under Repository/Branches. Once you are satisfied with the results of your work you can ask to merge your branch with the master, so the changes or new lines will be executed in the next stripping campaign. To do so, click on the box Merge Request that follows the name of the branch, and the coordinators will check your changes and eventually accept it. You will be contacted by the coordinators in case that they found something to be changed.
Deleted:
<
<
REMEMBER ALWAYS TO ASK FOR THE MERGE REQUEST ONCE YOU ARE SATISFIED WITH THE CHANGES
 \ No newline at end of file
Added:
>
>
REMEMBER ALWAYS TO ASK FOR THE MERGE REQUEST ONCE YOU ARE SATISFIED WITH THE CHANGES. AND CHECK HOW THAT YOUR MERGE REQUEST CONTAINS ONLY YOUR OWN CHANGES!
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback