<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:09:21 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-928] Integrate stripes-cli into Jenkins</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-928</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Stripes-cli is a new repo containing a prototype CLI for developing and Stripes UI modules.&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/stripes-cli&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-cli&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I&apos;d like to integrate this new repository with Jenkins CI workflow so that stripes-cli is automatically published to npm-folioci.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80457">FOLIO-928</key>
            <summary>Integrate stripes-cli into Jenkins</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="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="5f9abc1eb45b2e007453f423">John Malconian</assignee>
                                                                <reporter accountid="557058:624212b9-5938-4e3b-84c6-8c8a8db84996">Matthew Jones</reporter>
                                    <labels>
                            <label>ci</label>
                    </labels>
                <created>Wed, 8 Nov 2017 18:22:47 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:50 +0000</updated>
                            <resolved>Thu, 9 Nov 2017 02:02:04 +0000</resolved>
                                                                    <component>Continuous Integration</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                    <timespent seconds="1800">30 minutes</timespent>
                                <comments>
                                                            <comment id="190658" author="5f9abc1eb45b2e007453f423" created="Wed, 8 Nov 2017 23:10:12 +0000"  >&lt;p&gt;Set up repo for CI, however, for some reason,  there is an auth error publishing the package to the CI repo, npm-folioci.&lt;/p&gt;

