Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Travis integration?

未关闭
#273 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
javascript, node.js
领域
cli, cloud, devops

调研方向

Start with the package.json and travis.yml examples in the issue, then read the linked Travis Lambda deployment documentation. The issue is a general comparison question rather than a defined code change; it would need a decided scope and an explicit description of what guidance or project documentation should be added before work can be considered done.

由索引模型根据 Issue 内容生成。

描述

question

Just a general question regarding automated deployment of Lambda functions via Travis. I can see a couple of options here:

The first would be to run the node-lambda CLI as an after_success step. For example:

package.json:

{
  "scripts": {
    "deploy": "node-lambda deploy"
  }
}

travis.yml:

after_success:
  - npm run deploy

However, travis also has build in support for Lambda deployment:

e.g.

deploy:
  provider: lambda
  function_name: "lambda-test"
  region: "us-east-1"
  role: "arn:aws:iam::0123456789012:role/lambda_basic_execution"
  runtime: "nodejs4.3"
  handler_name: "handler"
  access_key_id: "AWS ACCESS KEY ID"
  secret_access_key: "AWS SECRET ACCESS KEY"

The only difference I can spot is that Travis doesn't seem to have any options for setting Lambda Environment variables.

Are there any other reasons why it might be better to use node-lambda from a Travis build?

主要语言
JavaScript
星标
1.4k
派生
185
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

motdotla/node-lambda 的其他 Issue

查看 motdotla/node-lambda 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。