Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7308

Pipelines as Code Does Not Report Error For Invalid `on-cel-expression` value

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Before this update, invalid on-cel-expression annotations in the PipelineRun configuration could silently prevent it from triggering, without any error messages in user facing UI. This made it difficult to identify issues when PipelineRun failed to start due to misconfigured expressions. This is solved by a new feature in Pipelines-as-Code (PaC), which now detects invalid CEL expressions and reports the error directly as a comment on the pull request, making troubleshooting much easier.
      Show
      Before this update, invalid on-cel-expression annotations in the PipelineRun configuration could silently prevent it from triggering, without any error messages in user facing UI. This made it difficult to identify issues when PipelineRun failed to start due to misconfigured expressions. This is solved by a new feature in Pipelines-as-Code (PaC), which now detects invalid CEL expressions and reports the error directly as a comment on the pull request, making troubleshooting much easier.
    • Feature
    • Done
    • Pipelines Sprint Tekshift 32, Pipelines Sprint Crookshank 33, Pipelines Sprint Crookshank 34

      Request type: Other
      Reason of urgency: Information request - no urgency

      Request info

      Team: sandboxed-containers
      Tenant: https://console.redhat.com/application-pipeline/workspaces/ose-osc
      Application: openshift-sandboxed-containers
      Component: osc-operator

      Details: 

              How to troubleshoot a problem with build pipelines
        I have a question about the possibility to troubleshoot a problem with build pipelines.
The concrete example is: we modified the 'on-cel-expression' annotation to prevent our operator to be built when non-related files were modified.
We made a typo in the expression making it invalid, merged the change without catching it, and this prevented the build to trigger at all for any PR.

We could find the problem and fix it (see https://github.com/openshift/sandboxed-containers-operator/pull/571), but we couldn't find any error message, logs, anything, saying why the build was not triggering.

From the Konflux console, I could just see the list of triggered builds, but no error about the bad expression.

I'm pretty sure that *something* parsed the expression and made an error, and hopefully logged it somewhere... but where?
Do we have access to some debug logs in the Console, CLI, or from the Konflux bot maybe?

              rh-ee-zashaikh Zaki Shaikh
              jrope Julien ROPE
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: