catalog
catalog copied to clipboard
Added jira-get-ticket-status new task
Changes
Added a new task jira-get-ticket-status
to get the current status of a Jira ticket.
Hi @jlozano-rh. Thanks for your PR.
I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
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.
Catlin Output
FILE: task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
ERROR: Step "get-ticket-status" uses image "registry.access.redhat.com/ubi8/python-39" which must be tagged with a specific version
WARN : Step "get-ticket-status" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables
/assign @vinamra28
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: To complete the pull request process, please ask for approval from vinamra28 after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
Catlin Output
FILE: task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
WARN : Step "get-ticket-status" uses image "registry.access.redhat.com/ubi8/python-39@sha256:27e795fd6b1b77de70d1dc73a65e4c790650748a9cfda138fdbd194b3d6eea3d"; consider using a image tagged with specific version along with digest eg. abc.io/img:v1@sha256:abcde
Catlin Output
FILE: task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
WARN : Step "get-ticket-status" uses image "registry.access.redhat.com/ubi8/python-39@sha256:27e795fd6b1b77de70d1dc73a65e4c790650748a9cfda138fdbd194b3d6eea3d"; consider using a image tagged with specific version along with digest eg. abc.io/img:v1@sha256:abcde
thanks @jlozano-rh for submitting the PR. Will it be possible to add some tests? /ok-to-test
I don't know, because we would have to have a jira platform available for testing. And also leave in the PR the credentials in the Secret
object. This worries me, how did you solve this issue in other tasks?
Catlin Output
FILE: task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
WARN : Step "get-ticket-status" uses image "registry.access.redhat.com/ubi8/python-39@sha256:27e795fd6b1b77de70d1dc73a65e4c790650748a9cfda138fdbd194b3d6eea3d"; consider using a image tagged with specific version along with digest eg. abc.io/img:v1@sha256:abcde
@jlozano-rh: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-tekton-catalog-build-tests | 98e934d044978de11379d0e8c8ca71a130f5aee4 | link | true | /test pull-tekton-catalog-build-tests |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Catlin Output
FILE: task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
WARN : Step "get-ticket-status" uses image "registry.access.redhat.com/ubi8/python-39@sha256:27e795fd6b1b77de70d1dc73a65e4c790650748a9cfda138fdbd194b3d6eea3d"; consider using a image tagged with specific version along with digest eg. abc.io/img:v1@sha256:abcde
also the build test seems to be failing, can you please look at that as well?
also the build test seems to be failing, can you please look at that as well?
Hi @vinamra28, need some help with this, I'm not already implemented the tests yet. I don't know how to integrate a Jira platform well without expose sensible credentials. In another tasks ¿how have solved this kind of situations?
also the build test seems to be failing, can you please look at that as well?
Hi @vinamra28, need some help with this, I'm not already implemented the tests yet. I don't know how to integrate a Jira platform well without expose sensible credentials. In another tasks ¿how have solved this kind of situations?
@jlozano-rh, my bad, I guess testing this won't be that easy. Can you please fix the build test failure and squash the commits?
task/jira-get-ticket-status/0.1/jira-get-ticket-status.yaml
62:1 error trailing spaces (trailing-spaces)
@vinamra28 done!
[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
- ~~OWNERS~~ [vdemeester]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/lgtm