-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Export-PipeScript
should allow conditional builds
#907
Labels
enhancement
New feature or request
Comments
StartAutomating
pushed a commit
that referenced
this issue
Feb 16, 2024
StartAutomating
pushed a commit
that referenced
this issue
Feb 16, 2024
StartAutomating
pushed a commit
that referenced
this issue
Feb 17, 2024
Merged
StartAutomating
pushed a commit
that referenced
this issue
Mar 6, 2024
StartAutomating
pushed a commit
that referenced
this issue
Mar 6, 2024
StartAutomating
pushed a commit
that referenced
this issue
Mar 6, 2024
StartAutomating
pushed a commit
that referenced
this issue
Mar 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a number of places throughout PipeScript,
[ValidateScript]
and[ValidatePattern]
are used to determine validity of a thing, given an input.Export-PipeScript
should use this pattern to allow builds to be conditional.*.build.ps1
should be considered valid if the commit matches[ValidatePattern]
*.build.ps1
should be considered valid if it has a[ValidateScript]
that returns true*.build.ps1
with no validation should always be considered validHandling these three variations on a theme allow for long running/slow changing builds to be run less frequently.
For example, a build could run only when "test" is present in the CI message.
Or, more interestingly, a portion of build could run only if the last checkin was older than a timeframe.
The text was updated successfully, but these errors were encountered: