feat(triggers) Adds support for payloadConstraints on property files for build triggers

[linjmeyer]

Implements Spinnaker Issue #5053

Use case is conditionally triggering pipelines after a successful Jenkins build. For example, Jenkins may be setup for builds on all branches but Spinnaker pipelines should only be master. More complex use cases are possible too, like triggering 'stage' pipelines on feature/* branches or when a Jenkins build has something like deploy_target=stage.

• Adds support for payloadConstrains: {} dictionary for Build triggers (e.g. Jenkins).
• If payloadConstraints are present, then properties in the properties file must pass the constraints to trigger a build
• Regexp is supported (works the same as webhook and pub/sub payloadConstraints)
• Does not support Manual Pipeline triggers (ie: if build 30 fails constraints it can still be manually triggered after the fact)
• Only tested with Jenkins

I think it will work with other build systems as long as they support properties, but unfortunately I don't have any available to test.

[linjmeyer]

I should probably add: I'm not a Java dev and this is my first time contributing to Spinnaker outside the spin cli. Feedback is very welcome

[spinnakerbot]

The following commits need their title changed:

• 6923ae3: Added simple jenkins check constraints

• ab96fe4: Moved logic into BuildHandler

• 7907f27: removed uneeded code for PipelineInitiator

• f89f474: Added logging, cleaned up code

• df3d55d: Reverted static change to getKorkUser

Please format your commit title into the form:

<type>(<scope>): <subject>, e.g. fix(kubernetes): address NPE in status check

This allows us to easily generate changelogs & determine semantic version numbers when cutting releases. You can read more about commit conventions here.

[cfieber]

This looks pretty reasonable. Can you add some unit testing around the constraint evaluation?

[linjmeyer]

@cfieber done! Let me know what you think, and if you want me to fix the incorrect commit messages.

[cfieber]

Thanks for this!

[emjburns]

@linjmeyer Thanks for this, this is awesome!