You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a module is only published if git detects code changes for a module when comparing with Head^-1.
This can lead to some undesired behavior if you set up CARML for the first time, directly in main, and run the pipelines without any module changes. If that's the case, you won't be able to publish unless you apply a workaround such as a modification of the version.json file.
To mitigate this behavior we could add some logic to the publishing to the dedicated target locations (i.e., ACR, Template Specs, Universal Packages) that not only checks for changes, but also if there is already a version in that target location. If there is none, the pipeline could then decide to publish even if there are no module changes.
The text was updated successfully, but these errors were encountered:
Also as a separate issue, but related to the last point above, we should restrict the comparison logic which triggers the publishing to ignore changes to readme and test files as those should not impact the module version.
AlexanderSehr
changed the title
[Feature Request]: Enable Publishing to always publish if not version was found in the target location
[Feature Request]: Enable Publishing to always publish if no version was found in the target location
Sep 30, 2022
AlexanderSehr
changed the title
[Feature Request]: Enable Publishing to always publish if no version was found in the target location
[Feature Request]: Enable Publishing to always publish if no version was found in the target location & compare the hashes if there is
Dec 2, 2022
AlexanderSehr
changed the title
[Feature Request]: Enable Publishing to always publish if no version was found in the target location & compare the hashes if there is
[Feature Request]: Enable Publishing to always publish if no version was found in the target location
Dec 2, 2022
Description
Currently, a module is only published if git detects code changes for a module when comparing with Head^-1.
This can lead to some undesired behavior if you set up CARML for the first time, directly in main, and run the pipelines without any module changes. If that's the case, you won't be able to publish unless you apply a workaround such as a modification of the
version.json
file.To mitigate this behavior we could add some logic to the publishing to the dedicated target locations (i.e., ACR, Template Specs, Universal Packages) that not only checks for changes, but also if there is already a version in that target location. If there is none, the pipeline could then decide to publish even if there are no module changes.
The text was updated successfully, but these errors were encountered: