Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with the "One of the secure variables in your .travis.yml has an invalid format.\" warning #920

Closed
chorrell opened this issue Nov 20, 2018 · 7 comments

Comments

@chorrell
Copy link
Contributor

I think the One of the secure variables in your .travis.yml has an invalid format. travis warning is maybe being caused by other branches in the repo, like here for example:

https://github.com/nodejs/docker-node/blob/temp/.travis.yml#L86

Can everyone go through their branches and either rebase them or delete them?

@chorrell
Copy link
Contributor Author

I did a little bit of cleanup of "stale" branches

@LaurentGoderre
Copy link
Member

OOh, it would never have occured to me that it might be older branches

@chorrell
Copy link
Contributor Author

Yeah, me neither! It's a hunch at this point, but it seems like the only likely cause.

@LaurentGoderre
Copy link
Member

It looks like it might have cached an old verison of the TRavis because were not using any secure var in the Travis Config

@LaurentGoderre
Copy link
Member

@chorrell
Copy link
Contributor Author

So does this apply to values set in travis via settings as well? I ask because we have something set there.

@LaurentGoderre
Copy link
Member

I would assume so. I'm going to do some test builds on my account to try to narrow it down.

LaurentGoderre added a commit to LaurentGoderre/docker-node that referenced this issue Dec 6, 2018
LaurentGoderre added a commit to LaurentGoderre/docker-node that referenced this issue Dec 6, 2018
LaurentGoderre added a commit to LaurentGoderre/docker-node that referenced this issue Dec 6, 2018
LaurentGoderre added a commit to LaurentGoderre/docker-node that referenced this issue Dec 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants