My Experience Creating an Orca Plugin for the First Time
summary
Built a Spinnaker Orca stage that POSTs a New Relic custom event with artifact, execution URL and outcome; configuration exposes endpoint, insert key and event type, pipeline inputs include title, environment, execution URL and change status, and the stage returns the HTTP status code. Development uses the PF4J example and IntelliJ, renaming Java packages and Gradle work takes the most time, the team implements an own HTTP client (instead of the opaque Orca client) and hits a secret substitution timing bug later fixed in v2; success is a response code 200.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:00What were we wanting to achieve
- 1:42Our previous solutions
- 3:46Getting a client
- 5:03Plugin configuration
- 6:07Plugin logic
- 8:07Stumbling blocks
- 9:10Summary
related talks
01h 54mFirst-time Spinnaker Contributors Workshop
43mSpinnaker Plugins: Extending...
32mMaking Spinnaker Your Own
45mEvolution of Spinnaker Internals & Operations
22mThe Ortelius Journey with GitOps and Event Driven CI/CD
01h 04mOpening Keynote [Full]
15mIntegrating Fortify Security Scans in Spinnaker Pipelines
20mEmpowering Continuous Delivery with Spinnaker: A State of th...