-
Notifications
You must be signed in to change notification settings - Fork 156
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
Rultor fails to parse a valid yaml #1312
Comments
@glusk2/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot! |
Originally posted by @rultor in Glusk/sprouts#163 (comment) The following - "version=${tag#'v'}" is successfully stored as an XML element in rultor store: <item>version=${tag#'v'}</item> but on rultor execution it degenerates into: version=${tag`#'\''\'\'''\''v'\''\'\'''\''}` |
@Glusk2 the problem still exists? |
@yegor256 But the issue is still present in rultor. Minimal reproducible example
architect:
- Glusk2
release:
script:
- "version=${tag#'v'}" Such configuration would fail upon invoking rultor like this:
It does seem futile to undo all the effort that was put into dealing with the comment lines and make significant changes to how rultor starts its builds (as suggested here) But as it stands, the following commands will not work in
Resource: Shell Parameter Expansion |
Unfortunately the information on the topic of this issue is scattered between several other issues. Here is a list of my comments in related issues:
This is a full list of related issues:
|
This is the
.rultor.yml
file I am using:The online parser classifies it as a valid
yml
and parses it successfully. YAMLlint also confirms that it is in fact a valid.yml
file!However, invoking rultor like this:
failed with this error message (full log):
The text was updated successfully, but these errors were encountered: