You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our development teams use a software development lifecycle process that builds a versioned artifact for the final product. This process has been extended to the development of Ansible projects, which include the roles, modules, plugins, and playbooks required for the project's goals. The build process produces an immutable artifact in Artifactory, and our users need to be able to pull that artifact into AWX instead of pulling it from the git repository used in development.
A generic feature to pull archives from a remote URL would fill this use case, as well as other use cases, such as GitHub Releases
From the UI perspective, all that is necessary for this SCM type is the SCM URL field, as there is no generic concept of branch/ref spec/version for artifact URLs.
To kick off this discussion, PR #7911 implements the feature as I envision it for general use.
The text was updated successfully, but these errors were encountered:
This has been tested and is functional -- there is a small follow-up issue about tooltips which will be filed separately. This tooltip should have a black background like other tooltips, and the links should maybe be formatted.
ISSUE TYPE
SUMMARY
Our development teams use a software development lifecycle process that builds a versioned artifact for the final product. This process has been extended to the development of Ansible projects, which include the roles, modules, plugins, and playbooks required for the project's goals. The build process produces an immutable artifact in Artifactory, and our users need to be able to pull that artifact into AWX instead of pulling it from the git repository used in development.
A generic feature to pull archives from a remote URL would fill this use case, as well as other use cases, such as GitHub Releases
From the UI perspective, all that is necessary for this SCM type is the SCM URL field, as there is no generic concept of branch/ref spec/version for artifact URLs.
To kick off this discussion, PR #7911 implements the feature as I envision it for general use.
The text was updated successfully, but these errors were encountered: