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

Sourcing files from the project repository fails to deploy when creating the releases using a scheduled trigger #8756

Closed
geofflamrock opened this issue Apr 30, 2024 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@geofflamrock
Copy link

Severity

Not blocking anyone as far as I am aware

Version

2024.1+

Latest Version

I could reproduce the problem in the latest build

What happened?

When a project is stored in Git using the config-as-code feature, since 2024.1 files can be sourced on a step using the Project repository (i.e. the repository configured in version control settings). The commit that is saved on the release will be used to source the files.

When a release is created using a scheduled trigger, the Git ref is selected on the trigger (e.g. a branch or a tag), however the release doesn't contain the Git commit and therefore the "Acquire packages" step fails during deployment.

Reproduction

  • Create a project that is stored in Git
  • Add a step that sources files from the Project repository e.g. the run a script step
  • Create a scheduled trigger that will deploy a new release, selecting the relevant branch and environment
  • Wait for the trigger to create a release and deploy

The deployment will fail because there is no Git commit.

Error and Stacktrace

An operation in "Acquire Packages" failed Tiny type values should never be null. If the value you want to communicate is null then just pass a null rather than a tiny type wrapping a null. (Parameter 'value')
System.ArgumentNullException: Tiny type values should never be null. If the value you want to communicate is null then just pass a null rather than a tiny type wrapping a null. (Parameter 'value')

More Information

No response

Workaround

Only workaround is to either not use the project repository, or not use a scheduled trigger to create the release.

@geofflamrock geofflamrock added the kind/bug This issue represents a verified problem we are committed to solving label Apr 30, 2024
@octoreleasebot
Copy link

Release Note: Fixes issue where sourcing files from the project repository for a version controlled project would fail if the release was created from a scheduled trigger

@Octobob
Copy link
Member

Octobob commented May 16, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.2 2024.2.7301
2024.3+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants