<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:25: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-3067] Replace Jenkins UI and Stripes CI pipelines with Github Action pipelines</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-3067</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Replace existing Jenkins CI pipelines with comparable Github Actions workflows for all Stripes and UI module repositories in folio-org.    This is an umbrella issue.   Specific tasks should be linked to this issue.  &lt;/p&gt;</description>
                <environment></environment>
        <key id="82084">FOLIO-3067</key>
            <summary>Replace Jenkins UI and Stripes CI pipelines with Github Action pipelines</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="10005" iconUrl="https://dev.folio.org/assets/jira-priority/tbd.svg">TBD</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="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30">Ankita Sen</assignee>
                                                                <reporter accountid="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                    </labels>
                <created>Tue, 9 Mar 2021 16:40:33 +0000</created>
                <updated>Mon, 13 Feb 2023 09:22:25 +0000</updated>
                            <resolved>Mon, 13 Feb 2023 09:22:25 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                                                            <comment id="196668" author="5f9abc1eb45b2e007453f423" created="Tue, 9 Mar 2021 19:25:51 +0000"  >&lt;p&gt;Following the work completed by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; in the spike 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2913&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2913&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;SPIKE: Evaluate Github Actions&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-2913
        &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;
,  we can now proceed toward a goal of replacing existing folio-org UI and Stripes modules Jenkins CI pipelines with Github Actions workflows.    The following prerequisites need to be met before rollout can commence.  &lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Github Actions workflows for branch builds, PRs, master branch builds, and tagged release builds need to be developed, tested, and reviewed.  Workflow parameters that can be customized on a per repository basis should be adequately documented.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Testing should be performed on selected Stripes and UI repositories.   I propose testing and initial implementation and refinement on the following folio-org repositories - stripes-core, ui-orders, ui-users, and ui-plugin-find-organization followed by incremental rollouts to remaining Stripes and UI repositories.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Workflows should be deployed as workflow templates that are maintained for the folio-org Github organization.&lt;/li&gt;
&lt;/ul&gt;

</comment>
                                                            <comment id="196677" author="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30" created="Tue, 25 May 2021 12:42:50 +0000"  >&lt;p&gt;The build Job fails when the FOLIO_NPM_REGISTRY env variable is set to&#160;&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;
https:&lt;span class=&quot;code-comment&quot;&gt;//repository.folio.org/repository/npm-folioci-test/&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The logs show the following error:&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;
npm ERR! code E401
npm ERR! Unable to authenticate, need: BASIC realm=&lt;span class=&quot;code-quote&quot;&gt;&quot;Sonatype Nexus Repository Manager&quot;&lt;/span&gt;

npm ERR! A complete log of &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; run can be found in:
npm ERR!     /home/runner/.npm/_logs/2021-05-21T15_12_30_188Z-debug.log
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;On doing further research I found the error related to setting the REALM configuration of the repository. I do not have rights to do that, so would need &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;&apos;s help. Last week the error was thought to be the outcome of the Nexus server being down and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cd423bebc70090d6ce241b1&quot; class=&quot;user-hover&quot; rel=&quot;5cd423bebc70090d6ce241b1&quot; data-account-id=&quot;5cd423bebc70090d6ce241b1&quot; accountid=&quot;5cd423bebc70090d6ce241b1&quot; rel=&quot;noreferrer&quot;&gt;Ian Hardy&lt;/a&gt; had created a ticket for that, but even after the issue was resolved the same error was faced. &lt;/p&gt;</comment>
                                                            <comment id="196680" author="5f9abc1eb45b2e007453f423" created="Tue, 25 May 2021 17:24:21 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; Can you link to the latest buildNPM workflow you are working with (the one that fails in the comment above).  &lt;/p&gt;</comment>
                                                            <comment id="196683" author="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30" created="Wed, 26 May 2021 09:50:48 +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;&#160;it is updated in the .github workflow repository. Below is the link&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/.github/blob/master/workflow-templates/buildNPM.yml&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/.github/blob/master/workflow-templates/buildNPM.yml&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Also for the non-master steps, whenever the FOLIO_NPM_REGISTRY is set to the &lt;b&gt;folioci-test&lt;/b&gt;&#160;registry, the yarn install step fails with the below error:&lt;/p&gt;

&lt;p&gt;&#160;&lt;br/&gt;
&#160;&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;
error Couldn&apos;t find &lt;span class=&quot;code-keyword&quot;&gt;package&lt;/span&gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;@***/eslint-config-stripes&quot;&lt;/span&gt; on the &lt;span class=&quot;code-quote&quot;&gt;&quot;npm&quot;&lt;/span&gt; registry.    info Visit https:&lt;span class=&quot;code-comment&quot;&gt;//yarnpkg.com/en/docs/cli/install &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; documentation about &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; command. &lt;/span&gt;&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;br/&gt;
&#160;&lt;/p&gt;</comment>
                                                            <comment id="196686" author="5f9abc1eb45b2e007453f423" created="Wed, 26 May 2021 14:56:23 +0000"  >&lt;p&gt;Ok.  I see now.   &lt;/p&gt;

