密码变量在新版本中已损坏 [英] Password variable corrupted in new releases

查看:70
本文介绍了密码变量在新版本中已损坏的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

 我已经配置了一个使用FTP将tomcat应用程序部署到azure app服务的版本。我已根据指南https://www.visualstudio.com/en-us/docs/build/apps/java/maven-to-azure将Azure凭据设置为azure并将其存储为我的发布配置中的变量。

 I've got a release configured that uses FTP to deploy a tomcat app to an azure app service. I've setup FTP credentials in azure and stored them as variables in my release config, as per the guidance https://www.visualstudio.com/en-us/docs/build/apps/java/maven-to-azure.

我已经设置了持续部署,因此在新构建之后,会创建一个新版本并将其部署到我的第一个环境中。但是在每个新版本中,第一次部署都会失败并显示以下内容:

I've setup continuous deployment so after a new build, a new release is created and deployed to my first environment. But on every new release, the first deploy fails with the following:

2017-02-22T10:53:21.4192964Z curl: (67) Access denied: 530
 
2017-02-22T10:53:21.4382955Z ##[error]curl failed with return code: 67
 
2017-02-22T10:53:21.4382955Z ##[error]curl failed with error: curl failed with return code: 67

如果我再将密码输入秘密变量并重新运行部署,则可以正常运行。除了手动重新输入密码之外,是否有人遇到此错误或有解决方法?

If I then re-enter the password into the secret variable and rerun the deploy, it works. Anyone come across this bug before or have a workaround other than manually reentering the password?

谢谢。

推荐答案

因为它需要敏感信息来调查更多,我建议你在这里创建一个技术支持票
https://www.visualstudio.com/team-services / support /


这篇关于密码变量在新版本中已损坏的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