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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
build a feature in CodePipeline that allows AWSTOE document testing and then integration with junit CodePipeline report groups. CodePipeline is the preferred cloud native CICD, and we want the ability to test component documents prior to deployment.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The problem is that there is no frictionless pathway for CICD with the AWSTOE document testing and we want a solution that uses native services. The solution would provide a pattern for repository structure and would also give guidance on how to setup an AWSTOE EC2 for RHEL and Windows.
Are you currently working around this issue?
How are you currently solving this problem?
We are not, we wait for ImageBuilder to fail.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
build a feature in CodePipeline that allows AWSTOE document testing and then integration with junit CodePipeline report groups. CodePipeline is the preferred cloud native CICD, and we want the ability to test component documents prior to deployment.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The problem is that there is no frictionless pathway for CICD with the AWSTOE document testing and we want a solution that uses native services. The solution would provide a pattern for repository structure and would also give guidance on how to setup an AWSTOE EC2 for RHEL and Windows.
Are you currently working around this issue?
How are you currently solving this problem?
We are not, we wait for ImageBuilder to fail.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered: