Ryan opened 2 years ago
|
|||||||
Currently OneDev can not skip CI based on commit message pattern. However you may specify patterns of changed files applicable for a job: For instance, you may specify below pattern to exclude all html files from triggering the job:
|
|||||||
Robin Shen changed fields 2 years ago
|
|||||||
Robin Shen changed title 2 years ago
|
|||||||
OneDev changed state to 'Closed' 2 years ago
|
|||||||
State changed as code fixing the issue is committed |
|||||||
OneDev changed state to 'Released' 2 years ago
|
|||||||
State changed as build #2749 is successful |
Type |
Improvement
|
Priority |
Normal
|
Assignee |
Issue Votes (0)
Apologies if I'm completely missing this somewhere, but is there an option in OneDev to "skip" a CI run?
Use case: My CI/CD build is set to run on all branch pushes. My CI build actually commits code changes to the repository. When the CI runs, it actually triggers another run because the commit fires the CI again. I'd like my CI build to include a commit message like other CI/CD solutions to skip the run and ignore it.
Ref: