Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Package condition dilema

For every package I have, I have 2 collections. 1) all endpoint with the package. 2) all endpoints with an old version of the package. 

I process updates once a month. Tp make life easier, and not run into multiple packages trying to install at once on an endpoint, I have a schedule that includes all the packages. The target of that schedule is all endpoints. Each package has a condition that they have to be members of the "old version" collection for that package.

I run into 2 things. 

1) for the schedule deployment, I get a lot of failed because an endpoint does not meet the condition. Not all endpoints have every package. This just makes it harder to quickly see how the deployment went.

2) If i try to push a package on a new endpoint, it also fails because it does not meet the condition. 


I need a way to only show failed messages when a package should have installed and didn't and to allow me to force a package on an endpoint.




1 comment
Date Votes
  • I recommend 1 Schedule per Package, targeted at the corresponding "old version" Collection, with "Stop deploying to targets once they succeed" disabled, and no Collection Condition on the Packages.

    not run into multiple packages trying to install at once on an endpoint

    Deploy already handles this. It will add deployments to a queue, and process them 1 by 1.