Labels

Admin
193
AlreadyInOctane
0
Analysis
74
Authentication
36
Content - Integrations
24
Install
41
Integrations
157
Monitors
56
Permissions
45
Platform
100
Protocols
72
Reporting
93
REST API
70
Scenario
136
Idea ID: 2880066

Looking for a way to allow vugen to upload folders to git repository.

Rugigi Rugira  
Status: Needs Clarification

Hello,

I have a customer who is integrating Jenkins and Git with LRE.

All the configuration for the integration is done correctly, and in Jenkins, the customer specifies where the script should be stored after he commits and pushes the changes.

In Jenkins, we can see that the changes were done correctly, but when the customer goes to LRE, he can’t find the script under the scripts folder created in the LRE application.

The customer is looking for a way that Vugen can upload the script folder in .zip format to GIT repository.

It seems that VuGen only updates the root branch of the repository, not subfolders.

Thank you in advance

  •  

    This is how we do it in our lab:

    Git - Jenkins - LRE integration is accomplished via

    1. LR Script(s) in Git according path in LRE project.(not stored as a zip file)
    2. Source Code Management: Git integration from Jenkins.
    3. Build Steps: Synchronize LoadRunner Enterprise With Git (plugin: OpenText LoadRunner Enterprise integration With Git Version)

    You should use tool like TortoiseGit (or the good old command line) to clone repo to local computer and access script locally with VuGen.
    Also use a good designed .gitignore to prevent to upload to many temp files in Git.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.