# Background Un-obfuscate thread launching [comment]: # (If this is a bug, fill in the following sections) # Observed behavior [comment]: # (Please provide as many details as you can about steps to reproduce, operating system, browser, and version used, screenshots, example submission IDs, example XML, example queries, etc) # Expected behavior [comment]: # (What did you expect to happen before you observed the anomalous behavior?) # How urgent [comment]: # (There are myriad factors that go into prioritizing and scheduling development work, but any information you can provide to help us understand severity, urgency, relative priority, or deadlines, is much appreciated.) [comment]: # (No need to update the Definition of ready when filing issues, but feel free to have a go if you're familiar with the territory.) # Definition of ready - [ ] Product owner: - [x] Tech lead: @jjshoe - [x] Service:: label applied - [ ] Definition of done updated - [ ] Acceptance testing plan: - [ ] Weight applied [comment]: # (Feel free to leave this as is, or suggest changes. We'll update these during Backlog Refinement, prior to bringing this into a sprint.) # Definition of done - [ ] Unit tests identified, implemented, and passing - [ ] Code reviewed - [ ] Available for acceptance testing via a staging URL, or otherwise - [ ] Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed - [ ] Knowledge base reviewed and updated - [ ] Public documentation reviewed and updated - [ ] Acceptance criteria met - [ ] Decide the best way to implement starting threads - [ ] Leave as is on build2 - [ ] Integrate into the cs .gitlab-ci.yml file - [ ] A third unknown option - [ ] Implement changes - [ ] Acceptance testing passed # Notes Right now after a deployment is done .gitlab-ci.yml for content system ssh's to build2 and runs both `/usr/local/qs/bin/SP-START-STANDARD.sh` and `/usr/local/qs/bin/SP-START-STANDARD-STAGING.sh`. I don't believe these are in SCM anywhere. Additionally the shelling away makes it less visible then in the pipeline. I believe at minimum we should move them into the pipeline. I'm open to other ideas as well, like if there's some way to bake it into the war, and each system can start it's own threads based on it's hostname. I'm open to discussions about best practices here. https://gitlab.com/crossref/content_system/-/blob/develop/.gitlab-ci.yml [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)