Versions Compared

Old Version 10

changes.mady.by.user Vismay Shah

Saved on

compared with

New Version 11

changes.mady.by.user Jacob Pagnotta

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleSTEP 3: See the local code change in effect

The code change from the previous step was committed to the remote repository, but the component is not yet using the new code. The component must updated to use the new commit.

  • In the component card, use the Using Commit dropdown and change the commit the component is running on to the commit you made.

    Image RemovedImage Added

  • Now close the card and run the component. You should see it get a red outline

    Image RemovedImage Added

Expand
titleSTEP 4: Clone in your component on a different Iguana and update the code

Since the changes made have been pushed to the cloud, this component can now be cloned into any other Iguana.

Note: To try out this step you need to have a different Iguana instance ready with Bitbucket access configured. See: Setting up Bitbucket Access

  • Open the component that was created. From the component card, copy the Connected To field

  • In a different Iguana instance, from the dashboard click + From Url. Give the component a name, and paste in the url from before then click Add

    Image RemovedImage Added

  • Once the component is created, click Edit Script to go to Translator

    • You may have to click and expand the Implementation section

  • See that the code changes made in the previous step have been brought across

  • Change to the code to the following, then commit and push the change.

    Code Block
    function main()
	component.setBorder{color="green"}
end
main()

  • Back on your other Iguana instance, update the component to run from this new commit. It can take a minute or two for the new commits to show up.

    • Use the Using Commit dropdown and select the commit you just made

      Image RemovedImage Added

  • Now run the component and verify that the border turns green

  • Click on Edit Script to go to the Translator. To see the code changes, we have to pull in the changes from the remote repository.

    • Do this by clicking on the Pull Changes button which looks like a cloud with an arrow pointing away from it.

    • Notice that it has a blue dot, indicating that there are changes available to be pulled in. Click it and see that the code updates.

Expand
titleSTEP 5: Add the component to a collection

The process above outlined what it takes to create a component with some code that can be easily brought over to any number of Iguana instances. To make this process even easier, you can group components you make into a collection.

  • From the component card, click on Add to Collection, in the window that appears set the dropdown to Create New Collection and click Select

  • Create a name for the collection, then click Create & Add. Wait for this to finish, and then in the window that appears click Select.

  • In the Edit collection screen that appears, create a name for your collection and click Save

  • Once it is done, you will see this. Click Dismiss.

  • Now go back to the dashboard and click + Component. You should see your component appear in the list of components available

    • Depending on the name you gave it, you may have to scroll through the list

  • This collection has been added to the current Iguana instance. To see this, go to the settings screen Settings and click on Git Collection. Your newly created collection will appear in the repositories list.

    • To use this collection in a different Iguana instance, first copy the url

    • Then in the other instance go to settings, click Git Collection and click Edit in the top right

    • Then click Add Collection and paste in the copied url and click Save

      Image RemovedImage Added

  • Now go back top the dashboard Dashboard and click + Component and you will see your component appear

...