Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Selection of Apps when creating a Release #172

Closed
StefanMaron opened this issue Jun 28, 2022 · 10 comments
Closed

[Question] Selection of Apps when creating a Release #172

StefanMaron opened this issue Jun 28, 2022 · 10 comments
Labels
bug Something isn't working Fix Ready Fix Ready

Comments

@StefanMaron
Copy link

I am wondering how the release action selects the apps to include in that release in a multi Project repository.
Sometimes I have multiple changes on 2 of the 3 projects but only one apps gets included in the release.
I was not really able to find any logic on how the apps get selected yet.

@freddydk
Copy link
Collaborator

The intention should be that it would grab the latest build from all projects (if no specific version was specified)
I assume that this doesn't happen?

@StefanMaron
Copy link
Author

Specific version? That explains why it would grab one project only. I copied the version from one extension.

But last time I tried, the version for the release was mandatory. How would I create a release without a specific version?

@freddydk
Copy link
Collaborator

Create release should allow you to say latest:

workflow_dispatch:

    inputs:
      appVersion:
        description: App version to promote to release (default is latest)
        required: false
        default: 'latest'

@StefanMaron
Copy link
Author

ah, I was talking about name and tag.
The App version is always latest.
but most of the time the latest build only built one project.

image

@freddydk
Copy link
Collaborator

This might be a bug.
For now, you can probably set "alwaysBuildAllProjects": true in the repo settings file (.github\AL-Go-Settings.json) - then it should build all projects every time - and probably release them as well.

@StefanMaron
Copy link
Author

Okay, thanks.
Let me know if I can give any more input.

@freddydk
Copy link
Collaborator

I think I will need to make an overhaul on the multi-project repo - I have found a few things.
That might be after my vacation (which starts tomorrow)

@freddydk
Copy link
Collaborator

Have a fix for this.
Will be in the preview branch tomorrow.

@freddydk
Copy link
Collaborator

This fix is in preview now.

@freddydk
Copy link
Collaborator

Shipped in v2.0

freddydk added a commit that referenced this issue Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fix Ready Fix Ready
Projects
None yet
Development

No branches or pull requests

2 participants