Repository navigation
Create CI pipeline for xreds #7
Description
We already have a service running on nextgen-dev Kubernetes which is hosting the XREDS website: https://nextgen-dev.ioos.us/xreds/
Currently this service is manually deployed by @mpiannucci.
Source code and instructions for deploying xreds: https://github.com/asascience-open/xreds
We would like to create a CI pipeline to build this project. We can also explore CD options but for now a simple build process and one-line to deploy is fine without taking too much time. Please work with @mpiannucci if you have questions configuring the build process.
Activity
jonmjoyce commentedon Jul 31, 2023
Since XREDS is intended to be an open-source project we want to keep that repo as "clean" as possible from specific configurations. This means that our CI/CD pipelines (which are specific to our environment) should be part of a different repo for build. We could call this other repo xreds-build or something.
We want to keep this other repo private and accessible only to our team. It will pull from the public xreds repo as one of the build steps. We also don't want to auto-build off a push to the public repo. For now we can make this a manual build process until we determine what we want. It will also be important to be able to reference which version/commit of xreds was grabbed for a particular build.
pavaniankam92 commentedon Aug 10, 2023
Code has been built to use CI for Xreds and tested. Seems to be working as expected now. Please check the code below
https://github.com/asascience-open/xreds-Deploy-CI/tree/main
Please review and let me know
mpiannucci commentedon Aug 11, 2023
it looks good! I think the main thing that remains is how make it so we can tag versions, cuz right now it looks like it will always have the same version number
good work!
pavaniankam92 commentedon Aug 11, 2023
Instead of keeping the version number for image tag, we can go with "latest" as before. So whenever there is a new version it would come up as "Latest".
If we want to go with version tagging, every time we need to modify manually in deploy.yaml to tag whatever is needed.
Let me know if this what we are looking for or something am missing.
mpiannucci commentedon Aug 11, 2023
Lets go with latest for now! Thank you!