Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCM: SCM job import action when both import/export are enabled can show incorrect status #7010

Merged
merged 1 commit into from
Apr 29, 2021

Conversation

gschueler
Copy link
Member

  • if git import/export use "preserve" uuid feature, and both are enabled, after git import is performed, jobs can still show modified status, because a random UUID was being saved in job metadata as "srcId".

Is this a bugfix, or an enhancement? Please describe.
fixes https://github.com/rundeckpro/rundeckpro/issues/1700

Describe the solution you've implemented

  • Removed the behavior that stored random UUID as srcId on job create from export listener
  • refactor export listener into separate class
  • add tests for export listener
  • also alleviates a race condition: both job import and export would create new job metadata entry in the DB in different threads unaware of the other entry.

* if git import/export use "preserve" uuid feature, and both are enabled, after git import is performed, jobs can still show modified status, because a random UUID was being saved in job metadata as "srcId".
* Removed the behavior that stored random UUID as srcId on job create from export listener
* refactor export listener into separate class
* add tests for export listener
* also alleviates a race condition: both job import and export would create new job metadata entry in the DB in different threads unaware of the other entry.
@gschueler gschueler added this to the 3.4.0 milestone Apr 28, 2021
@mergify mergify bot added the 3.4.x label Apr 28, 2021
Copy link
Contributor

@ronaveva ronaveva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gschueler gschueler merged commit ab1a4bf into main Apr 29, 2021
@gschueler gschueler deleted the issue/pro-1700 branch April 29, 2021 18:41
gschueler added a commit that referenced this pull request Apr 29, 2021
fix: SCM job import action when both import/export are enabled can show incorrect status (backport #7010)
@fdevans fdevans changed the title fix: SCM job import action when both import/export are enabled can show incorrect status SCM: SCM job import action when both import/export are enabled can show incorrect status May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants