4 ms·

Lots of people use Netlify with GitLab as well. Some using our connection to GitLab and some pushing from GitLab's CI to Netlify via CLI.

sytse 8y ago
Any way we could make the connection with Netlify better? Netlify already added support for GitLab https://www.netlify.com/blog/2016/07/13/gitlab-integration-for-netlify/ https://www.netlify.com/blog/2016/07/13/gitlab-integration-f... Maybe a JAMS template?
- bobfunk 8y ago
  Yeah, we integrate pretty deeply already. We do have some new flows that could potentially make the story around publishing to Netlify from GitLab cloud seamless from an authentication standpoint, would be happy to brainstorm!
  - sytse 8y ago
    Great, please send an email to kirsten@ our company domain with a link to this comment and we'll discuss.
    - isaacdl 8y ago
      Off-topic, but can I compliment you/GitLab on a truly useful cookie notification popup? For me, that meets the spirit of the GDPR!
      - sytse 8y ago
        Great to hear!
    - mkopinsky 8y ago
      The one thing I've experienced on this front that was clunky was integration between netlify and self-hosted Gitlab. If y'all could come up for a solution for that (which is prettier than "manual" deploy using webhook), I'd love both of your companies even more than I already do.
breckuh 8y ago
I just built a test site with Netlify + GitLab. Why must I give it full access to all of my GitLab repositories? I just want to deploy 1 repo. Seems like that opens up unnecessary possibilities for a security breach.
- bobfunk 8y ago
  It's the only option with the current OAuth model, however, we only use the token generated in your web browser, and talk directly to GitLab's API from there. We use the token to add a deploy key and a webhook to the specific repository we're linking to, and after that it's discarded. That way there's no long lived token stored on our end that has access to your whole account.
  - breckuh 8y ago
    Awesome. Great workaround. Thanks!

sytse 8y ago

Any way we could make the connection with Netlify better? Netlify already added support for GitLab https://www.netlify.com/blog/2016/07/13/gitlab-integration-for-netlify/ https://www.netlify.com/blog/2016/07/13/gitlab-integration-f... Maybe a JAMS template?

bobfunk 8y ago
Yeah, we integrate pretty deeply already. We do have some new flows that could potentially make the story around publishing to Netlify from GitLab cloud seamless from an authentication standpoint, would be happy to brainstorm!
- sytse 8y ago
  Great, please send an email to kirsten@ our company domain with a link to this comment and we'll discuss.
  - isaacdl 8y ago
    Off-topic, but can I compliment you/GitLab on a truly useful cookie notification popup? For me, that meets the spirit of the GDPR!
    - sytse 8y ago
      Great to hear!
  - mkopinsky 8y ago
    The one thing I've experienced on this front that was clunky was integration between netlify and self-hosted Gitlab. If y'all could come up for a solution for that (which is prettier than "manual" deploy using webhook), I'd love both of your companies even more than I already do.

breckuh 8y ago

I just built a test site with Netlify + GitLab. Why must I give it full access to all of my GitLab repositories? I just want to deploy 1 repo. Seems like that opens up unnecessary possibilities for a security breach.

bobfunk 8y ago
It's the only option with the current OAuth model, however, we only use the token generated in your web browser, and talk directly to GitLab's API from there. We use the token to add a deploy key and a webhook to the specific repository we're linking to, and after that it's discarded. That way there's no long lived token stored on our end that has access to your whole account.
- breckuh 8y ago
  Awesome. Great workaround. Thanks!