Sagar Bud
opened 2 years ago
-
You may run build.sh via a command step before the Kaniko step. As long as the generated dist directory is placed under job workspace, you can access it from Kaniko step via build context property.
-
Hello @robin
Thank you for the update.
I will check it and update you. Meanwhile, is Onedev provide deploy key feature like gitlab? if yes, kindly provide the doc for the same. You can refer the below URL for deploy key feature in GitLab. https://docs.gitlab.com/ee/user/project/deploy_keys/
Thanks
-
No deploy key currently. You may use access token instead.
-
Previous Value Current Value Open
Closed
-
Previous Value Current Value Closed
Open
-
Hello @robin
Thank you for the update.
We're using access token while clone the private repo but it give the error(remote: You do not have permission to pull from this project). We have already assigned project owner permission to the user.
We're cloning the private repo while building the docker file using docker kaniko (kubernetes executor). Also, I have checked same docker file is running with docker and shell executor. Is there any user identities we need pass or do you have any solution for the same?
-
Previous Value Current Value Open
Closed
-
This issue duplicates OD-1892
| Type |
Question
|
| Priority |
Major
|
| Assignee | |
| Labels |
No labels
|
Hello @robin,
I have one angular project. In this project I have run build.sh file to create dist directory and use this directory to copy data while build the docker image. Is there any option to run the build.sh file before build the docker file in Build Docker Image (Kaniko) option?
If i run the build.sh file(it will generate dist directory as a Artifact) before the Kaniko build stage. how we can pass this Artifact in Kaniko build stage? Because in Kaniko stage we can run only build command and i want to run the build.sh file before build command.