Versions Compared

Key

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

...

9. Enter Tool Name, Tool Identifier (Select the repository tool from the drop down) & Description

...

10. Click Create Tool

...

12. Click on the Tool → Click on ‘Connection’ tab → Enter URL, Username, and Personal Access Token.

...

13. Click ‘Save’ → Tool Configuration will be updated successfully. This would successfully add the repository tool to the Opsera portal. After saving the tool, ensure the Connection is successful but clicking ‘Test Connection’

Next, Jenkins tool to be added, and integrated with source code repository

14. Click on Tool Registry on left navigation panel and click on ‘New ‘+New Tool’.

...

15. Enter Tool Name, Tool Identifier (From the drop down - Select Jenkins), Description

...

16. Click Create Tool

...

17. Click on the Tool → Click on ‘Connections’ tab → Enter Jenkins URL, UserID, Jenkins Token

...

21. New Jenkins Account adding form will be openedopen

...

23. Select Platform [Select your source code repository tool from the drop down - gitlabGitlab/githubGithub/bitbucketBitbucket], Then drop down for “tools” will be enabled - Select the tool that you just created.

...

24. Enter Name and Description of credentials to be added in Jenkins and click on ‘Add Jenkins Credentials’. This would link the ‘Save’. The Jenkins job is now linked to your source code repository.

...

25. On the Opsera portal - click on Tool Registry, Click on the “Jenkins” tool you just created. Then Click on Jobs tab and click on ‘Create ‘+Create Job’ button (as shown below)

...

26. Select Job Type as ‘SFDC Jobs’ , Name, Description and Job Type as ‘Validate XML Package’ and Build Step as ‘SFDC Validate XML Package’. Enter a Name and Description.

...

27. Click ‘Save Job’ to finish creating the job.

...

32.To give a meaningful name for the pipeline, On Summary tab, click on the little pencil icon (next to salesforce template name - to edit the SalesForce Template name).

...

33. Edit the pipeline. Click the Save icon to save the new name.

...

Create Package XML job & Configuration

...

36. Enter the below fields and click Save

  • Tool → From the dropdown, select the Jenkins tool created in Tool Registry;

  • Job Type → default for Package creation job is ‘SFDC Package generation job’, for other steps, it should be ‘Opsera managed jobs’

...

  • SalesForce Credentials → Source Org from which modified files will be fetched

  • Account → [gitlab/github/bitbucket] credentials added inside Jenkins tool in tool registry

...

  • Workspace/Project → Based upon the Account - All

...

  • Projects will be fetched [Select one]

...

  • Repository → Based upon the

...

  • Project - All the

...

  • repositories available will be fetched [Select one]

37. Click Save → all the configurations made to the step will be saved.

...