Support Gitlab CI as Git and CI provider in Igor

[mdirkse]

At my company we use Gitlab as an SCM hosting solution and we use Gitlab CI to do our CI. We also use Spinnaker, triggering pipelines when new docker images are added to the registry, but we'd like to have the tighter integration that is available for Jenkins (and Travis) and Github (and Stash and Bitbucket).

For this to happen Igor (and various interface things in Deck) would need to be extended to support Gitlab CI.

[tomaslin]

can you describe what you mean by tighter integration and outline what you're trying to do in each service?

[mdirkse]

There are 2 use cases I want to support:

First: the v2 Kubernetes provider will allow the direct application of manifest files via Spinnaker. These manifest files can be sourced in a couple of ways, including having Spinnaker pick them up directly from SCM. Currently the only SCM providers supported by Igor are Stash/Bitbucket and Github. I want to add Gitlab as that's what we use.

Second: Spinnaker provides integration with Jenkins and Travis that allows Spinnaker to kick off jobs in those CI engines, get triggered by jobs and generally do more than is possible with just a web hook. I'd like to implement the same kind of integration with Gitlab CI as, once again, that's what we use.

[tweakmy]

Is this now possible kubernetes v2 provider? Is there any documentation on how this can be done?

[mdirkse]

No docs yet, and fetching stuff from gitlab is not yet supported.

[lwander]

Fetching from gitlab is supported as of 1.8 (the release candidate can be tried at version release-1.8.x-latest-unvalidated): https://www.spinnaker.io/reference/artifacts/types/gitlab-file/

[tweakmy]

Does one need to deploy igor and how (through hal pod)?

[banghuaji]

the doc also supported ,there is no gitlab

artifacts:
gcs:
enabled: false
accounts: []
github:
enabled: true
accounts:
- name: my-github-artifact-account
tokenFile: /home/spinnaker/.hal/default/staging/dependencies/528498863-github
http:
enabled: false
accounts: []
s3:
enabled: false
accounts: []

[vdoodala]

any update on triggering pipeline in spinnaker through gitlab ?

[spinnakerbot]

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

[ilansh]

@spinnakerbot remove-label to-be-closed

[jasonmcintosh]

@spinnakerbot remove-label to-be-closed

[northrup]

I take it by the endless "remove-label-to-be-closed" that there has been no progress on this and no involvement from developers. Is there any way to push this forward? I am in the same circumstances having a GitLab instance for our SCM and CI and wanting to use Spinnaker for a tighter integration between the two.

[dnsmichi]

@northrup I was planning to look into this in the coming months, and add my thoughts or code. For now, I cannot tell exactly when and how unfortunately.

[northrup]

Thanks @dnsmichi - I’ll keep my fingers crossed. Really hoping for this!

[jasonmcintosh]

I will say that artifacts & triggers work pretty well today :)

[karlskewes]

Same thoughts as Jason.
Since this issue was created we have started using webhooks with object store artifacts to achieve desired results.
Be nice to have webhook token/auth support rather than use x509 or basic auth not otherwise all good.

[spinnakerbot]

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

[metri]

@spinnakerbot remove-label to-be-closed

[metri]

@spinnakerbot remove-label stale

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

[metri]

@spinnakerbot remove-label stale

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

[NicolaiSchmid]

@spinnakerbot remove-label stale

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

[metri]

@spinnakerbot remove-label stale

[ahmei0]

@jasonmcintosh please advise if this feature was ever implemented.

i.e. I need to trigger by spinnaker pipeline when a commit is made in gitlab repo - but I don't want to push webhook from gitlab to spinnaker as it needs spinnaker api to be public. So my requirement is Spinnaker does a detect/poll on gitlab commits

[gal-yardeni]

Hi @ahmei0, I don't think Spinnaker is currently able to detect/poll gitlab commits without setting up a webhook. I'm going to close this issue it's pretty old and it's hard to follow. I'd recommend opening a new issue if needed, although I suspect that it's a missing functionality as of now (contributions are welcomed!).