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

SBE scripts cannot handle failed commands #26

Closed
3F opened this issue Dec 17, 2014 · 1 comment
Closed

SBE scripts cannot handle failed commands #26

3F opened this issue Dec 17, 2014 · 1 comment

Comments

@3F
Copy link
Owner

3F commented Dec 17, 2014

Originally reported by: Anonymous


git will often generate failures on common scenarios:

git describe
fatal: No names found, cannot describe anything.

However, this is not allowed in an SBE script - it breaks


@3F
Copy link
Owner Author

3F commented Dec 17, 2014

Original comment by Denis Kuzmin (Bitbucket: 3F, GitHub: 3F):


you about FileComponent and commands like this ?:

#!java

#[File sout("git", "<<command>>")]

please details... problem with new-lines from received result ? or with the post-command for interaction with git shell ?

the most commands require values without newline symbols. You can read doc, also see params in code completion that marked as 'In' etc.

otherwise, for example, if this value is needed to use with conditional statements

this value should be without newlines, like this

#!java

#[( #[File out("git", "rev-parse --short HEAD")] == "a234df" ) { 
  ...
}
else { 
  ...
}]

it's not a bug, however i think need an additional helper for work with strings, e.g. work without newlines

Related Issue: #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant