Summary:
As part of our migration from Jenkins to Konflux, our integration testing depends on bonfire-tekton to deploy applications into Kubernetes namespaces. However, the current basic.yaml pipeline is too limited to support our use cases. We need the ability to define and run custom post-deployment tasks such as make, pytest, atfd, or other steps.
Background: * We rely on bonfire-tekton to deploy applications via the ClowdApplication CRD.

• This is a critical dependency for test cases that require live application deployments.
• The current pipeline (basic.yaml) lacks flexibility for teams needing custom test execution flows post-deployment.

Problem: * Limited documentation on extending the pipeline.

• No examples showing integration of custom commands (make, pytest, etc.) or external tools (e.g., ATFD).
• Difficult to maintain multiple forked pipeline versions across teams.

Request:
 We’re requesting your team to: # Document how teams should extend or fork basic.yaml, including:

• • Referencing custom tasks
  • Updating konflux-release-data appropriately
  • Best practices for organization-specific steps

1. Implement a reference pipeline, such as basic_custom.yaml, that:
   • Includes a post-deploy task hook
   • Demonstrates running a sample make test or pytest
   • Uses placeholders for test execution logic so teams can customize easily
2. Review or help implement tasks such as:
   • make-task.yaml: Run make targets
   • pytest-task.yaml: Run pytest in a mounted workspace
   • Optional: Task integration with ATFD or other internal tooling

Relevant Links: * basic.yaml

• Tasks directory
• konflux-release-data