<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chimed Altandush on Medium]]></title>
        <description><![CDATA[Stories by Chimed Altandush on Medium]]></description>
        <link>https://medium.com/@caltandush?source=rss-3f3919da9e62------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Uf4knkN9X-Zdfjjn.jpg</url>
            <title>Stories by Chimed Altandush on Medium</title>
            <link>https://medium.com/@caltandush?source=rss-3f3919da9e62------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:17:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@caltandush/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Top 5 Jenkins Plugins You Should Have in 2021]]></title>
            <link>https://medium.com/starschema-blog/the-top-5-jenkins-plugins-you-should-have-in-2021-96a7932d6f15?source=rss-3f3919da9e62------2</link>
            <guid isPermaLink="false">https://medium.com/p/96a7932d6f15</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[jenkins-pipeline]]></category>
            <dc:creator><![CDATA[Chimed Altandush]]></dc:creator>
            <pubDate>Mon, 10 May 2021 17:03:54 GMT</pubDate>
            <atom:updated>2021-05-17T17:33:22.463Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve been working with open-source automation server Jenkins for some time or have worked with Jenkins in different organizations, then you know that, like other open-source tools, the experience can vary vastly based on how the team is maintaining the platform.</p><p>Based on my experience administrating Jenkins, here are the five most essential plugins that you need to make life easier for yourself and the users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YE5eAK89hfVmOOCLJQ-51Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@melindamartinkhan?utm_source=medium&amp;utm_medium=referral">Melinda Martin-Khan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>1. </strong><a href="https://plugins.jenkins.io/slack/"><strong>Slack Integration</strong></a></p><p>If your organization uses Slack, you can have your post-build notifications sent directly to your Slack and avoid all the annoying automated emails when your inbox is already crammed.</p><p>This is what Jenkins looks like in Slack:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3_cQCg8ZlDP_braieoO-Yg.png" /></figure><p>The plugin makes browsing through your Jenkins-related notifications a breeze compared to searching through your inbox.</p><p>And these are your Slack notification options in Jenkins:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHxptrDe7ooA5XqBsfzl5w.png" /></figure><p><strong>2. </strong><a href="https://plugins.jenkins.io/jobConfigHistory/"><strong>Job Configuration History</strong></a></p><p>We’ve all been through the pain of either making some changes to your job and it starts to fail or wishing we could revert our job back to its old glorious self. Job Configuration History is here to make all of that possible.</p><p>The plugin grabs a config.xml file of each change that you make to your jobs, thereby creating a version control for all your Jenkins jobs — which is ultra convenient, especially when the users are playing around to optimize their jobs or during troubleshooting. What makes this plugin especially convenient is that it enables the user to have a side-by-side comparison of the changes that they’ve made:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5af-Jex9B-DuL-XFykN1Ww.png" /></figure><p>This plugin saves a copy of the configuration file of jobs and agents config.xml for every change made and of the system configuration &lt;config-name&gt;.xml. And if you configure a security policy, you can also see what changes specific users have made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8hyoNYsS7_Fke62kkMglA.png" /></figure><p><strong>3. </strong><a href="https://plugins.jenkins.io/PrioritySorter/"><strong>Priority Sorter</strong></a></p><p>The Priority Sorter plugin allows you to prioritize jobs. If your Jenkins deployment often has a large queue and users have certain jobs that have higher priority than others, then you can use this plugin to ensure the precedence of the most important jobs.</p><p>In a nutshell, it works as follows: imagine you’re waiting in line at a fast food place, when certain people — seemingly in a rush — start cutting to the front of the line and receiving service. When all workers are occupied, these “VIPs”/priority jobs are the first to receive service and execute as soon as a worker frees up.</p><p><strong>4. </strong><a href="https://plugins.jenkins.io/simple-theme-plugin/"><strong>Simple Theme</strong></a></p><p>Ever felt like your Jenkins just feels like a foreign tool in your company’s software pool? That’s likely because you’re still using the default Jenkins theme. Luckily, you can customize the look and feel of Jenkins from its default theme to whatever you want.</p><p>Using the Simple Theme plugin, you can customize Jenkins to make the tool more familiar for users and in line with your organization’s visual brand. There are pre-built themes you can adopt, which can give you a head start especially if your company uses Atlassian products, for example.</p><p><strong>5. </strong><a href="https://plugins.jenkins.io/purge-build-queue-plugin/"><strong>Purge Build Queue</strong></a></p><p>Ordinarily, you can remove jobs from the queue one-by-one, but, this is incredibly inconvenient, especially when there are tons of jobs. The Purge Build Queue plugin unlocks the ability to — you guessed it — instantly purge the built-up queue. You may be wondering why you would need this functionality — fantastic question! Allow me to paint a scenario where even I didn’t know I needed it until the following happened:</p><p>Our main DWH, where the majority of jobs query data from, ran into an issue where no query was executing. Once the DWH came back up, we had a massive queue that the scheduled builds had built up. We needed to clear this queue, which at the time involved removing jobs one-by-one. Lesson learned — the next time we ran into the same issue, we tried the Purge Build Queue plugin and saved a lot of time and frustration.</p><p>I strongly encourage you to give these plugins a try and bring them to the attention of your Jenkins admin. If you have any questions, see my contact details below.</p><p><strong><em>Chimed Altandush</em></strong><em> is a senior consultant at </em><a href="https://starschema.com/"><strong><em>Starschema</em></strong></a><em>, a professional services firm that helps data leaders and their organizations to derive value from their data and analytics technology investments. Connect with Chimed on </em><a href="https://www.linkedin.com/in/caltandush/"><em>LinkedIn</em></a><em> or at </em><a href="/service/mailto:altandushc@starschema.net"><em>altandushc@starschema.</em></a><em>com.</em></p><h4><em>REACH OUT TO STARSCHEMA </em><a href="https://starschema.com/contact"><em>HERE</em></a><em>:</em></h4><p><a href="https://starschema.com/contact">Contact</a></p><h4>READ MORE STORIES FROM STARSCHEMA</h4><ul><li><a href="https://medium.com/starschema-blog/starsnow-http-client-for-snowflake-sql-e1b329293fc6">StarSnow: HTTP Client for Snowflake SQL</a></li><li><a href="https://medium.com/starschema-blog/testing-sql-pool-performance-in-azure-synapse-analytics-a5dadcdea978">Testing SQL Pool Performance in Azure Synapse Analytics</a></li><li><a href="https://medium.com/starschema-blog/monitoring-with-jmx-how-to-integrate-tableau-server-with-influxdb-d99e87119750">Monitoring with JMX: How to Integrate Tableau Server with InfluxDB</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96a7932d6f15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/starschema-blog/the-top-5-jenkins-plugins-you-should-have-in-2021-96a7932d6f15">The Top 5 Jenkins Plugins You Should Have in 2021</a> was originally published in <a href="https://medium.com/starschema-blog">HCLTech-Starschema Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tableau Version Control is here to make your life easier]]></title>
            <link>https://medium.com/starschema-blog/tableau-version-control-is-here-to-make-your-life-easier-80ecf5da1ce4?source=rss-3f3919da9e62------2</link>
            <guid isPermaLink="false">https://medium.com/p/80ecf5da1ce4</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[tableau-server]]></category>
            <category><![CDATA[tableau]]></category>
            <category><![CDATA[dataviz]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Chimed Altandush]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 20:41:47 GMT</pubDate>
            <atom:updated>2019-03-18T17:53:17.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*oPENeoraaGTpQcxgF37lOQ.jpeg" /></figure><p>If you are a Tableau server admin or interact with your Tableau admin, then the chances of you desperately crying out for their help over some accidental action is a quiet common possibility. Currently, retrieving just one workbook or select few items from a Tableau backup is time costly and counter-productive work. Imagine having to move the entire box that will take you five hours to move from your storage into your room just to get two items. Pretty rough huh? That is what Tableau admins currently have to go through in order to restore workbooks from a backup, but there is little more hassle to that too. Let me explain:</p><p>Currently, Tableau uses the all-or-nothing backup system when it comes to backing up your workbooks. What that means is that there is no way we can individually backup workbooks but in bulk that can only be then restored as a bulk. That translates to having to restore the entire backup into a test server then retrieve the workbooks that are needed. Depending on the size of your backup, this process takes a total of staggering 12–15 hours to complete. This gruesome process is required surprisingly often since people accidentally delete workbooks or older version is needed for various reasons. Tableau currently do have their own version of version control, however it is not the most optimal option. It also deletes all previous versions along with its newest version if accidentally deleted.</p><p>Luckily for you Tableau admins, we have a solution that would make your life easy and make others happy by getting that precious workbook in a fraction of the time than it normally takes to retrieve. We make this possible by running a version control on all the workbooks on the production server. The version control will scan all the workbooks and only backup the ones that have been modified since the previous backup (meaning it doesn’t waste time backing up something that hasn’t been changed since the last backup). Best of all, it will keep all the old versions as well! More importantly, you would have an ability to individually restore desired workbooks without having to go through the old all-or-nothing way. This saves a tremendous amount of time for all parties involved and adds the convenience of being able to access old workbooks at any given time. Lastly, this is an open-source tool, and you can sprinkle this amazingness into your life now if you’d like! Or if you have any questions so far, reach out to us at <strong>contact@starschema.com.</strong></p><p>HOW IT WORKS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*gTUR5-AXLRqTvRMgrIDWgQ.jpeg" /><figcaption><strong>Without </strong>our Version Control</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*TSZngAV4qahuydJsle8lbQ.jpeg" /><figcaption><strong>With </strong>our Version Control</figcaption></figure><p>Let’s take a deeper dive into the technical side of things so you can install it on your server. Here is all you need to get started:</p><ul><li>It’s an <strong>Open Source </strong>tool!</li><li>Requires <strong>Python 3.7 or later version</strong></li><li>You would need <strong>git </strong>command line installed and configured</li><li>The script use Tableau Server Client library in Python to interact with the Tableau Server REST API</li></ul><p>Ready to get started? Let me walk you through the steps:</p><ul><li>Clone the git from <a href="https://gitlab.com/brilliant-data/tableau-server-backup"><strong><em>here</em></strong></a></li><li>Once you cloned the files then open the <strong>README.md </strong>which will walk you through the configuration part</li><li>After the configuration is done then all you have to do is run the python script <strong>tableauBackup.py </strong>along with the required arguments</li><li>You can schedule the script to run periodically by utilizing the <strong>Windows Scheduler</strong> or <strong>crontab(1)</strong></li></ul><p>Tableau Server Client library allows us to makes this process possible with less than 100 lines of code. Using TSCL, we can login to Tableau server, iterate through all the sites, iterate through each workbook and data source within the site, download the .xml of each workbook and data source, and back them up to git.</p><p>Want me to pour some more technical juice to satisfy your hunger for how things work? Good. That means you are 1% of the people who will most likely to read past this, and I salute you sir.</p><p><em>Here is how the script works:</em></p><ul><li>First, we login to Tableau by using:</li></ul><pre>tableau_auth = TSC.TableauAuth(cfg[‘tableauServer’][‘user’], tableauPassword)<br>server = TSC.Server(cfg[‘tableauServer’][‘url’], use_server_version = True)<br></pre><pre>server.auth.sign_in(tableau_auth)</pre><p><em>tableau_auth — </em>setting up the user name and password and <em>cfg</em> is grabbing the user name from the <em>config.ini </em>file which you have setup during the README.md phase.</p><p><em>server — </em>setting up the url to login the server.</p><p><em>use_server_version — </em>to use the latest version of the REST API that is supported by the instance of the Tableau Server you are connecting to.</p><ul><li>Password is saved securely using the keyring:</li></ul><pre>if not keyring.get_password(service_id, cfg[‘tableauServer’][‘user’]):<br>      keyring.set_password(service_id, cfg[‘tableauServer’][‘user’],                           getpass.getpass(‘Enter Tableau Server Password For {}:    ‘.format(cfg[‘tableauServer’][‘user’])))</pre><p><em>keyring —</em> function allows you to not have to store your passwords directly in the source code. The keyring module provides a wrapper around your system’s password store. For example, OS X Keychain or the Windows Credential Vault. So you will never have to worry about forgetting to expunge secrets or leak passwords in your source code.</p><p><em>if —</em> statement searches for a password associated with the tableauServer user within the keyring. If none is found, you will be asked to input a password for the user from command line. you will only need to type the user password once as it is saved within the keyring, so any other time you run this script, it will automatically pull the password.</p><ul><li>Next we iterate through each site and set up sign in credentials:</li></ul><pre>remove_punctuation_map = dict((ord(char), None) for char in &#39;\/*?:&quot;&lt;&gt;|&#39;)</pre><pre>for site in TSC.Pager(server.sites):</pre><pre>     tableau_auth1 = TSC.TableauAuth(cfg[‘tableauServer’][‘user’], tableauPassword, site_id = site.content_url)</pre><pre>     server.auth.sign_in(tableau_auth1)</pre><pre>     sPath = os.path.join(oPath, site.name.translate(remove_punctuation_map))</pre><pre>     if os.path.isdir(sPath) is False:<br>          os.makedirs(sPath)</pre><p>After initially signing into the Tableau server from above this for loop iterates through each site within the Tableau server.</p><p><em>TSC.pager —</em> is used to get all the resources on Tableau server since the number of resources on Tableau Server can be very large, Tableau Server only returns the first 100 resources by default.</p><p><em>tableau_auth1 —</em> then sets up authentication to log into that specific site within the tableau server.</p><p><em>sPath — </em>sets up the directory for the site while <em>remove_punctuation_map </em>removes illegal characters</p><p><em>if —</em> statements checks if there is a folder/directory of that site and if not it will create a folder/directory with that site name</p><ul><li>Then the script will iterate through all the workbooks within that site:</li></ul><pre>req_option = TSC.RequestOptions()<br>req_option.filter.add(TSC.Filter(TSC.RequestOptions.Field.UpdatedAt,TSC.RequestOptions.Operator.GreaterThanOrEqual,downloadChangesSince))</pre><pre>for workbook in TSC.Pager(server.workbooks, req_option):</pre><pre>     workbookName = workbook.project_name.translate(remove_punctuation_map)</pre><pre>     xPath = os.path.join(sPath, workbookName)</pre><pre>     if os.path.isdir(xPath) is False:<br>          os.makedirs(xPath)</pre><pre>     file_path = server.workbooks.download(workbook.id, filepath = xPath, no_extract = True)</pre><pre>     extractWorkbook(file_path, site.name, workbookName, workbook.project_id, workbook.id, os.path.basename(file_path), xPath)</pre><p>First, we set up the filtering using <em>req_option</em> which enables us to filter based on the updated time of the workbook.</p><p><em>TSC.RequestOptions.Field.UpdatedAt —</em> grabs the last updated time of the workbook, and <em>TSC.RequestOptions.Operator.GreaterThanOrEqual </em>compares the <em>UpdatedAt</em> time with the <em>downloadChangesSince</em> time and ignores those workbooks that have <em>UpdateAt</em> time less than the <em>downloadChangesSince time</em>.</p><p>We define the <em>downloadChangesSince </em>like so:</p><pre>currentTime = datetime.now()</pre><pre>downloadChangesSince = (datetime.fromtimestamp((currentTime.timestamp() — args.incremental*3600)).replace(microsecond = 0)).isoformat() + ‘Z’</pre><pre>if args.full_load == True:<br>    downloadChangesSince = ‘2000–01–01T00:00:00Z’</pre><p>The time used in Tableau Server REST API is in ISO 8601 format. <em>args.incremental </em>and <em>args.full_load</em> is specified at the command line upon running this script.</p><p>Then we iterate through all the workbooks using the filtering <em>req_options </em>within the Tableau server site using the <em>TSC.Pager</em> function.</p><p>Up next, we check to see if there is a folder/directory for the project name associated with the workbook, by removing all illegal characters and checking if exists. If not, create a folder/directory with that project name.</p><p>Next, we download each workbook using <em>server.workbooks.download</em> by specifying the <em>workbook.id</em> which is the identifier for that workbook, filepath of where to download which is in its associated project folder.</p><p><em>no_extract</em> is to specify downloading only .xml files without the extracts.</p><p>Finally, we extract the workbook and rename the file so that it includes the workbook name as well as its workbook id.</p><ul><li>We repeat for downloading the data sources.</li><li>Then we back up to git if it detects any changes/updates for any workbooks or data sources.</li></ul><p>Since we have finished backing up all the workbooks and data sources in .xml format, now you would be able to view all the files and versions when you go to your git repository.</p><p>Thank you for going along the journey with me and if you have any questions then feel free to reach out to us at <strong>contact@starschema.com!</strong></p><p><em>by Chimed Altandush and Alan Tang.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80ecf5da1ce4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/starschema-blog/tableau-version-control-is-here-to-make-your-life-easier-80ecf5da1ce4">Tableau Version Control is here to make your life easier</a> was originally published in <a href="https://medium.com/starschema-blog">HCLTech-Starschema Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>