Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Andrea Veri (@averi)
Issue was closed by Andrea Veri Issue #606: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 You're receiving this email because of your account on gitl

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Andrea Veri (@averi)
Andrea Veri commented: OK, I see your user now, landed your access against the damned-lies namespace, you should be all set :-) -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606#note_1271826 You're receiving this email

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Andrea Veri (@averi)
Andrea Veri commented: For some reason I thought we granted you access there already, mind logging in at https://openshift.gnome.org:8443 please? -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606#note_1271825 You're re

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard commented: I have no access with my GNOME Id :shrug: -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606#note_1271815 You're receiving this email because of your account on gitlab.gnome.org. __

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Andrea Veri (@averi)
Andrea Veri commented: @gbernard you get yourself to https://openshift.gnome.org:8443/console/project/damned-lies/browse/pods, from there you look for the target pod name (make sure pod state is 'running'), in this case httpd-testing, from the you click on logs and you should be good to go

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard commented: Hi ! There an Internal Server Error with https://l10n-testing.openshift.gnome.org/. Can you tell more about this, or give indices on how to debug by myself or access logs in order not to disturb you any time there’s an issue with DL Deployment? 🙄 -- Reply to

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-09-17 Thread Guillaume Bernard (@gbernard)
Issue was reopened by Guillaume Bernard Issue 606: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 You're receiving this email because of your account

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-07 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard commented: Thanks! I updated the `.gitlab-ci.yml` file to deploy DL automatically after a successful pipeline and set the same on `develop`. I updated the `Dockerfile` in `oscp-testing` to track the `develop` branch as well. Thanks for your precious help! -- Reply to th

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-07 Thread Guillaume Bernard (@gbernard)
Issue was closed by Guillaume Bernard Issue #606: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 You're receiving this email because of your account o

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-05 Thread Andrea Veri (@averi)
Andrea Veri commented: The data you see there is a dump taken from a database backup from weeks ago, let me know if you want us to rebase to a newer copy of the database :) -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-05 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard commented: Thanks! I will include this in Gitlab CI jobs and probably solicite you in a near future to proofread the documentation I’ll write on the `damned-lies` wiki :-). What can you tell me about the data in https://l10n-testing.openshift.gnome.org/? Thanks! -- R

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-02 Thread Andrea Veri (@averi)
Andrea Veri commented: The Dockerfile is already there on this branch: https://gitlab.gnome.org/Infrastructure/damned-lies/-/tree/oscp-testing. I've bumped the number of pods to 1 so that the website is live. Once you send a POST against the webhook URL I provided it will schedule a build a

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-07-01 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard commented: Hi, Thanks for this reply. 1. I’ve no idea what you’re talking about. I would like for instance having a specific branch, maybe `develop` being deployed on this instance, possibly with `oscp-testing`. I suppose we’ll need to have two Dockerfile, one deriving fr

Re: Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-06-30 Thread Andrea Veri (@averi)
Andrea Veri commented: 1. There's a DL test instance setup already at https://l10n-testing.openshift.gnome.org, you'll have to scale the pods up as they're currently set to 0. The branches it is attached to are: testing / oscp-testing. 1. I've landed 2 new secret variables against the damne

Infrastructure | Deploy on trigger for DL and pre-production instance (#606)

2021-06-29 Thread Guillaume Bernard (@gbernard)
Guillaume Bernard created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/606 Hi, For Damned Lies, I encountered an issue with automatic deployment in production (which I ignored) when pushing commits on `master`. Is it possible to reverse this behavior and let, f