https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-397 DRP 2-D Pipeline <p>Following <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-36" title="make PFS pipeline installable with eups distrib install" class="issue-link" data-issue-key="PIPE2D-36"><del>PIPE2D-36</del></a>, regular eups binaries of the 2D DRP from master should be created to and made available, to allow users to install the latest or recent version for development and testing purposes.</p> PIPE2D-397

Create regular eups binaries from master

Story Normal Done Done price hassan Fri, 5 Apr 2019 16:37:18 +0000 Wed, 22 May 2019 12:54:37 +0000 Tue, 21 May 2019 19:35:48 +0000 0 2 <p>I've set up a job on Princeton's Jenkins server that builds the pipeline and makes a distribution whenever the pfs_pipe2d package is tagged. The same tag may be added to the other products (datamodel, obs_pfs, drp_stella) before tagging pfs_pipe2d; otherwise the tip of the master branch will be used. The pfs_pipe2d git repo is polled every 5 minutes for new tags.</p> <p>The build is done in the usual PFS stack on Tiger (<tt>source /tigress/HSC/PFS/stack/loadLSST.bash</tt>).</p> <p>Users wishing to use <tt>eups distrib install</tt> should set their <tt>EUPS_PKGROOT</tt> based on their system:</p> <ul> <li>Systems compatible with Springdale Linux 7.6 (based on Redhat/CentOS): <tt><a href="https://eups.lsst.codes/stack/redhat/el7/devtoolset-6/miniconda3-4.3.21-10a4fa6" class="external-link" rel="nofollow">https://eups.lsst.codes/stack/redhat/el7/devtoolset-6/miniconda3-4.3.21-10a4fa6</a>|https://eups.lsst.codes/stack/src|http://tigress-web.princeton.edu/~HSC/pfs-drp-2d/Linux64|http://tigress-web.princeton.edu/~HSC/pfs-drp-2d/src</tt></li> <li>All other systems: <tt><a href="https://eups.lsst.codes/stack/src" class="external-link" rel="nofollow">https://eups.lsst.codes/stack/src</a>|http://tigress-web.princeton.edu/~HSC/pfs-drp-2d/src</tt></li> </ul> <p>(Note that the first part, containing <tt>eups.lsst.codes</tt> is usually set by <tt>loadLSST.bash</tt>.)</p> <p>My suggestion is that developers tag pfs_pipe2d whenever they merge to master, and tags should be <tt>MM.mm</tt> where <tt>MM</tt> is the major version (set by the development plan) and <tt>mm</tt> is the minor version, incrementing from 0. E.g., I believe the next tag should be <tt>5.1</tt>.</p> <p>I think this is ready for prime time.</p> <p>I think this is fine and should be merged to <tt>master</tt>.</p> <p>One comment on the tags. We may need to 'reserve' the minor version for formal DRP releases. Can we use a third component, eg. <tt>pp</tt> in <tt>MM.mm.pp</tt>, for whenever developers tag <tt>pfs_pipe2d</tt>?</p> <p>That's fine with me.</p> <p>Merged to master.</p> Relates PIPE2D-36 Development Rank 0|02qpt6:508yjp Reviewers hassan Sprint 2DDRP-2019 D 2DDRP-2019 E Story Points 2.0