Skip to main content
deleted 155 characters in body
Source Link

I have used Azure Pipeline for CI/CD on various small projects that I have worked and it has been a great experience. I am working now on a decent size project that has a web app, mobile(xamarin) app and API. We plan to use Gitflow along with Azure Devops for the delivery process. But I have got a few questions that is really bothering me, and would like to hear other opinion.

  1. I understand that feature branches are created to work on a user story, but when multiple people are working on a user story, do we create a feature branch, and then each developer branch of it and then work on the individual sub-tasks? And when they complete their work, they merge back to the feature branch. Is this a standard practice? Or do developers merge back to develop branch as they finish their sub-tasks?
  2. Is it a good practice to do a build in Azure Devops for every PR merge to develop branch?
  3. When a feature branch is merged with develop branch, do we immediately sent out a release or do we group and send out as nightly builds to QA?
  4. I understand that both build and release pipelines offer a great flexibility. But generally does the build pipeline generates the artifacts or is it the release pipeline that does that?
  5. I see that in most tutorials, both build and release pipelines do restore the packages, compile the code, and create artifacts. Is that how its done?

I appreciate if someone can help me with these questions. Or atleast point me in the right direction

I have used Azure Pipeline for CI/CD on various small projects that I have worked and it has been a great experience. I am working now on a decent size project that has a web app, mobile(xamarin) app and API. We plan to use Gitflow along with Azure Devops for the delivery process. But I have got a few questions that is really bothering me, and would like to hear other opinion.

  1. I understand that feature branches are created to work on a user story, but when multiple people are working on a user story, do we create a feature branch, and then each developer branch of it and then work on the individual sub-tasks? And when they complete their work, they merge back to the feature branch. Is this a standard practice? Or do developers merge back to develop branch as they finish their sub-tasks?
  2. Is it a good practice to do a build in Azure Devops for every PR merge to develop branch?
  3. When a feature branch is merged with develop branch, do we immediately sent out a release or do we group and send out as nightly builds to QA?
  4. I understand that both build and release pipelines offer a great flexibility. But generally does the build pipeline generates the artifacts or is it the release pipeline that does that?
  5. I see that in most tutorials, both build and release pipelines do restore the packages, compile the code, and create artifacts. Is that how its done?

I appreciate if someone can help me with these questions. Or atleast point me in the right direction

I have used Azure Pipeline for CI/CD on various small projects that I have worked and it has been a great experience. I am working now on a decent size project that has a web app, mobile(xamarin) app and API. We plan to use Gitflow along with Azure Devops for the delivery process. But I have got a few questions that is really bothering me, and would like to hear other opinion.

  1. I understand that feature branches are created to work on a user story, but when multiple people are working on a user story, do we create a feature branch, and then each developer branch of it and then work on the individual sub-tasks? And when they complete their work, they merge back to the feature branch. Is this a standard practice? Or do developers merge back to develop branch as they finish their sub-tasks?
  2. Is it a good practice to do a build in Azure Devops for every PR merge to develop branch?
  3. When a feature branch is merged with develop branch, do we immediately sent out a release or do we group and send out as nightly builds to QA?
  4. I understand that both build and release pipelines offer a great flexibility. But generally does the build pipeline generates the artifacts or is it the release pipeline that does that?

I appreciate if someone can help me with these questions. Or atleast point me in the right direction

Source Link

Using Azure Devops with Git Workflow

I have used Azure Pipeline for CI/CD on various small projects that I have worked and it has been a great experience. I am working now on a decent size project that has a web app, mobile(xamarin) app and API. We plan to use Gitflow along with Azure Devops for the delivery process. But I have got a few questions that is really bothering me, and would like to hear other opinion.

  1. I understand that feature branches are created to work on a user story, but when multiple people are working on a user story, do we create a feature branch, and then each developer branch of it and then work on the individual sub-tasks? And when they complete their work, they merge back to the feature branch. Is this a standard practice? Or do developers merge back to develop branch as they finish their sub-tasks?
  2. Is it a good practice to do a build in Azure Devops for every PR merge to develop branch?
  3. When a feature branch is merged with develop branch, do we immediately sent out a release or do we group and send out as nightly builds to QA?
  4. I understand that both build and release pipelines offer a great flexibility. But generally does the build pipeline generates the artifacts or is it the release pipeline that does that?
  5. I see that in most tutorials, both build and release pipelines do restore the packages, compile the code, and create artifacts. Is that how its done?

I appreciate if someone can help me with these questions. Or atleast point me in the right direction