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

Stop producing thisbuild artifacts and instead always produce artifacts with configurable retention #1376

Open
freddydk opened this issue Dec 31, 2024 · 0 comments · May be fixed by #1374
Open
Assignees
Labels
enhancement New feature or request

Comments

@freddydk
Copy link
Contributor

When building a multi-project solution with dependencies, AL-Go will produce build artifacts called thisbuild-*
These artifacts are only used by other projects for dependency resolution and have a retention period of 1 day.
This construct was created as NextMajor, NextMinor, Current and PullRequest builds normally don't produce any build artifacts.

Instead of producing thisbuild artifacts - we should produce normal artifacts with a suffix indicating that they are not useful for normal consumption (this already happens with thisbuild artifacts). The retention period for these artifacts should default to one 1, but be configurable - obviously not below one day.

This means that PR builds, NextMajor builds etc will produce artifacts, which can be used for testing purposes as requested by multiple partners.

Another request (and one of the reasons to do the above) we have is to be able to publish a PR build to an environment for testing purposes - i.e. tying an environment to a specific PR, meaning that the environment will not be picked up by normal CI/CD or publish to environment, but only will receive new successful builds from this PR - in order for QA to approve the PR before it merges and is published to FAT.

Lastly - creating a setting to define preprocessorsymbols, which can be set differently in NextMajor or NextMinor will make it possible to uptake new features which are incompatible with current version while still only having one branch.

@freddydk freddydk self-assigned this Dec 31, 2024
@freddydk freddydk converted this from a draft issue Dec 31, 2024
@freddydk freddydk added the enhancement New feature or request label Dec 31, 2024
@freddydk freddydk linked a pull request Dec 31, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

1 participant