<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:21:40 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-2575] New CI/CD pipeline for Integration tests</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-2575</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Please, create a new CI/CD pipeline for Integration tests. The pipeline should be a copy of CI/CD for Performance tests with the exception that it should trigger Integration tests.&lt;br/&gt;
The Integration tests are created by using Karate framework.&lt;/p&gt;

&lt;p&gt;Link to the tests repo will be added as a comment to this ticket.&lt;/p&gt;

&lt;p&gt;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2574&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2574&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create folio-integration-tests github repository&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            FOLIO-2574
        &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;a href=&quot;https://github.com/folio-org/folio-integration-tests&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-integration-tests&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="81717">FOLIO-2575</key>
            <summary>New CI/CD pipeline for Integration tests</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</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="61cd0ca0bce5e00069e98be7">David Crossley</assignee>
                                                                <reporter accountid="5ef076ba60d3c80ac9ed8b81">Vasily Gancharov</reporter>
                                    <labels>
                            <label>ci</label>
                    </labels>
                <created>Wed, 29 Apr 2020 11:53:45 +0000</created>
                <updated>Thu, 13 Aug 2020 03:01:57 +0000</updated>
                            <resolved>Mon, 1 Jun 2020 14:11:10 +0000</resolved>
                                                                    <component>Continuous Integration</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>10</watches>
                                                                <comments>
                                                            <comment id="198552" author="5ef076ba60d3c80ac9ed8b81" created="Wed, 29 Apr 2020 12:03:55 +0000"  >&lt;p&gt;A ticket to create folio-integration-tests github repository for Integration tests: &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2574&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/FOLIO-2574&lt;/a&gt; &lt;/p&gt;</comment>
                                                            <comment id="198554" author="5c706fbb47a54a6728e59df2" created="Wed, 29 Apr 2020 13:27:05 +0000"  >&lt;p&gt;We will address 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2574&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2574&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create folio-integration-tests github repository&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            FOLIO-2574
        &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 this sprint, further information is needed for this ticket however. We will try to pull it into the next sprint. &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; will follow up.&lt;/p&gt;</comment>
                                                            <comment id="198557" author="5ef076ba60d3c80ac9ed8b81" created="Thu, 30 Apr 2020 08:36:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&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;, what additional information is required to fulfill this ticket?&lt;/p&gt;</comment>
                                                            <comment id="198559" author="5cffed1a5d548b0c51d6b19b" created="Mon, 4 May 2020 20:48:58 +0000"  >&lt;p&gt;The goal is to create a Jenkins job similar to &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&lt;/a&gt;&lt;br/&gt;
1) This job can use the same folio system ( if I remember correctly it is being deployed before test execution)&lt;br/&gt;
2) Instead of executing jMeter tests  it will execute API integration tests located in the folio-integration-tests repo&lt;br/&gt;
3) Any test committed to folio-integration-tests repo will be automatically picked up and executed on by this Jenkins job.&lt;br/&gt;
4) Build fails If system unavailable or failed to deploy. On the contrary, one failed test doesn&apos;t render build as failed (just like in &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&lt;/a&gt;)&lt;br/&gt;
5) Also, it would be great to have a carbon copy Jenkins job for &lt;a href=&quot;https://github.com/folio-org/folio-api-tests&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-api-tests&lt;/a&gt;&lt;br/&gt;
6) All performance and integration test jobs can be executed against the same system and it can provisioned once for all tests. My understanding that we&apos;re already doing this for folio-perf-test and folio-perf-platform jobs.&lt;/p&gt;</comment>
                                                            <comment id="198563" author="5ef076ba60d3c80ac9ed8b81" created="Thu, 14 May 2020 10:15:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&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;, on the one hand, this is a pretty important CI/CD pipeline and on the other, I believe it should be easy to implement it since it re-uses almost all steps of existing CI/CD (&lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&lt;/a&gt;). &lt;br/&gt;
Please, handle this ticket as high-priority. &lt;/p&gt;

&lt;p&gt;When DevOps team will be able to implement the pipeline?&lt;/p&gt;</comment>
                                                            <comment id="198565" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 20 May 2020 13:16:42 +0000"  >&lt;p&gt;GUys,&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&lt;/a&gt; is dedicated for Platform team&apos;s perf test and SHOULD NOT be used for any other type of testing.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&lt;/a&gt; COULD be used for running integration tests but looking at the maven build it&apos;s been broken for many weeks.&lt;/p&gt;</comment>
                                                            <comment id="198568" author="5ef076ba60d3c80ac9ed8b81" created="Fri, 22 May 2020 12:43:13 +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;, is there any ticket to fix folio-perf-test pipeline: &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&lt;/a&gt; ? Is this issue related to the pipeline itself or the environment it uses?&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;, can you please:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;base the new Integration tests pipeline on &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;use the same environment as is used by &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/&lt;/a&gt;&lt;br/&gt;
