<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:14:22 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-1577] Automated builds for FOLIO &apos;release&apos;</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1577</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;&lt;b&gt;Summary&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Continuously integrate and test new releases of both front-end and server-side components into&lt;br/&gt;
a current and stable FOLIO instance that is accessible to POs, developers, and manual testers. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Implement automated build pipelines for stripes platforms (platform-core and platform-complete) &lt;br/&gt;
designed to integrate newly released modules into a stable FOLIO instance based solely on &lt;br/&gt;
&quot;released&quot; versions of artifacts.  PRs will be submitted in order add and test newly released &lt;br/&gt;
stripes and UI modules into the on-going, stable release branch (master) of each platform&apos;s git &lt;br/&gt;
repository.  The PRs can either be manually created or generated automatically by an NPM dependency&lt;br/&gt;
bot app that integrates with Github like Renovate or Greenhopper. These bots check for NPM &lt;br/&gt;
dependency updates for specified NPM packages and repositories and automatally initiate&lt;br/&gt;
pull requests to merge updated dependencies.  Each PR will first trigger a build of the stripes&lt;br/&gt;
platform, and, if successful will then attempt to build a FOLIO full stack by utlizing Okapi&apos;s &lt;br/&gt;
&quot;install&quot; endpoint to resolve required interface dependencies provided by released server-side &lt;br/&gt;
modules.  If the build is successful, the UI integration test suite is run against the built &lt;br/&gt;
FOLIO instance.  If all tests pass, the PR can be then be merged to the stable release branch &lt;br/&gt;
of the platform which will, in turn, can be used to build a publically accessible current and&lt;br/&gt;
stable instance of FOLIO that can be used for additional testing/demos, etc.  &lt;/p&gt;

