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.

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

Merging to release-5.0.15: [TT-13110] remove trimpath from 5-lts build (#6546) #6666

Conversation

buger
Copy link
Member

@buger buger commented Oct 24, 2024

TT-13110 remove trimpath from 5-lts build (#6546)

Description

Remove -trimpath build flag from goreleaser build so that plugins
built with tyk plugin compiler loads.

Related Issue

https://tyktech.atlassian.net/browse/TT-13110

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing
    functionality to change)
  • Refactoring or add test (improvements in base code or adds test
    coverage to functionality)

Checklist

  • I ensured that the documentation is up to date
  • I explained why this PR updates go.mod in detail with reasoning
    why it's required
  • I would like a code coverage CI quality gate exception and have
    explained why

<!-- Provide a general summary of your changes in the Title above -->

## Description
Remove `-trimpath` build flag from goreleaser build so that plugins
built with tyk plugin compiler loads.


## Related Issue
https://tyktech.atlassian.net/browse/TT-13110

## Motivation and Context

<!-- Why is this change required? What problem does it solve? -->

## How This Has Been Tested

<!-- Please describe in detail how you tested your changes -->
<!-- Include details of your testing environment, and the tests -->
<!-- you ran to see how your change affects other areas of the code,
etc. -->
<!-- This information is helpful for reviewers and QA. -->

## Screenshots (if appropriate)

## Types of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Refactoring or add test (improvements in base code or adds test
coverage to functionality)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply -->
<!-- If there are no documentation updates required, mark the item as
checked. -->
<!-- Raise up any additional concerns not covered by the checklist. -->

- [ ] I ensured that the documentation is up to date
- [ ] I explained why this PR updates go.mod in detail with reasoning
why it's required
- [ ] I would like a code coverage CI quality gate exception and have
explained why

(cherry picked from commit 56ec4bc)
@buger buger requested a review from a team as a code owner October 24, 2024 13:25
@buger buger enabled auto-merge (squash) October 24, 2024 13:25
@buger
Copy link
Member Author

buger commented Oct 24, 2024

💔 The detected issue is not in one of the allowed statuses 💔

Detected Status Closed
Allowed Statuses In Dev,In Code Review,Ready for Testing,In Test,In Progress,In Review ✔️

Please ensure your jira story is in one of the allowed statuses

Copy link
Contributor

API Changes

no api changes detected

Copy link

sonarcloud bot commented Oct 24, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
56.8% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

@buger buger disabled auto-merge October 24, 2024 14:24
@buger buger merged commit d3fded6 into release-5.0.15 Oct 24, 2024
30 of 33 checks passed
@buger buger deleted the merge/release-5.0.15/56ec4bc8f2ce2bfd593a2020f93f274a2ca899df branch October 24, 2024 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants