CODEWITHSUNDEEP
gitgitlab
rab
rab

Reputation: 163

Commit and Branch disappeared suddenly

EDIT: We are not from the dev team. I have cloned the repo to try command listed below.

My colleague has launched a deploy via Jenkins and 5 min after the deploy stopped with error: 

[WARNING] The requested profile "ntic" could not be activated because it does not exist.
[ERROR] Failed to execute goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) on project nsnet-parent: Error starting release: Error starting release: a release branch [refs/remotes/origin/release/8.15.0] already exists. Finish that first! -> [Help 1]

Here the part of the log where the commitis specified find in jenkins jobs output.

> git.exe config --local --remove-section credential # timeout=10
 > git.exe rev-parse "refs/remotes/origin/RCI^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/RCI^{commit}" # timeout=10
Checking out Revision 7e91bd1bf2353bc74ddb491faf2f83917b487211 (refs/remotes/origin/RCI)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 7e91bd1bf2353bc74ddb491faf2f83917b487211
 > git.exe rev-list 7e91bd1bf2353bc74ddb491faf2f83917b487211 # timeout=10

Since I cannot see the branch Name RCI or the last commit. I have tryed git reflog but I cannot see the commit 7e91bd1bf2353bc74ddb491faf2f83917b487211 or the branch RCI used in deployment. Have you any idea, is it still possible to restore RCI branch and all the code ?

We have Jenkins on Windows and Gitlab-ci for git project Thanks

Upvotes: 1

Views: 637

Answers (1)

VonC
VonC

Reputation: 1328292

I have cloned the repo but it's seems still an error with the command: error: malformed object name 7e91bd1bf

I have tryed git reflog but I cannot see the commit 7e91bd1bf2353bc74ddb491faf2f83917b487211

That happens if the commit was overriden by a force push: cloning the repository, and doing a git log or git reflog in it would not retrieve that commit.
It is best to:

  • recover the old commit/branch from the currently cloned repo one by the Jenkins job (it has the history before the force push)
  • or relaunch the Jenkins job, using the new modified history of the remote repository, and check if the error persists.

Upvotes: 1

Related Questions