Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lkingland The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
94c8089 to
7512faf
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2938 +/- ##
==========================================
- Coverage 53.91% 51.81% -2.11%
==========================================
Files 162 162
Lines 14763 19131 +4368
==========================================
+ Hits 7959 9912 +1953
- Misses 5876 8241 +2365
- Partials 928 978 +50
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b68e41f to
e398349
Compare
5600e62 to
e2184c3
Compare
42c9fb7 to
de08716
Compare
|
It ain't perfect, but I would prefer we merge this sooner rather than later as folks need this, and we can open new PRs for any niggling issues. |
twoGiants
left a comment
There was a problem hiding this comment.
Looks pretty awesome! What a great refactoring! 🥇 😸
Learned a lot about the project reviewing it. And I always like it in PRs when many files are removed and only a few added. It feels more cleaned up then. 🧹 😆 🧹
I have 3 files to review left. Will continue on Monday.
Most, if not all comments are non-blocking.
twoGiants
left a comment
There was a problem hiding this comment.
Great job 😸 🚀 🎸 🥇!
This is a big improvement to what is there and the structure is nice, clean and clear.
I haven't found anything critical. Just typos, TODOs which can be extracted into issues and a few minor nice-to-haves.
I am mostly done. The last file I am still reviewing are the e2e-test.go which is the biggest one. I will submit what I have so far for it and the rest today/tomorrow.
twoGiants
left a comment
There was a problem hiding this comment.
Hi @lkingland! Finished the e2e_test.go. That was the biggest one! 😅
Looks good to me!
I have only found some typos and propose to cleanup a bit here and there, extract issues from TODOs and reduce duplication. Can all be done in a follow up, except the TODOs, those I would remove now and create issues. But you decide, its all good 😸
e2e/e2e_test.go
Outdated
| // repo: github.com/functions-dev | ||
| // runtime: go | ||
| // template: http (the default. can be changed with --template) | ||
| if err := newCmd(t, "init", "-l=go", "--repository=https://github.com/functions-dev/func-e2e-tests").Run(); err != nil { |
There was a problem hiding this comment.
https://github.com/functions-dev/func-e2e-tests => hosted on the gitlab instance in the bootstrapped cluster would be nice and more independent 😸 . Maybe also a help-wanted issue for later.
There was a problem hiding this comment.
It could be even be hosted on the git-server available for remote tests.
There was a problem hiding this comment.
I decided to use this so that the E2E tests didn't have a dependency on the cluster having a git server installed, and to test "real world" expected behavior more closely; however I am happy to revisit these assumptions on the call if you'd like and open a ticket to refactor!
e2e/e2e_test.go
Outdated
| } | ||
|
|
||
| // Validate that the name matches what we expect | ||
| if instance.Name != name { |
There was a problem hiding this comment.
Describe shows more than just the name. Maybe we could assert for the entire content?
There was a problem hiding this comment.
Rationale: E2E tests should verify that "describe describes". Unit tests verify that "what describe describes".
| To remove built artifacts, use `make clean`. | ||
|
|
||
| ### Build affecting environment variables | ||
| * `FUNC_REPO_REF` affects which github repo will be used to fetch tekton tasks for on cluster build. Default: `knative/func`. |
There was a problem hiding this comment.
there is still reference to this variable in test/presubmit-tests.sh
| // Buildpacks do not currently support ARM | ||
| if builder == "pack" && (runtime.GOARCH == "arm64" || runtime.GOARCH == "arm") { | ||
| t.Skip("Paketo buildpacks do not currently support ARM64 architecture. " + | ||
| "See https://github.com/paketo-buildpacks/nodejs/issues/712") |
There was a problem hiding this comment.
i dont think this is the right link? it links to general github-config update (go bump and version change); its from 2 years ago
install git server in workflow disable dapr service-to-service test only run private repo test on Linux test full script etc test failure fixes remote s2i builder test full stuffs python functions fixes update func-python e2e wait by duration wait options with extended timeouts for java runtimes import common in git-server.sh disable make buffering import common to dump-logs.sh update dump-logs.sh to handle missing binaries update common.sh to be resilient to missing binaries fix: gitlab tests (retries and skip in CI) full test target - script reenable http default matrix template support user vs system config in registry setup script e2e_test.go increase default timeout full test target add CleanFS option unified github workflow renamed env var standardized envs for int tests dedicated Podman scripts integration test name prefix registry.sh skip docker restart add missing io import to gitlab_int_test.go improve prechecks
|
/lgtm |
| - name: Build and push | ||
| run: | | ||
| for a in amd64 arm64 ppc64le s390x; do | ||
| CGO_ENABLED=0 go build -o "func-util-$a" -trimpath -ldflags '-w -s' ./cmd/func-util |
There was a problem hiding this comment.
How did GOARCH="$a" disappear here?
Refactors E2E tests and workflows
/kind cleanup
Notable Name Changes: the scripts in ./hack were renamed to be simple nouns:
hack/cluster.sh
hack/binaries.sh
hack/images.sh
hack/gitlab.sh