I have a use case of where I want my pipeline to run an execution at a
scheduled time, which may be externally or internally provided and may or
may not be blocking. I'm still new to the Jenkinsfile and pipeline, but I'm
wondering if others have any experience with any of the following types of
use cases:
- External time window blacklist/whitelist (think of a Google calendar
or some calendar provider that gives approval windows, where this is an
input in a fan-in scenario)
- Allow all to pass through if in whitelist timewindow
- Block changes and wait until time window is open. Take the newest
change and 'promote' (continue) with it
- Internal time window/scheduler (run this nightly, once, and in a
nonblocking fashion with the latest code at this stage in this pipeline)
- Run this "stage" (execution?) at a desired time each night. For
example, upload the most up-to-date succeeding 'pipeline' somewhere. Do
not
block other pipelines from progressing past (no fan-in)
Has anybody modeled these in the Jenkinsfile, or in a delivery pipeline?
Also, are there any good example of the fan-in and fan-out?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/428cbe19-97c8-4b66-835c-fcce2b7a6880%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
