ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Download Artifact from GIT
Article ID: 103068
Updated On:
Products
CA Release Automation - Release Operations Center (Nolio)
CA Release Automation - DataManagement Server (Nolio)
Issue/Introduction
When using Artifact Management to download artifact from GIT, what has to go into following fields
Repository URL - Can the repository URL be https (I believe it is https always, not sure)? If yes , how does it's implement key or certificate , if needed?
Branch - If I use master, how I fill it
Full Executable Path - does it mean full path to download? Some detail should help, is it the git.exe path?
File from repository - How does it fill? can it be folder
Environment
Release:
Component: RAROC
Component: RAROC
Resolution
** Repository URL is generally like this - https://github.com/users/New_Repo1.git
If you have a key or certificate, you may have to include that in the Repository URL and does not have to fill username and password.
https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'rs/
** Branch is generally not master, but if it is master, you should be able to specify 'master'.
** Full Executable path is the location from where the actual download will happen.
** File from Repository is the file that you are tying to pull and cannot be a folder.
If you have a key or certificate, you may have to include that in the Repository URL and does not have to fill username and password.
https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'rs/
** Branch is generally not master, but if it is master, you should be able to specify 'master'.
** Full Executable path is the location from where the actual download will happen.
** File from Repository is the file that you are tying to pull and cannot be a folder.
Feedback
Yes
No
Powered by
