search

HodorNV / ALOps

ALOps
59 stars 24 forks source link

Build warnings make changes re-appear in every subsequent build #467

Closed StevenHit closed 2 years ago

StevenHit commented 2 years ago

Sometimes we have AL compilation warnings in a build pipeline run. The result is an app that can be released without issues. Unfortunately, when we have a run with warnings like this one:

image

The same (commits) changes keep re-appearing again on subsequent runs, until a run gets the succeeded status:

image

Is there a way to avoid this? I mean, when a build succeeds with warnings, the changes should still be assigned to that build. Not to the next build.

Thanks for your help

waldo1001 commented 2 years ago

This is pure DevOps context. It basically reports the commits that it's building.
Not sure what you want us to do about that?

StevenHit commented 2 years ago

You are right. The fact that DevOps keeps repeating changes when the build status is "succeeded with warnings" is a DevOps thing.

But, as there is a "failed_on_warnings" parameter. There isn't something like "succeed on warnings" in ALOps?

Thanks

waldo1001 commented 2 years ago

But you can accomplish that with a ruleset and/or disabling codecops, no?

waldo1001 commented 2 years ago

If you need help on setting up the rulesets, let me know - for now, I'll close this issue.