Sharing input sets between projects
long-term
T
Turquoise Ox
We have the ability to share pipeline templates between projects so logically would be to share input sets also between projects.
Log In
Canny AI
Merged in a post:
InputSets at project/org level independent of pipelines
I
Iron grey Chicken
Ability to have InputSets at project/org level to eliminate duplication and inconsistencies on updates.
Canny AI
Merged in a post:
Shared Inputsets
X
Xenacious Unicorn
Is it possible to use the same inputset for multiple pipelines using the git experience?
In my case I’m just trying to avoid what would otherwise be duplicate input set definitions.
Rohan Gupta
Merged in a post:
reuse input sets between different pipelines
K
Kryptonite green Orangutan
we would like to reuse input sets between different pipelines
how can we achieve it?
could you make a feature to make pipeline identifier an array to handle?
inputSet:
name: input-set-pullrequest
identifier: inputsetpullrequest
orgIdentifier: company
projectIdentifier: companyproject
pipeline:
identifier: name
properties:
ci:
codebase:
build:
type: PR
spec:
number: <+trigger.prNumber>
stages:
- stage:
identifier: build
type: CI
variables:
- name: BUILD_TYPE
type: String
value: release
- name: BYPASS_UNIT_TESTS
type: String
value: "false"
I
Iron grey Chicken
Do we have any update on this requests availability?
T
Turquoise Ox
For example versions of helm charts. Lets take a use case where we have to projects one for testing pipelines and developing new ones and changes and on prod ready that's used to deploy to all the environments daily(stable one). I can share pipeline templates between them but I cannot share input sets as there is a reference to the project in the yaml file.
Sudarshan Purohit
Thank you for your request. This is in the long term roadmap for us at Harness. Could you share the kinds of data you'd like to share using Input Sets, between projects? It will help us design the feature.
Sudarshan Purohit
long-term
X
Xenacious Unicorn
I left feedback. Can the status of this request be updated?
Rohan Gupta
Hi Xenacious Unicorn can you elaborate on the use case? Are your pipelines designed similarly?
X
Xenacious Unicorn
Rohan Gupta: We are currently moving away from this design, but we had a pipeline per environment that was hardcoded to that environment. When we cut a release, we were having to create essentially what was duplicate input-sets, one for each pipeline in order to release into each environment. We wanted the ability to associate inputsets to a range of pipelines.
I
Iron grey Chicken
Not all pipelines would have disjoint inputs, it would be better if shared inputs can be stored in git and can be imported in File Store to be referred during execution
Load More
→