-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add first version of deployment on dev script #17
Conversation
Did you think about the option to have no branches for scilog-ci for "normal" development updates ? |
I still haven't understood what the idea is on that... |
I guess the idea was to only have a single branch in scilog-ci and automatically deploy whatever is on main. We test locally, discuss the PR on git, merge it, test it on our dev server and potentially later deploy it on production. |
now the deployment has 3 steps: to dev, to qa, to prod. What you described is actually what happens in qa. I still struggle to understand what it simplifies, it only removes the PR opening need |
Okay, now I'm also confused... I understood that there is no automatic deployment from scilog main? |
everything it's more or less explained here: https://github.com/paulscherrerinstitute/scicat-ci/#scicat-ci (happy to discuss further ofc) |
f7e880e
to
bee4ece
Compare
bee4ece
to
8ca7300
Compare
@stephan271 , @wakonig this would be the first version of the deployment script. Unfortunately, I've checked the git client hooks and the post-push does not exist.
This script might change (depending on what you need). For now, the idea is that using this script, steps 1, 7, (8 partially) are automated.
This script has to be run from the scilog-ci folder, every time one wants to deploy.
It can be modified to run directly in the scilog (submodule) folder to cover points 2 and 6 (
cd
commands).Let me know if it is good enough or needs changing.