As you're deploying from both development and master branch you do have to use 2 separate build pipelines and 2 separate release pipelines. So what you're doing seems right.
However, I'm not sure why you are not using ng build --prod for the development environment. Not using --prod will remove some optimizations done by the ng cli.
I have an article on how you can implement runtime configuration so you can have different configurations while still using ng build --prod.
Hi Frederik, thank you for your response. I'm using "ng build" because I thought this was the way to build your project based on the development configuration. Is it really bad, if so, can you please provide me the article link? : )
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As you're deploying from both development and master branch you do have to use 2 separate build pipelines and 2 separate release pipelines. So what you're doing seems right.
However, I'm not sure why you are not using ng build --prod for the development environment. Not using --prod will remove some optimizations done by the ng cli.
I have an article on how you can implement runtime configuration so you can have different configurations while still using ng build --prod.
Hi Frederik, thank you for your response. I'm using "ng build" because I thought this was the way to build your project based on the development configuration. Is it really bad, if so, can you please provide me the article link? : )