Add Task to Trigger Jenkins Build using Tekton

[vinamra28]

Changes

The following task can be used to trigger an existing Jenkins pipeline from Tekton using the CURL request by providing the required parameters.

Signed-off-by: vinamra28 [email protected]

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Yaml file complies with yamllint rules.
• Complies with Catalog Orgainization TEP, see example. Note An issue has been filed to automate this validation

  • File path follows <kind>/<name>/<version>/name.yaml

  • Has README.md at <kind>/<name>/<version>/README.md

  • Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource

  • Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

  • mandatory spec.description follows the convention

      ```
    
      spec:
        description: >-
          one line summary of the resource
    
          Paragraph(s) to describe the resource.
      ```
    

See the contribution guide
for more details.

---

[bobcatfish]

neat!!

[imjasonh]

This seems like it could be a good candidate for a Custom Task, that invokes a remote Jenkins installation and polls the status until it completes, and reports success/failure.

If you're interested I'd love to help work on something like this as an example that could help hone the Custom Tasks proposal, and provide this as a higher-level feature of Tekton.

(This shouldn't block this specific PR, but it jumped out to me as something we could support at a higher level)

[vinamra28]

@imjasonh Thanks for the review. Sure, will love to do that and take this task to the higher level. 😄

[vinamra28]

hi @imjasonh, what can I do to get this PR merged and start with the Custom Task proposal or are we going to include that(Custom Task Proposal) in the current PR. Also please guide me as how to get started with that 😄

[imjasonh]

hi @imjasonh, what can I do to get this PR merged and start with the Custom Task proposal or are we going to include that(Custom Task Proposal) in the current PR. Also please guide me as how to get started with that 😄

Hey, sorry for the delay. I don't think we should drop this PR in favor of a Custom Tasks approach, so submitting it as a regular Task like you're doing here should be fine. The only problem is I actually have no familiarity with Jenkins and so probably can't really review it very well. Is there someone else you think could review it that might know more about Jenkins?

[vdemeester]

/lgtm

[waveywaves]

/lgtm

[vdemeester]

/lgtm

[waveywaves]

@imjasonh I just went through the manisfests and tried it out on Jenkins with @vinamra28. It looks good to me. It is definitely useful to have this to allow tekton users to trigger their jenkins jobs.

[waveywaves]

/lgtm

[vdemeester]

/meow

[tekton-robot]

@vdemeester:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment