Clarification on Install actions and Bundle versions pls.

Hi.

I seem to remeber (and I may be phantasizing it), that at some point in time, each install action in a bundle had it's own internal revision, and when a bundle version increased, only the actions that actually got changed (if any) executed agein when set to e.g "run once per device".

That no longer seems to be the case, and whenever one changes any of the install actions, they *all* get run again with the next bundle version.

For instance, I have a "first install" bundle, that consists of a dozen or more "install bundle" actions pointing to other bundles that it installs, e.g on a freshly installed workstation.

When I add another install action to that Bundle (e.g a new software), *all* other, unchanged bundles apparently get installed again. Which in some cases is just annoying and a waste of time and CPU cycles, but in some cases causes real issues. Setting gets overwritten, and some badly coded software installers (Citrix, I see you) fail in really bad ways when they get run a second time.

So am I phantasizing? Is this WAD,  bug, or am I oberlooking something?

Parents
  • Suggested Answer

    0  

    I don't believe it's the individual actions themselves that is versioned but rather the collection of install actions.  Thus if you update a bundles name, icon, etc. and give it a new version the installs do not run again unless you alter an install action.  Sometimes it is necessary to do a dummy edit on an install action to get them to run again.  I've never had to actually "dummy edit" every single install action to get them to run again.   (Under the Hood I can't say if each action has a version # or the Set has the Version#, but it operates as a "Set" so that any change to the set will cause everything to run again.)

    Getting the behavior to make the changes would require updating the GUI and exposing additional options because quite often the desire is to re-run everything so there would need to be an ability for finer control.  That would be useful but an RFE.  At this point, you would need to use "Action Level Sys Reqs" to skip actions you don't want to run again.  You could check to see if Citrix was installed and the version before calling the MSI or if calling a Citrix Install Bundle I presume the "Bundle is Installed Action" would only run if the current version was old though I personally don't use the "Is Bundle Installed" very often and would need to verify if it checked to see if any version vs current version was installed.  I presume current because that is logical to me but that does not mean it's logical to others or always the best option.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0   in reply to   

    Hmm. I wonder where my brain has this from. Maybe Zen7. ;)
    The individual system req to check if a bundle is installed is an interesting idea. I originally thought that won't work as you can't check the same bundle you're just installing, but this isn't the case here.
    I'll test this...

Reply
  • 0   in reply to   

    Hmm. I wonder where my brain has this from. Maybe Zen7. ;)
    The individual system req to check if a bundle is installed is an interesting idea. I originally thought that won't work as you can't check the same bundle you're just installing, but this isn't the case here.
    I'll test this...

Children
No Data