Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    10
  • Views views
    663
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AccuRev with Jenkins Pipeline

Shane Walton

Does anybody use or have tried to use AccuRev with Jenkins Pipeline?  I'd like to start using containers as agents with Pipeline, but am having trouble figuring out how to add scm steps that involve AccuRev.  I could just create steps with /usr/bin/accurev, but that seems like I'm reinventing the wheel as well as needing to do some dumb/insecure things with passwords.  I'd love to hear other's experiences or approaches. 

Parents
  • 0

    After some trial and error, I have found that using the "Pipeline script from SCM" option in a Pipeline job is a valid approach.  One limitation is that a Jenkinsfile must be maintained in the source tree.  This enables a Jenkins Pipeline job to start on any available agent, "pop" the needed AccuRev stream, map the workspace into and start the container. 

Reply
  • 0

    After some trial and error, I have found that using the "Pipeline script from SCM" option in a Pipeline job is a valid approach.  One limitation is that a Jenkinsfile must be maintained in the source tree.  This enables a Jenkins Pipeline job to start on any available agent, "pop" the needed AccuRev stream, map the workspace into and start the container. 

Children
No Data

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.