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.

Sign up for GitHub

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

Jump to bottom

Explore "macro" step definitions #48

Open
rtyler opened this issue Nov 28, 2020 · 0 comments
Open

Explore "macro" step definitions #48

rtyler opened this issue Nov 28, 2020 · 0 comments
Labels
component/agent Agent related issues component/parser Parser or Otto description language issues enhancement New feature or request

Comments

@rtyler
Copy link
Owner

rtyler commented Nov 28, 2020

For some use-cases it might make sense to support a "macro" type of step which is just a step which invokes other steps. For example, an rspec step might just be the following snippet:

sh 'bundle exec rspec'
archive 'reports/*.xml'

I'm thinking handlebar templates for mapping variables in properly.

Not sure yet what the best approach for handling this, but a type field in the manifest.yml is a good start.
@rtyler rtyler added enhancement New feature or request component/agent Agent related issues component/parser Parser or Otto description language issues labels Nov 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/agent Agent related issues component/parser Parser or Otto description language issues enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rtyler