Fix Dependabot CI Pipeline

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
docker, github-actions, typescript
领域
build-system, ci-cd, devops

调研方向

从 Dependabot 创建的分支作业日志以及构建并将镜像推送到 registry 的 CI pipeline 步骤开始。确定针对 Dependabot 分支预期采用哪种发布行为，然后验证所选方法是否能让构建和测试作业完成，同时不暴露 registry 凭据，也不让预期的 pipeline 处于故障状态。

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

描述

The Branches that Dependabot creates dont succeed. According to the job logs, they cant authenticate to the registry where the images should be pushed. This seems to be related to dependabot requiring credentials to be allowed to push, which currently are not provided to dependabot to restrict malicious dependencies of reading the registry credentials on automatic updates by dependabot.

We have several options now:

  • Ignore publishes and just merge on success of build & test steps, leaving the pipeline as-is and always creating faulty pipelines
  • Restrict docker push to non-dependabot authored branches only
  • Use renovate instead of dependabot, although renovate will suffer the same problem when trying to push
  • Use pnpm instead of npm when building images. pnpm by default ships with version 11 (current, stable) a minimumReleaseAge that only allows builds of an application that is at least 24hours old. (this can be configured to whatever is needed. specified in minutes). https://pnpm.io/settings#minimumreleaseage
  • provide dependabot with credentials to push to the registry. -> Do we ever need to have an image available of a patch/minor/major release in a seperate image?
主要语言
TypeScript
星标
1
派生
0
平均合并
22 小时 6 分钟
30 天内合并 PR
12

贡献指南

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

从这里开始

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

stackabletech/cockpit 的其他 Issue

查看 stackabletech/cockpit 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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