Answered

Azure DevOps pipeline for version control use questions

(0) Share

Report

Posted on by Cooper01

664

I set up a pipeline in Azure DevOps to add an unmanaged solution to a repository. I am brand new to this so was hoping to get some feedback from anyone who uses these

Do the developers themselves (as opposed to a team lead) usually run the pipelines themselves after completing a significant task/feature? Or how does running them fit into your timeline?
Can/would you implement any sort of review process before the changes are committed? In the files I have in my repo, it doesn't really look like content you could give that much feedback on anyway but just wondering if there's any way to add any extra "checks" to the process. I am aware of the Review App task but not sure that this is exactly what I'm looking for as it sounds like it deploys PRs.

Thanks!

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

cchannon 4,702 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hey @Cooper01, no idea how your question sat on this forum for so long without an answer, but here's my two cents:

When you have manually triggered release automation, it is definitely best practice to designate a Release Manager role so there is one accountable person who is in charge of making sure the release gets from environment to environment and that necessary updates to the pipeline are made over time. This person might be the "lead" or they might just be any developer on the team; what's important is simply having one designated responsible party so the ball doesn't get dropped.

As far as review of what gets checked into DevOps, I mean, you can review the XML but you will miss so much in that. I am sure there are teams that do double-check the package in source, but in my opinion it is MUCH more important to be diligent with your code reviews than trying to figure out from some XML mapping whether fields on a form are in the right order.

Was this reply helpful? Yes No
Cooper01 664 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply @cchannon. Having a release manager role definitely makes sense and I agree there is not much benefit to reviewing XML. As far fitting the code reviews into the timeline, is this something you would manually do (as in look at the app changes in studio, review the flows) before you check into DevOps?

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (1)

Report
Copy link

Link copied!

Code reviews are a very team-specific thing. For my teams, I usually only require code reviews on more complex content (i.e. I don't 'review' basic form changes, but I may review a rewrite of a plugin). In my case, since my reviews are almost always limited to the VS and VS Code content being checked into source, that is the catchpoint.

Other teams, however, like to review more thoroughly. Some even require that a peer review be performed on every change as part of the definition of done on a work item. The right balance will be determined by your team makeup, the challenges of the project you're on, and the risk aversion of your team and client. There is really no one-size-fits-all strategy here.

Was this reply helpful? Yes No
amanverma 53 on at

Like (0)

Report
Copy link

Link copied!

@Cooper01 Not sure if this is relevant anymore but MS has released version control feature + enabled multiple developers to work on canvas app simultaneously. You can find more information here https://amanvarama1.wordpress.com/2022/01/10/power-apps-enable-multiple-developer-and-app-makers-to-work-simultaneously-on-a-canvas-app-part-1/

Was this reply helpful? Yes No