Sagar Bud
opened 2 years ago
-
Name Previous Value Current Value Type
Question
Bug
Affected Versions
empty <=10.7.1
-
Name Previous Value Current Value Priority
Major
Minor
-
This is a bug. To work around it, just restart OneDev server after importing.
-
OneDev
changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (8098eec4)
-
Previous Value Current Value Closed
Open
-
Hello @robin,
Is the Bug fixed?
Thanks,
-
At this side, issue is closed as long as code fixing the issue is committed. When the release is available, the issue will be marked as released.
-
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 2 years ago
Previous Value Current Value Closed
Released
-
State changed as build OD-5077 is successful
| Type |
Bug
|
| Priority |
Minor
|
| Assignee | |
| Affected Versions |
<=10.7.1
|
| Labels |
No labels
|
Issue Votes (0)
Watchers (3)
Hello @robin
We have imported repo from GitLab to Onedev and created .onedev-buildspec.yml file. After that, we have pushed some content from our system(laptop) to Onedev then pipeline is not trigger automatically but the changes seeing in repo. Also, we have already set trigger ("When update branches 'develop'") in stages. Also, changes from ui are triggering pipeline but push from laptop not triggering pipeline.
To replicate the issue, we have clone the repo from GitLab to our local system and pushed to Onedev. After that, we have created .onedev-buildspec.yml file then pushed some content from our system(laptop) to Onedev then pipeline is trigger automatically.
So it's working with repos directly created on onedev but imported repos doesn't trigger as per build-spec.yml
Should we need to tweak any setting after importing repo?