-
Notifications
You must be signed in to change notification settings - Fork 4
Validate Queue Behavior #19
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
Conversation
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
deaf622 to
84060e4
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
1933166 to
0d8decf
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Given that we are kicking off workflows on timestamp, it seems like an equal value will consider it to be the workflow in question and ready to go. While this isn't terrible, it's not great either. |
621fa05 to
13c101e
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
7f956b6 to
9428454
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
dae700b to
9620571
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
43f0d68 to
256826d
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
0fe7570 to
37d88cf
Compare
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
* Intrapipeline Queueing (#16) * documentation: update comments * feat: add internal queue * Job, Command, Renames / Recontextulization (#18) * feat: renames * feat: add ability to ignore specific workflows * fix: formatting * fix: shellcheck * fix: job name * fix: shellcheck * Validate Queue Behavior (#19) * feat: ensure we can validate the correct ordering of jobs * fix: rename to the correct pipeline to ignore * debugging * fix: debug * walk back validation * feat: update documentation * Update src/jobs/global-queue.yml Co-authored-by: Andy Horner <[email protected]> * Update src/commands/global_block.yml Co-authored-by: Andy Horner <[email protected]> --------- Co-authored-by: Andy Horner <[email protected]>
Attempts to programmatically test the queueing mechanisms.
Edit: There is no easy way to do this, given that we want the last step to be the pipeline queue, but also need it to be the one that reports on the pipeline queue completing. Will remove the validation and just incorporate the QOL adjustments.