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

Allow for choosing default state of optional commands #69

Closed
criography opened this issue Jul 8, 2015 · 0 comments
Closed

Allow for choosing default state of optional commands #69

criography opened this issue Jul 8, 2015 · 0 comments

Comments

@criography
Copy link

Use case:

compiling CSS and JS (potentially image optim) should happen most of the time, but in some cases, with an unaffected release, we want to save that 30-60secs of compilation by excluding these processes from given deployment. This obviously assumes that compiled files are stored as persistant anyway.

REBELinBLUE added a commit that referenced this issue Sep 17, 2015
* master: (29 commits)
  Clean up
  DB migration to add the additional status to deployments, horrible!
  Added status to model #95
  Add a "Finished with errors" status for deployments which fail after activation for issue #95
  Updated dependencies
  Updated dependencies
  Remove whitespace
  Adding missing trait
  Updating to Laravel 5.1.11 to make sure of the Authorization feature
  Removing unneeded folder
  Updating dependencies
  Fixes #88
  Fixes #90 By including deleted commands in the associations for DeployStep
  Fixes #87 by removing the builds_to_keep from pagination
  Updated dependencies
  Fix the namespace for broadcast events
  Fix #69 by adding a the ability to define optional commands to default to on
  Updating list of service providers for optimizing
  Fixing the compiled path for laravel 5.0.16
  Typo
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants