Skip to content

Feedback on trying to adopt cherry-picker within @ansible/ansible #263

Closed

Description

@webknjaz

Hi @Mariatta,

So as other people started trying out cherry_picker-based flow, some failures to use it happened:

  • It seems like there's not enough terminal output to completely understand when something goes wrong
  • Failed branches disappear without explanation
  • It looks like it pushes into wrong branch, but there's not enough verbosity to verify this.

Ref: ansible/ansible#41403
cc: @abadger

Activity

  1. Mariatta commented on Aug 24, 2018

    @Mariatta
    Member

    I think all of these have been resolved in the 1.2.1 release, right?

  2. webknjaz commented on Aug 24, 2018

    @webknjaz
    MemberAuthor

    Yes, #277 will be addressed separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions