-
Name Previous Value Current Value Type
Bug
Support Request
-
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?
-
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.ymlstill 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.
-
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.
-
Previous Value Current Value Open
Closed
-
Previous Value Current Value Closed
Open
-
Mistakenly closed. Reopening.
-
Previous Value Current Value Open
Closed
-
Close due to no future input.
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
Hi and thank you for OneDev.
.onedev-buildspec.ymlfile in the new OneDev project and work from there.onedev-buildspec.ymlfile in the remote repo of GiteaEXCEPT for the
.onedev-buildspec.ymlfile 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.ymlfile...How do I solve the issue?
Thanks, S.