Forked from piscisaureus
To identify one particular pull request, find the pull request number on the Azure DevOps site:
Then fetch and checkout the pull request in a local branch named pull/137
Forked from piscisaureus
To identify one particular pull request, find the pull request number on the Azure DevOps site:
Then fetch and checkout the pull request in a local branch named pull/137
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
########## Install NGINX ############## | |
# Install software-properties-common package to give us add-apt-repository package | |
sudo apt-get install -y software-properties-common | |
# Install latest nginx version from community maintained ppa | |
sudo add-apt-repository ppa:nginx/stable | |
# Update packages after adding ppa |
# http://stackoverflow.com/questions/5735666/execute-bash-script-from-url | |
bash <(curl -s http://mywebsite.com/myscript.txt) | |
# http://stackoverflow.com/questions/4642915/passing-parameters-to-bash-when-executing-a-script-fetched-by-curl | |
curl http://foo.com/script.sh | bash -s arg1 arg2 |
/** | |
* Unhook and remove WooCommerce default emails. | |
*/ | |
add_action( 'woocommerce_email', 'unhook_those_pesky_emails' ); | |
function unhook_those_pesky_emails( $email_class ) { | |
/** | |
* Hooks for sending emails during store events | |
**/ |
<?php // only copy this line if needed | |
/** | |
* Function adds a BCC header to emails that match our array | |
* | |
* @param string $headers The default headers being used | |
* @param string $object The email type/object that is being processed | |
*/ | |
function add_bcc_to_certain_emails( $headers, $object ) { |
The following are some 'good' patterns within Azure DevOps to allow visibility within Build and Release pipeline. They are not a replacement for symver but could easily be incorporated to increase visibility.
The defaults for AzureDevOps for naming only refer to the Build number
without a context - this makes traceability difficult if you wish to use any of the built in reporting.
A Variable
can be used to enable/disable elements of build/release pipelines in Azure DevOps. This GIST shows how this can be implemented within a pipeline.
Within the Variables
tab create a new variable for this toggle, and set this to a suitable default.
The following example creates a variable Deploy.Arm
that defaults to false
that can be overridden at the creation of the queue.