-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
e2e: add e2e tests for job submission api #16841
Conversation
e2e/e2eutil/allocs.go
Outdated
@@ -65,11 +69,38 @@ func WaitForAllocStatusComparison(query func() ([]string, error), comparison fun | |||
return err | |||
} | |||
|
|||
// SingleAllocID returns the ID for the first allocation found for jobID in namespace | |||
// at the specified job version number. Will retry for a ten seconds before returning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// at the specified job version number. Will retry for a ten seconds before returning | |
// at the specified job version number. Will retry for ten seconds before returning |
variable "Z" { | ||
type = bool | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it's relevant as a test case here, but there's also a shorter version for declaring variables:
variables {
A = "B"
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah these kinds of variables that have the value set directly in the original job are "invisible", at least not without doing some work with the hcl parser.
This PR adds e2e tests around the new job submissions api, added in #16763
No backport, feature is in 1.6