I am trying to pull files from an existing Gitea-hosted repo
At first, the project and its repo in OneDev are empty
I create a .onedev-buildspec.yml file in the new OneDev project and work from there
I create a job and define one step with a Pull from remote instruction; besides, I also add the credentials to the remote repo as a Secret
I take the precaution to copy the .onedev-buildspec.yml file in the remote repo of Gitea
When executing the Job, everything works fine: the files from the Gitea repo are indeed transferred to the OneDev Project's repo
EXCEPT for the .onedev-buildspec.yml file in the newly pulled OneDev project repo which is nowhere to be found...
And yet the file may have had TWO origins: preexisting in the OneDev Project's repo and in the distant Gitea repo.
As a result I am unable to re-launch the job because it has disappeared as a result of the disparition of the .onedev-buildspec.yml file...
How do I solve the issue?
Thanks,
S.
Stephen Schanged fields1 year ago
Name
Previous Value
Current Value
Type
Bug
Support Request
Stephen Schanged title1 year ago
Previous Value
Current Value
Pulling from an existing mirror git repo: how to keep the .onedev-buildspec.yml file?
Pulling from an existing mirror git repo: how to persist the .onedev-buildspec.yml file?
Stephen S commented 1 year ago
Besides, in my case, this is specially annoying as I have created:
a parent Project
a child project with the name of the distant repo as a Property
So:
The parent-child relationship needs to save the status of the parent repo with a tag.
So, in a way, the .onedev-buildspec.yml still exists in the parent repo as a previously tagged version, and can be recovered.
But it totally disappears from the child repo/project, which is annoying because the name of the distant repo is saved as a Property of the child project > it is lost after a Pull.
Robin Shen commented 1 year ago
Your setup seems complicated. Can you please give me a step-by-step procedure to reproduce the issue including how you set up parent/child relationship, and what do you mean by property here.
You may also reproduce the issue with a sample project in a brand new OneDev setup, and zip and attach the "sampledb" and "site" folder.
Hi and thank you for OneDev.
.onedev-buildspec.yml
file in the new OneDev project and work from there.onedev-buildspec.yml
file in the remote repo of GiteaEXCEPT for the
.onedev-buildspec.yml
file in the newly pulled OneDev project repo which is nowhere to be found... And yet the file may have had TWO origins: preexisting in the OneDev Project's repo and in the distant Gitea repo.As a result I am unable to re-launch the job because it has disappeared as a result of the disparition of the
.onedev-buildspec.yml
file...How do I solve the issue?
Thanks, S.