On 2019-08-28T14:22:12 -0400 Mark Waite <[email protected]> wrote:
> You're using a relatively special case. The git plugin does not support it > directly. > > You might consider splitting the task into two Jenkins jobs: > > 1. Job that takes a SHA-1 as a parameter that should be built, but never > polls the repository > 2. Job that detects changes on the remote repository and runs a script > that computes the list of changes since the last run, then launches the job > defined step 1 with each of the SHA-1 values that have arrived since the > last run That's a shame, I was under the impression that what I was doing was pretty standard. Launching a second job makes sense though, and will be useful for other reasons. -- Mark Raynsford | http://www.io7m.com -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190830173706.78e5e989%40almond.int.arc7.info.
pgpmbtjaZDv86.pgp
Description: OpenPGP digital signature
