opendevstack / opendevstack/ods-component-catalog-front

Provisioning of new component with the same name as the product product fails in deployment.

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
56m
Merged PRs (30d)
5

Description

Hi,

when deploying a new component that has the same name as the product this does does work in the component catalog. However, the provisioning of this new component will fail with the following error once it tries to copy the quickstarter [1]:

[Initialize output directory-renovate] **** ENDED stage 'Initialize output directory' for component 'renovate' branch 'master' **** (took 145 ms)
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
ERROR: Target directory 'renovate' must not exist yet
Finished: FAILURE

In this case:
product: renovate
component name: renovate

Maybe either a front end validation or some kind of hint would help here.
Thanks already in advance.

[1] https://github.com/opendevstack/ods-jenkins-shared-library/blob/b813ad48f983816b7642ae51320cb83717735c3b/src/org/ods/quickstarter/CreateOutputDirectoryStage.groovy#L13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the component and product-name validation in the catalog frontend, then compare it with the linked CreateOutputDirectoryStage.groovy failure at line 13. Done means the duplicate-name case is prevented or clearly explained before deployment, with a test covering the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.