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

Improve the Key Used to Keep Track of Requirements #90

Open
VincenzoFerme opened this issue Aug 23, 2016 · 0 comments
Open

Improve the Key Used to Keep Track of Requirements #90

VincenzoFerme opened this issue Aug 23, 2016 · 0 comments
Assignees
@VincenzoFerme
Labels
enhancement
Milestone
Next Tasks

Comments

@VincenzoFerme
Copy link
Member

VincenzoFerme commented Aug 23, 2016 •
edited
Loading

Currently the data-transformers and analysers configuration file assume unique keys across the files. This is due the way we construct the keyword to track scripts requirements. We should improve the keyword structure, so that we also differentiate between data-transformers and analysers as part of the key, so that we only need unique keys wishing the same file.
VincenzoFerme added a commit to benchflow/analysers that referenced this issue Aug 23, 2016
@VincenzoFerme
Changes the name for the Faban analyser script
e525ea0 
See benchflow/data-analyses-scheduler#90
@VincenzoFerme VincenzoFerme added this to the Next Tasks milestone Aug 23, 2016
@VincenzoFerme VincenzoFerme self-assigned this Aug 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VincenzoFerme VincenzoFerme

Labels
enhancement
Milestone
Next Tasks
Development

No branches or pull requests
1 participant
@VincenzoFerme