Ask HN: What does your deployment workflow look like?

All of our code repos follow the same example:<p>1) PRs create whole environments using master for everything except the repo listed in your PR which uses the PR branch. QA and developers use this for QA<p>2) Once the PR is accepted the code is merged into master<p>3) CI builds the code, tags the repo, uploads to s3 as versioned artifact<p>4) CI checks current version on stg env, deploys new version. CI checks current version on stg env, runs git diff btween the two versions, checks for jira tickets, gets jira ticket summary, and prepares slack &#x2F; email notifications<p>5) CI runs tests<p>6) If tests pass, QA can deploy the release to prd.<p>7) CI releases to prd, adds released_version to each jira ticket, sends out email&#x2F;slack notifications (with commit, jira summaries) then runs tests

I have built a generic deployment tool that does the following<p>1. Does dependencies installation 2. Does Code linting 3. Creates a new release folder and gets the entire codebase there.<p><pre><code> shared&#x2F; - for common assets like user upload data and images releases&#x2F; 2018060291205&#x2F; 2018060300703&#x2F; current&#x2F; - ll be pointing to the active release. </code></pre> 4. Notify the team on slack, emails and whatever 5. You can rollback at just click of a button and it ll point to one of its previous release.<p>Currently it works well for php. First project is completely free, but only for first 100 signups. Please make this opportunity and signup at <a href="http:&#x2F;&#x2F;grandappstudio.com&#x2F;roll-out?utm_source=news_yc" rel="nofollow">http:&#x2F;&#x2F;grandappstudio.com&#x2F;roll-out?utm_source=news_yc</a><p>Docs at <a href="http:&#x2F;&#x2F;rollout-docs.grandappstudio.com?utm_source=news_yc" rel="nofollow">http:&#x2F;&#x2F;rollout-docs.grandappstudio.com?utm_source=news_yc</a><p>Appreciate your feedback, Also we are applying for YC Winter18 batch, if someone could help in reviewing the application and give recommendation would be more than happy. Drop a mail to hello@grandappstudio.com, I would sync up.

For us at Phaser (<a href="https:&#x2F;&#x2F;phasersec.com" rel="nofollow">https:&#x2F;&#x2F;phasersec.com</a>) chatops was a revolution.<p>1) git push master (Gitlab CI to run tests, builds...)<p>2) notification received when CI pipelines finished<p>3) @bot deploy api production (in our messaging app)<p>if errors happen:<p>4) @bot rollback api [commit]

I started trying to answer this question, but we produce so many different types of build types (binary, loose file, digital, ISO, and more..) for so many different purposes and audiences (coders, content creators, embedded QA, external QA, 1st party QA, cert, and a mix thereof) that this is actually impossible without typing out a full-on guide of some sort.<p>Extremely rough general flow which does not apply to everything: presub, submit to p4, build code, upload symbols, build data, run tests, run relevant deployment step, register metadata, send-to-one-of-numerous-external-or-internal-partners, and a bunch of support steps inbetween.

1. rpmbuild;<p>2. upload to the software deployment server;<p>3. deploy;<p>4. test the hell out of the software;<p>5. upload to the peer review tool;<p>6. passing review, commit.<p>I oversimplify, but everything starts with writing a .spec file for a future package, and then writing everything else and testing the hell out of it and having it peer reviewed before committing.

1) Git push&#x2F;merge request in gitlab<p>2) Manual code review (I&#x27;m working on getting the CI to work with sonar. Still haven&#x27;t.)<p>3). Manual push to Test server. (No idea how to automate deploying to JBoss server on behind a VPN on Windows.)