<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:49:17 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INFRA-87] Create pipe2d repo</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-87</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;Please create a &quot;pipe2d&quot; repo on GitHub, and give the Princeton team admin access.  This repo will host the scripts to build and test our products.  Creation of this repo is the last step required to get Continuous Integration (&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-83&quot; title=&quot;Use Travis-CI as a regression test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-83&quot;&gt;&lt;del&gt;PIPE2D-83&lt;/del&gt;&lt;/a&gt;) running routinely.&lt;/p&gt;

&lt;p&gt;Minor changes to the name (e.g., &quot;pfs_pipe2d&quot;) are fine.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11351">INFRA-87</key>
            <summary>Create pipe2d repo</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="atsushi.shimono">shimono</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                            <label>GitHub</label>
                    </labels>
                <created>Mon, 28 Nov 2016 18:13:03 +0000</created>
                <updated>Wed, 30 Nov 2016 23:17:19 +0000</updated>
                            <resolved>Wed, 30 Nov 2016 23:17:19 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="11635" author="atsushi.shimono" created="Wed, 30 Nov 2016 08:45:43 +0000"  >&lt;p&gt;I originally thought possibility to share (like as pfs_travis) among all CIs over Subaru-PFS repos, but it seems scripts are specific to LSST based ones. &lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;note; I refer &lt;a href=&quot;https://github.com/PaulPrice/pipe2d&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/PaulPrice/pipe2d&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;How about &apos;pfs_travis_pipe2d&apos; for name?&lt;/p&gt;</comment>
                            <comment id="11637" author="price" created="Wed, 30 Nov 2016 13:29:53 +0000"  >&lt;p&gt;The script that Travis runs from pipe2d is specific to the 2D pipeline (hence the name), but there&apos;s no reason other repos couldn&apos;t use Travis with their own scripts.  I&apos;m happy to help with that if you like.&lt;/p&gt;

&lt;p&gt;I would prefer &lt;b&gt;not&lt;/b&gt; to have &lt;tt&gt;travis&lt;/tt&gt; in the name of the repo because the repo will ultimately contain more than just Travis scripts.  Already the installation and integration_test scripts are useful outside Travis, and I think RHL has plans to put other things in there as well.  Can we go with &lt;tt&gt;pfs_pipe2d&lt;/tt&gt;?&lt;/p&gt;</comment>
                            <comment id="11639" author="atsushi.shimono" created="Wed, 30 Nov 2016 13:43:19 +0000"  >&lt;p&gt;ok, then go with &lt;tt&gt;pfs_pipe2d&lt;/tt&gt;.&lt;br/&gt;
could you transfer your repository to the organization (via your setting panel for that repo)?&lt;/p&gt;</comment>
                            <comment id="11641" author="price" created="Wed, 30 Nov 2016 22:51:39 +0000"  >&lt;p&gt;I cannot: it says &quot;You don&#8217;t have the permission to create repositories on Subaru-PFS&quot;.&lt;/p&gt;

&lt;p&gt;Could you please create an empty repo under Subaru-PFS, give the Princeton team admin access, and I will push contents into it.&lt;/p&gt;</comment>
                            <comment id="11642" author="atsushi.shimono" created="Wed, 30 Nov 2016 23:01:55 +0000"  >&lt;p&gt;ah. totally forgot about that restriction.&lt;br/&gt;
I&apos;ve setup, so please push existing one including branches...&lt;/p&gt;

&lt;p&gt;Once you finished, close this.&lt;/p&gt;</comment>
                            <comment id="11643" author="price" created="Wed, 30 Nov 2016 23:17:19 +0000"  >&lt;p&gt;Done!  Thanks!&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/Subaru-PFS/pfs_pipe2d&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/pfs_pipe2d&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="11153">PIPE2D-83</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii0133:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>price</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>