archive-nl.com » NL » L » LIMOENGROEN.NL

Total: 242

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    the current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering

    Original URL path: https://www.limoengroen.nl/en/blog/continuous-integration-drupal-at-limoengroen (2016-01-27)
    Open archived version from archive


  • Rijksoverheid Cookie Opt-in module released on Drupal.org | LimoenGroen
    when visitors of a website are informed and give implicit consent to use cookies the Dutch cookie law takes it a step further and demands explicit consent to use cookies and logging of the approvals This means that the cookie law modules that were already available on drupal org EU Cookie Compliance and Cookie Control do not suffice for Dutch websites Furthermore patches supplied by us on the first module are still pending in the issue queue at the time of writing and the latter module actually uses a third pary service from Civic UK Solution by the Dutch government The Dutch government has released a standard JavaScript based solution that complies with the Dutch cookie law The Rijksoverheid Cookie Opt in solution may be used by government as well as non government organisations under the conditions of the Creative Commons Attribution ShareAlike 3 0 Unported CC BY SA 3 0 We recently created the Rijksoverheid Cookie Opt in project on Drupal org that provides a module that integrates the Rijksoverheid Cookie Opt in library with Drupal See the project page on drupal org for more information Martijn Vermeulen Directeur Projectleider Topics Module Cookielaw Drupal Cookiewet Rijksoverheid Blog menu Show

    Original URL path: https://www.limoengroen.nl/en/blog/rijksoverheid-cookie-opt-in-module-released-on-drupalorg (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/6 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/48 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/49 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/50 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/51 (2016-01-27)
    Open archived version from archive

  • Continuous Integration & Drupal at LimoenGroen | LimoenGroen
    current production website drush archive dump Schedule downtime in the monitoring tool Nagios in our case Put the website in maintenance mode drush variable set Update the code on the production environment drush rsync Apply updates drush updatedb drush features revert all Get the website out of maintenance mode drush variable set Jenkins setup and scripts We run a Jenkins instance on a Tomcat application server Our target environments run on several other servers so Jenkins needs to be able to remotely execute drush commands We have created several generic shell scripts that take arguments to actually call the required drush commands Next to that we use drush alias files read more about alias files in this blog post by Baris Wanschers to execute the drush commands on the appropriate target Of course the Jenkins system user has to have the ability to send ssh commands to the target environment without being prompted for passwords by using public private key authentication For example the shell script that applies the updates on a Drupal website calls drush fra like this if usr local bin drush ALIAS fra y then echo Features reverted successfully else echo Reverting features failed exit 1 fi The corresponding build step Execute shell in Jenkins calls the shell script like this usr share jenkins scripts apply updates sh a example prod The a argument indicates which alias to use and differs per Jenkins job You can use Getopts in your shell scripts to use arguments like this Jenkins will respond to the return value from the shell script to see if the step was successful or a failure That is what the exit 1 or exit 0 at the end of the shell script is for This way you can execute any drush command from Jenkins using variables to make the build step project specific Jenkins also provides useful environment variables for each build that you can use as an argument For instance the shell script that updates the code on the target environment needs to know where the Git repository of the Jenkins job is located Jenkins provides the WORKSPACE variable for that so the script is called by the Jenkins build step Execute shell like this usr share jenkins scripts update code sh a example prod w WORKSPACE By splitting up the scripts into separate generic small steps in the build process we can create jobs in Jenkins that suit the specific needs for each target environment without having to create scripts for each project For instance making a backup on each build on the test environment might not be required Example separate build steps in Jenkins job To make sure that a production environment can only be built with a tagged release we use the Git Parameter Plug in to require a user to enter the name of a tag before the build starts and use that name to build the specific release A tag is required to start a production job Triggering Jenkins

    Original URL path: https://www.limoengroen.nl/comment/59 (2016-01-27)
    Open archived version from archive



  •