achilleas-k
commented
5 years ago Some up-front requirements for the service:
- [x] The web service/form should guide the user through specifying at least 3 parts with respect to the processing pipeline:
- [x] Input files: This should consist of annexed files to download which our clone plugin container should take care of (see Issue #11).
- [x] The processing script or commands (the core processing pipeline). This can be a snakemake file, for which we can have a special configuration option, or just a shell script.
- [x] Output files: List of filenames, directories, or globs/wildcards that will be made available to user for download (either gin-proc branch or special repository, see #6) (see also Issue #7).
- [x] When setting up the configuration for the user, the SSH key pair should be generated and set up automatically (see Issue #12).
Nice features These are extra features that would be nice to have if all else is completed:
- [x] Notification channel: The user can specify how to be notified of completion (or failure) of the processing pipeline.
- [x] Editing for existing drone.yml: The user should be able to reconfigure the builds by going through the web frontend guide. Initially, a reconfiguration could start from scratch every time and overwrite any existing drone.yml. In the future however, it would be nice if the guide could read any existing drone.yml and populate the fields with existing values for the user to edit.
mrinalwahal
A web frontend that guides users to set up their builds. It should give users the ability to configure the most important options (input files, scripts/pipelines to run, output files to be pushed back) and generate a drone.yml (or update an existing one) for the builds.