Test firewatch jira cloud token#76368
Conversation
|
Skipping CI for Draft Pull Request. |
Changes: 1. Update firewatch JIRA_SERVER URL to Atlassian Cloud - Changed from issues.redhat.com to redhat.atlassian.net 2. Add new test step: firewatch-test-jira-token - Validates Jira Cloud token connectivity - Tests authentication and project access - Verifies issue creation permissions 3. Add test job configuration - Daily cron job to validate token remains valid - Uses firewatch container and credentials This allows testing the Jira Cloud migration without affecting production firewatch jobs. Related: Red Hat Jira migration to Atlassian Cloud
0659353 to
9a11d95
Compare
|
/test all |
…huang/release into test-firewatch-jira-cloud-token
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@tanfengshuang: job(s): periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation either don't exist or were not found to be affected, and cannot be rehearsed |
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Changes: - Remove cluster_profile (not needed for token validation) - Use 'container' test type instead of 'steps' - Inline the test script in the config - Add base_images reference to firewatch:main This fixes the missing dependency error: 'step is missing dependencies: release:latest' Token validation doesn't need a cluster, just the firewatch container with Jira credentials mounted.
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@tanfengshuang, Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@tanfengshuang, If the problem persists, please contact Test Platform. |
The test configuration needs both 'commands' and 'container' fields. The container field specifies: - Which image to use (firewatch:main) - Credentials to mount (firewatch-tool-jira-credentials) Generated periodic job: - periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation Validated with: make update (exit code 0)
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tanfengshuang The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 480 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-openshift-release-master-firewatch-jira-token-test-firewatch-jira-cloud-token-validation |
|
@tanfengshuang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/test all |
|
@tanfengshuang: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
No description provided.