-
For what I am trying to do I found an elegant workaround, nonetheless this seems like a bug, or at least unclear behavior.
-
Previous Value Current Value Open
Closed
-
This is expected behavior. When a branch is updated, only the build spec defined in updated commit is checked (in your case, no build spec in master branch) to trigger necessary jobs.
-
Whenever a commit is involved in CI/CD, only its associated build spec is used. This makes CI/CD logic living together with code and is key for "CI/CD as code".
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
10.2.1
|
| Labels |
No labels
|
Issue Votes (0)
I have an instance of OneDev deployed in a private network for the purposes of doing CD inside of the private network. My repo has two branches:
masterandprod.prodis the default branch which contains a.onedev-buildspec.yml. One of the jobs defined is to syncmasterwith a public GitHub repo:Since
masteris synced with the public GitHub repository, it does not and should not contain a.onedev-buildspec.ymlfile. The syncing ofmasterbranch works fine.However, in the
.onedev-buildspec.ymlof theprodbranch I have a second job which is supposed to trigger when themasterbranch updates:This trigger does not work and the job does not run when the
masterbranch is updated, no matter whether it's updated by thePull from GitHubjob or manually from the command line withgit push origin master.