Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: same vcs info appened twice when running jf rt build-add-git command twice #250

Open
wants to merge 21 commits into
base: dev
Choose a base branch
from
Open

fix: same vcs info appened twice when running jf rt build-add-git command twice #250

wants to merge 21 commits into from

Commits on Jun 3, 2024

  1. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    72790c6 View commit details
    Browse the repository at this point in the history

  2. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    9f19532 View commit details
    Browse the repository at this point in the history

  3. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    c3fd8a3 View commit details
    Browse the repository at this point in the history

  4. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    dd7ab41 View commit details
    Browse the repository at this point in the history

  5. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    559b84c View commit details
    Browse the repository at this point in the history

  6. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    3489587 View commit details
    Browse the repository at this point in the history

  7. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    e6913a9 View commit details
    Browse the repository at this point in the history

  8. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    b31bce4 View commit details
    Browse the repository at this point in the history

  9. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    08c407c View commit details
    Browse the repository at this point in the history

  10. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    164be69 View commit details
    Browse the repository at this point in the history

  11. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    fd26cf3 View commit details
    Browse the repository at this point in the history

  12. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    acb85d0 View commit details
    Browse the repository at this point in the history

  13. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    9bdb6dc View commit details
    Browse the repository at this point in the history

  14. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    af823a5 View commit details
    Browse the repository at this point in the history

  15. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    a2f6b1d View commit details
    Browse the repository at this point in the history

  16. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    3b1bc45 View commit details
    Browse the repository at this point in the history

  17. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    33e4baf View commit details
    Browse the repository at this point in the history

  18. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    c0b1d24 View commit details
    Browse the repository at this point in the history

  19. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    39204be View commit details
    Browse the repository at this point in the history

  20. Update build-info.json file

    @gerrnot
    JFrog Pipelines Step authored and gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    44387ef View commit details
    Browse the repository at this point in the history

  21. fix: same vcs info appened twice when running jf rt build-add-git com… 

    …mand twice

It turns out to be practical if you can perform issue collection
multiple times using different configurations (different regexes).
However, in this case (and in any case) you do not want to see the vcs
information duplicated. This is fixed hereby.
    @gerrnot
    gerrnot committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    f4cdc63 View commit details
    Browse the repository at this point in the history