cjtibule/YABA
1
0
Fork 0
Code Issues 10 Pull Requests Packages Projects 1 Releases Wiki Activity

Add CI/CD pipeline #3

New Issue
Closed
opened 2023-02-19 15:53:08 -06:00 by carltibule · 2 comments
carltibule commented 2023-02-19 15:53:08 -06:00 (Migrated from github.com)
Copy Link

The pipeline should build the back and front ends, run unit tests, and create separate docker images for both. If there's any failure at any step, send a Discord message to specified webhook.

Consider the following:

  • Should a new project and network be created, with new VMs spun up, with properly configured access (IE: VPN access only). - - How should some services be publicly exposed?
  • Should a special environment be spun up specifically for YABA? One consideration is Yes, but there would be 2 YABA prod environments: one for public access and one for self-hosting.
  • Should new db containers be spun up or use existing one? One consideration is Yes, follow the setup as above
The pipeline should build the back and front ends, run unit tests, and create separate docker images for both. If there's any failure at any step, send a Discord message to specified webhook. Consider the following: - Should a new project and network be created, with new VMs spun up, with properly configured access (IE: VPN access only). - - How should some services be publicly exposed? - Should a special environment be spun up specifically for YABA? One consideration is Yes, but there would be 2 YABA prod environments: one for public access and one for self-hosting. - Should new db containers be spun up or use existing one? One consideration is Yes, follow the setup as above
carltibule commented 2023-03-29 23:23:08 -05:00 (Migrated from github.com)
Copy Link

There will be 3 environments: prod, staging and dev. All will be publicly accessible on the same project as all of the other services running on iwanaga. DBs already setup for all of the environment

There will be 3 environments: prod, staging and dev. All will be publicly accessible on the same project as all of the other services running on iwanaga. DBs already setup for all of the environment
carltibule commented 2023-04-01 00:54:01 -05:00 (Migrated from github.com)
Copy Link

Might have to switch to using env for storing credentials, for easier dockerizing https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration-providers#environment-variable-configuration-provider

Might have to switch to using env for storing credentials, for easier dockerizing https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration-providers#environment-variable-configuration-provider
cjtibule added reference feature/CreateCIPlans 2024-04-07 14:07:16 -05:00
cjtibule self-assigned this 2024-04-07 14:07:39 -05:00
cjtibule added this to the YABA project 2024-04-07 14:08:48 -05:00
Sign in to join this conversation.
feature/CreateCIPlans
Branches Tags
Labels
Clear labels
bug
Something isn't working
devops
Anything not directly code related such as CI/CD, infra setup, etc..
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
invalid
This doesn't seem right
question
Further information is requested
wontfix
This will not be worked on
No Label
enhancement
Milestone
No items
No Milestone Version 0.1.0
Projects
Clear projects
No project YABA
Assignees
Clear assignees
cjtibule
No Assignees cjtibule
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cjtibule/YABA#3
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?