Docs

Development

What this screen is for

Development connects Fenwave to the things your teams already use: their Git repositories, the CI/CD tools that build and deploy, the projects and components that appear in the catalog, the addons installed on clusters, and third-party integrations.

Nothing in Build or Deploy works until this area is filled in. A pipeline needs a repository and a CI/CD integration; a catalog entry needs a project.

Before you start

Tab Read Change
Projects platform-settings.project.read .project.create .update .delete .assign-owner .manage-components .view-details
Repositories platform-settings.repository.read .repository.create .update .delete .validate, plus .repository.ssh.generate .regenerate .delete
CI/CD platform-settings.cicd.read .cicd.create .update .delete .validate
Addons platform-settings.addon.read .addon.create .update .delete
Integrations platform-settings.project.read platform-settings.project.update

Register your clusters in Infrastructure first. CI/CD integrations and addons are attached to clusters, so neither can be configured before a cluster exists.

Opening it

  1. Settings in the sidebar.
  2. Development.

Direct URL: /platform-settings/development

The interface

📸 Screenshot Placeholder: The Development page with its five tabs. Mark: (1) the tab bar showing Projects, Repositories, CI/CD, Addons, Integrations, (2) the table for the selected tab, (3) the Add button.

# Control What it does When you’d use it
1 Tab bar Projects · Repositories · CI/CD · Addons · Integrations Switching between configuration jobs
2 Table The entries for the selected tab Reviewing what is connected
3 Add button Opens the creation dialog for that tab Connecting something new

Walkthroughs

Use the tabs in this order on a new install, since each depends on the one before it:

  1. Repositories — connect the Git repositories.
  2. CI/CD — connect Argo CD or Argo Workflows so pipelines can run.
  3. Projects — declare projects and components so they appear in the catalog.
  4. Addons — install cluster addons where needed.
  5. Integrations — connect Jira and Slack if you use them.

Scenario

Connect a new Git repository and wire it up so the first pipeline can run.

  1. Repositories — click Add, choose the provider, and pick an authentication method. If you choose SSH key, either provide one or have Fenwave generate it; the generated public key must then be added as a deploy key on the provider side. This step is what silently blocks every later clone if skipped.
  2. Use the revalidate action on the row. Do not assume the credentials work — validation is the only thing that proves it, and it is cheap.
  3. CI/CD — add the integration for the tool that will run the build. Choose the correct location: Same Cluster if the tool runs on the cluster Fenwave deploys to, External Cluster or External otherwise.
  4. Test the integration. The Last Tested column records when this last succeeded — an empty value there means it has never been proven to work.
  5. Projects — create the project and its components so the repository appears in the catalog with an owner.
  6. Go to Build › Create an Application and start a pipeline.

If step 6 fails, come back to step 2 and step 4: an unvalidated repository or an untested CI/CD integration accounts for most first-pipeline failures.

When it doesn’t work

Symptom Cause How to check Fix
A tab is missing You lack its read permission Access Explorer Ask for a role granting it
Cannot add a CI/CD integration — no cluster to pick No cluster registered Infrastructure › Clusters Register a cluster first
Pipeline fails at clone Repository credentials never validated, or SSH key not installed on the provider The repository row’s validation state Revalidate; add the public key as a deploy key
Pipeline never starts CI/CD integration untested or pointing at the wrong location The Last Tested column Test the integration; check the location type

Next