
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2017 11:24 AM
Pulling files into your app from a raw, public GitHub path is easy. But for private repo's we need to use a personal token. Has anyone been able to successfully configure a CloudCenter repo pointing at a private GitHub repo and pull those files into your CloudCenter app? Token, SSH key/cert or otherwise?
Thanks!
Solved! Go to Solution.
- Labels:
-
CloudCenter
-
Integrations
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2017 02:07 PM
Michael,
We are going to release a CICD dCloud lab that has Jenkins/Artifactory/GitLab (not GitHub) integrated. The communication between Jenkins & GitLab will be token-based, as is the communication between the local repo and the remote GitLab repo. I could share the details with you privately if you would like. Does that satisfy your use case or are you thinking of something different?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2017 02:07 PM
Michael,
We are going to release a CICD dCloud lab that has Jenkins/Artifactory/GitLab (not GitHub) integrated. The communication between Jenkins & GitLab will be token-based, as is the communication between the local repo and the remote GitLab repo. I could share the details with you privately if you would like. Does that satisfy your use case or are you thinking of something different?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2017 02:51 PM
Hi Tuan,
Thanks for the reply. Yes, please send what you have and hopefully I can figure it out from there.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2017 08:07 AM
If you want to directly refer to a private github file from CloudCenter, what you could do is specify a command to download the file, then pipe it to bash. The command to download the file can be found here:
Don't use the -O option though, as that saves the file. Instead so something like
<command to download using token> | bash
All of that would go into the lifecycle action field using the choice "Command or URL"
