sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SLING-8747) establish @apachesling npmjs organization
Date Mon, 28 Oct 2019 09:33:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960885#comment-16960885
] 

Bertrand Delacretaz commented on SLING-8747:
--------------------------------------------

I got more info about how OpenWhisk manages this: it's a release manager who uploads the artifacts
to npmjs, after building from an official release. That's a manual process, not automated
so far.

The credentials for doing that are shared via the equivalent of https://svn.apache.org/repos/private/pmc/sling/

Details of their answer are on the private@openwhisk.a.o list in the "Publishing to NPM..."
thread.

> establish @apachesling npmjs organization
> -----------------------------------------
>
>                 Key: SLING-8747
>                 URL: https://issues.apache.org/jira/browse/SLING-8747
>             Project: Sling
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Ruben Reusser
>            Priority: Major
>
> now that the donation for the slingpackager has been accepted we need to create a common
apachesling organization on npmjs and start setting up a ci/cd flow to release the slingpackager
> https://issues.apache.org/jira/browse/SLING-8584



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message