DA: Manual import of component version creates incorrect version if incorrect version number is supplied

ID:    D26600
Published:    15 April 2019
Updated:    25 June 2019

Defect Id


Originally Reported Against

Release Automation

Resolved In

Deployment Automation 6.3




If a component is configured with source type Maven and a user specifies a non-existent version number during a manual import request, DA would create an empty component version with this non-existent version number.  Request that this be changed to log this as a non-existent version and do not create a version if none exists in Maven/Artifactory.

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs