-
Notifications
You must be signed in to change notification settings - Fork 4
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
Added jib-maven #38
base: main
Are you sure you want to change the base?
Added jib-maven #38
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Aneesh-M-Bhat The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Makefile
Outdated
E2E_MAVEN_PARAMS_PROXY_CONFIGMAP ?= config-proxy-maven | ||
|
||
|
||
E2E_JIB_MAVEN_IMAGE ?= docker.io/aneeshmbhat/tekton-maven:latest |
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.
why this image 🤔
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.
that is where it gets published changing now.
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.
its just for test.
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.
empty docker repo with latest tag for it to get published to
value: $(context.pipelineRun.name) | ||
- name: maven-clean | ||
taskRef: | ||
name: maven |
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.
This also we need to use cluster resolver isn't it ??
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.
we can yes, but not needed necessarily since make install, applys all task in current namespace so it can be directly accessed.
--param="VERBOSE=true" \ | ||
--param="IMAGE=${E2E_JIB_MAVEN_IMAGE}" \ | ||
--workspace="name=source,claimName=task-maven,subPath=source" \ | ||
--workspace="name=dockerconfig,secret=docker-config" \ |
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.
where did we create docker-config
secret 🤔
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.
oh ya that was locally when i was testing, changing that.
f06d8c1
to
489c467
Compare
@Aneesh-M-Bhat: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Added support for jib-maven task.