&lt;p&gt;The PR test process includes the following quality gates:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Successful webpack build of the stripes platform.  If the stripes platform cannot be built,&lt;br/&gt;
then the PR will fail. &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Successful interface dependency resolution between frontend and backend modules (releases only).&lt;br/&gt;
If the new frontend module requires an interface that cannot be resolved by a released backend &lt;br/&gt;
module, then PR will fail.  This will ensure that frontend and backend module releases are &lt;br/&gt;
coordinated.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Successful build of FOLIO instance to ensure installation processes are configured and working&lt;br/&gt;
as expected and tenent initialization is successful.  &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Ensure passing UI integration tests to indicate either successful integration of the new module&lt;br/&gt;
into the platform or to ensure tests are kept and current and compatible with new functionality.  &lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Tools/Platforms&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Each platform git repository will be integated with a Jenkins pipeline responsible for coordinating &lt;br/&gt;
builds and testing using additional tools like folio-ansible and AWS.  Each platform will also &lt;br/&gt;
be configured with a NPM dependency bot like Renovate to provide updates to the platform and &lt;br/&gt;
initiate PRs. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;Additional Outputs&lt;/b&gt;&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;An automatically updated &quot;next-release&quot; FOLIO instance. e.g &lt;a href=&quot;http://folio-release.aws.indexdata.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-release.aws.indexdata.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;A yarn.lock file representing a stable set of fixed NPM dependencies committed to the platform&apos;s&lt;br/&gt;
stable, release branch. &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;install.json files committed to each platform&apos;s stable, release branch that can be used to&lt;br/&gt;
build a FOLIO system from the most recent set of released and stable module. &lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Prerequisites/Considerations&lt;/b&gt;&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Front-end and backend module releases must occur on a regular, continuous basis in order&lt;br/&gt;
for this process to work.  Integration is more successful at regular, steady intervals (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1614&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1614&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;SPIKE: decide on frequency of releases&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-1614
        &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;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;An existing set of released compatible modules must be exist in order to build initial system&lt;br/&gt;
(initial set to be based on Q4 release).  &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;AWS resource utilization. We need to design a system that is cognizant of AWS resource&lt;br/&gt;
utilization.  Each PR will utilize an AWS EC2 instance and attached storage to build a&lt;br/&gt;
FOLIO stack.  Additionally,  the process could be simplified to initialize a new tenant&lt;br/&gt;
for each PR on an existing okapi cluster as long as larger number of released backend modules&lt;br/&gt;
can be distributed across a cluster.  Such a setup would most likely require additional &lt;br/&gt;
orchestration tools, however.  These ideas can be explored at a latter stage. &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Determine how new backend module releases that are not explicitly required by frontend&lt;br/&gt;
modules will be integrated into stable, release system. &lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Some Renovate initiated changes will fail, e.g consider the following scenario:&lt;br/&gt;
   &quot;PR is issued to include new ui-users that depends on mod-circulation v2 but ui-checkin still depends on v1&quot; in this and similar cases, a manual intervention will be required and a single PR that updates all ui- versions and a version of a shared dependency will be needed&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Definition of Done&lt;/b&gt;&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Determine if prerequisites and considerations described above have been initially addressed.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Implement the process as described above and produce initial folio-release instances&lt;br/&gt;
for platform-core and platform-complete. &lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="80951">FOLIO-1577</key>
            <summary>Automated builds for FOLIO &apos;release&apos;</summary>
                <type id="10006" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium">Umbrella</type>
                                            <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</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="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                            <label>ci</label>
                            <label>platform-backlog</label>
                            <label>q1-2019</label>
                            <label>sprint49</label>
                            <label>sprint50</label>
                            <label>sprint51</label>
                            <label>sprint52</label>
                            <label>sprint53</label>
                            <label>sprint54</label>
                    </labels>
                <created>Fri, 12 Oct 2018 18:31:47 +0000</created>
                <updated>Thu, 4 Apr 2019 13:48:21 +0000</updated>
                            <resolved>Thu, 4 Apr 2019 13:48:21 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>11</watches>
                                                                <comments>
                                                            <comment id="192733" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 24 Oct 2018 12:52:09 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; any relation to what we are discussing as 1. on 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1827&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1827&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;CI-integrated continuous deployment (Q3, FOLIO setup)&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;
            UXPROD-1827
        &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;</comment>
                                                            <comment id="192736" author="5f9abc1eb45b2e007453f423" created="Thu, 25 Oct 2018 17:17:47 +0000"  >&lt;p&gt;This is blocked due to the fact that we have not yet established a regular release interval for modules.   It is currently not possible to build a working folio instance based on the next-release branch of either platform-core or platform-complete because &lt;/p&gt;

&lt;p&gt;1. The requisite backend modules required by frontend modules have not been released.   The &apos;next-release&apos; platform needs to be based solely on released frontend and backend modules.   It is not sufficient to use  snapshot versions of backend modules because sample data needs to be pinned to tagged releases. &lt;/p&gt;

&lt;p&gt;2. The current configuration of frontend modules have conflicting interface dependency requirements. &lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;jenkins@8e6da5a15783:~/platform-core$ curl -X POST -d @stripes-install.json -H &apos;Content-Type: application/json&apos; &quot;http://next-release-core.aws.indexdata.com:9130/_/proxy/tenants/test1/install?simulate=true&amp;amp;preRelease=false&quot;
Incompatible version for module mod-inventory-10.0.0 interface item-storage. Need 6.0. Have 5.3
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="192739" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 30 Oct 2018 11:22:39 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; keeping this aligned would require keeping track of all module releases and pushing fro a release where one is missing. This would be the same as we do with Q-releases where we coordinate a spreadsheet of all module versions. Do you want to do something like that here or did you have something else in mind?&lt;/p&gt;</comment>
                                                            <comment id="192741" author="5f9abc1eb45b2e007453f423" created="Tue, 30 Oct 2018 18:56:16 +0000"  >&lt;p&gt;I created a Q4 release spreadsheet similar to the Q3 release spreadsheet.    The link is included in the &apos;release-q4-2018&apos; Slack channel.   &lt;/p&gt;</comment>
                                                            <comment id="192743" author="5f9abc1eb45b2e007453f423" created="Wed, 31 Oct 2018 17:50:27 +0000"  >&lt;p&gt;Specifically,  we need updated releases for mod-inv, mod-inv-storage, mod-circ, mod-circ-storage, and mod-users-bl (service-points).  &lt;/p&gt;</comment>
                                                            <comment id="192745" author="5cffed1a5d548b0c51d6b19b" created="Tue, 6 Nov 2018 22:18:51 +0000"  >&lt;p&gt;Reached out to &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c38e8d616ac1e4f7cbc660a&quot; class=&quot;user-hover&quot; rel=&quot;5c38e8d616ac1e4f7cbc660a&quot; data-account-id=&quot;5c38e8d616ac1e4f7cbc660a&quot; accountid=&quot;5c38e8d616ac1e4f7cbc660a&quot; rel=&quot;noreferrer&quot;&gt;Kurt Nordstrom&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; via email to help with the latest releases of the above modules&lt;/p&gt;</comment>
                                                            <comment id="192748" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 7 Nov 2018 08:44:45 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; Guys, I&apos;d like to understand why we need those modules released &amp;#8211; is it because (released) ui-modules require new versions of their backend dependencies? Is there a problem creating the Q4/next-release environment with the set of last released modules?&lt;/p&gt;

&lt;p&gt;We will cover release planning for backend modules in the coming days/early next week and come up with a schedule for November. I&apos;d like this schedule to be focused on delivering support for planned features though so I&apos;d like to know if there are other factors that would prompt certain releases.&lt;/p&gt;</comment>
                                                            <comment id="192751" author="63e2a2771b13d42998e4e706" created="Wed, 7 Nov 2018 09:02:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; My understanding is there have already been new features added to some of the backend modules (mod-circulation, mod-circulation-storage, mod-inventory, mod-inventory-storage and mod-users-bl) that have changed the interface versions.&lt;/p&gt;

&lt;p&gt;These new versions have become dependencies of the current versions of the UI modules, and so it is not possible to build the first iteration of the Q4 without formal releases of these modules, as they currently stand.&lt;/p&gt;

&lt;p&gt;My intention was to attempt to make those releases today.&lt;/p&gt;

&lt;p&gt;Mod-inventory-storage is a little challenging as we do not want to release the head of master at this point. My intention here was to branch from a previous revision, release from there and then manually update master with the news and a new implementation version.&lt;/p&gt;

&lt;p&gt;I am aware this isn&apos;t ideal, and I would&apos;ve preferred not to commit anything to master whilst we are working on the current issues. I&apos;d like &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed5e2434bf3a1a91d37a&quot; class=&quot;user-hover&quot; rel=&quot;5bffed5e2434bf3a1a91d37a&quot; data-account-id=&quot;5bffed5e2434bf3a1a91d37a&quot; accountid=&quot;5bffed5e2434bf3a1a91d37a&quot; rel=&quot;noreferrer&quot;&gt;Niels Erik Nielsen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; thoughts on whether this sounds like the most sensible approach?&lt;/p&gt;

&lt;p&gt;We should anticipate needing further releases fairly soon, of at least mod-circulation (likely a minor and a major) for the service points related changes, and of mod-inventory-storage (minor) for the second phase of additional holdings properties (&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed5e2434bf3a1a91d37a&quot; class=&quot;user-hover&quot; rel=&quot;5bffed5e2434bf3a1a91d37a&quot; data-account-id=&quot;5bffed5e2434bf3a1a91d37a&quot; accountid=&quot;5bffed5e2434bf3a1a91d37a&quot; rel=&quot;noreferrer&quot;&gt;Niels Erik Nielsen&lt;/a&gt; correct me if I am wrong).&lt;/p&gt;</comment>
                                                            <comment id="192754" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 7 Nov 2018 09:10:05 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; let&apos;s hold off on making releases for now. The ui- modules that you are referring to: are those snapshots (tip of master)? If so, are we saying that there is an expectation that for non-release (snapshot) versions of ui- modules all backend modules (with corresponding releases) need to be released? &lt;/p&gt;</comment>
                                                            <comment id="192755" author="5bffed5e2434bf3a1a91d37a" created="Wed, 7 Nov 2018 10:24:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; that&apos;s correct; we merged but did not yet release first phase (minor) of holdings properties and there is an upcoming second phase (also minor) and a third phase (major) for holdings properties. &lt;/p&gt;</comment>
                                                            <comment id="192758" author="63e2a2771b13d42998e4e706" created="Wed, 7 Nov 2018 10:49:38 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; Ok, based upon that, and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; comment yesterday, I shall not work on releasing any of these modules until further notice.&lt;/p&gt;

&lt;p&gt;Whether the UI modules had already been, or were intended to also be released, for this initial build, was a question I was trying to figure out when to ask. I would like to gain a better understanding of what is intended to go in the environment and the process for updating it.&lt;/p&gt;

&lt;p&gt;However, I deferred asking about that, as I wanted to be clear as to what the immediate requirements were for me, and didn&apos;t want to distract from that (or give the impression I was avoiding them).&lt;/p&gt;</comment>
                                                            <comment id="192761" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 8 Nov 2018 12:00:47 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; Guys, my guess would be that the &apos;next-release&apos; should include ONLY released modules, bottom to top, both UI and backend. Is this a valid assumption?&lt;/p&gt;</comment>
                                                            <comment id="192763" author="5f9abc1eb45b2e007453f423" created="Thu, 8 Nov 2018 12:53:48 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; yes.  absolutely.&lt;/p&gt;</comment>
                                                            <comment id="192764" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 14 Nov 2018 11:55:41 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Cool, so I think we are on the same page. If so, are you saying that some of the &lt;b&gt;released&lt;/b&gt; UI modules are missing backend dependencies? If so which UI modules and versions are those? It would seem to be that it is a problem with the release process that would allow releasing modules with unreleased dependencies.&lt;/p&gt;</comment>
                                                            <comment id="192767" author="63e2a2771b13d42998e4e706" created="Wed, 14 Nov 2018 12:26:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; Am I understanding you correctly, that we need to check that an interface dependency is fulfilled by at least one &lt;b&gt;formally released&lt;/b&gt; module version (excluding snapshots) during a dependent module release, and fail / deny the release if that isn&apos;t satisfied?&lt;/p&gt;</comment>
                                                            <comment id="192769" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 14 Nov 2018 15:38:13 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; is there a way to extend this message:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
jenkins@8e6da5a15783:~/platform-core$ curl -X POST -d @stripes-install.json -H &lt;span class=&quot;code-quote&quot;&gt;&apos;Content-Type: application/json&apos;&lt;/span&gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;http:&lt;span class=&quot;code-comment&quot;&gt;//next-release-core.aws.indexdata.com:9130/_/proxy/tenants/test1/install?simulate=&lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;&amp;amp;preRelease=&lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;&quot;&lt;/span&gt;
&lt;/span&gt;Incompatible version &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; module mod-inventory-10.0.0 &lt;span class=&quot;code-keyword&quot;&gt;interface&lt;/span&gt; item-storage. Need 6.0. Have 5.3
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;so that we see what module needs the interface in question?&lt;/p&gt;</comment>
                                                            <comment id="192772" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 14 Nov 2018 15:54:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; we have discussed that &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; will investigate what is the cause for the above failure but will not attempt to perform any &quot;recovery&quot; releases right now, instead we will plan new releases for backend and front-end that will coincide with the Q4 release plan.&lt;/p&gt;</comment>
                                                            <comment id="192774" author="5f9abc1eb45b2e007453f423" created="Wed, 14 Nov 2018 17:24:58 +0000"  >&lt;blockquote&gt;
&lt;p&gt;jenkins@8e6da5a15783:~/platform-core$ curl -X POST -d @stripes-install.json -H &apos;Content-Type: application/json&apos; &quot;http://next-release-core.aws.indexdata.com:9130/_/proxy/tenants/test1/install?simulate=true&amp;amp;preRelease=false&quot;&lt;br/&gt;
Incompatible version for module mod-inventory-10.0.0 interface item-storage. Need 6.0. Have 5.3&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Just to elaborate on this particular error: &lt;/p&gt;

&lt;p&gt;The following UI modules require item-storage 5.0 OR 6.0:&lt;/p&gt;

&lt;p&gt;ui-checkin v1.3.0&lt;br/&gt;
ui-checkout v1.3.0&lt;br/&gt;
ui-inventory v1.4.0&lt;/p&gt;

&lt;p&gt;mod-inventory-storage v13.0.1 provides item-storage 6.0&lt;br/&gt;
mod-inventory v10.0.0 also requires item-storage 6.0&lt;/p&gt;

&lt;p&gt;So far so good.   However,   the last released version of mod-circulation v12.0.0 requires item-storage 5.3.     In order to satisfy the mod-circulation requirement,  an older version of mod-inventory-storage that provides item-storage 5.3 is enabled instead of v13.0.1.   Since the UI modules require item-storage 5.0 or 6.0,  the UI modules are happy,  however, mod-inventory still requires 6.0.&lt;/p&gt;

</comment>
                                                            <comment id="192776" author="5f9abc1eb45b2e007453f423" created="Wed, 14 Nov 2018 17:38:02 +0000"  >&lt;p&gt;So I guess the next question is why didn&apos;t okapi attempt to downgrade mod-inventory to a version that requires item-storage 5.  mod-inventory-9.5.0 requires item-storage 5.3.   That&apos;s because there are other dependencies at play here.    mod-inventory-9.5.0 provides inventory 6.4, however, ui-inventory needs inventory 7.0&lt;/p&gt;</comment>
                                                            <comment id="192778" author="63e2a2771b13d42998e4e706" created="Thu, 15 Nov 2018 10:33:34 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; for digging deeper into this.&lt;/p&gt;

&lt;p&gt;UI Inventory requiring only &lt;tt&gt;inventory 7.0&lt;/tt&gt;, which is provided only by mod-inventory 10.0.0 which requires only &lt;tt&gt;item-storage 6.0&lt;/tt&gt; effectively forces the resolution to &lt;tt&gt;item-storage 6.0&lt;/tt&gt; across the board.&lt;/p&gt;

&lt;p&gt;Hmm, as far as I can tell, the latest tagged released version of mod-circulation 12.1.0 supports &lt;tt&gt;item-storage 5.3&lt;/tt&gt; or &lt;tt&gt;item-storage 6.0&lt;/tt&gt;. This was done last week (&lt;a href=&quot;https://jenkins-aws.indexdata.com/job/folio-org/job/mod-circulation/view/tags/job/v12.1.0/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/folio-org/job/mod-circulation/view/tags/job/v12.1.0/&lt;/a&gt;) and published to the registry (&lt;a href=&quot;http://folio-registry.aws.indexdata.com/_/proxy/modules/mod-circulation-12.1.0&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-registry.aws.indexdata.com/_/proxy/modules/mod-circulation-12.1.0&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;I wonder what meant this wasn&apos;t picked up?&lt;/p&gt;

&lt;p&gt;Maybe there is something else that is forcing resolution to &lt;tt&gt;item-storage 5.3&lt;/tt&gt; and so we have an unresolvable divergence. What I&apos;m less sure about is why the conflict was discovered at mod-inventory.&lt;/p&gt;

&lt;p&gt;Did you try this build yesterday?&lt;/p&gt;</comment>
                                                            <comment id="192781" author="5f9abc1eb45b2e007453f423" created="Thu, 15 Nov 2018 14:37:56 +0000"  >&lt;p&gt;No,  I haven&apos;t tried a build for a couple of weeks so it&apos;s probable the item-storage/mod-circulation issue has been resolved.   I&apos;ll try another build today. &lt;/p&gt;</comment>
                                                            <comment id="192783" author="63e2a2771b13d42998e4e706" created="Thu, 15 Nov 2018 15:29:39 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Thanks, I&apos;ll be curious to see if mod-circulation 12.1.0 is picked up and resolves this, or if there is something else driving this version conflict&lt;/p&gt;</comment>
                                                            <comment id="192786" author="5f9abc1eb45b2e007453f423" created="Mon, 19 Nov 2018 19:50:14 +0000"  >&lt;p&gt;Next build error while attempting to build platform-core/next-release with releases only: &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Incompatible version for module mod-users-bl-4.0.2 interface service-points. Need 2.1. Have 3.0
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;mod-inventory-storage 13.0.1 provides service-points 3.0 but the last release of mod-users-bl, v4.0.2 requires service-points 2.1.  A new release of mod-users-bl compatible with service-points 3.0 is required. &lt;/p&gt;</comment>
                                                            <comment id="192787" author="5f9abc1eb45b2e007453f423" created="Mon, 25 Mar 2019 12:24:43 +0000"  >&lt;p&gt;This issue has been essentially superceded/duplicated by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1738&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1738&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;PR build pipeline for platform-core releases&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-1738
        &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;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1739&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1739&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;PR build pipeline for platform-complete releases&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-1739
        &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;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="80889">FOLIO-1596</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="80776">FOLIO-1519</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81119">FOLIO-1738</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81118">FOLIO-1739</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81120">FOLIO-1740</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81122">FOLIO-1742</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="54146">OKAPI-683</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="80538">FOLIO-1043</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80902">FOLIO-1614</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80935">FOLIO-1631</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="54147">OKAPI-684</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80963">FOLIO-1597</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80892">FOLIO-1602</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81075">FOLIO-1755</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10809">UXPROD-1155</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10863">UXPROD-1428</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_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxlg7:</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>Wed, 24 Oct 2018 12:52:09 +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>