Using GitLab for application packages in CloudCenter 4.8.2

[AJSandham]

Hi there,

I'm not sure if this is a supported approach or not, but I am trying to leverage a GitLab repo for storing and accessing application packages as part of a pipeline we are putting together. I am not having any luck when either setting the zip location in the application properties for our apache application in the modeller, nor in the Service Initialization configuration section.

I have set up a GitLab.com repo, so it can be selected from the drop down. The file path specified after includes the following "<groupName>/<ProjectName>/tree/master/<package>.zip" with no luck. We have performed this with the provided repository appliance, that is installed on AWS. However, we are not having success with gitlab.com unfortunately.

Any help/guidance would be very much appreciated.

Thanks,

Adrian

[viparame · Accepted solution]

Hi Adrian,

GitLab for application packages are not supported in 4.8.2 because while downloading any files / zip files it adds a commit ID to the zip file due to which CloudCenter does not recognize the service ID. 

You can alternatively use Github or any other source of repository to store your app service.

Regards

Vihar Kuruppathukattil

[AJSandham]

Hi Vihar,

Thanks for the response and workaround, do you know if it will potentially be supported in any up coming releases?

Thanks,

Adrian

[viparame · Accepted solution]

Hi Adrian,
We have already filled an enhancement for this but still its not resolved yet.
CDETS Ref: CSCvi68367

[Boobalan Rathinam]

Hi Adrian,

I have tried downloading archive files from Gitlab in app profile external lifecycle workflows and it has worked fine in v4.8.2. One thing to note is, archive files should be read as raw files from Gitlab, otherwise uncompressing it would fail.

For example, the package i used in my external lifecycle was using the format <groupName>/<projectName>/raw/<branchName>/<package>.zip & GitLab was added as a HTTP repository in CloudCenter.

Try this and let us know how it goes. If this is still failing, i would recommend you to open a SR and attach debug level traces to troubleshoot this further.

[AJSandham]

Hi there,

Sorry for the delay, thanks for the detailed response here. The way you have described this below is the same approach I have been using unfortunately. I will work on getting the logs back to you and look at the other request that has been previously opened.

Thanks,

Adrian