The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Eiffel Broadcaster Plugin

View this plugin on the Plugins site

createPackageURL: Construct a package URL and return it as a string

Create a well-formed Package URL (purl) based on a set of discrete input strings and return the result as a string. Package URLs are for example used in the data.identity member of EiffelArtifactCreatedEvent .
  • name : String (optional)
    The name of the package. Required. See the full Package URL specification for all details and examples.
  • namespace : String (optional)
    A name prefix such as a Maven groupid, a Docker image owner, a GitHub user or organization. Optional and type-specific. See the full Package URL specification for all details and examples.
  • qualifiers (optional)
    • Type: java.util.Map<java.lang.String, java.lang.String>
  • subpath : String (optional)
    Extra subpath within a package, relative to the package root. Optional. See the full Package URL specification for all details and examples.
  • type : String (optional)
    The package "type" or package "protocol" such as maven, npm, nuget, gem, pypi, etc. Required. See the full Package URL specification for all details and examples.
  • version : String (optional)
    The version of the package. Optional. See the full Package URL specification for all details and examples.

publishEiffelArtifacts: Publishes previously announced Eiffel artifacts

Sends an EiffelArtifactPublishedEvent for each EiffelArtifactCreatedEvent that has been recorded in the build using a sendEiffelEvent step with the publishArtifact argument enabled. Optionally also EiffelArtifactCreatedEvent events recorded in a file in the workspace.

This requires that each EiffelArtifactPublishedEvent has at least one file defined in its data.fileInformation array and that each relative file path in data.fileInformation.name matches a Jenkins artifact in the build. Because of the latter requirement it's normally used after an archiveArtifacts step.

The EiffelArtifactPublishedEvent will have two links; one ARTIFACT link to the EiffelArtifactCreatedEvent and one CONTEXT link to the parent build's EiffelActivityTriggeredEvent.

sendEiffelEvent: Send an Eiffel event

Sends an Eiffel event expressed as a Groovy map. This map is passed in the event argument.

By default the event passed by the user will be decorated with a CONTEXT link to the current build's EiffelActivityTriggeredEvent . Optionally a CAUSE link can be created instead or the link can be omitted entirely.

This step returns immediately as soon as the event has been validated and put on the internal outbound queue. The actual delivery of the event to the broker might not have happened at the time of the return.

  • event
      Nested Choice of Objects
  • activityLinkType (optional)
    • Values: ACTIVITY_EXECUTION, ARTIFACT, BASE, CAUSE, CHANGE, COMPOSITION, CONFIGURATION, CONTEXT, DERESOLVED_ISSUE, ELEMENT, ENVIRONMENT, FAILED_ISSUE, FLOW_CONTEXT, INCONCLUSIVE_ISSUE, IUT, MODIFIED_ANNOUNCEMENT, ORIGINAL_TRIGGER, PARTIALLY_RESOLVED_ISSUE, PRECURSOR, PREVIOUS_ACTIVITY_EXECUTION, PREVIOUS_VERSION, RESOLVED_ISSUE, REUSED_ARTIFACT, RUNTIME_ENVIRONMENT, SUB_CONFIDENCE_LEVEL, SUBJECT, SUCCESSFUL_ISSUE, TERC, TEST_CASE_EXECUTION, TEST_SUITE_EXECUTION, VERIFICATION_BASIS
  • linkToActivity : boolean (optional)
  • publishArtifact : boolean (optional)
  • signatureCredentialsId : String (optional)
  • signatureHashAlgorithm : String (optional)

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.