<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:07:38 UTC 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 add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-690] folio-testing.aws.indexdata.com does not use latest stripes-connect etc.</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-690</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;As shown in the About page &lt;a href=&quot;http://folio-testing.aws.indexdata.com/about&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-testing.aws.indexdata.com/about&lt;/a&gt; this site is using:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;stripes-core 1.14.1-SNAPSHOT.610&lt;/li&gt;
	&lt;li&gt;stripes-loader&lt;/li&gt;
	&lt;li&gt;stripes-connect 2.2.1&lt;/li&gt;
	&lt;li&gt;stripes-components 0.15.0&lt;/li&gt;
	&lt;li&gt;stripes-logger 0.0.2&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;(Ignore stripes-loader for the moment: it&apos;s a special case.)&lt;/p&gt;

&lt;p&gt;As you can see, while we have a snapshot representing the latest stripes-core, we are using the most recent &lt;em&gt;released&lt;/em&gt; versions of stripes-connect, stripes-components and stripes-logger.&lt;/p&gt;

&lt;p&gt;This prevents some new facilities from working: for example, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; is unable to verify the fix for 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIT-29&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIT-29&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Newly created Item records should be in focus&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UIIT-29
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80242">FOLIO-690</key>
            <summary>folio-testing.aws.indexdata.com does not use latest stripes-connect etc.</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="5f9abc1eb45b2e007453f423">John Malconian</assignee>
                                                                <reporter accountid="5bffed52a1b46046f530c8f7">Mike Taylor</reporter>
                                    <labels>
                    </labels>
                <created>Thu, 22 Jun 2017 14:31:28 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:36 +0000</updated>
                            <resolved>Mon, 26 Jun 2017 16:18:58 +0000</resolved>
                                                                    <component>Continuous Integration</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                    <timespent seconds="21600">6 hours</timespent>
                                <comments>
                                                            <comment id="188614" author="5f9abc1eb45b2e007453f423" created="Thu, 22 Jun 2017 15:48:10 +0000"  >&lt;p&gt;I just noticed that as well.   Very strange.  It should be picking up the latest snapshot versions but it isn&apos;t.   Will check into this. &lt;/p&gt;</comment>
                                                            <comment id="188616" author="5f9abc1eb45b2e007453f423" created="Thu, 22 Jun 2017 19:58:01 +0000"  >&lt;p&gt;So the good news is that the stripes components running on folio-testing are now all from tip of master.   The bad news is that you won&apos;t know that by looking at the versions.   I&apos;ve had to roll back some of the changes I made previously in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STRIPES-420&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STRIPES-420&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Building Stripes platform from HEAD of master&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STRIPES-420
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.   In short, NPM and semver don&apos;t work as you&apos;d expect with pre-release tags.    Turns out that, for example,  0.16.1-SNAPSHOT.23 &amp;gt; 0.15.0 is NOT true.    So when stripes-core looks for other stripes dependencies like stripes-components and stripes-logger it wasn&apos;t actually getting the latest snapshots of those packages.     I&apos;ve disabled the changes I made in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STRIPES-420&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STRIPES-420&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Building Stripes platform from HEAD of master&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STRIPES-420
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 for stripes-loader, stripes-connect, stripes-components, and stripes-logger only since these packages are really the only ones called bu other modules and stripes-core. &lt;/p&gt;

&lt;p&gt;We should revisit this and try to come up with a better solution.  I thought it best, however, to &lt;b&gt;just make it work for now&lt;/b&gt; so that other things don&apos;t break. &lt;/p&gt;</comment>
                                                            <comment id="188619" author="5bffed52a1b46046f530c8f7" created="Thu, 22 Jun 2017 22:01:44 +0000"  >&lt;p&gt;Thanks, John. But &amp;#8211; I may be being dumb here &amp;#8211; I don&apos;t understand. How have you got this running from the tip of master but displaying the version-numbers of the last releases?&lt;/p&gt;</comment>
                                                            <comment id="188621" author="5f9abc1eb45b2e007453f423" created="Fri, 23 Jun 2017 13:12:37 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; Every time there is a commit to master,  a build is triggered in Jenkins which, for Stripes and UI modules,  essentially does an &apos;npm install&apos; and &apos;npm publish&apos;.   The &apos;publish&apos; is performed to a CI NPM repository.    The package versions that are published are the same versions specified in the package.json and the existing package in the CI NPM repository from the previous  CI build is overwritten with the latest one.  That is why the package version is the same as the &apos;released&apos; version but  the contents are HEAD of master. &lt;/p&gt;

&lt;p&gt;This is less than ideal of course, because you&apos;d like more accurate information about which version of an NPM package you are using which is the problem I attempted to solve in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STRIPES-420&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STRIPES-420&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Building Stripes platform from HEAD of master&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STRIPES-420
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, however, because of the lame way NPM handles &quot;prerelease&quot; dependency resolution, the solution implemented in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STRIPES-420&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STRIPES-420&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Building Stripes platform from HEAD of master&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STRIPES-420
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 caused problems with some of the core stripes packages which is why I&apos;ve had to reverse some of the changes I made to how those core stripes dependencies are packaged for snapshot testing.  &lt;/p&gt;

&lt;p&gt;Let me know if this still doesn&apos;t make sense.    I&apos;d like to solve this problem for all NPM snapshot packages but, at the same time, I don&apos;t want to break everything while trying to figure out a better solution. &lt;/p&gt;

</comment>
                                                            <comment id="188623" author="5bffed52a1b46046f530c8f7" created="Fri, 23 Jun 2017 13:16:31 +0000"  >&lt;p&gt;Thanks, John, got it. The key bit I was missing i that you are now &lt;em&gt;overwriting&lt;/em&gt; your previous build/install of the package each time.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;0.16.1-SNAPSHOT.23 &amp;gt; 0.15.0 is NOT true&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;That is so broken it hurts. Is it special to &quot;SNAPSHOT&quot;? Could we use some other term?&lt;/p&gt;

&lt;p&gt;Or just use super-high patchlevels, like 0.16.10003&lt;/p&gt;</comment>
                                                            <comment id="188624" author="5f9abc1eb45b2e007453f423" created="Fri, 23 Jun 2017 14:22:44 +0000"  >&lt;p&gt;Super-high patchlevels is an interesting idea.  I like it.  Let me chew on that. &lt;/p&gt;</comment>
                                                            <comment id="188625" author="5bffed52a1b46046f530c8f7" created="Mon, 26 Jun 2017 15:43:05 +0000"  >&lt;p&gt;John, why don&apos;t you close this one &amp;#8211; since the actual bug is fixed &amp;#8211; and add a new one for the nicer generated-package version numbers?&lt;/p&gt;</comment>
                                                            <comment id="188626" author="5f9abc1eb45b2e007453f423" created="Mon, 26 Jun 2017 16:18:58 +0000"  >&lt;p&gt;Closing issue.  Opened related issue 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-696&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-696&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Rethink NPM package versioning for generating packages from HEAD. &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-696
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 to investigate other solutions for CI package versioning. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80211">FOLIO-696</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="38987">UIIT-29</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxpqn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 22 Jun 2017 15:48:10 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>