Andy in the Cloud

From BBC Basic to Force.com and beyond…

GitHub Salesforce Deploy Tool Lightning Edition

14 Comments

A recent discussion on Twitter around sharing Salesforce configuration between admins has motivated me to revisit this tool. Before getting into anything major (watch this space). I decided to get back into the tools code by addressing a few outstanding maintenance tasks, enhancements and bug fixes, as well as treating it to a face lift!

LightningGitHubSFDeploy.png

As some of you may have noticed the tool has now adopted the Salesforce Lightning Design System look and feel. This new version is not just cosmetic, its also addressed some key enhancements and bug fixes…

LightningGitHubSFDeploy2.png

In keeping with the Lightning principles, this release makes the Deploy to Salesforce button (example shown below), even easier to place in your repository README files with less configuration required. The button will now automatically detect the GitHub repository. Which is useful if you Fork a repository into your own account or rename it, you no longer need to change the README file. The button code is now also smaller.

LightningGitHubSFDeployButton.png

IMPORTANT NOTE: This only works if your placing the button code in a GitHub README file. If your planning on using the button on a blog, article or wiki etc tick Use Specified Owner and Repository checkbox to have the specified repository details encoded into the button code as before.

This release has now also addressed issues preventing use with repositories that have Reports or Lightning Components in them. So you can now use the tool to deploy your favourite open source Lightning Components!

Finally if you have any private repositories, an improvement around the error handling in this area has also been made. Thanks to some great code contributions from Moti Korets and  Nathan Kramer for the whole GitHub private repository support! Thanks guys!

 

 

14 thoughts on “GitHub Salesforce Deploy Tool Lightning Edition

  1. hi! I’m having an issue with the deploy where it says:

    Deployment Complete
    Failures:
    customMetadata/README.md(1,1):Error parsing file: Content is not allowed in prolog.

    All I have in my README.md is the button itself. Not sure how to fix. Any help appreciated thanks!!

  2. Pingback: GitHub Salesforce Deploy Tool Lightning Edition — Andy in the Cloud | SutoCom Solutions

  3. Hi Andy,

    Thank you very much for your contributions around the Metadata API tools.
    I’m a Developer based out of Los Angeles, trying to get my toes wet with the API tools.

    I tried the “deploy to Salesforce” button but am met with a failed attempt (Oath failed).
    My developer org does not have IP restrictions so not sure what to do in order to get this to work.
    Is there a specific IP I can whitelist or sometime like that in order to try this out?

    Thanks!
    Joseph

    • Do you get the prompt to select sandbox?

    • And thanks for your kind words! 🙂

      • I do get the prompt to select production – developer / sandbox as well as the Owner and Repository. I leave it as Production – Developer and keep the Owner at financialforcedev and Repo at apex-mdapi. I then login to my org, it processes, and then gives Oath error.

        I do have mydomain turned on, if that matters.

        On Mon, May 30, 2016 at 5:52 AM, Andy in the Cloud wrote:

        > Andrew Fawcett commented: “And thanks for your kind words! :-)” >

      • Hmmm this could be a bug, I see someone else has pointed it out on the repo, there is a GitHub issue that seems to relate to this. Can you add your information to that please, it will help when I get to it, debug wise.

    • I’m facing the same issue: OAuth error after access granted.

      • Yes there is some issue here I need to dig into. Meanwhile the workaround is to quit your browser and try the button again, this will force the login flow to activate

  4. Hi Andy,

    The sandbox version when I’m trying to install this repository keep coming up with an application error. I get the first screen, choose sandbox, add the owner and repo link, when I click on login with SF it errors. If I choose Production it works.

    Link: https://githubsfdeploy-sandbox.herokuapp.com/app/githubdeploy/benedwards44/sf-address-autocomplete

  5. Your tool seems great … congratulation.

    I have a question regarding the use of your tool on a customer environment.

    I have to build a Design Authority Asset Management tool to expose source codes of reusable components to a community (not a salesforce one).

    The customer wants to use a GIT repository so your tool sounds great for deployment (like an unmanaged packaged deployment but on GITHUB source).

    My question is: Is it possible to use your HEROKU enviromenent for my customer purpose (part of my asset management process), and if not, is it possible to get your tool source code to deploy on my customer dedicated HEROKU instance.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s