[
https://issues.apache.org/jira/browse/SLING-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844942#comment-16844942
]
Robert Munteanu commented on SLING-8395:
----------------------------------------
The [discussion on
users@infra|https://lists.apache.org/thread.html/060451184a8abc3502147ca4986999f64ac4978292adb6c015dee72c@%3Cusers.infra.apache.org%3E]
(privately archived) resulted in two points:
- infra does not sanction using Jenkins for the purposes of running bots
- the OpenWhisk project does have some automation using a serverless
infrastructure around slack and release verification
Coming back from the OpenWhisk slack workspace I get the following information:
- they have a number of slack/release integrations as OW actions:
-- slack to dev list digest: https://github.com/rabbah/slack-email-digest (
cron-triggered function and via travis cron )
-- travis to slack bot https://github.com/rabbah/travis-to-slack
-- release verification tooling
https://github.com/jthomas/openwhisk-release-verification
- there a number of OW providers we can use
-- IBM Cloud ( [free tier|https://www.ibm.com/cloud/free/] could potentially
fit our work )
-- nimbella.io ( will be free for open source projects )
> Investigate automatically issuing GitHub PRs with the Committer CLI
> -------------------------------------------------------------------
>
> Key: SLING-8395
> URL: https://issues.apache.org/jira/browse/SLING-8395
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> Some actions ( site update, starter update ) would require pushing code.
> Ideally we would make these part a bot which issues pull requests which would
> then be merged by a Sling Committer.
> Major question is - how do we host this? Is Jenkins enough or do we need to
> handle our own server (which would be a major disadvantage ).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
