Docs

CI/CD

What this screen is for

The CI/CD tab connects Fenwave to the tools that actually build and deploy: Argo CD, Argo Workflows, and Bitbucket Pipelines. Without an integration here, pipelines have nothing to run on.

Before you start

To do this You need
See the tab platform-settings.cicd.read
Add an integration platform-settings.cicd.create
Edit one platform-settings.cicd.update
Delete one platform-settings.cicd.delete
Test one platform-settings.cicd.validate

A cluster must be registered first — see Infrastructure › Clusters.

Opening it

  1. Settings › Development
  2. Select the CI/CD tab.

The interface

📸 Screenshot Placeholder: The CI/CD Integrations tab with two integrations listed. Mark: (1) the Type column showing Argo CD, (2) the location chip, (3) the status badge, (4) the Last Tested column, (5) the test action.

# Control What it does When you’d use it
1 Type Argo CD, Argo Workflows, or Bitbucket Pipelines Identifying the integration
2 Location chip Same Cluster, External Cluster, or External Understanding how Fenwave reaches the tool
3 Status badge Whether the integration is currently healthy Triage
4 Last Tested When validation last succeeded, as a relative time The single most useful column on the page
5 Test action Re-runs validation now After any credential or network change

Location types

Location Means Implication
Same Cluster The tool runs on the cluster Fenwave deploys to Reached in-cluster; no external network path needed
External Cluster The tool runs on a different registered cluster Needs that cluster’s credentials to be valid too
External The tool runs outside any registered cluster Needs a reachable URL and its own credentials

Choosing the wrong location is a common setup error, and it fails at pipeline time rather than at save time.

Walkthroughs

Connect Argo CD

Requires platform-settings.cicd.create.

  1. Settings › Development › CI/CD, click Add.
  2. Choose Argo CD as the type.
  3. Choose the location. If Argo CD runs on the cluster you already registered, choose Same Cluster.
  4. Supply the credentials.
  5. Save, then test. Confirm Last Tested now shows a recent time.

Connect Argo Workflows

Same procedure, choosing Argo Workflows. Argo CD and Argo Workflows are separate integrations even when they run on the same cluster — deployments use one, pipelines the other, and connecting only one leaves half the platform inert.

Re-test after a change

Requires platform-settings.cicd.validate.

Whenever credentials rotate or the cluster’s network changes, test the integration rather than waiting for a pipeline to discover the problem.

Scenario

Pipelines submit but never start.

Deployments through Argo CD are fine, so the cluster and its credentials are sound. That narrows it considerably.

  1. Settings › Development › CI/CD.
  2. Look at the Argo Workflows row, not the Argo CD one — pipelines run on Workflows.
  3. Check Last Tested. If it is empty, this integration has never been proven to work; a green save is not a successful test.
  4. Click test. The error names what is unreachable.
  5. If the location is External but Argo Workflows in fact runs on the deployment cluster, edit the integration and set Same Cluster. This is the most frequent cause: the integration saves happily with the wrong location and only fails when a pipeline tries to use it.
  6. Test again, then re-submit the pipeline.

When it doesn’t work

Symptom Cause How to check Fix
Pipelines submit but never run Argo Workflows integration missing or untested Last Tested on that row Add or test the Argo Workflows integration
Deployments work, pipelines do not Only Argo CD is connected The Type column Add Argo Workflows as a separate integration
Integration saves, then fails in use Wrong location type The location chip against where the tool really runs Edit and correct the location
Test fails with a connection error Tool unreachable, or credentials rotated The error from the test action Fix the credentials or the network path, then re-test
Add button absent Missing platform-settings.cicd.create Access Explorer Ask for a role granting it

Next