Severity
No response
Version
Earliest tested was 2025.4.10664
Latest Version
I could reproduce the problem in the latest build
What happened?
When a package is required by an external trigger, Octopus retrieves its latest version information from the feed and writes a log for each trigger, even for triggers that do not require the package. When there are many active triggers and many packages, this can result in a large volume of logs.
Reproduction
- Create Project1 and Project2
- Create an external feed with two packages
- In Project1, create a run a script step with referenced package A and set up an external feed trigger to create a release when package A version changes
- In Project2, create a run a script step with referenced package B and set up an external feed trigger to create a release when package B version changes
- In the external feed, increment the version of Package A only
- View the task log to see that both version information retrieval is logged for both package A and package B for both external triggers
Error and Stacktrace
More Information
No response
Workaround
No response
Severity
No response
Version
Earliest tested was 2025.4.10664
Latest Version
I could reproduce the problem in the latest build
What happened?
When a package is required by an external trigger, Octopus retrieves its latest version information from the feed and writes a log for each trigger, even for triggers that do not require the package. When there are many active triggers and many packages, this can result in a large volume of logs.
Reproduction
Error and Stacktrace
More Information
No response
Workaround
No response