-
Notifications
You must be signed in to change notification settings - Fork 76
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
Please update the format used for build config imports on Travis CI #33
Comments
Thanks for reporting this! I'll go over the repositories in the next few days to migrate everything to the new syntax. |
just to be sure ... the format for referencing a file in a foreign repo is:
i am seeing something trying to reference:
which i believe probably should be:
|
I believe we updated all the users of the shared snippets in our organization, so let's close this. Thanks for the report! By the way, I haven't found the repository with the configuration you mentioned in #33 (comment). Do you have the name of the repository on hand? |
@pietroalbini ah, sorry, i have missed your last comment. no, i do not have that repo available any more. i suppose it may have been coming from a fork, or something trying things out. i'll keep an eye out and notify them myself (or get back here) if i spot it again. thanks a lot for taking care of this! ❤️ |
rust-lang
has been one of the early alpha adopters of our build config import feature.Various repositories are still using an early format for build config sources:
During the product development process this has been superseded by the format:
The format has been publicly announced in Nov 2019 with the feature.
The format you are currently using is not available any more for public use,
rust-lang
is currently safelisted for this outdated format, so your imports continue to work. However, in future versions of the build config processing component will not be able to support this.Please update
.travis.yml
files that are importing config sources using the outdated format to use the new format:Pretty sure I'm missing other places ...
Also mentioned on:
Btw, if you are importing a single config source only then you can specify it as a string (as opposed to a sequence of strings)
The sequence you have will work just fine of course, too:
The text was updated successfully, but these errors were encountered: