Skip to content
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.

NuKeeper is reverting my other changes in it's pull requests. #1112

Open
3 tasks done
MarkFl12 opened this issue Aug 9, 2021 · 7 comments
Open
3 tasks done

NuKeeper is reverting my other changes in it's pull requests. #1112

MarkFl12 opened this issue Aug 9, 2021 · 7 comments
Labels

Comments

@MarkFl12
Copy link

MarkFl12 commented Aug 9, 2021

🐛 Bug Report

I'm running it in TeamCity using a powershell command and quite a few times now it's put in a pull request with the package upgraded but a selection of other recent changes reverted out.

I'm using the command:
nukeeper repo https://company.visualstudio.com/CompanyName/_git/ProjectName %GitAccessToken% --maxpackageupdates 500 --exclude "^(AWSSDK|Microsoft|Hangfire|Amazon)\." --age=0 --verbosity detailed --checkout-directory C:\nk\%build.number%all\

Expected behavior

That it upgrades my packages and doesn't undo other work.

Reproduction steps

I can't see anything different about when it does this compared to when it doesn't even with --verbosity detailed.
Cancelling the PR and deleting the branch followed by re-running will usually not cause the issue again.

Configuration

Version: 0.34.0

Platform if applicable:

  • 🛠️ NuKeeper CLI
  • Windows
  • TeamCity
@msallin
Copy link
Member

msallin commented Sep 20, 2021

Can you provide a repro?

@MarkFl12
Copy link
Author

That makes it happen every time? I'm not sure, I could try running it until the issue happens to get some logs?

@msallin
Copy link
Member

msallin commented Sep 21, 2021

It does not happen every time?
Could it be that the branch you are creating the PR from is behind?

@MarkFl12
Copy link
Author

It might well be that the branch is behind, however the checkout directory doesn't even exist until NuKeeper creates it so if this is the case, it's NuKeeper itself that's pulling already behind.

@msallin
Copy link
Member

msallin commented Sep 21, 2021

Do you have the chance to check the directory which was pulled by NuKeeper after the problem happened?
I.e. check the commit hash and verify that the correct state was pulled.

@MarkFl12
Copy link
Author

I might well be able to, leave it with me.

@stale
Copy link

stale bot commented Dec 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants