...
Use the following documentation as a guideline to set up a Git Operations pipeline step and analyze pipeline logscorresponding Pipeline Activity Logs.
| Table of Contents | ||||
|---|---|---|---|---|
|
Git Operations Step Configuration
SCM Type - Choose a source management type. Choose Bitbucket, Github, Gitlab or Azure Devops. It does not yet support Azure Devops.
SCM Account - Choose configured account
Workspace/Project -
Repository -
Branch - Select a source branch. This branch
Git Action - Choose between ‘Create PR’ or ‘Create a Tag’
Target Branch - Select the destination branch where changes will reflect.
Description - Add a description of the change.
pipeline: https://test.opsera.io/workflow/details/628b482ea764f800b0a346f8/model
jira:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Git Action: Create a PR
Create a pull request
Branch -
Git Action - Select ‘Create PR’.
Target Branch -
Description -
Pipeline Activity Logs
Successful Pull Request:
...
Pull Request Already Exists:
...
No Commits Between Branch and Target Branch:
...
Git Action: Create a Tag
Branch -
Git Action - Select ‘Create a Tag’.
Dynamic Tag Name - Provide a name. To make the name dynamic, changing for each pipeline run, add the following text: date, timestamp and run_count.
...
...
Pipeline Activity Logs
...
Create a PR Request
Successful Pull Request:
...
Pull Request Already Exists:
...
No Commits Between Branch and Target Branch:
...
Successful Tag Creation:
...