Re:What’s Next for Gitlab CI: Auto DevOps
by u801e on Friday July 07, 2017 @10:09AM
(#14718423)
For CI, you could have a git hook that could trigger a Jenkins build. For code review, you could use a tool like gerrit or phabricator or even set up an email list to send patch sets.
What other features do Gitlab, Github, or Bitbucket have that wouldn't be covered by that type of setup?
Re:What’s Next for Gitlab CI: Auto DevOps
by pizza234 on Friday July 07, 2017 @04:54PM
(#14722000)
There are no bounds in engineering to how many wheels one can reinvent/reimplement. Ultimately, it's a matter of deciding where to invest the (limited) engineering resources.
What other features do Gitlab, Github, or Bitbucket have that wouldn't be covered by that type of setup?