Ignore [***NO_CI***] commits

[uankola1]

Anyway to flag Changed files task to ignore commits due to maven release builds (comment will start with [NO_CI], so pull request will not be triggered for such changes in master branch in ADO)
refer https://mohitgoyal.co/2018/12/31/prevent-the-continuous-integration-build-in-azure-pipelines-after-pushing-commit/ for more details on the need for this request

[SomaticIT]

Hello @uankola1,

Thank you for your comment.
As for now, I don't see any way to do this.

Can you give me a sample config and some paths that are modified by maven?

[uankola1]

Hi Maxime, Really appreciate the quick reply https://mohitgoyal.co/2018/12/31/prevent-the-continuous-integration-build-in-azure-pipelines-after-pushing-commit/ When we use maven to do release builds it does 2 commits – one to change version to release version and then another to change the version to next development version. Any commit to branch in ADO Git will trigger the pull request pipeline if we have configured a branch policy. But if we prefix the comment with a pattern like [***NO_CI***], ADO Git knows not to trigger pull request ADO pipeline for such changes. Similar skipping by Check Changes will be highly helpful. Uma Ankolekar Lead Member of Technical Staff, EDI DevOps From: Maxime LUCE ***@***.***> Sent: Thursday, November 24, 2022 9:43 PM To: touchifyapp/vsts-changed-files ***@***.***> Cc: Uma Ankolekar ***@***.***>; Mention ***@***.***> Subject: Re: [touchifyapp/vsts-changed-files] Ignore [***NO_CI***] commits (Issue #36) Hello @uankola1, Thank you for your comment. As for now, I don't see any way to do this. Can you give me a sample config and some paths that are modified by maven? — Reply to this email directly, view it on GitHub, or unsubscribe. You ZjQcmQRYFpfptBannerStart [CAUTION - EXTERNAL EMAIL ] Do not reply, click links, or open attachments unless you have verified the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd Hello @uankola1<https://urldefense.com/v3/__https:/github.com/uankola1__;!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OUnRC1EWw$>, Thank you for your comment. As for now, I don't see any way to do this. Can you give me a sample config and some paths that are modified by maven? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/touchifyapp/vsts-changed-files/issues/36*issuecomment-1326643960__;Iw!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OUSLWctuw$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A4HDXBDZQ5HVLQJW3EAQAZLWJ6H2PANCNFSM6AAAAAASKOZFO4__;!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OVkeHORow$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[uankola1]

  Hi Maxime, Here is a screenshot of the commit that showed up in Check Changes but it due to maven release build commit with [***NO_CI***] in comment. Change is only version update from 11.8.0.1 to 11.8.0.2-SNAPSHOT. All maven release builds will make 2 commits one for release version and the next for Next development version. These are not real changes but only to get a build done and thus the Pull request in ADO allows it without a pull request and also does not trigger any CI pipeline. ***@***.*** Uma Ankolekar Lead Member of Technical Staff, EDI DevOps From: Uma Ankolekar Sent: Thursday, November 24, 2022 9:49 PM To: touchifyapp/vsts-changed-files ***@***.***> Subject: RE: [touchifyapp/vsts-changed-files] Ignore [***NO_CI***] commits (Issue #36) Hi Maxime, Really appreciate the quick reply https://mohitgoyal.co/2018/12/31/prevent-the-continuous-integration-build-in-azure-pipelines-after-pushing-commit/ When we use maven to do release builds it does 2 commits – one to change version to release version and then another to change the version to next development version. Any commit to branch in ADO Git will trigger the pull request pipeline if we have configured a branch policy. But if we prefix the comment with a pattern like [***NO_CI***], ADO Git knows not to trigger pull request ADO pipeline for such changes. Similar skipping by Check Changes will be highly helpful. Uma Ankolekar Lead Member of Technical Staff, EDI DevOps From: Maxime LUCE ***@***.******@***.***>> Sent: Thursday, November 24, 2022 9:43 PM To: touchifyapp/vsts-changed-files ***@***.******@***.***>> Cc: Uma Ankolekar ***@***.******@***.***>>; Mention ***@***.******@***.***>> Subject: Re: [touchifyapp/vsts-changed-files] Ignore [***NO_CI***] commits (Issue #36) Hello @uankola1, Thank you for your comment. As for now, I don't see any way to do this. Can you give me a sample config and some paths that are modified by maven? — Reply to this email directly, view it on GitHub, or unsubscribe. You ZjQcmQRYFpfptBannerStart [CAUTION - EXTERNAL EMAIL ] Do not reply, click links, or open attachments unless you have verified the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd Hello @uankola1<https://urldefense.com/v3/__https:/github.com/uankola1__;!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OUnRC1EWw$>, Thank you for your comment. As for now, I don't see any way to do this. Can you give me a sample config and some paths that are modified by maven? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/touchifyapp/vsts-changed-files/issues/36*issuecomment-1326643960__;Iw!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OUSLWctuw$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A4HDXBDZQ5HVLQJW3EAQAZLWJ6H2PANCNFSM6AAAAAASKOZFO4__;!!E3l7wfIP!mcAc7oYEf4hw5Tnw40X9VQa9rr0IcFJsFjejqcYYuV6-1GgC4jDsPFnvEtAevlSESmUIDRTVtvT4Aiqx8OVkeHORow$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[SomaticIT]

Hello,

I don't see the screenshoot can you attach it to your comment (in Github).
Thanks

[uankola1]

[uankola1]

If the latest commit has the pattern [NO_CI] then it should be considered as if there was no change because we have completed the maven release build.

[NO_CI]prepare for next development iteration

[NO_CI]prepare release <**-version>