Goal

Implement --team for remaining fly commands. fly/integration tests should be updated. Cases should be added to the error_handling file as well https://github.com/concourse/concourse/blob/587483424a47f3eebb2ed8e861687b60cccb9ec7/fly/integration/error_handling_test.go#L92

# use default team
fly -t ci <command> <command-options>
# use another team
fly -t ci <command>

Spug运维平台在过去的公司里稳定运行3年以上，开源的大部分代码也是基于稳定版本之上，为了增加更多用户在企业使用的信心，如您愿意，请将您在企业中使用Spug的案例展示给我们，请在该issue页面提供您的使用案例，提交格式：企业名称 + 公司官网地址。官网地址为可选项，您可以直接提供企业名称即可。

此外，您也可以通过其他渠道如QQ、微信、邮件的方式联系项目作者提供使用案例。

征集长期有效，感谢大家支持！

Spug部分案例：

• 上海家谐网络科技有限公司
• 上海爱上慧家信息技术有限公司
• 南京白鸥网络技术有限公司
• 杭州中艺实业股份有限公司
• [北京步鼎方舟科技有限公司](http://

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

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.

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-ns

k logs po/gitkub

Add following Contents to Cloud Providers - https://github.com/Tikam02/DevOps-Guide/tree/master/Cloud_providers

• Add basic concepts of following providers:
  • AWS
  • GCP
  • Azure
• Add tips & tricks
• Add commands

External PRs does not pass the tests due to token autentication

 ● CML e2e › cml-send-comment

    Command failed: node ./bin/cml-send-comment.js comment.md
    Resource not accessible by integration

log here

What happened:

Nodes in workflow graph are placed at minimum possible depth which can cause graph rendering constricted.

What you expected to happen:
Each node in workflow graph should be placed in maximum possible depth

How to reproduce it:

screwdriver.yaml

shared:
    image: node:12
jobs:
    A:
        requires: [~pr, B]
        steps:
            - r

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.