Git Support for Existing Repository

The Welkin Suite Forum

Git Support for Existing Repository



Git Support for Existing Repository

  • Please log in to reply

#1

henri.keeble

    Posted 13 Jan 2016

    Hi all,


    Have been exploring TWS for a short time, and it looks to be very promising. However, I have a question about both Git support and support for existing local projects. The Force.com IDE for eclipse allows me to clone an existing Git repository to my local machine, and then import the project and point it to a Salesforce instance. Does TWS have any support for an existing git repository at the moment? All I can find is how to initialize a new repository into a TWS project, but not import an existing local repository.



    9 replies to this topic

    #2

    kate.dulko

      Posted 13 Jan 2016

      Hi Henri,


      Thank you for joining us, and for your question.


      Currently The Welkin Suite doesn't support the import of the existing repositories.
      However, if your TWS project is located in a Git repository and you open this project in TWS, the repository is initialized with the IDE.

      If you have more question, please feel free to ask us - we will be glad to answer them.


      Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      henri.keeble

        Posted 14 Jan 2016

        Hi Kate,


        Thanks for the reply, certainly hope we see this feature sometime in the future!


        Henri



        #4

        brian.triplett

          Posted 15 Jun 2016

          I'm having the same issue.  Welkin Suite looks very appealing but our Salesforce project source is stored in Github.  


          To initialize a project we typically follow the workflow of:

          1. Clone our repo locally from github
          2. Create a project in whatever IDE we are using from that repo folder
          3. Push/sync those change to a Salesforce org

          It seems like TWS does this in reverse and it makes it hard for us to use a remote repository solution like Github unless I'm missing how to do this in TWS.



          #5

          kate.dulko

            Posted 16 Jun 2016

            Hi Brain,


            Thank you for your post.


            Your workflow means the import of your local (cloned) repository with the included project that was created inside another IDE.

            Currently, TWS doesn't support this integration.


            The only way you can use to follow your workflow is to create TWS project in your Git repository.


             You can do this the following way:

            1. make sure that all project changes are present on Salesforce;
            2. create a new project inside The Welkin Suite in the Git folder;
            3. build this project;
            4. select the project folder in the Git folder and execute Git Repository creation;
            5. create a new branch by the Git client or make an initial commit to the first branch;
            6. reopen your project in the IDE and open the Version Control Window (Main Menu -> Show Version Control)​.

            I kindly ask to inform us if this way works for you.


            Thank you,

            Kate


            Kate Dulko
            Customer Relations

            The Welkin Suite

            twitter: @KateDulko
            skype id: d_katerina
            e-mail: kate.dulko@welkinsuite.com

             

              


            #6

            angusmaul

              Posted 12 Jan 2017

              Having similar issue here, our existing work was all done with eclipse and Git, and there are multiple developers in the team.

              Can't see us moving to TWS until this is possible.

              Likely I will cancel my subscription unless its confirmed this feature isn't too far off.



              #7

              vlgubanovich

                Posted 17 Jan 2017

                Hi angusmaul,

                 

                Thank you for letting us know about your issue with The Welkin Suite.

                 

                The reason why this approach is still not implemented in TWS is because Salesforce's development model right now assumes the org as the only "source of truth". This why all approaches to work with Salesforce and Git always results in additional issues and performance/productivity trade-offs. We do not want to affect the general approach to the projects in The Welkin Suite - because of it's current organization we are able to provide a lot of different features as well as provide improved performance compared to the Force.com IDE.

                 

                Especially this is actual in terms of Salesforce's new SalesforceDX development approach, where code repository is the only "source of truth" - this why we would like to get as much details as possible on the Salesforce's own vision of the proper development process with Git. As soon as their development workflow will get finalized we will for sure implement it's support as one of the highest priorities.

                In the current situation I suggest using Ant (Salesforce) Migration Tool for operations related to the repository operations, while keeping The Welkin Suite as a main working tool. Such approach will allow you to enjoy all of The Welkin Suite's benefits like improved performance, Apex Retrospective Debugger, great Debug Logs Viewer and others while keeping very low overhead on repository changes management.

                 

                With this approach I assume the following preparations:

                1. Configure a standard Ant Migration Tool deploy task for Salesforce to use your org's credentials. With this task you will be able to deploy changes from the git to the org with just a simple command line command.
                2. (Optional) Create a simple bat file which will perform a pull from the Git repository and subsequently execute the Ant task from the first step.
                3. Create a project in TWS (not in the repository) pointing to that org.
                4. Configure a standard Ant Migration Tool retrieve task for Salesforce to use your org's credentials. With this task you will be able to retrieve changes from the org to your git repository.
                5. (Optional) Create a simple bat file which will perform ant-retrieve and subsequently commit&push your changes to the Git repository.

                 

                With this preparations your workflow will look like this:

                1. Execute a bat file to pull from Git and deploy to the org
                2. Open TWS project and pull changes from Salesforce
                3. Develop in TWS
                4. When you ready to commit execute a bat file to push to Git

                 

                In average the preparations should not require more than 30-40 minutes for one time, while regular overhead should not be more than 5 minutes per commit - this amount of time can be easily saved with The Welkin Suite within a day just with the overall performance improvements, not talking about the Retrospective Debugger, for example.

                 

                Hope this helps.

                 

                Thank you,

                Vladimir


                Vladimir Gubanovich
                Head of Product
                 
                The Welkin Suite
                skype id: vladimir.gubanovich
                e-mail: vladimir.gubanovich@welkinsuite.com

                • 1

                #8

                douglascayers

                  Posted 19 Mar 2017

                  Thanks for the transparency @Vladimir and glad you all are keeping eye on SalesforceDX. That is major shift in where "source of truth" lives for orgs from the Salesforce instance to the source control repo (e.g. git). Look forward to scratch org support if/when the pilot goes beta/general availability.



                  #9

                  vlgubanovich

                    Posted 20 Mar 2017

                    Hi Douglas,

                    Glad to see you on our forum :)

                    We're also waiting for more details of the DX program to finally start implementing it. And if you participate in the pilot and have any ideas of what we should implement and in what way - please don't hesitate to share with us and we'll be happy to do this as it is very important to implement DX support in the best way to allow comfortable work with it.

                    Thank you,

                    Vladimir


                    Vladimir Gubanovich
                    Head of Product
                     
                    The Welkin Suite
                    skype id: vladimir.gubanovich
                    e-mail: vladimir.gubanovich@welkinsuite.com


                    #10

                    vlgubanovich

                      Posted 04 Sep 2017

                      Hi guys!

                      I'm happy to let you know that we've added support for Salesforce DX in the Bloom R6 version! This means that if you're working with Git, Continuous Integration, Continuous Delivery or everything together - you can now do this much easier, using SFDX and TWS.

                      Check out our release notes and we will be happy to answer any your questions!


                      Thank you,

                      Vladimir


                      Vladimir Gubanovich
                      Head of Product
                       
                      The Welkin Suite
                      skype id: vladimir.gubanovich
                      e-mail: vladimir.gubanovich@welkinsuite.com

                      • 1




                      Boost Your Productivity. Get Started Today

                      Try Free Trial