-
Job trigger has an applicable projects setting to allow it being triggered only for designated projects. For CI/CD applicable projects is not specified as I think it is good to turn on for all projects. What causes failure of CI/CD at your side?
-
OK, the release and sync job runs if the project path is
onedev/server. Just use some other name will not trigger that job. -
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
Is there currently any method to prevent builds from running. I have a bunch of forked projects, such as the fork of this repository, and the docs repository, and every time I sync they attempt to run the CI/CD builds and all fail (for obvious reasons).
I can not delete the CI/CD configuration as it would cause divergent branches, so is there any repository setting to prevent CI/CD or disable it. If not, would you mind adding it?
Thanks, Polarian