&lt;p&gt;So we need FOLIO_NPM_REGISTRY to be set to its original value (&lt;a href=&quot;https://repository.folio.org/repository/npm-folioci&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://repository.folio.org/repository/npm-folioci&lt;/a&gt;),  because that&apos;s where the module gets its dependencies from.   However,  we need to define a separate registry (for testing purposes only) when we publish the new NPM.&lt;/p&gt;

&lt;p&gt;Also, I see you have the publish step early in the workflow.   &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;- run: |
          git clone https://github.com/folio-org/folio-tools.git
          npm --no-git-tag-version version `folio-tools/github-actions-scripts/folioci_npmver.sh`
          rm -rf folio-tools
          npm publish
        env:
          JOB_ID: ${{ github.run_number }}
          NODE_AUTH_TOKEN: ${{ secrets.FOLIO_NEXUS_NPM_TOKEN }}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Instead, &apos;npm publish&apos; should be performed as a separate step right before publishing the module descriptor, because we do not want to publish a package that fails unit testing or any other quality gates.     Something like this: &lt;/p&gt;

&lt;p&gt;1.  Remove this step.&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;    - name: Set FOLIO NPM snapshot version and publish to NPM snapshot repository
        if: contains(github.REF,&apos;master&apos;)
        uses: actions/setup-node@v2
        with:
          node-version: ${{ env.NODEJS_VERSION }}
          registry-url: https://repository.folio.org/repository/npm-folioci-test/
      - run: |
          git clone https://github.com/folio-org/folio-tools.git
          npm --no-git-tag-version version `folio-tools/github-actions-scripts/folioci_npmver.sh`
          rm -rf folio-tools
          npm publish
        env:
          JOB_ID: ${{ github.run_number }}
          NODE_AUTH_TOKEN: ${{ secrets.FOLIO_NEXUS_NPM_TOKEN }}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;2.  Add the following the step right before the publish module descriptor step.&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;        if: contains(github.REF,&apos;master&apos;)
        uses: actions/setup-node@v2
        with:
          node-version: ${{ env.NODEJS_VERSION }}
          registry-url: https://repository.folio.org/repository/npm-folioci-test/
      - run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{ secrets.FOLIO_NEXUS_NPM_TOKEN }}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We may need to do some cleanup before the publish step,  but let&apos;s worry about that later.    Let me know if this works.   If you still have an issue authenticating to &lt;a href=&quot;https://repository.folio.org/repository/npm-folioci-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://repository.folio.org/repository/npm-folioci-test/&lt;/a&gt; with FOLIO_NEXUS_NPM_TOKEN, let me know.  It&apos;s quite possible I have the wrong token defined.  &lt;/p&gt;</comment>
                                                            <comment id="196689" author="5f9abc1eb45b2e007453f423" created="Wed, 26 May 2021 15:02:10 +0000"  >&lt;p&gt;One other thing to note:   We will be changing the default github repo branch from &apos;master&apos; to &apos;main&apos; in the near future,   so conditionals for &apos;master&apos; should also include &apos;main&apos;.   If there&apos;s something we can use that covers both cases that would be ideal - I thought I saw somewhere that you can use a GA built-in variable like $default_branch (or something like that) that just knows what the default branch is for a repo. &lt;/p&gt;</comment>
                                                            <comment id="196692" author="5f9abc1eb45b2e007453f423" created="Wed, 26 May 2021 15:21:41 +0000"  >&lt;p&gt;More feedback:  &lt;/p&gt;

&lt;p&gt;This step should be run on any branch - not just the default or master branch. &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;       - name: Generate Module descriptor
        if: contains(github.REF,&apos;master&apos;) 
        run: stripes mod descriptor --full --strict | jq &apos;.[]&apos; &amp;gt; ${{ env.MODULE_DESCRIPTOR_DIR }}/${{ env.FOLIO_NAME }}.json
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;But more importantly,  not all Node-based repos include a module descriptor.  Therefore, we should add an environment variable called PUBLISH_MODULE_DESCRIPTOR that is either set to (true or false).   And the modify &apos;Generate Module descriptor&apos; step and &apos;Publish module descriptor&apos; step to only run if PUBLISH_MODULE_DESCRIPTOR  is set to &apos;true&apos;.  &lt;/p&gt;</comment>
                                                            <comment id="196694" author="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30" created="Tue, 1 Jun 2021 12:50:21 +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;&#160;I have for the time being included both &apos;master&apos; and &apos;main&apos; branches in the conditional steps. I still however get the following error when trying to do an `npm publish` step:&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;
Error: Error: Unable to determine the current version of @***/stripes-core on NPM. 
npm view @***/stripes-core version exited with a status of 1.
npm ERR! code E401 
npm ERR! Unable to authenticate, need: BASIC realm=&lt;span class=&quot;code-quote&quot;&gt;&quot;Sonatype Nexus Repository Manager&quot;&lt;/span&gt;

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt; 
&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="196697" author="5f9abc1eb45b2e007453f423" created="Fri, 4 Jun 2021 19:57:58 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; Currently doing testing and debugging on the &apos;malc-test&apos; branch of stripes-core.  I still haven&apos;t been able to resolve the &apos;npm publish&apos; authentication issue.   This is tricky.   I believe that there is some additional complexity here due to, I think,  the repository being a private Nexus repo.  Will continue to investigate. &lt;/p&gt;</comment>
                                                            <comment id="196700" author="5f9abc1eb45b2e007453f423" created="Wed, 16 Jun 2021 17:21:51 +0000"  >&lt;p&gt;Adding comments discussed during last DevOps meeting:&lt;/p&gt;

&lt;p&gt;1.   Currently the builNPM workflow includes the following: &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;on: 
  push:
    paths-ignore:
      - &apos;translations/**&apos;
  pull_request:
     paths-ignore:
      - &apos;translations/**&apos;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;which is meant to bypass triggering the workflow when only translations updates have been made.   However,  there is a new requirement described in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-3184&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-3184&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;execute formatjs-compile in CI for translation PRs&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-3184
        &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;
 that includes adding a CI step to compile translation files.    Perhaps the easiest solution to address this requirement is to add a configurable environment variable that enables or bypasses this step (&apos;yarn formatjs-compile&apos;) during every workflow run since some Node-based projects don&apos;t include translations files.  Also, &apos;paths-ignore: - &apos;translations/**&apos;&apos; would need to be removed from the workflow.  &lt;/p&gt;</comment>
                                                            <comment id="196703" author="5f9abc1eb45b2e007453f423" created="Wed, 16 Jun 2021 17:27:51 +0000"  >&lt;p&gt;2. Another issue we need to address is ensuring artifact snapshot versions are sufficiently higher than ones generated from Jenkins.   Snapshot versions are based on build numbers.   If we make no changes, GA workflows snapshot artifacts will be generated with lower build numbers than the artifacts generated from Jenkins.  This is a problem.   A potential easy solution is to pad the snapshot artifact versions with two extra zeros.   This change can be made in this script:  &lt;a href=&quot;https://github.com/folio-org/folio-tools/github-actions-scripts/folioci_npmver.sh&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-tools/github-actions-scripts/folioci_npmver.sh&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="196706" author="615afd1cd9820f0070a09ef0" created="Thu, 8 Jul 2021 16:31:19 +0000"  >&lt;p&gt;&lt;del&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=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt;: I was doing some work in stripes-core, the repo where the pilot work for this ticket is happening, and wanted to clean up the PR comments provided by the CI workflow since all PRs currently show failed checks even when they are safe to merge.&lt;/del&gt;&lt;/p&gt;

&lt;p&gt;&lt;del&gt;I have a &lt;a href=&quot;https://github.com/folio-org/stripes-core/pull/1089&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;PR up that cleans up a few things WRT how stripes is invoked&lt;/a&gt; to generate the MDs but I&#8217;m hesitant to merge additional changes to it because I&#8217;m driving waaaaay outside my lane here. I have a few questions/concerns:&lt;/del&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;&lt;del&gt;Do we in fact want to publish MDs when building PRs, i.e. before they have merged? It feels like that should be part of Automation/build-platform-complete-snapshot instead.&lt;/del&gt;&lt;/li&gt;
	&lt;li&gt;&lt;del&gt;The POST destination those MDs is a hard-coded AWS URL. That feels like a maintenance headache. Is there some other way we can pass that value into this script?&lt;/del&gt;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;del&gt;As noted on my comment in the PR, I think there&apos;s one final change to &lt;tt&gt;buildnpm.yml&lt;/tt&gt;&#160;that&apos;ll allow this workflow to succeed. Should I go ahead and commit that change?&lt;/del&gt;&lt;/p&gt;

&lt;p&gt;Nevermind; I see &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; has a &lt;a href=&quot;https://github.com/folio-org/stripes-core/pull/1083&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;follow-up PR&lt;/a&gt; that runs cleanly. Sorry for the noise!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="82087">FOLIO-3070</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82086">FOLIO-3069</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82088">FOLIO-3071</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="81915">FOLIO-2913</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82097">FOLIO-3192</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82198">FOLIO-3205</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82123">FOLIO-3272</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82093">FOLIO-3184</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="82244">FOLIO-3452</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82406">FOLIO-3504</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="10155"><![CDATA[FOLIO DevOps]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02fm7:</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>Tue, 25 May 2021 12:42:50 +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>