[Feature] Clone branch configurations

[SandroMachado]

What App Center service does this feature apply to?
Build system

Describe the solution you'd like
We should be able to copy build configurations to other branches.

Additional context
Every time we want to create a build from a branch, we need to copy all the configurations. The objective of this feature is to simplify this process.

[nilofer]

Hi @SandroMachado, thanks for this feature request! We aim to make the process as simple for you as possible, and this could definitely help. We'll keep this issue open to track total interest in this ability.

[hitmanmcc]

Can we please make this happen? It's a useful feature!

[adcuz]

This would be very useful, currently it is really difficult when you have many environment variables. I have resorted to building a tool dedicated to mass-updating them via the API.

[struct78]

+1

Being able to automatically clone configuration based off a feature branch's parent would be good too.

[RWOverdijk]

Yes please, this would be really nice. Feature builds are near impossible without configuring each branch now.

I haven't tried this yet but I think it should be possible using these two APIs:

• https://openapi.appcenter.ms/#/build/branchConfigurations_get
• https://openapi.appcenter.ms/#/build/branchConfigurations_create

[patniko]

The issue with those API's are the missing secrets @RWOverdijk. We need to do some work on our end to allow you to clone the configs with secrets, certificate, provisioning profiles, keystores, etc intact.

[RWOverdijk]

Maybe configs shouldn't be branch based at all? Maybe build configs should be their own thing. That way you can add powerful features such as wildcard branch names (feature/* for example). That would be really really neat 😄 Met vriendelijke groet / Kind regards, Roberto Wesley Overdijk SpoonX Founder M. +31 (0)6 15 55 32 43 W. www.spoonx.nl E. wesley@spoonx.nl KvK. 60422696

…

On 15 Feb 2019, 20:12 +0100, Patrick Nikoletich ***@***.***>, wrote: The issue with those API's are the missing secrets @RWOverdijk. We need to do some work on our end to allow you to clone the configs with secrets, certificate, provisioning profiles, keystores, etc intact. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[armyofmarkness]

Being able to clone build configurations would be very useful.

[patniko]

Adding this to next months iteration plan so we can start designing a proper solution for this.

[ogezue]

On buddy build there is a default configuration that is applied automatically. Developers can override it if needed.
Please copy every feature of buddybuild as this has been the best mobile ci/cd on the market (feedback by screenshot, ...)

[RWOverdijk]

Yes. I second that. But, buddybuild has betrayed us all. Leave out the betrayal bit when cloning features.

I cri evrytim :(

[chrisheninger]

From what I've been building– the biggest pain point has been needing to re-upload the provisioning profile, certificates, or keystore each time I want to deploy a new branch.

If cloning branch configurations will also pull the signing info over– this feature will be amazing. 🙏

[appfabtech]

Yes. I second that. But, buddybuild has betrayed us all. Leave out the betrayal bit when cloning features.

I cri evrytim :(

Don't tell me, I met them in october 2017 in Verona for #pragmamark conference. And they convinced me to move on their platform. And they assured me they would never sell...
They already sold to apple.

[nilofer]

Added a PR for our initial proposal for this feature - leave any feedback you have on this experience!

[yyou]

Instead of implementing something "copying settings from another build configuration" in the build configuration UI (if my understanding is correct), how about create a new UI for users (mainly developer) to maintain a list of build configurations. User can create / edit / delete / copy-from-another a build configuration in this UI. then in the current branch list UI, we don't need to open the build configuration by clicking the small icon at the right side. We just "link" the branch with a build configuration by selecting a build configuration from a drop-down list.

[RWOverdijk]

@yyou take a look at the proposal pr and the comments. I share your opinion and it's written down there already.

[jjhampton]

I agree with @yyou 's comment - it would be useful if build configurations were not strongly coupled to branches.

[dgobaud]

👍 really need this!

[marstall]

or configure builds via a file checked into your repo, a la chef?

[RWOverdijk]

@marstall There are passwords involved. Please don't put that in your repository.

[marstall]

@RWOverdijk - agreed. recommend using ENV vars for sensitive stuff like that. there are more advanced ways - see chef data bags, ansible vault ... worth a dive.

[abdeweese]

or configure builds via a file checked into your repo, a la chef?

This is the answer. I just created a similar feature request here:
#437

[piterwilson]

Decoupling configurations from branches would be amazing. At the moment i am "cloning" (via branchConfigurations_get and branchConfigurations_create ) from my develop branch but it seems somehow less than ideal. Configurations could be their own thing, which can be applied to branches.

[nilofer]

We have shipped the ability to clone existing branch configurations today! Take a look at our documentation for more info. Happy building!