You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Note - branch/version is a bit blurry, but we can think of version as another 'main' branch that is being actively worked on. ex: epics 3 vs 7, both 3 and 7 are actively getting fixes.

Create Issue:

{
	"caterNumber": "string"
	"component": "string"
	"issueTracker": "string", // OPTIONAL
	"linux_username": "string",
	"gitub_username": "string"
}

Add new version for active development on component:

{
	"component": "string"
	"version": "string"
 	"linux_username": "string",
	"gitub_username": "string"
}

Create new branch

{
	"component": "string"
	"version": "string"
	"type": "string"		// ex: [fix, dev] where fix is meant to merge to main, and dev is not
	"branchPoint": "string" // where to start the branch from: [branch, tag, commit]
 	"linux_username": "string",
	"gitub_username": "string"
}

Checkout component

{
	"component": "string"
	"branch": "string"
 	"linux_username": "string",
	"gitub_username": "string"
}

Push 

// Any reason we can't use git directly?

Mark complete (use when a dev is done, to notify backend the development is considered done)

{
	"component": "string"
	"branch": "string"
 	"linux_username": "string",
	"gitub_username": "string"
}

Start Build (called by runner / cli)

{
  	"component": "string"
	"branch": "string"   
	"linux_username": "string",
	"gitub_username": "string" 
}
  • No labels