Skip to content

Helm autodiscovery failed when "groupby: all" and stash (BitBucket) #8926

Open

Description

@nlevee

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When applying, updatecli open the PR, but try to open PR for other commit even if we have "groupby: all"

18-May-2026 14:58:39	DEBUG: No CI pipeline detected (unknown CI Engine)
18-May-2026 14:58:41	DEBUG: http cache store: https://bitbucket.mydomain.com/rest/api/1.0/projects/POC/repos/helm-values/pull-requests?limit=30
18-May-2026 14:58:41	DEBUG: http cache store: https://bitbucket.mydomain.com/rest/api/1.0/projects/POC/repos/helm-values/branches?limit=30
18-May-2026 14:58:41	DEBUG: Title:        "Bump Helm Chart Dependencies"
18-May-2026 14:58:41	Body:        "\n\n\n# Bump dependency ..."
18-May-2026 14:58:41	Source:
18-May-2026 14:58:41	"updatecli_main_update-helm-chart-dependencies-dev"
18-May-2026 14:58:41	target:        "main"
18-May-2026 14:58:42	Bitbucket pullrequest successfully opened on "https://bitbucket.mydomain.com/projects/POC/repos/helm-values/pull-requests/1469"
...

18-May-2026 14:58:50	DEBUG: No CI pipeline detected (unknown CI Engine)
18-May-2026 14:58:50	DEBUG: http cache hit: https://bitbucket.mydomain.com/rest/api/1.0/projects/POC/repos/helm-values/pull-requests?limit=30
18-May-2026 14:58:50	DEBUG: http cache hit: https://bitbucket.mydomain.com/rest/api/1.0/projects/POC/repos/helm-values/branches?limit=30
18-May-2026 14:58:50	DEBUG: Title:        "Bump Helm Chart Dependencies"
18-May-2026 14:58:50	Body:        "\n\n\n# Bump dependency ...."

18-May-2026 14:58:50	Source:
18-May-2026 14:58:50	"updatecli_main_update-helm-chart-dependencies-dev"
18-May-2026 14:58:50	target:        "main"
18-May-2026 14:58:50	DEBUG: RC: 409
18-May-2026 14:58:50	Body:
18-May-2026 14:58:50	{%!s(*otelhttp.wrappedBody=&{{<nil> {[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] [0 0 0 0 0 0 0 0] 0 {[]} false} 0x81944e3fe50} {{} 1} 0xc17860 0x81943bdb200 {{} {} 4079}})}
18-May-2026 14:58:50	ERROR: action stage:        "Only one pull request may be open for a given source and target branch"

...

18-May-2026 14:58:50	Run Summary
18-May-2026 14:58:50	===========
18-May-2026 14:58:50	Pipeline(s) run:
18-May-2026 14:58:50	  * Changed:        1
18-May-2026 14:58:50	  * Failed:        14
18-May-2026 14:58:50	  * Skipped:        0
18-May-2026 14:58:50	  * Succeeded:        1
18-May-2026 14:58:50	  * Total:        16
18-May-2026 14:58:50	
18-May-2026 14:58:50	One action to follow up:
18-May-2026 14:58:50	  * https://bitbucket.mydomain.com/projects/POC/repos/helm-values/pull-requests/1469
18-May-2026 14:58:50	ERROR: running actions failed: errors occurred while running actions:
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch
18-May-2026 14:58:50	        * Only one pull request may be open for a given source and target branch

Expected Behavior

  • Pipeline finish without error

Steps To Reproduce

update.yaml (template)

name: "Bump Helm Chart Dependencies"
pipelineid: "update-helm-chart-dependencies-{{ .environment }}"

scms:
  bitbucket:
    kind: stash
    spec:
      url: "https://bitbucket.mydomain.com"
      owner: "{{ .bitbucketProjectKey }}"
      repository: "{{ .bitbucketRepoSlug }}"
      username: '{{ requiredEnv "BITBUCKET_USER" }}'
      token: '{{ requiredEnv "BITBUCKET_TOKEN" }}'
      branch: "main"
      commitmessage: 
        hidecredit: true

autodiscovery:
  groupby: all
  scmid: bitbucket
  actionid: pr-{{ .environment }}
  crawlers:
    helm:
      rootdir: "."
      ignorecontainer: true
      only:
        {{- range .scanPath }}
        - path: "{{ . }}"
        {{- end }}
      versionincrement: "none"
      versionfilter:
        kind: regex
        pattern: '^v\d+\.\d+\.\d+-{{ .environment }}-(\d+)$'

actions:
  pr-{{ .environment }}:
    kind: stash/pullrequest
    scmid: bitbucket
    title: "Bump Helm Chart Dependencies for {{ .environment }}"

values.yaml :

# Configuration Bitbucket / Stash
bitbucketProjectKey: "POC"
bitbucketRepoSlug: "helm-values"

# Path to the folder containing the Chart.yaml in the target repository
scanPath: 
  - "apps/dev/*/*/nginx-*" # ex: apps/dev/emea/my-app/my-ms

# Environment to filter the versions to update, e.g. dev, uat, prd
environment: "dev"

File tree exemple :

dev
 ┗ emea
 ┃ ┣ sandbox
 ┃ ┃ ┣ mfe-image-dashboard
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ mfe-image-dashboard.yaml
 ┃ ┃ ┣ pes-front-test
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ pes-front-test.yaml
 ┃ ┃ ┗ pes-ms-test
 ┃ ┃ ┃ ┣ Chart.yaml  
 ┃ ┃ ┃ ┗ pes-ms-test.yaml
 ┃ ┗ tools
 ┃ ┃ ┣ bamboo
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ bamboo.yaml
 ┃ ┃ ┣ buildkitd
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ buildkitd.yaml
 ┃ ┃ ┣ deployment-notification
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ deployment-notification.yaml
 ┃ ┃ ┗ sonarqube
 ┃ ┃ ┃ ┣ Chart.yaml
 ┃ ┃ ┃ ┗ sonarqube.yaml

Environment

- OS: Ubuntu 20.04
- updatecli: v0.117.0

Activity

  1. olblak commented on May 19, 2026

    @olblak
    Member

    @nlevee Thanks for the issue, could you try the setting groupby instead of groupeby ?
    If you use an IDE that support jsonschema like neovim or vscode, you get manifest validation if you manifest has directory parent named updatecli.d

  2. nlevee commented on May 19, 2026

    @nlevee
    Author

    Hi @olblak ,
    As you can see in my configuration dump, it's already "groupby: all", i've made a mistake in my description only.

  3. olblak commented on May 19, 2026

    @olblak
    Member

    Good to know, I'll try to reproduce

  4. nlevee commented on May 19, 2026

    @nlevee
    Author

    Good to know, I'll try to reproduce

    I added a repository tree exemple to helm you to reproduce. If you need anything else I can Help.

  5. olblak commented on May 21, 2026

    @olblak
    Member

    To better understand the issue, Updatecli tries to create the same pull request for the 15 pipelines it generated by the autodiscovery but then fails for the remaining 14
    All commits have already been pushed to the remote branch.
    And all generated pipelines shares the same pipelineid something like update-helm-chart-dependencies-dev
    You can verify this in the generated manifest by running updatecli manifest show ...

  6. nlevee commented on May 21, 2026

    @nlevee
    Author

    Yes this is what I understand, but I think it's not normal that the autodiscovery plugin for Helm need to orchestrate correcly when groupby: all is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions