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

Octo.exe doesn't allow setting an expiry time for a deployment (QueueTimeExpiry) #5159

Closed
MichaelJCompton opened this issue Dec 11, 2018 · 2 comments

Comments

@MichaelJCompton
Copy link

commented Dec 11, 2018

Octo.exe deploy-release ... allows setting the QueueTime (with --deployat), but doesn't allow setting an expiry time for the deployment task.

We should add an option like --dontStartAfter to allow setting the QueueTimeExpiry for the deployment.

@MichaelJCompton MichaelJCompton self-assigned this Dec 11, 2018
@droyad droyad changed the title Octoc.exe doesn't allow setting an expiry time for a deployment (QueueTimeExpiry) Octo.exe doesn't allow setting an expiry time for a deployment (QueueTimeExpiry) Feb 20, 2019
@thedewi thedewi self-assigned this Apr 3, 2019
@octoreleasebot octoreleasebot added this to the 2019.4.1 milestone Apr 5, 2019
@octoreleasebot

This comment has been minimized.

Copy link

commented Apr 5, 2019

Release Note: Add Octo.exe argument --noDeployAfter to set QueueTimeExpiry

@lock

This comment has been minimized.

Copy link

commented Jul 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.