OCI Devops functional Enhancement request

[brokedba]

Community Note

• 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

Hi team , I wanted to share my feedback after trying OCI devops for few weeks . Especially the CI part.

Enhancement Request for OCI DevOps

Title: Suggestions for Improved OCI DevOps User Experience

Feature Suggestions:

1. Consolidate Build Stages in a Single YAML File

   • Allow users to define and manage all build stages within a single YAML file.
   • Simplify the configuration process by consolidating build stage definitions.

   example github workflow can have many jobs which contain multiple steps

2. Pause Build Stage with Manual Trigger or Approval

   • Introduce the ability to pause a build stage during the pipeline execution.
   • Enable manual triggers or approvals to control when the build stage continues.

   

3. Standard Runner Compute Configuration for Build and Deployment Stages

   • Provide predefined, standard compute configurations for both build and deployment stages.

   • Simplify the setup process by offering default configurations, reducing user effort.

     • example github actions: only choose the os rest is default

     

4. Introduce Cache Management for Maximum Reusability

   • Implement cache management functionality to optimize the reuse of necessary binaries and files across build stages.
   • Reduce the load on each stage by efficiently storing and retrieving cached artifacts.
     • example github cache actions:

5. Flexible Variable Type

   • Offer a variable type that can be either var or file when the value exceeds 255 characters.
   • Enhance flexibility in handling variable types for different use cases.

6. Variable Masking and Vault Integration

   • Allow variable masking if needed
   • Integrate Vault secrets directly into the interface (parameters tab) so we won't need to use ocids in the yaml file.

7. Improved Log Formatting and Readability

   • Reduce the aggressiveness of log refresh and enhance log formatting for better readability.
   • Optimize log space usage, such as minimizing the space taken by the date.
   • Enable expanding and collapsing of step/job content for easier navigation and analysis.

   • example github workflow

     

8. Support for Extensions

   • Allow for extensions similar to GitHub Actions or GitLab extensions.
   • Enable the reuse of existing solutions and reduce code footprint by leveraging extensions.

9. OIDC Authentication Support (BONUS)

   • Add the possibility to use OIDC (OpenID Connect) authentication in the future (JSON Web Tokens).
   • Support workload federation identity providers for enhanced authentication options.

These feature suggestions aim to enhance the user experience of OCI DevOps in my humble opinion, providing additional convenience, flexibility, and efficiency for users in managing their build and deployment pipelines.

Please note that these suggestions are intended as improvements and not as criticisms of the existing features. They aim to further empower users and optimize their workflow within OCI DevOps.

Thank you for the innovation you're bringing to OCI.

[RahulMR42]

Thank you for the feedback .We will pass these to concerned team to check for further.

[brokedba]

Adding an additional enhancement suggestion regarding OCI devops Code repository.

10. The famous edit button for files so we can edit and commit in the GUI like any other major git solution(GitHub/Gitlab)