Skip to content

Keep apps installed during Apps build and add RunNumberOffset to build numbers#4760

Merged
aholstrup1 merged 1 commit intomainfrom
private/aholstrup/extensions_runnumberoffset
Sep 15, 2025
Merged

Keep apps installed during Apps build and add RunNumberOffset to build numbers#4760
aholstrup1 merged 1 commit intomainfrom
private/aholstrup/extensions_runnumberoffset

Conversation

@aholstrup1
Copy link
Copy Markdown
Contributor

@aholstrup1 aholstrup1 commented Sep 12, 2025

Summary

During the Apps (W1) build where we compile, publish and test the add-on apps we start out by creating the container and then we uninstall all apps and unpublish a certain set of apps. The set of apps we unpublish contains the apps under the Apps/W1 folder here in BCApps.

Right now, the unpublish step fails in #4757 due to the fact that there are apps that take dependency on the Power BI app. To avoid having to unpublish a lot of apps, we can instead just uninstall all apps but keep the apps published.

There is one slight challenge with this though. When we want to publish a new version of App A that takes dependency on App B. If App B is already published to the container in two different versions, it will use the version with the highest version number. Right now, the apps with the highest version numbers are the apps that come with the BC Artifact. To get around this, we can add a runNumberOffset to ensure that the apps produced in BCApps have higher version numbers than the ones on the BC Artifact.

Work Item(s)

Fixes AB#602818

@aholstrup1 aholstrup1 requested a review from a team as a code owner September 12, 2025 14:52
@github-actions github-actions bot added Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files labels Sep 12, 2025
@github-actions github-actions bot added this to the Version 28.0 milestone Sep 12, 2025
@aholstrup1 aholstrup1 merged commit 700d044 into main Sep 15, 2025
31 checks passed
@aholstrup1 aholstrup1 deleted the private/aholstrup/extensions_runnumberoffset branch September 15, 2025 06:31
miljance pushed a commit to miljance/BCApps that referenced this pull request Oct 22, 2025
…d numbers (microsoft#4760)

<!-- Thank you for submitting a Pull Request. If you're new to
contributing to BCApps please read our pull request guideline below
* https://github.com/microsoft/BCApps/Contributing.md
-->
#### Summary <!-- Provide a general summary of your changes -->
During the Apps (W1) build where we compile, publish and test the add-on
apps we start out by creating the container and then we uninstall all
apps and unpublish a certain set of apps. The set of apps we unpublish
contains the apps under the Apps/W1 folder here in BCApps.

Right now, the unpublish step fails in microsoft#4757 due to the fact that there
are apps that take dependency on the Power BI app. To avoid having to
unpublish a lot of apps, we can instead just uninstall all apps but keep
the apps published.

There is one slight challenge with this though. When we want to publish
a new version of App A that takes dependency on App B. If App B is
already published to the container in two different versions, it will
use the version with the highest version number. Right now, the apps
with the highest version numbers are the apps that come with the BC
Artifact. To get around this, we can add a runNumberOffset to ensure
that the apps produced in BCApps have higher version numbers than the
ones on the BC Artifact.

#### Work Item(s) <!-- Add the issue number here after the #. The issue
needs to be open and approved. Submitting PRs with no linked issues or
unapproved issues is highly discouraged. -->
Fixes
[AB#602818](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/602818)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants