-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update build-gcs resource type to support .tar.gz archives #1200
Conversation
The following is the coverage report on pkg/.
|
This translates Build requests with StorageSource into TaskRun requests with a storage-type input resource using `build-gcs` and the newly* t supported `TarGzArchive` artifact type. *This depends on the not-yet-merged tektoncd/pipeline#1200 and that PR's merge commit is pinned until it's merged.
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
/assign @bobcatfish |
The following is the coverage report on pkg/.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a bunch of minor comments!
Since this does include a breaking change, we should get a couple more owners to review also - like you said its probably a fair guess that no one was using the upload functionality (cuz it wouldnt have worked anyway?) so im okay with it ( @dlorenc @afrittoli @vdemeester @dibyom @abayer and soon to be owner @sbwsg )
) | ||
|
||
// GCSArtifactType defines a type of GCS resource. | ||
type GCSArtifactType string | ||
|
||
const ( | ||
// GCSArchive indicates that resource should be fetched from a typical archive file. | ||
// | ||
// Deprecated: Use GCSZipArchive instead. | ||
GCSArchive GCSArtifactType = "Archive" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make a follow up issue (unless you did already!) to remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any concerns about me just removing it in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we're sure no one is using it, im okay with it but we'll need a few more owners to sign off on it (2 more so we have a total of 4? 1/2 + 1)
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
- support both `ZipArchive` and `TarGzArchive` types now supported by `gcs-fetcher` - mark `Archive` type as deprecated ❌ (`ZipArchive` is the equivalent) - rename `gcs-resource-spec-taskrun.yaml` -> `build-gcs-{targz,zip}.yaml` to make their purposes clearer - make the taskrun name more descriptive - fetch a smaller file (`archive.{zip,tar.gz}`) containing a single file for faster tests ⏩ - remove `test/gcs_taskrun_test.go` which didn't usefully test anything that wasn't tested in the YAML test - update docs to reflect these changes 📜 - explicitly set `gcs-fetcher` image entrypoint And, while I'm at it: - remove support for `build-gcs` upload functionality - this doesn't appear to have worked and AFAIK nobody used it anyway - if we want to support it, we can, but probably not like that... it only supported `Manifest`-style uploads, for instance 🌵 - remove `gcs-uploader` image from flags, and from `vendor/` and from `tekton/` release pipeline YAMLs 🎉
The following is the coverage report on pkg/.
|
/lgtm |
/hold (gotta get one more owner) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ImJasonH, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
Changes
ZipArchive
andTarGzArchive
types now supported bygcs-fetcher
Archive
type as deprecated ❌ (ZipArchive
is the equivalent)gcs-resource-spec-taskrun.yaml
->build-gcs-{targz,zip}.yaml
to make their purposes clearerarchive.{zip,tar.gz}
) containing a single file for faster tests ⏩test/gcs_taskrun_test.go
which didn't usefully test anything that wasn't tested in the YAML testAnd, while I'm at it:
build-gcs
upload functionalityManifest
-style uploads, for instance 🌵gcs-uploader
image from flags, and fromvendor/
and fromtekton/
release pipeline YAMLs 🎉Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task and TaskRun to build and release this image
Reviewer Notes
If API changes
are included, additive changes
must be approved by at least two OWNERS
and backwards incompatible changes
must be approved by more than 50% of the OWNERS,
and they must first be added
in a backwards compatible way.
Release Notes