?&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="198571" author="61cd0ca0bce5e00069e98be7" created="Fri, 22 May 2020 14:05:28 +0000"  >&lt;p&gt;Regarding the folio-perf-test Jenkins job, following the general fix by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt; yesterday i expected it to be okay. There now seems to be some additional failure today. Not sure what yet. So yes, someone should raise a new ticket for that.&lt;/p&gt;

&lt;p&gt;Regarding the focus of this 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2575&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2575&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;New CI/CD pipeline for Integration tests&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-2575
        &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;
, yes, i will be doing that on Monday. Thanks for the clarification.&lt;/p&gt;</comment>
                                                            <comment id="198573" author="5ef076ba60d3c80ac9ed8b81" created="Fri, 22 May 2020 14:11:03 +0000"  >&lt;p&gt;Thank you &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;. Can I ask you to create a ticket for folio-perf-test Jenkins job fix, please, and add the link to it to this thread? &lt;br/&gt;
Appreciate your help.&lt;/p&gt;</comment>
                                                            <comment id="198576" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Fri, 22 May 2020 14:12:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;, looks like that folio-perf-platform failed to build because it was trying to get okapi version from &lt;a href=&quot;https://folio-snapshot-core-okapi.aws.indexdata.com/_/version&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-snapshot-core-okapi.aws.indexdata.com/_/version&lt;/a&gt;, but unfortunately, that site returned 503 (still does at this moment).&lt;/p&gt;</comment>
                                                            <comment id="198579" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 May 2020 11:47:40 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt;. Yes we subsequently got past that intermittent problem with folio-perf-platform Jenkins job.&lt;/p&gt;

&lt;p&gt;The failure with folio-perf-test Jenkins job is something different, and seems to have been happening for many runs. That is now described at 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2616&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2616&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Jenkins job folio-perf-test fails install second batch of modules&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-2616
        &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="198582" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 May 2020 11:49:36 +0000"  >&lt;p&gt;I have made some progress with this, but have reached some blockages.&lt;/p&gt;

&lt;p&gt;There is a Jenkins job &quot;folio-integration&quot; which is essentially a replica of the folio-perf-test Jenkins job. It utilises a new Jenkinsfile.integration in &lt;a href=&quot;https://github.com/folio-org/folio-perf-test&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-perf-test&lt;/a&gt; (on a branch at the moment).&lt;/p&gt;

&lt;p&gt;That uses the configuration and resources in folio-perf-test repo to set up the FOLIO instance. Until 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2616&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2616&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Jenkins job folio-perf-test fails install second batch of modules&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-2616
        &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;
 is solved, this setup is using the module install lists from folio-snapshot-core reference environment (it should eventually be using folio-snapshot). Yes, the integration tests will fail against that temporary setup.&lt;/p&gt;

&lt;p&gt;The Jenkins job then goes on to checkout the folio-integration-tests repo and run maven there to operate the tests. Using a branch there which accepts the Okapi IP address of the test instance.&lt;/p&gt;

&lt;p&gt;Currently failing because we also need a away to provide the admin user credentials, so that the maven tests can login, install tenants, and run the tests.&lt;/p&gt;</comment>
                                                            <comment id="198585" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Tue, 26 May 2020 15:32:45 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;, I added a comment to 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2616&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2616&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Jenkins job folio-perf-test fails install second batch of modules&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-2616
        &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;
. Basically it is blocked by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;ERM-903&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/ERM-903&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Migration scripts has hardcoded diku tenant&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            ERM-903
        &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;MODSOURMAN-318&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODSOURMAN-318&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Remove hardcoded diku tenant in db schema.json&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODSOURMAN-318
        &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="198587" author="61cd0ca0bce5e00069e98be7" created="Wed, 27 May 2020 10:46:46 +0000"  >&lt;p&gt;Other issues are now addressed, and the recent run of Jenkins job &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-integration/14/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-integration #14&lt;/a&gt; is good.&lt;/p&gt;

&lt;p&gt;Except of course that it still does not use folio-snapshot until 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2616&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2616&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Jenkins job folio-perf-test fails install second batch of modules&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-2616
        &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="198589" author="61cd0ca0bce5e00069e98be7" created="Fri, 29 May 2020 09:41:46 +0000"  >&lt;p&gt;The 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2616&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2616&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Jenkins job folio-perf-test fails install second batch of modules&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-2616
        &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;
 is fixed, and now we have our first complete run at &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-integration/17/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-integration #17&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Still need some tweaks to the job, but this is good progress.&lt;/p&gt;</comment>
                                                            <comment id="198592" author="61cd0ca0bce5e00069e98be7" created="Mon, 1 Jun 2020 05:44:09 +0000"  >&lt;p&gt;The Jenkins job is now ready at &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/Automation/job/folio-integration/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-integration&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It uses the FOLIO system built by the configuration in the repository &quot;&lt;a href=&quot;https://github.com/folio-org/folio-perf-test&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-perf-test&lt;/a&gt;&quot; (see Jenkinsfile.integration there). That uses the set of modules from &quot;folio-snapshot&quot; reference environment daily build. So each time that the job is run, it rebuilds that system.&lt;/p&gt;

&lt;p&gt;It then follows on, to checkout master branch of the repository &quot;&lt;a href=&quot;https://github.com/folio-org/folio-integration-tests&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-integration-tests&lt;/a&gt;&quot;, and runs all of the maven tests that are configured there.&lt;/p&gt;

&lt;p&gt;The Jenkins job is configured to automatically run once per day, starting around 05:00 UTC. It could be triggered manually at other times, but be aware that the &quot;folio-snapshot&quot; reference environment must be available.&lt;/p&gt;</comment>
                                                            <comment id="198595" author="63e2a2771b13d42998e4e706" created="Fri, 7 Aug 2020 10:45:30 +0000"  >&lt;p&gt;What does the &lt;tt&gt;populate data&lt;/tt&gt; stage do in that pipeline?&lt;/p&gt;</comment>
                                                            <comment id="198597" author="63e2a2771b13d42998e4e706" created="Fri, 7 Aug 2020 10:48:04 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;It uses the FOLIO system built by the configuration in the repository &quot;folio-perf-test&quot; (see Jenkinsfile.integration there). That uses the set of modules from &quot;folio-snapshot&quot; reference environment daily build. So each time that the job is run, it rebuilds that system.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Does that mean that the &lt;tt&gt;folio-integration&lt;/tt&gt; pipeline relies on an environment built by the &lt;tt&gt;folio-perf-test&lt;/tt&gt; pipeline?&lt;/p&gt;</comment>
                                                            <comment id="198599" author="61cd0ca0bce5e00069e98be7" created="Mon, 10 Aug 2020 02:48:10 +0000"  >&lt;p&gt;No, the environments are separate.&lt;/p&gt;

&lt;p&gt;The &quot;folio-integration&quot; Jenkins job uses the &lt;a href=&quot;https://github.com/folio-org/folio-perf-test/blob/master/Jenkinsfile.integration&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Jenkinsfile.integration&lt;/a&gt; file which is housed in the repository &quot;folio-perf-test&quot;.&lt;/p&gt;

&lt;p&gt;That &quot;Jenkinsfile.integration&quot; uses the same &quot;cloudformation configuration&quot; that is provided by that &quot;folio-perf-test&quot; repository. See the &quot;sharedLib&quot; references in the various &quot;Jenkinsfile.*&quot; files there.&lt;/p&gt;

&lt;p&gt;So the configuration is very similar, to essentially piggyback on the configuration of the other older jobs. But the built environments are separate.&lt;/p&gt;</comment>
                                                            <comment id="198601" author="61cd0ca0bce5e00069e98be7" created="Mon, 10 Aug 2020 02:49:25 +0000"  >&lt;p&gt;Marc asked:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;What does the populate data stage do in that pipeline?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;The &quot;Populate data&quot; stage (of each of those pipelines that are configured via that repository) obtains a package from S3 that contains a large amount of library data, and various shell scripts to create users and load data.&lt;/p&gt;

&lt;p&gt;Search the Jenkins console output for &quot;folio-public-sample-data&quot; to see it download and unpack the huge archive, then do various postgres ops to add users, then load inventory and circulation test data.&lt;/p&gt;

&lt;p&gt;The EBSCO devops people would be able to explain better than me.&lt;/p&gt;</comment>
                                                            <comment id="198604" author="63e2a2771b13d42998e4e706" created="Mon, 10 Aug 2020 10:15:05 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="57799">MODSOURMAN-318</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="41344">ERM-903</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80767">FOLIO-1380</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81712">FOLIO-2574</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81636">FOLIO-2616</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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="10155"><![CDATA[FOLIO DevOps]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00xpl:i</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1985">DevOps: sprint 89</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 29 Apr 2020 13:27:05 +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>