Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FLPATH 1048: Extend software template to offer the CI pipeline (Tekton option) #19

Merged
merged 39 commits into from
Mar 6, 2024

Conversation

dmartinol
Copy link
Contributor

  • Add CI option to select b/w Tekton (default) and None
  • In case of Tekton, also generates a tekton folder with the workflow templates to generate the triggering resources
  • In case of Tekton, also generates a GitHub workflow folder to deploy the resources
  • The deploy workflow is invoked by the template

clusterDomain:
title: Cluster domain
type: string
default: cluster-jkrpp.dynamic.redhatworkshops.io
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need for a default for this field.

title: Cluster domain
type: string
default: cluster-jkrpp.dynamic.redhatworkshops.io
description: Cluster domain
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we specify in this context this cluster domain is for the tekton pipeline so it won't be mixed with being also the cluster to run the workflows?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, even if having workflows and tekton on different clusters is something we have never experiment so far (probably the ArgoCD will need its own cluster configuration, in this multi-cluster deployment)

@masayag masayag merged commit 43c8906 into rhdhorchestrator:main Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants