Continuous integration?

Highlighted
New Contributor

Continuous integration?

We're just looking at setting up our development release process, working with a partner and Anaplan architect. The solution that has initially been proposed seems very rudimentary, and I was expecting the ability for us to develop multiple features independently and in parallel with the ability to release these at different times and in the spirit of agile and failing fast, maybe even not release some of the changes at all.

 

It's not easy to explain to users that we either

  1. can't fix their bug until we've finished the low priority functionality we're developing for them
  2. can fix their bug but will have to start over developing the low functionality we're building.

 

gitflow.jpg

 

Does anyone have experience developing their Anaplan models using CI? How do you all build/release?

 

 

 

Relevant links:

Continuous Integration with Gitflow – this is pretty much what I'm looking for.

Idea suggestion that comes close 

1 REPLY 1
Regular Contributor

Re: Continuous integration?

Hi,

 

not sure what you mean by 2 but bug fixing while working on future relese with ALM happens all the time.

It's not the best dev to prod in the world of devops but we have a way to manage it:

 

https://community.anaplan.com/t5/Knowledge/Save-Incomplete-Changes-when-Synchronizing-in-ALM/ta-p/33...

Nathan Rudman
Anaplan Model Builder