|
TheAnachronism opened 2 weeks ago
|
||||
|
OneDev CI/CD is maintained in a yaml file. For instance, the CI/CD file for OneDev itself: https://code.onedev.io/projects/160/files/main/.onedev-buildspec.yml?view-plain=true You can copy/paste/diff, or even change it directly. The GUI simply helps you to author it without any knowledge of the grammar. |
||||
|
|
Ah, OK! Thanks, |
||||
|
|
TheAnachronism changed state to 'Closed' 2 weeks ago
|
| Type |
Discussion
|
| Priority |
Minor
|
| Assignee |
Issue Votes (0)
Watchers (4)
Many git SaaS platforms and CI/CD platforms support the definition of their CI/CD workflows as code. Be it with YAML or some other format, one can apply these workflows by simply committing them inside the repository.
An example for that would be GitLab, which has it's .gitlab-ci.yaml system. I've worked with Atlassian Bamboo before and have some experience with setting up multiple workflows with a GUI and even though I was against it in the beginning, I realized that creating these workflows is much easier if one can have them inside some code structure.
Is there any plan to support this?