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

Running pipeline(s) is NOT obvious #997

Closed
pombredanne opened this issue Nov 3, 2023 · 7 comments
Closed

Running pipeline(s) is NOT obvious #997

pombredanne opened this issue Nov 3, 2023 · 7 comments

Comments

@pombredanne
Copy link
Member

pombredanne commented Nov 3, 2023

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

@silverhook
Copy link

Also you cannot start the develop_2_deploy pipeline from creation of the scan either.

@tdruez
Copy link
Member

tdruez commented Jan 10, 2024

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.

tdruez added a commit that referenced this issue Jan 10, 2024
tdruez added a commit that referenced this issue Jan 11, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez added a commit that referenced this issue Jan 11, 2024
* Add a can_start_pipelines and start_pipelines Project methods #997

Signed-off-by: tdruez <tdruez@nexb.com>

* Display a "Run pipelines" button in the "Pipelines" panel #997

Signed-off-by: tdruez <tdruez@nexb.com>

---------

Signed-off-by: tdruez <tdruez@nexb.com>
@tdruez
Copy link
Member

tdruez commented Jan 11, 2024

#1046

There's now a single "Run pipelines" button directly available in the Pipelines panel:
Screenshot 2024-01-11 at 10 42 42

@tdruez tdruez closed this as completed Jan 11, 2024
@silverhook
Copy link

@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.

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.

@tdruez
Copy link
Member

tdruez commented Jan 11, 2024

From https://scancodeio.readthedocs.io/en/latest/built-in-pipelines.html#deploy-to-develop

This pipeline is expecting 2 archive files with "from-" and "to-" filename
    prefixes as inputs:
    - "from-[FILENAME]" archive containing the development source code
    - "to-[FILENAME]" archive containing the deployment compiled code

I'm not sure what you mean by "you could only add one resource".

@pombredanne pombredanne reopened this Jan 12, 2024
@silverhook
Copy link

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.

@tdruez
Copy link
Member

tdruez commented Jan 16, 2024

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.
The "Add inputs" is not possible after pipelines have started on a project though.

@tdruez tdruez closed this as completed Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants