99 lines
2.7 KiB
Markdown
99 lines
2.7 KiB
Markdown
---
|
|
route: bench/overview-new
|
|
allow_guest: 1
|
|
published: 1
|
|
---
|
|
|
|
This is information about pagetypes required to manage benches and apps on FC
|
|
from [desk](https://jcloud.jingrow.com/app). Roughly, the build process goes
|
|
through these pagetypes (that you're concerned with) in order.
|
|
|
|
App => App Source => Release Group => Deploy Candidate => Bench
|
|
|
|
To build a bench, we need documents of the following pagetypes.
|
|
|
|
## App
|
|
|
|
It's simply a master of all apps on FC. Only detail it has is the name of the app.
|
|
|
|
|
|
|
|
|
|
## App Source
|
|
|
|
We use this pg to specify Github \_repo\_ and \_branch\_ for an App. An App can have multiple of these.
|
|
|
|
|
|
|
|
## Release Group
|
|
|
|
This is like a blueprint of a series of benches. It contains a list of Apps and
|
|
App Sources as child table.
|
|
|
|
> Must have jingrow as first app.
|
|
> You can use `visit dashboard` link in sidebar to see corresponding dashboard view
|
|
|
|
|
|
|
|
|
|
It also contains a list of servers to deploy your bench on.
|
|
|
|
## Deploy Candidate (created automatically)
|
|
|
|
This pg becomes more specific than the Release Group in the sense that it also
|
|
has information on which \_commit\_ of each app you're going to put on your
|
|
bench.
|
|
|
|
|
|
|
|
|
|
> The information of each commit of an App Source is in an App Release pg.
|
|
|
|
Deploy Candidates are created for each update to the Release Group (could be
|
|
update to an app, could be addition/removal of apps, etc..). It is not intended
|
|
to deploy all of the ones created. Latest one is deployed when you update bench
|
|
from dashboard view.
|
|
|
|
|
|
|
|
|
|
You can also manually trigger creation by using `Create Deploy Candidate`
|
|
Action on the Release Group.
|
|
|
|
|
|
|
|
|
|
Use the `Build and Deploy` button to deploy a new Bench.
|
|
|
|
|
|
|
|
|
|
This will create an image that'll be used for creating a bench. In case of any
|
|
issue, you can see the log of all commands executed in the Deploy Candidate
|
|
pg. `Build` will just create the image, not create a new bench on server.
|
|
|
|
|
|
|
|
|
|
You can also get live output in the dashboard view.
|
|
|
|
|
|
|
|
After build and upload is successful, there should be a link to the new bench
|
|
job, which should also be successful for you to use your bench.
|
|
|
|
|
|
|
|
|
|
## Bench (created automatically)
|
|
|
|
|
|
|
|
|
|
Will be created after successful deploy. Represents a bench on each individual server.
|
|
|
|
Many can be created for a Deploy Candidate deploy depending on list of servers
|
|
in Release Group.
|
|
|
|
|
|
 |