On Deploy Screen when switching contexts it reverts the connection to the project connection

Issue #744 resolved
Justin Julicher created an issue

If I'm trying to deploy to a another sandbox using 'Deploy All Metadata' and I select the sandbox then I change the context it reverts the connection to the project connection.

It should keep the connection to the one selected.

Another annoying trait is that it loads all the metadata again when you change context or connection which for our large org takes in excess of 5 minutes. If I'm deploying I don't see why it has to load the metadata on those changes? If I'm deploying I want a dialog box to pop up and ask me if I want to compare what I'm deploying and then it should be smart enough to only load that specific metadata. (I know I can change this in the connection dialog but is that only for when you do a deploy on save?).

thanks

Comments (14)

  1. Scott Wells repo owner

    Yeah, I've run into this bug a few times as well. I'll definitely take care of it. As for it reloading metadata on switch, that would also be a bug. It should only have to load from server once then it should be able to load from cache. I'll investigate that as well. Thanks for reporting!

  2. Scott Wells repo owner

    Okay, this is fixed and will be in the next build. I've also implemented some MAJOR performance optimizations to the deploy/retrieve dialog so that it shouldn't be even close to 5 minutes to refresh. Hopefully it'll just be a few seconds now. Since you're seeing much more egregious times, though, I'd really appreciate if it you'd provide feedback on these performance optimizations upon taking the next build to help quantify them. Thanks!

  3. Justin Julicher Account Deactivated reporter

    Hi Scott

    The performance is definitely a lot better... probably cut down the wait by at least half I would guess (as I didn't really take any real metrics before this update) - but definitely a noticeable improvement!

    thanks!

  4. Scott Wells repo owner

    Justin, I haven't published the new version yet. That means to me that your org was probably under duress when you saw these long times before. Hopefully the new version (which I'll publish in the next several hours) will make an even more noticeable difference! I'll comment here again when the new version is available.

  5. Scott Wells repo owner

    Justin, try the latest build and see whether it makes a difference for you. I'm hoping you see a considerable difference, but if you don't it would be good to know that as well.

  6. Scott Wells repo owner
    • changed status to open

    Due to an issue with the Salesforce APIs found by at least one user, I've pulled the 1.8.0.9 update temporarily.

  7. Justin Julicher Account Deactivated reporter

    Ha! Ah must be the lack of sleep I've had recently ;)

    Looks like it has made an even bigger difference than I stated erroneously earlier! Great work thanks!

  8. Log in to comment