-
Notifications
You must be signed in to change notification settings - Fork 85
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
Running pipeline(s) is NOT obvious #997
Comments
Also you cannot start the develop_2_deploy pipeline from creation of the scan either. |
@silverhook could you elaborate on this? It seems that this may needs a new ticker/issue including more information about how to reproduce the problem. |
Signed-off-by: tdruez <[email protected]>
Signed-off-by: tdruez <[email protected]>
* Add a can_start_pipelines and start_pipelines Project methods #997 Signed-off-by: tdruez <[email protected]> * Display a "Run pipelines" button in the "Pipelines" panel #997 Signed-off-by: tdruez <[email protected]> --------- Signed-off-by: tdruez <[email protected]>
Unless I am missing something (at least when I wrote that comment), a “d2d” scan needed at least two (often three) resources, but when starting the scan initially, you could only add one resource, not several. |
From https://scancodeio.readthedocs.io/en/latest/built-in-pipelines.html#deploy-to-develop
I'm not sure what you mean by "you could only add one resource". |
Nevermind, it seems to either be fixed, or I was blind. I could have sworn that the WebUI only allowed you to upload one resource, before starting the scan, any additional ones I could only add afterwards. |
There's no limit to the number of inputs (uploaded file or download URLs) that can be provided at the project creation, or from the "Add inputs" panel. |
If I have a project with pipelines that were NOT started at creation (say from a clone), there is no obvious way to start the pipeline(s): I need to click on each and click on run.
I would like to have a simpler way to run all not started pipelines of my project
The text was updated successfully, but these errors were encountered: