Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create new production release builds #936

Closed
mattyweb opened this issue Feb 9, 2021 · 5 comments
Closed

Create new production release builds #936

mattyweb opened this issue Feb 9, 2021 · 5 comments
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) Feature: Optimization Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work size: 8pt Can be done in 31-48 hours Tech Stack: Old

Comments

@mattyweb
Copy link
Collaborator

mattyweb commented Feb 9, 2021

We redid the GitHub actions for building the dev environment but need to do the same thing for the production environment.

Builds should run off of /release branches and create and tag the needed Docker images.

@mattyweb mattyweb added the size: 8pt Can be done in 31-48 hours label Feb 9, 2021
@mattyweb mattyweb self-assigned this Feb 9, 2021
@mattyweb mattyweb added this to the Initial v2 Launch milestone Feb 9, 2021
@mattyweb mattyweb added Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work labels Feb 17, 2021
@mattyweb mattyweb removed their assignment Apr 3, 2021
@mattyweb
Copy link
Collaborator Author

mattyweb commented Apr 3, 2021

Not quite ready to move forward with this one. Actually, this is a bit of a placeholder issue. I think we might decompose this into separate production deploy tasks for API and Report Server. Also, originally I had conceived of having semver versioned releases, but not sure that makes sense anymore. Let's keep this in backlog for now.

@mattyweb mattyweb self-assigned this Apr 13, 2021
@github-actions

This comment was marked as outdated.

@EchoProject
Copy link
Contributor

This may be tied to Adam needing to fix the build pipeline for some PR tickets found here.

@EchoProject
Copy link
Contributor

@nichhk I think we talked about this some time ago, but I can't remember where we landed. Is this still relevant or will it be addressed in the ops migration or something else?

@nichhk
Copy link
Member

nichhk commented Sep 15, 2022

This still needs to be worked on. We can work on this closer to when we're ready to launch, and I expect it to be pretty straightforward--just changing a couple lines of configuration code.

@ExperimentsInHonesty ExperimentsInHonesty moved this to Done (without merge) in P: 311: Project Board Jun 7, 2024
@cottonchristopher cottonchristopher added the Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) Feature: Optimization Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work size: 8pt Can be done in 31-48 hours Tech Stack: Old
Projects
Status: Done (without merge)
Development

No branches or pull requests

7 participants