devcharly opened 2 years ago
|
|||||
Regarding the message:
I think that the part |
|||||
Robin Shen changed state to 'Closed' 2 years ago
|
|||||
When clone submodules, the default credential will not work, you will need to create a build secret with value set to an access token with permission to access relevant projects, and use that build secret as clone credential in checkout step. This tutorial has details on how to use custom clone credential: https://code.onedev.io/projects/162/blob/main/pages/push-in-job.md As to OneDev process being killed upon git prompting for password, this should be a bug of JSW (service wrapper library used by OneDev), and I filed an bug as below: https://code.onedev.io/projects/160/issues/649 To avoid this, you will need to run OneDev in service mode: https://code.onedev.io/projects/162/blob/main/pages/run-as-system-service.md |
Type |
Bug
|
Priority |
Major
|
Assignee | |
Affected Versions |
Not Found
|
Having a major problem with git submodule checkout in builds, that hangs OneDev.
My setup:
Have a git repo with two submodules and created a new
.onedev-buildspec.yml
that simply checks out the repo including submodules using step type "Checkout Code" (depth is 1).Running the build shows following and then whole OneDev is dead:
In the Terminal.app, where I started OneDev with
bin/server.sh console
, it outputs:There are still some git processes (used
ps -ef | grep git
):Pressing
Ctrl+C
two times in the terminal kills OneDev.When I try to restart OneDev using
bin/server.sh console
, same message as above appears after some seconds and OneDev is dead. Seems that OneDev tries to continue/restart the build at startup because it deletes an existing<onedev-install>/temp/server/onedev-build<number>
directory and creates a new one.Killing OneDev again with
Ctrl+C
and restarting it sometimes brings it back to life. If not I have to restore a database backup...On the client I'm using SSH to access git. The url of the submodule is specified as relative path in
.gitmodules
. E.g.url = ../mySubmodule
. This works fine on the client. BTW all git repos of submodules are stored in OneDev projects on same machine. The two log filesconsole.log
andserver.log
do not contain any exception or error message. Only standard messages.Any idea how to fix this?