&lt;p&gt;NPM debug Log: &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;0 info it worked if it ends with ok
1 verbose cli [ &apos;/usr/bin/node&apos;, &apos;/usr/bin/npm&apos;, &apos;publish&apos; ]
2 info using npm@3.10.10
3 info using node@v6.11.4
4 verbose publish [ &apos;.&apos; ]
5 silly cache add args [ &apos;.&apos;, null ]
6 verbose cache add spec .
7 silly cache add parsed spec Result {
7 silly cache add   raw: &apos;.&apos;,
7 silly cache add   scope: null,
7 silly cache add   escapedName: null,
7 silly cache add   name: null,
7 silly cache add   rawSpec: &apos;.&apos;,
7 silly cache add   spec: &apos;/home/jenkins/stripes-cli&apos;,
7 silly cache add   type: &apos;directory&apos; }
8 verbose addLocalDirectory /home/jenkins/.npm/@folio/stripes-cli/0.1.0/package.tgz not in flight
; packing
9 verbose correctMkdir /home/jenkins/.npm correctMkdir not in flight; initializing
10 info lifecycle @folio/stripes-cli@0.1.0~prepublish: @folio/stripes-cli@0.1.0
11 silly lifecycle @folio/stripes-cli@0.1.0~prepublish: no script for prepublish, continuing
12 verbose tar pack [ &apos;/home/jenkins/.npm/@folio/stripes-cli/0.1.0/package.tgz&apos;,
12 verbose tar pack   &apos;/home/jenkins/stripes-cli&apos; ]
13 verbose tarball /home/jenkins/.npm/@folio/stripes-cli/0.1.0/package.tgz
14 verbose folder /home/jenkins/stripes-cli
15 verbose addLocalTarball adding from inside cache /home/jenkins/.npm/@folio/stripes-cli/0.1.0/p
ackage.tgz
16 verbose correctMkdir /home/jenkins/.npm correctMkdir not in flight; initializing
17 silly cache afterAdd @folio/stripes-cli@0.1.0
18 verbose afterAdd /home/jenkins/.npm/@folio/stripes-cli/0.1.0/package/package.json not in fligh
t; writing
19 verbose correctMkdir /home/jenkins/.npm correctMkdir not in flight; initializing
20 verbose afterAdd /home/jenkins/.npm/@folio/stripes-cli/0.1.0/package/package.json written
21 silly publish { name: &apos;@folio/stripes-cli&apos;,
21 silly publish   version: &apos;0.1.0&apos;,
21 silly publish   description: &apos;Stripes Command Line Interface&apos;,
21 silly publish   repository:
21 silly publish    { type: &apos;git&apos;,
21 silly publish      url: &apos;git+https://github.com/folio-org/stripes-cli.git&apos; },
21 silly publish   publishConfig: { registry: &apos;https://repository.folio.org/repository/npm-folio/
&apos; },
21 silly publish   license: &apos;Apache-2.0&apos;,
21 silly publish   engines: { node: &apos;&amp;gt;=6.0.0&apos; },
21 silly publish   main: &apos;index.js&apos;,
21 silly publish   bin: { str: &apos;./lib/stripes-cli.js&apos; },
21 silly publish   scripts:
21 silly publish    { test: &apos;echo &quot;Error: no test specified&quot; &amp;amp;&amp;amp; exit 1&apos;,
21 silly publish      lint: &apos;eslint ./&apos; },
21 silly publish   dependencies:
21 silly publish    { &apos;@folio/stripes-core&apos;: &apos;github:folio-org/stripes-core#stripes-cli&apos;,
21 silly publish      commander: &apos;^2.11.0&apos;,
21 silly publish      &apos;just-kebab-case&apos;: &apos;^1.0.0&apos;,
21 silly publish      &apos;just-pascal-case&apos;: &apos;^1.0.0&apos;,
21 silly publish      kopy: &apos;^8.2.3&apos;,
21 silly publish      resolve: &apos;^1.4.0&apos;,
21 silly publish      &apos;update-notifier&apos;: &apos;^2.3.0&apos; },
21 silly publish   devDependencies: { eslint: &apos;^4.7.2&apos;, &apos;eslint-config-stripes&apos;: &apos;^1.0.0&apos; },
21 silly publish   readme: &apos;# Stripes CLI\n\nCopyright (C) 2017 The Open Library Foundation\n\nTh
is software is distributed under the terms of the Apache License,\nVersion 2.0. See the file &quot;[LI
CENSE](LICENSE)&quot; for more information.\n\n## Introduction\n\n*Note: This is an early prototype an
d not ready to fully scaffold a new Stripes UI module.*\n\nStripes CLI is a command line interfac
e to facilitate the creation, development, building, and testing of Stripes UI modules.\n\n## Ins
tallation\n\nStripes CLI is currently unpublished, so a quick way to take it for a spin is to run
:\n```\nnpm install -g folio-org/stripes-cli\n```\n\nTo develop the CLI:\n1. Clone this repo\n1. 
From the `stripes-cli` directory, run:\n```\nnpm install -g\n```\n\n## Available commands\n\nStri
pes CLI is currently invoked using `str` rather than `stripes` so it can run side-by-side with co
mmands currently integrated within stripes-core.\n\n* `serve` or `dev`: Serve up an app or platfo
rm with the development server.\n* `build`: Build a static tenant bundle.\n* `new`: Create a new 
UI module (work in progress).\n* `test`: Runs tests (not implemented).\n\nRun each command with `
--help` to view available options.\n\nPrevious `dev` and `build` commands continue to work as exp
ected for existing platforms given a file argument like `stripes.config.js` is provided.  However
, stripes-cli will now generate a config when the config file is omitted.  This is most useful fo
r developing a new ui-app in isolation within its own virtual platform as there is no need clone 
or link supporting repositories.\n\n\n## Example usage\n\nCreate a new stripes UI app and directo
ry: \n```\nstr new app &quot;Hello World&quot;\n```\n\nRun the newly created stripes UI app from within its
 own directory:\n```\nstr serve --allperms\n```\n(This assumes dependencies have previously been 
yarn installed and a suitable OKAPI backend is running locally on port 9130)\n&apos;,
21 silly publish   readmeFilename: &apos;README.md&apos;,
21 silly publish   gitHead: &apos;4f99b0ab7b4fd2ddf19117788bc988522659338d&apos;,
21 silly publish   bugs: { url: &apos;https://github.com/folio-org/stripes-cli/issues&apos; },
21 silly publish   homepage: &apos;https://github.com/folio-org/stripes-cli#readme&apos;,
21 silly publish   _id: &apos;@folio/stripes-cli@0.1.0&apos;,
21 silly publish   _shasum: &apos;f8ca0492cc9d244cf4934cc6cb150d1a0043bfab&apos;,
21 silly publish   _from: &apos;.&apos; }
22 verbose getPublishConfig { registry: &apos;https://repository.folio.org/repository/npm-folio/&apos; }
23 silly mapToRegistry name @folio/stripes-cli
24 silly mapToRegistry scope (from package name) @folio
25 silly mapToRegistry registry https://repository.folio.org/repository/npm-folioci/
26 silly mapToRegistry data Result {
26 silly mapToRegistry   raw: &apos;@folio/stripes-cli&apos;,
26 silly mapToRegistry   scope: &apos;@folio&apos;,
26 silly mapToRegistry   escapedName: &apos;@folio%2fstripes-cli&apos;,
26 silly mapToRegistry   name: &apos;@folio/stripes-cli&apos;,
26 silly mapToRegistry   rawSpec: &apos;&apos;,
26 silly mapToRegistry   spec: &apos;latest&apos;,
26 silly mapToRegistry   type: &apos;tag&apos; }
27 silly mapToRegistry uri https://repository.folio.org/repository/npm-folioci/@folio%2fstripes-c
li
28 verbose publish registryBase https://repository.folio.org/repository/npm-folioci/
29 silly publish uploading /home/jenkins/.npm/@folio/stripes-cli/0.1.0/package.tgz
30 verbose stack Error: auth required for publishing
30 verbose stack     at CachingRegistryClient.publish (/usr/lib/node_modules/npm/node_modules/npm
-registry-client/lib/publish.js:30:14)
30 verbose stack     at /usr/lib/node_modules/npm/lib/publish.js:138:14
30 verbose stack     at mapToRegistry (/usr/lib/node_modules/npm/lib/utils/map-to-registry.js:62:
3)
30 verbose stack     at publish_ (/usr/lib/node_modules/npm/lib/publish.js:107:3)
30 verbose stack     at Array.&amp;lt;anonymous&amp;gt; (/usr/lib/node_modules/npm/node_modules/slide/lib/bind-
actor.js:15:8)
30 verbose stack     at LOOP (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:15:14)
30 verbose stack     at LOOP (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:14:28)
30 verbose stack     at chain (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:20:5)
30 verbose stack     at /usr/lib/node_modules/npm/lib/publish.js:73:5
30 verbose stack     at RES (/usr/lib/node_modules/npm/node_modules/inflight/inflight.js:23:14)
31 verbose cwd /home/jenkins/stripes-cli
32 error Linux 4.9.38-16.33.amzn1.x86_64
33 error argv &quot;/usr/bin/node&quot; &quot;/usr/bin/npm&quot; &quot;publish&quot;
34 error node v6.11.4
35 error npm  v3.10.10
36 error code ENEEDAUTH
37 error need auth auth required for publishing
38 error need auth You need to authorize this machine using `npm adduser`
39 verbose exit [ 1, true ]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I think its due to the presence of a .npmrc in the project directory that is overriding the default .npmrc that contains the authentication token. &lt;/p&gt;</comment>
                                                            <comment id="190664" author="5f9abc1eb45b2e007453f423" created="Thu, 9 Nov 2017 02:02:04 +0000"  >&lt;p&gt;Modified NPM build pipeline to always override any existing .npmrc.    &apos;npm publish&apos; now works. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="71375">STCLI-1</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzy2p3:</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, 8 Nov 2017 23:10:12 +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>