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

uptest: latest reusable workflow golang related enhancements are breaking platform-refs uptest pipelines #86

Closed
ytsarev opened this issue Mar 21, 2023 · 0 comments · Fixed by #87
Labels
bug Something isn't working

Comments

@ytsarev
Copy link
Member

ytsarev commented Mar 21, 2023

What happened?

Uptest is failing in platform-refs, see upbound/platform-ref-aws#99

Investigation showed that it happens with the introduction of golang related steps in the reusable workflows https://github.com/upbound/uptest/blob/main/.github/workflows/pr-comment-trigger.yml#L125-L144

These steps are not relevant for Configuration testing where were are not compiling any golang code in contrast to provider repositories

How can we reproduce it?

Follow upbound/platform-ref-aws#99
ел

What environment did it happen in?

  • Uptest Version:
@ytsarev ytsarev added the bug Something isn't working label Mar 21, 2023
ytsarev added a commit to ytsarev/official-providers-ci that referenced this issue Mar 21, 2023
* Introduce new input for the pacakge type
* Execute golang related steps for Provider package type by default
* Intention is to skip them in situations like Configuration package
  type testing and not fail in cases like upbound/platform-ref-aws#98
* Fixes upbound#86

Signed-off-by: Yury Tsarev <yury@upbound.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant