Re: Gitlab CI builds for multiple branches
I don't have any suggestions, maybe someone else can chime in. It should not be due to using CE or having the master branch as default branch. Best regards, Sytse Sijbrandij CEO GitLab B.V. On Sun, Sep 21, 2014 at 7:32 PM, tru...@gmail.com wrote: Is there anything to check in gitlab logs for to determine/trace signals to linked gitlab CI? Maybe that's due to the fact i am using gitlab CE? May it be because `master` branch has mark `default` in gitlab? -- You received this message because you are subscribed to the Google Groups GitLab group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/b70611d1-1352-4756-b60e-0e12b788dce4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GitLab group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAJTzhG_fivtXFydzbinWeDtGma%3DH3ioS47BcHwb51v44yiO%2BnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Gitlab CI builds for multiple branches
Is there anything to check in gitlab logs for to determine/trace signals to linked gitlab CI? Maybe that's due to the fact i am using gitlab CE? May it be because `master` branch has mark `default` in gitlab? -- You received this message because you are subscribed to the Google Groups GitLab group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/b70611d1-1352-4756-b60e-0e12b788dce4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Gitlab CI builds for multiple branches
As you expected all commits should be build, not just the ones on master, I have no idea what is wrong. Please let me know if you have any questions or comments. Best regards, Sytse Sijbrandij CEO GitLab B.V. On Fri, Sep 19, 2014 at 4:01 PM, tru...@gmail.com wrote: I have recently set up gitlab CI, integrated with gitlab server. I have suddenly run into an issue: commits to the branches other then `master` do not cause new builds to appear in gitlab CI coordinator. This is not how things are supposed to be, yet i am at loss as to what could e the reason. What should i do to ensude all commits to the project will trigger builds in Gitlab CI. regardless of what branch they are in? -- You received this message because you are subscribed to the Google Groups GitLab group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/73c8e8ce-48f6-46bb-b4c7-0c9d170ac3f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GitLab group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAJTzhG_USJJAxrk7waS_a9S7uwA41Sj0ZQQjtoG%2Bua9Tx4p9Mg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
