Polara Group
opened 3 months ago
-
Build spec import will only import the spec itself. Build secrets will not be imported for security reasons. To work around this issue, you may define the job secret in a project that is ancestor of both projects.
-
Build spec import will only import the spec itself. Build secrets will not be imported for security reasons. To work around this issue, you may define the job secret in a project that is ancestor of both projects.
Ah, so I'd need to create in theory a master project which can be like "my-organization" and then set both the template and other projects as children of that master project, and define the secret in the master project?
-
Yes, that is correct.
-
Yes, that is correct.
Gotcha, just to confirm, this is how CI/CD is usually conducted? A master project is at the organization or application name level, then a template is inside that is imported by other child projects of the master project?
Sorry if this is basic! Just new and trying to learn to do this the right and "standard" DevOps way.
-
This is specific to OneDev. Other CI/CD approach may not have template or inheritance concept.
-
This is specific to OneDev. Other CI/CD approach may not have template or inheritance concept.
Got it, thank you so much for the help!
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
Not assigned
|
| Labels |
No labels
|
Hi, I am new to OneDev and CI/CD entirely, and trying to understand how to share Job Secrets between multiple projects.
I setup a build spec on a new project called "PROJECT-TEMPLATE" with a job secret used for pushing to GitHub. It works like a charm in that PROJECT-TEMPLATE project and builds, however, when I create a new project, let's call it "Proj-A" and in it's build spec import the "PROJECT-TEMPLATE," it doesn't build because it's reporting that it's missing the job secret defined in the "PROJECT-TEMPLATE" steps.