-
Updated
Aug 27, 2020 - Go
ci-cd
Here are 891 public repositories matching this topic...
-
Updated
Aug 28, 2020 - Go
-
Updated
Aug 28, 2020 - Java
Spug案例征集
Spug运维平台在过去的公司里稳定运行3年以上,开源的大部分代码也是基于稳定版本之上,为了增加更多用户在企业使用的信心,如您愿意,请将您在企业中使用Spug的案例展示给我们,请在该issue页面提供您的使用案例,提交格式:企业名称 + 公司官网地址。官网地址为可选项,您可以直接提供企业名称即可。
此外,您也可以通过其他渠道如QQ、微信、邮件的方式联系项目作者提供使用案例。
征集长期有效,感谢大家支持!
Spug部分案例:
- 上海家谐网络科技有限公司
- 上海爱上慧家信息技术有限公司
- 南京白鸥网络技术有限公司
- 杭州中艺实业股份有限公司
- [北京步鼎方舟科技有限公司](http://
Checklist:
- I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
- I've included steps to reproduce the bug.
- I've pasted the output of
argocd version.
Describe the bug
If an invalid token for a local user exists in argocd-secret, the API will refuse to process any request with an error message similar to:
FATA[0002] rpc error: code =
Hi,
It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).
Example
apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
name: app-remote
namespace: my-really-really-really-long-nsk logs po/gitkub-
Updated
Jun 16, 2020 - HTML
-
Updated
Aug 26, 2020 - Go
-
Updated
Aug 28, 2020 - Go
-
Updated
Nov 5, 2018
-
Updated
Aug 19, 2019 - Python
-
Updated
Aug 28, 2020 - Go
What happened:
UI is loading all the step log data in memory and looping through the data to create a blob to make it downloadable. This does not work for large step log files where there are hundred thousands of log lines.
What you expected to happen:
- UI should not do any custom logic and should defer to API for log download.
- New API to download step logs with proper cachi
https://github.com/google/starlark-go/blob/master/doc/spec.md
It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.
Like in #137 we should provide build context information.
-
Updated
Aug 28, 2020 - Groovy
-
Updated
Nov 10, 2018 - Go
-
Updated
Aug 9, 2020 - Smarty
Document ZAP
-
Updated
Apr 22, 2020 - Go
-
Updated
Aug 27, 2020 - TypeScript
-
Updated
Jun 28, 2020 - PowerShell
-
Updated
Jul 22, 2020 - Shell
-
Updated
Aug 12, 2020 - JavaScript
-
Updated
Jan 9, 2020 - JavaScript
-
Updated
Aug 21, 2020 - Smarty
-
Updated
Sep 16, 2019 - Shell
Improve this page
Add a description, image, and links to the ci-cd topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ci-cd topic, visit your repo's landing page and select "manage topics."
When viewing a build that reconfigures pipelines, it's hard to tell which pipelines were actually changed:
Quick suggestion: highlight it in yellow, like the
getstep? Or the opposite - dim steps which had no changes to apply? No strong preference!This would likely involve emittin