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

New pipeline(s) CLI argument #4

Closed
daveaglick opened this issue Apr 17, 2019 · 2 comments
Closed

New pipeline(s) CLI argument #4

daveaglick opened this issue Apr 17, 2019 · 2 comments
Labels
General Enhancement New feature or request
Milestone

Comments

@daveaglick
Copy link
Member

By default all pipelines are executed. It should be possible to specify specific pipeline(s) to execute, which will execute only them (and their dependent pipelines once pipeline parrallelism/dependencies are implemented in #189). You should be able to specify one or more pipelines to run.

Pipelines should also be able to specify that they shouldn't be run by default. That will allow special pipelines that only get run when the pipeline CLI argument specifies that they should.

@daveaglick daveaglick transferred this issue from statiqdev/Statiq.Web Jun 30, 2019
@daveaglick daveaglick transferred this issue from another repository Jun 30, 2019
@daveaglick daveaglick added this to the 1.0 milestone Jun 30, 2019
@daveaglick daveaglick added the General Enhancement New feature or request label Jun 30, 2019
@daveaglick
Copy link
Member Author

Pipelines probably have three states when it comes to explicit pipeline execution:

  • Default (runs when specified or during a normal run)
  • Manual (only runs when explicitly specified)
  • Always (always runs, even when not explicitly specified)

@daveaglick
Copy link
Member Author

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
General Enhancement New feature or request
Development

No branches or pull requests

1 participant