Skip to content

Conversation

reegnz
Copy link
Contributor

@reegnz reegnz commented Oct 13, 2025

When using the argocd.argoproj.io/manifest-generate-paths the user
explicitly requests argocd NOT to sync if files irrelevant to the
application change.
The repo server logic did properly report no changes when this
annotation is set, but it incorrectly reported the latest commit hash
known to the repo server. This commit hash then pollutes the sync
history of an application, because no actual sync of resources is
happening and the history will show commits unrelated to the service.

This change fixes this behaviour, and returns the provided syncRevision
back to the caller if no new changes were detected since the
syncRevision.

Fixes #17280

Signed-off-by: Zoltán Reegn [email protected]

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

When using the `argocd.argoproj.io/manifest-generate-paths` the user
explicitly requests argocd NOT to sync if files irrelevant to the
application change.
The repo server logic did properly report no changes when this
annotation is set, but it incorrectly reported the latest commit hash
known to the repo server. This commit hash then pollutes the sync
history of an application, because no actual sync of resources is
happening and the history will show commits unrelated to the service.

This change fixes this behaviour, and returns the provided syncRevision
back to the caller if no new changes were detected since the
syncRevision.

Fixes argoproj#17280

Signed-off-by: Zoltán Reegn <[email protected]>
@reegnz reegnz requested a review from a team as a code owner October 13, 2025 13:56
Copy link

bunnyshell bot commented Oct 13, 2025

❗ Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@reegnz reegnz changed the title fix: reposerver should return syncRevision if no changes detected fix: reposerver should return syncRevision if no changes detected (#17280) Oct 13, 2025
@reegnz
Copy link
Contributor Author

reegnz commented Oct 13, 2025

It would also be great if this could be cherry-picked to v3.0 and v2.14

@seanorama
Copy link

+1

The BunnyShell errors don't appear to be public. Requires a paid subscription and even with the trial, I can't see them.

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.

ArgoCD generates irrelevant history records/sync results in monorepo setups during manual sync.

2 participants