Recent Posts

    Authors

    Published

    Tag Cloud

    301 302 404 accessibility accounts ACLs advertising aggregation Agile Analytics android APP Article attachments awards backup BCM beta browser business continuity Calendar case-study categories Chrome citigroup cms codes coding standards Complaints contact management software control panel crm CSS customer management software customer relationship system customize database DataModel DDoS demo design designer device compatibility difference distribute a published article via email DND DNS documents drag & drop Editor email EOL erp event Excel featured feeds file manager file sharing file volume Firefox Firewall HA hack Handlebar how-to HTML HTML5 HTTP HTTPS iCal IE Instructions intranet iOS iPad Java JavaScript JDBC JDK Jenkins Job Track Journal JSON JVM landing-page launcher layered database layout logging login mac marketing menu meta Microsoft Outlook mobile module modules mustache navigation NTLM offline page painter password passwords PCI policy poll pricing privacy PROXY publish publisher publsher PWA redirect Redundancy release release-notes Report Tool Reports Responsive ReST RESTFul Rich text RSS Safari sandbox sanity schedule scrum search security SEO sessions setup shipping site builder source spell SQL Injection SSL SSO standards store stSoftware support survey Swagger Task template testimonial Threads timezone tinyMCE Transaction Search trigger twitter twitter bootstrap Ubuntu unit tests unsubscribe URL validation WC3 AAA web folders web services webdav windows 8 wizard workflow WYSIWYG XLS XLST XML XPath XSS

    What is the stSoftware deployment process?

    Agile continuous delivery pipeline

    Summary

    The stSoftware incremental upgrade process consists of a continuous integration system and three separate staged environments.

    Continuous integration system

    Main steps:- 

    1. Checks out the current code and databases
    2. Cleans the databases
    3. Creates the release.
    4. ~6,500 automated tests are run. 
    5. If ALL automated tests past then the release is then promoted for distribution.
    6. Distribution occurs Sunday -> Thursday to the Edge environment.

    Jenkins

    Test Trend

    Environments

    A release is firstly built and tested by the continuous integration system ( Jenkins), if ALL (~6,300 automated tests) pass then the release is automatically promoted for release.

    Edge

    Deployed daily (Monday-Friday between 4am and 4:30am) from a promoted release ( 100% successful tests). 

    Agile

    Deployed weekly on Sunday between 3am and 3:30 am from the current Edge release. The release has been in the Edge environment for at least 2 days.

    Stable

    Deployed monthly on the first Saturday of the month between 2am and 2:30am from the last Agile. The release has been in the Agile environment for at least 6 days.