-
Notifications
You must be signed in to change notification settings - Fork 27
Red Hat Trusted App Pipeline update centos-tier-0-stream9 #6
Conversation
The Github CI failure previously was just a flake; restarting the job fixed it. |
I guess an interesting question now is if we continue to use GH as a CI platform or not. Maybe we could keep the jobs but make them opt-in via labels as a fallback? |
I wondered how the job became green :-) I thought I didn't look at the right place |
I'd suggest to keep them for a while. They provide feedback in a shorter time. |
What do I need to do to be able to see the pipeline/workspace? |
Navigate to the https://console.redhat.com/preview/application-pipeline and request access. One of the RHTAP folks will approve you. /cc @brianwcook |
I already did that part - I can log into rhtap just fine. (Unless I'm misunderstanding something) |
- name: git-url | ||
value: '{{repo_url}}' | ||
- name: output-image | ||
value: quay.io/redhat-user-workloads/project-sagano-tenant/sagano/centos-tier-0-stream9:on-pr-{{revision}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's actually target tier-1...the tier-0 is not really fully baked yet.
taskRef: | ||
params: | ||
- name: url | ||
value: https://github.com/stuartwdouglas/build-definitions/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK this is a pretty load bearing part...looks like this points to
stuartwdouglas/build-definitions@bc7f072
/retest |
This should be ready to merge. I deleted the enterprise contract check so the failing check is from the previous run and will never be updated. Note the last green run is 15 hours and old and the failure is 18 hours old. |
Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content
/ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization