-
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
Add TaskRun to v1alpha2 🎋 #1725
Conversation
The following is the coverage report on pkg/.
|
I think we should try to do something hacky and bypass it so that we can embed ResourceSpecs in TaskRuns even though they are alpha. |
// ResourceSpec is specification of a resource that should be created and | ||
// consumed by the task | ||
// +optional | ||
// ResourceSpec *PipelineResourceSpec `json:"resourceSpec,omitempty"` |
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.
what if we move resources
e.g. something like pkg/apis/resources/v1alpha1
<-- i think then we'd be able to import resources here?
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.
@bobcatfish I can see multiple ways indeed 👼 I just need to see how easy or hard it is to bend the generators 👼 😈
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.
I am going to try that change in a separate PR btw 👼
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.
@bobcatfish experiment on this #1773 😅
Ok, will look into that 🙊 |
limitations under the License. | ||
*/ | ||
|
||
package v1alpha2 |
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.
one thing thats not clear to me reviewing: how many of these files and tests are duplicated from v1alpha1 and how many are new? (maybe we can include a docstring or something in the copied files explaining that, maybe in the v1lapha1 version, something like "this file is frozen, changes should now happen in " <-- we could even add automation if we do that to make sure ppl aren't changing files they shouldnt)
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.
bumpin this 😇
I think I'm doing a bad job of looking and/or dont know what im looking for: @vdemeester where can I find the logic that will automatically convert v1alpha1 TaskRuns that use the old syntax to the new v1alpha2 syntax? |
well, nowhere :
In a follow-up 🙇♂️ |
5f3e227
to
55d6c68
Compare
The following is the coverage report on pkg/.
|
55d6c68
to
88f9671
Compare
The following is the coverage report on pkg/.
|
88f9671
to
f12eea0
Compare
The following is the coverage report on pkg/.
|
f12eea0
to
ef01769
Compare
Rebased but depends on #1773 if we want to support PipelineResource embedded in |
The following is the coverage report on pkg/.
|
ef01769
to
2a37514
Compare
The following is the coverage report on pkg/.
|
/hold cancel |
/test pull-tekton-pipeline-integration-tests |
/hold This depends on #1841 too now 👼 😝 |
289b59b
to
4a20c66
Compare
The following is the coverage report on pkg/.
|
/hold cancel |
Oof. Rebase needed. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
4a20c66
to
a4c2595
Compare
The following is the coverage report on pkg/.
|
a4c2595
to
fa08b26
Compare
The following is the coverage report on pkg/.
|
This modify how `TaskRunSpec` looks from v1alpha1: - params is now directly under spec - no more inputs and outputs, get replaced by resources - resource has input and output resource declaration fields, similar to how it is used in Pipeline The next step are : - Add more types (Pipeline, PipelineRun, Condition) - Refactor v1alpha1 to embedded v1alpha2 (for storage purpose) - Auto-conversion from v1alpha1 Signed-off-by: Vincent Demeester <[email protected]>
fa08b26
to
b9de9ac
Compare
/lgtm Looking Good! 🤙🏽 |
The following is the coverage report on pkg/.
|
Changes
This modify how
TaskRunSpec
looks from v1alpha1:to how it is used in Pipeline
The next step are :
The spec will look like this (only thing that changed from
v1alpha1
).One important thing to note here though, is as we are keeping the current
PipelineResource
asalpha
, I can't have embeddedResourceSpec
inTaskRun
if we keepPipelineResource
in the same api group... 😅 😓. (That said, we may be able to do something hacky to bypass that problem 🙈 )This should more or less fix #1185
Depends on #1706 and #1720 😅
/hold
Signed-off-by: Vincent Demeester [email protected]
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 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.