• k6_429362
  • 688.5KB
  • zip
  • 0
  • VIP专享
  • 0
  • 2022-05-22 17:21
  • serverless-actions-main
  • self-hosted.png
  • architecture.png
# 🐑 Serverless GitHub Actions 🚀 Run hundreds of concurrent [GitHub Actions runners]( without needing to maintain servers. See a demo of it in action at the AWS re:Invent 2020 session [No more idling]( ## What is it? LambCI Serverless Actions enable you to run your GitHub Actions workflows on AWS Lambda and Google Cloud Run (Azure to come), and container-based services such as AWS Fargate or AWS CodeBuild. LambCI manages the connection to GitHub Actions and sends events over [Event Bridge]( or [PubSub]( The serverless resources live in your cloud account, so you only pay while your workflows are running. ## Why would you want this over hosted GitHub Actions? 1. More (much moar) concurrency, no queueing 🚀 2. Per-second (or ms) billing, on your cloud account ⏱ 3. Use IAM to access your cloud resources 🔒 4. Access to different instance sizes/capabilities (eg GPUs) 👩‍👩‍👧‍👦 ## Why would you want this over another CI tool? 1. First-class citizen in the GitHub UI 🎩 2. No need to context switch or manage accounts elsewhere 🏠 3. Familiar, well-documented build specs 📃 4. Use thousands of plugins/actions from the GH community 🏙 ## Project Philosophy 1. Don't reinvent the UI – stay in GitHub as much as possible. Organizations don't want yet-another tool to login to, and context-switching is a productivity killer. 2. Reducing build times is the goal. Serverless technologies are the means via fast start times and massive parallelization, but they can also be paired with vertical scaling (eg GPU CodeBuild instances). 3. All the software that runs your builds should be open-source. This includes the [GitHub Actions runner]( and all the "glue" necessary for invoking it (to be released soon). 4. Be a hub for all serverless-CI related resources. Serverless environments differ from traditional environments – typically they're more constrained in disk space. Provide guidance on how to operate in this context, including creating and curating Actions that work in these environments. ## Security GitHub Action payloads are encrypted ([at GitHub's end]( using RSA public/private key pairs. You can control this key (if you wish) so LambCI will have no visibility into the workflow job or secrets. So long as the resources in your account have access to the private key, they can decrypt the payload and run the workflow jobs in isolation. ## When? Soon, soon! Add your email to the list over at [LambCI's homepage]( to get updates on when this will be available to try out. ## Other Questions? Come and chat over in the [GitHub Discussions]( space. You can also reach out on Twitter at [@lamb_ci](
    • github-cdn::satellite:Github CDN服务器
      :satellite: Github CDN 是的 Github上用于回购资产的非官方内容交付网络。 :white_medium_star: 产品特点 获取回购元数据:分支机构,标签和PR 服务回购和Gist文件 即时访问被推送到Github的新更改* 非常适合...
    • serve:通过github页面的文件服务器
      服务 通过github页面的文件服务器
    • github-city-rankings-automated:西班牙的自动化服务器 GitHub 排名。 github-city
      Github 城市排名自动化 该项目是 的一个分支(witch 是的的一个分支) 用法 首先,创建要放置数据的目录。 您必须在项目文件夹中创建它(请参阅 config.json) +top-github-users-data |-- data |--formatted ...
    • PRLint-serverless:无服务器github webhook,用于检查PR标题的格式,以支持standard-ver
      公关皮棉 无服务器github webhook,用于检查PR标题的格式,以支持standard-version。
    • github状态
      由于该项目在GitHub Actions上运行,因此不需要服务器就可以定期使用更新的统计信息重新生成图像。 同样,由于用户自己通过GitHub Actions运行分析代码,因此他们可以使用GitHub访问令牌收集外部服务将无法访问的...
    •服务器网站 Palgania服务器网站
    • github状态
      由于该项目在GitHub Actions上运行,因此不需要服务器就可以定期使用更新的统计信息重新生成图像。 同样,由于用户通过GitHub Actions自己运行分析代码,因此他们可以使用GitHub访问令牌收集外部服务无法访问的私有...
    • 入门:使用无服务器功能扩展GitHub Enterprise
      当前,将GitHub Enterprise集成到SDLC中需要假设每个SDLC工作流程都始于GitHub Enterprise。 我们的业务合作伙伴将GitHub Enterprise视为客户购买整体工具链中的众多产品之一。 随着GitHub Enterprise演变为...
    • github状态
      由于该项目在GitHub Actions上运行,因此不需要服务器就可以定期使用更新的统计信息重新生成图像。 同样,由于用户自己通过GitHub Actions运行分析代码,因此他们可以使用GitHub访问令牌收集外部服务将无法访问的...
    • GaussDB_100_1.0.1-DATABASE-REDHAT-64bit.tar.gz