IBM Cloud - Structured Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you.

  1. To post a new idea - select "Add a new idea" and where asked select the appropriate category this idea relates to. Provide requested information to allow us to get a better understanding of your request.

  2. Vote ideas that matter most to you.

  3. Get feedback from the IBM team to refine your idea.

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

IBM Delivery Pipeline Logs

IBM Delivery Pipeline logs should be present and stored somewhere to keep a track of activities and errors for future reference

  • Guest
  • Jul 19 2021
  • Not under consideration
Idea priority Urgent
Needed By Month
  • Admin
    Peter Klenk commented
    17 Aug, 2021 02:53pm

    I believe this request is related to "Classic" delivery pipeline. In Tekton pipelines changes to the pipeline happen in code, in a repo, so there is an audit trail. The few cases in Tekton where this is not true will be moving in that direction. There is no plan to address this in Classic pipelines.

    Execution logs can be persisted from the pipeline, see the DevSecOps reference implementation templates for an example of preserving evidence in a repo.

    If I'm missing some other aspect of this request please let me know.

  • Guest commented
    20 Jul, 2021 03:38pm

    This is a nice feature to have! Especially when we deal with production pipelines with complicated configurations. This feature could help the team easily debug what went wrong and what should be done if there is anything wrong with the pipeline.

  • Guest commented
    20 Jul, 2021 02:15pm

    This would be great as we had issues where changes to the pipeline occured but we had no record of what or how it happened. There should be a place where you can see the logs of any issues or modifications made to the pipeline

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.