In this post, we will guide you on how to achieve basic<\/span> Continuous Integration using Jenkins in a <\/b>GeneXus<\/b><\/a> project.<\/b> This is a fundamental step for improving your productivity and development process (even if you are working in a Waterfall approach). By giving early feedback to developers regarding code status, every single one of them will know after committing their code if it doesn\u2019t break the \u201cconsolidated\u201d environment and also that it builds successfully outside their own environment.<\/span><\/p>\n Only after implementing Continuous Integration, you may be inspired to add some new automation pieces into this process to boost quality and productivity by achieving Continuous Delivery.<\/span><\/p>\n Let\u2019s assume that your Jenkins will also be used as your \u201cBuild Server\u201d, which means that the same machine that will host your Jenkins will be responsible for:<\/span><\/p>\n In order to integrate code, we need an <\/span>SCM<\/a>. The GeneXus SCM is GXServer, so you can\u2019t achieve Continuous Integration if you don\u2019t have GXServer.<\/span><\/p>\n In order to accomplish this, we will be using an example in GXServer Sandbox.<\/span><\/p>\n http:\/\/sandbox.genexusserver.com\/v15\/main.aspx<\/span><\/a><\/p>\n We have a KB called UnitTest2 for this example.<\/span><\/p>\n <\/p>\n Step 1 <\/b>(~30 mins)<\/span><\/p>\n > Check out your KB from GXServer and build it manually. <\/b><\/p>\n After creating your KB, build all from GeneXus. This step will force you to define the Database name, Server name and credentials to create database tables, which is recommended before setting things up in Jenkins (or any CI tool). As a result of this step, you should have a built KB in your local directory (in this guide we will be using the local KB folder set on C:\\Models\\KBExample)<\/span><\/p>\n These steps end when GeneXus IDE shows you the <\/span>\u201cBuild All Success\u201c <\/span>message.<\/span><\/p>\n <\/p>\n Step 2 <\/b>(~ 1 hour)<\/span> Build your KB using MSBuild tasks.<\/b> 2.1<\/strong> Check if your environment variable GX_PROGRAM_DIR is correctly set up.<\/span><\/p>\n You can see if this is already set by typing in your windows console (cmd.exe)<\/span><\/p>\n > echo %GX_PROGRAM_DIR% <\/span><\/p>\n The output should look something like: <\/span>C:\\Program Files\\GeneXus\\GeneXus15<\/span><\/p>\n If not, you need to set it up to your GeneXus installation folder.<\/span><\/p>\n 2.2<\/strong> – Download GeneXus MSBuild tasks.<\/span><\/p>\n . <\/span>Artech.Samples.GXServerExtraTasks.targets<\/span><\/a><\/p>\n . <\/span>Artech.Samples.GXserverExtraTasks.dll<\/span><\/a><\/p>\n Copy both files into your %GX_PROGRAM_DIR%<\/span><\/p>\n 2.3<\/strong> – Set MSbuild Path <\/span><\/p>\n MSbuild is the default mechanism to launch the build process in Microsoft Windows, so, for this step you need to put <\/span>MSBuild.exe<\/span> path in your command line, <\/span>e.g. <\/span>C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\<\/span><\/p>\n If your setup is right, you can just type \u201cmsbuild\u201d (plus Enter) in Windows console and see if MSBuild command is recognized.<\/span><\/p>\n 2.4<\/strong> – Download your build files (MSBuild scripts).<\/span><\/p>\n Create a new folder (e.g. c:\\msbuildtasks) and put your build scripts there (one for updating the KB from the server and another for building the KB). You can download examples from here: <\/span><\/p>\n . <\/span>buildKB.msbuild<\/span><\/a> (to build the KB)<\/span><\/p>\n . <\/span>TeamDev.msbuild<\/span><\/a> (to update from GXServer)<\/span><\/p>\n Edit both files with any text editor<\/b> and adjust the GeneXus installation folder path, your KB path, and GXServer URL and credentials.<\/span><\/p>\n Open your command line and type: <\/span><\/p>\n > <\/span>msbuild \u201cc:\\msbuildtasks\\buildKB.msbuild\u201d <\/span><\/p>\n You should see how your KB is building. Please note that this is the same as doing \u201cBuild All\u201d using GeneXus IDE, but from a Windows MSBuild process. \u201cTeamDev.msbuild\u201d script will be used in the next step…<\/span><\/p>\n <\/p>\n Step 3 <\/b>(~ 30 minutes)<\/span><\/p>\n Get KB latest version from GXserver using MSBuild tasks.<\/b><\/p>\n 3.1<\/strong> Start by downloading GXServer client (in order to connect to GXServer using MSBuild tasks). This is needed by MSBuild script to handle communication with the server. To do so, create a local directory in your machine (e.g. c:\\gxserverclient).<\/span><\/p>\n Download these 2 files and copy them into it:<\/span><\/p>\n . <\/span>TeamDev.exe<\/span><\/a><\/p>\n . <\/span>TeamDev.exe.config<\/span><\/a><\/p>\n If you already edited your TeamDev.msbuild file in previous step (2.4) pointing to your folders, then you will be able to open your command line and type: <\/span><\/p>\n > <\/span>msbuild \u201cc:\\msbuildtasks\\TeamDev.msbuild\u201d <\/span><\/p>\n You should now be seeing how the KB is being updated from GXServer (if it has new changes from the last update).<\/span><\/p>\n <\/p>\n Step 4 <\/b>(~ 1 hour)<\/span><\/p>\n Integrate it in Jenkins<\/b><\/p>\n 4.1<\/strong> First, you need to install 2 plugins in Jenkins, one for triggering MSBuild tasks (step 2 and 3), and another to see them in a \u201cpipeline\u201d style:<\/span><\/p>\n In Jenkins, click Manage Jenkins \/ Manage Plugins. <\/span><\/p>\n Look for these 2 plugins and install them:<\/span><\/p>\n 4.2<\/strong> Then, you will need to create 2 Jobs: <\/span><\/p>\n Job #1:\u00a0UPDATE KB:<\/span><\/p>\n Click on \u201cNew Item\u201d select \u201cFreestyle project\u201d and set the job\u2019s name (something like <\/span>\u201cUpdate from GXServer\u201d)<\/b>. Click Ok. Then navigate to \u201cBuild\u201d section and \u201cAdd build step\u201d by choosing the \u201cBuild a Visual Studio project or solution using MSBuild\u201d.<\/span><\/p>\n Over the text field \u201cMSbuild Build File\u201d just put your script (c:\\msbuildtasks\\TeamDev.msbuild).<\/span><\/p>\n Job #2:\u00a0BUILD KB:<\/span><\/p>\n The other job is for building, so again:<\/span> Over the text field \u201cMSbuild Build File\u201d just put your script (c:\\msbuildtasks\\buildKB.msbuild)<\/span><\/p>\n Finally, on the \u201cPost-build Actions\u201d section, add a \u201cBuild other projects\u201d action to automatically trigger the build after the update from GXServer (Continuous Integration). <\/span><\/p>\n This can be achieved by typing the name of your first task (job name \u201cUpdate from GXServer\u201d).<\/span><\/p>\n 4.3<\/strong> Create the pipeline<\/span><\/p>\n Now, you can create the pipeline. On your Jenkins dashboard, click the (+) icon, and add a \u201cBuild Pipeline View\u201d and select a name for your pipeline (e.g. \u201cdemo KB\u201d).<\/span><\/p>\n In the \u201cSelect Initial Job\u201d field, choose the first one to run: \u201cUpdate from GXSever\u201d job.<\/span><\/p>\n Your pipeline should look like:<\/span><\/p>\n You can now simply run the pipeline in Jenkins and see the output. <\/span><\/p>\n If you have problems with this step, check Windows\u2019 user privileges running your Jenkins service and ensure that it has proper access to folders and executables involved so far.<\/span><\/p>\n And there you have it!<\/span><\/p>\n If you want to set-up a different CI tool (like Bamboo, Circle CI, TeamCity, etc. ) OR, if you want to set up a more sophisticated approach (using building slaves, deploying to the cloud, etc.), just leave us a\u00a0message<\/a>!<\/strong><\/p>\n Not Convinced Yet About “Shift-Left Testing”?<\/a> Our step by step guide for using Jenkins in a GeneXus project In this post, we will guide you on how to achieve basic Continuous Integration using Jenkins in a GeneXus project. This is a fundamental step for improving your productivity and development process (even…<\/p>\n","protected":false},"author":21,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[61],"tags":[546,238,223],"yoast_head":"\n![\"Screen](\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/11\/Screen-Shot-2017-11-06-at-7.52.51-PM-min.png\")
<\/a><\/p>\n<\/span>Introduction<\/span><\/h2>\n
\n
<\/span>Prerequisites<\/span><\/h2>\n
\n
<\/span>Getting Started<\/span><\/h2>\n
\n
\n<\/b><\/p>\n
\n<\/b><\/p>\n\n
\n
\n<\/span>Click on \u201cNew Item\u201d select \u201cFreestyle project\u201d and put an item name like <\/span>\u201cBuild KB\u201d<\/b>. Click Ok. Then navigate to the \u201cBuild\u201d section and \u201cAdd build step\u201d by choosing the \u201cBuild a Visual Studio project or solution using MSBuild\u201d.<\/span><\/p>\n<\/a><\/p>\n
\n<\/span>Recommended for You<\/strong><\/span><\/h2>\n
\nHow to Use Monkop for Continuous Mobile Testing<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"