Mission:

To achieve core functionality in the UI and migrate more screens to console.redhat to win new customers, encourage existing customers to upgrade to a paid plan, increase retention of current paid users, and foster future Quay business through creating partnerships across the Red Hat ecosystem.

Epic Goal:

Enhance the performance and effectiveness of the Quay UI at scale  by building core functionality with all of the functionalities that exist on Quay.io today. 

Why is this important?

Supporting core UI functionality and performance at scale is crucial for providing a seamless user experience while providing large paying  customers with large content the functionality required to do business at scale.  Achieving UI parity with Quay.io ensures that users can utilize all functionalities without limitations. Addressing critical UI bugs enhances stability and usability, resulting in higher customer satisfaction and enhance their effectiveness on the Quay UI. 

Builds: Builds are fundamental to the container image lifecycle, as they are the process of creating runnable container images from source code or application artifacts. For developers and DevOps teams, builds are essential for maintaining version control, ensuring consistency, and automating the creation of container images. Builds directly impact the quality, security, and performance of containerized applications.

Key aspects of builds' importance:

• Builds are critical for producing reliable and up-to-date container images.
• Properly managed builds enhance the overall security of containerized applications.
• Automated builds streamline the deployment process and support continuous integration and continuous deployment (CI/CD) pipelines.
• Building container images efficiently leads to faster application development and deployment cycles.

Acceptance Criteria

• Initiating Builds: Users need to know how to initiate builds in Quay, including selecting the appropriate parameters and settings for the build.
• Monitoring Build Progress: Users need to know how to monitor the progress of their builds in real-time, including tracking the status of each build stage and accessing detailed build logs.
• Configuring Build Settings: Users need to know how to configure build settings in the UI, including adjusting build environment variables and settings to align with specific project needs.
• Accessing Build Logs: Users need to know how to access detailed build logs within the UI, facilitating efficient issue diagnosis.
• Managing Build Artifacts: Users need to know how to manage and organize build artifacts within the UI, including tagging, pushing, and pulling container images.

This general acceptance criteria ensure that the builds feature within Quay empowers users to effectively manage their development projects, optimize their workflows, and seamlessly navigate the build process.