Possible to inherit one yml file into another?
Hi - ok, this sounds weird, so hear me out :)
we have a number of developers doing lots of commits and autodeployment. Right now, each dev has a few projects in AV. I've manually set them all up. urgh.
Going to a file format is easier .. but .. they are all doing the same thing EXCEPT during deployment.
for example. They all:
- same silly node pre-init install dance
- build Foo.sln
- test blah.dll's
.. but they each have their own deployment web sites.
So it's like .. the top 60% of the .yml
file is
identical for each dev .. but the deploy:
section is
the only thing different. So, i was wondering... having a
.yml
file like this..
import: common.yml
deploy:
- provider: WebDeploy
....
more importantly, if we change the build process, i don't need
to update all the dev's .yml
files again :) just
common.yml
and viola! they all use the new
changes.
Can this be done already?
Another way of looking at it, is this: allow multiple yml files to be listed in the AV UI and then you can merge those files into a single one and use that single one as the source file.
eg
Space of comma delimited, etc...
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Feodor Fitsner on 10 Jul, 2015 01:54 AM
OK, I see. What would be the benefit of that if that
common.yml
is stored in all their repositories? How would you propagate any changes to common.yml across all devs' repos?2 Posted by Pure Krome on 10 Jul, 2015 01:59 AM
upstream/dev
is the main branch all people branch off.so for me, i have
origin/dev
(which is a copy ofu/dev
) and then I branch off that. Because of that, the upstream will always have the latest build steps incommon.yml
.If there's a change, I would then branch, make a change, PR up to
upstream/dev
.. get accepted and then all dev's do their daily pull-upstream/dev-into-my-current-branch, etc..So i make change, it goes up .. all devs then pull down .. and therefore they get new changes without having to think/worry.
Support Staff 3 Posted by Feodor Fitsner on 10 Jul, 2015 02:10 AM
OK, now I better understand your workflow. So, it's like all devs have the same build/test procedure but deploy to their own environments for testing?
4 Posted by Pure Krome on 10 Jul, 2015 02:25 AM
Exactly! I've also found out about Environments Tab (this morning) (which I think this is why this was made) .. so I'm not sure if that makes my idea obsolete.
5 Posted by Pure Krome on 11 Jul, 2016 03:51 AM
Closing this idea.
Pure Krome closed this discussion on 11 Jul, 2016 03:51 AM.