Westminster : medical insurance quotes

[BirminghamKn]

Кабринский Эдуард - Continuous monitoring devops - Eduard Kabrinskiy


<h1>Continuous monitoring devops</h1>
<p>[youtube]</p>
Continuous monitoring devops <a href="http://remmont.com">Top news today</a> Continuous monitoring devops
<h1>Continuous Testing in DevOps</h1>
<p><strong>What is Continuous Testing and Continuous Testing Pipeline in DevOps?</strong></p>
<p>Hope you all enjoyed the last tutorial on Continuous Deployment in DevOps.</p>
<p>We know the importance of testing in any software delivery and DevOps being short cycle of deliveries, it is impossible to run all the designed test cases each time manually, when a single line of code is updated in the version control tool and that is where continuous testing and automated continuous testing pipeline come into the picture in DevOps.</p>
<p style="clear: both"><img src="https://cdn.softwaretestinghelp.com/wp-content/qa/uploads/2019/11/Continuous-Testing-In-DevOps.png" /></p>
<p><strong>Benefits of CT:</strong></p>
<p><ul>
<li><ul>
<li>Quality and speed are the huge benefits of CT.</li>
<li>Faster and quicker feedback on the code.</li>
<li>Boosts the confidence of the team and encourages them to improve continuously.</li>
</ul>
</li>
</ul>
</p>
<p> <strong>VIDEO Part 3 Block 4: Continuous Testing – 14 minutes 39 seconds</strong></p>
<p><strong>Transcript:</strong></p>
<p><em>In this block, we will learn about <strong>Continuous testing and Continuous testing pipeline</strong> in detail.</em></p>
<p>Continuous testing is another important process of the continuous delivery pipeline along with Continuous Integration, in a pipeline, it includes, <strong>various testing phases</strong> wherein the automated tests are run along with the automated quality gates in between.</p>
<p>Thus, continuous testing is, executing automated tests, continuously and repeatedly against the code base and the various deployment environments.</p>
<p>Mainly, unit tests, static code analysis, security code analysis, integration tests, load and performance tests are part an of continuous testing which is run in an automated continuous testing pipeline.</p>
<p>As continuous integration and continuous deployment are called CI, CD, continuous testing is more often called as CT.</p>
<p>If you see this diagram, which is a continuous delivery pipeline, this pipeline includes two pipelines, one is a build pipeline which is CI pipeline or continuous integration pipeline, which consists of automated build trigger, compiling, building and deploying.</p>
<p>The other one is a Testing pipeline, which is a continuous testing pipeline</p>
<p><strong>Now let’s see more on continuous testing.</strong></p>
<p>We know the importance of testing, testing every line of code….. testing every time…and testing at different stages and it is almost impossible to run all of the designed tests each time manually when a line of code is updated into version control.</p>
<p>That’s where the continuous testing comes into the picture.</p>
<p>So, unless the code that gets into the automated continuous integrated pipeline, gets tested thoroughly and ensures the required quality, there is no use for releasing the software to the customers. I mean quality cannot be ensured unless the code is thoroughly tested.</p>
<p>So, continuous testing, as defined earlier is to execute various types of tests, continuously on the code base and on different environments that it gets deployed on to, as predefined and designed in the continuous delivery pipeline.</p>
<p>Like you see in the picture, unit tests happen on the CI server itself, which tests each unit of the system in isolation.</p>
<p>Integration tests happen on Integration environment which basically verifies the components integrated together. System tests in the system testing environment where the BIG system with all the integrated components and interfaces are tested through system-level scenarios in a system testing environment and so on.</p>
<p>And the depth of testing often progresses as the simulation of environment gets closer to production.</p>
<p>Continuous testing progressively becomes tougher and longer with the progression towards the production environment as we need to slowly add a number of tests and more complicated tests as the code matures and environment complexity advances.</p>
<p>It is not that the same test cases would be run throughout, the test cases need to be updated each time at different phases and automated scripts are updated, as the code becomes more matured, progresses to a higher level of environment where configurations and infrastructure also advance, till it gets into production.</p>
<p>So, even the time taken to run the tests increases as the testing progresses towards release point, like unit testing might take very less time to run whereas some integration tests or some system tests or load tests might take few long hours to run or might take few days to run.</p>
<p>Here the continuous testing would be mainly running the automated test cases automatically with a trigger. But as we defined earlier, continuous delivery also involves certain manual tests and gates, wherein certain tests are carried out manually, before pushing into production.</p>
<p>These intermediate quality gates at every stage of testing and increases the confidence in the code.</p>
<p>So, the continuous testing pipeline as such includes unit testing along with preliminary automated security verifications. Then gets into an integration level of testing, where automated integration tests are run, then on to a system level where system-level scenarios are automated and run.</p>
<p>Here even certain performance test scenarios are also carried out.</p>
<p>Then goes to the ‘Acceptance testing’ which basically includes the automated site acceptance test cases and then finally on to the ‘User Acceptance Testing’ which could be a manual execution and includes end-user participation to carry out the tests and a this will be a kind of final sign off on the product or a feature, where manual gate is invoked and finally deployed on to the production site.</p>
<p>So, basically, as continuous testing progresses, the complexity of tests and the test environment increases and gets to the environment which is closer to the production like simulation.</p>
<p>I need not specifically have to mention that all these test stages include build verification tests, sanity tests, smoke tests and regression tests as well, again as I said, it depends on what we design in the continuous testing and delivery pipeline.</p>
<p>This is the typical continuous testing pipeline, well it can be designed by the team based on the type of the product and the different levels of testing and types of testing that the product demands.</p>
<p>Continous testing requires integrating automation framework with the version control and CI tool and the various automated tools to carry out the functional and non-functional testing across different phases of testing, like:</p>
<p><ul>
<li><strong>Sonar for static code analysis,</strong></li>
<li><strong>Fortify for secure code analysis,</strong></li>
<li><strong>Selenium for functional testing,</strong></li>
<li><strong>Load runner for load testing etc.,</strong></li>
</ul>
</p>
<p>Microsoft TFS, Jenkins, chef, puppet are few tools that are available in the market to design the CI-CD pipeline.</p>
<p>But the thing is, these tools may not support the complete end to end automation, depending on the version control tool used, so few organizations may prefer to develop their own automation frameworks, which enables the end to end automation of the delivery pipeline from code commit to code delivery.</p>
<p>So, Continuous testing being a very crucial part of testing ensures the quality of the product or release and one should be very careful about selection of a tool, framework, etc., which primarily determines the quality and speed of delivery.</p>
<p>So set up of right continuous testing pipeline takes a bit more of time in the continuous delivery pipeline. Not just on the tool and framework part but also on the test cases part. Continuous testing also includes defining deployment pipeline within.</p>
<p>Because CT requires the automated deployment of the build on to various environments at different phases, which calls for automating the deployment and setting up the environments via automated scripts.</p>
<p>These automated scripts which include setting up infrastructure and environment configurations as a code are checked into version control tool and the Delivery pipeline picks it up from the version control tool to carry out the deployment. This is called the deployment pipeline.</p>
<p><strong>Now lets come to the benefits of CT,</strong></p>
<p>Achieving quality and speed is the biggest advantage of continuous testing.</p>
<p>Unlike earlier where testing used to happen only in the end, test throughout is the concept of continuous testing and hence the continuous testing in a delivery pipeline, allows the team to introduce quality gates anywhere and any number of quality gates, they want, in order to achieve the degree of quality that they need.</p>
<p>So, if at all, the code fails for testing at any particular point or gate in a pipeline, the team can go back and automatically fail the entire deployment up to that point.</p>
<p>This gives a clear indication to both the Dev and Ops team that something is missing there and the team can work upon to fix it. So, this is the advantage and flexibility of continuous testing pipeline.</p>
<p>So, the introduction of quality gates at various test phases governs the quality of the code better in the pipeline.</p>
<p>More the number of gates that the code passes, more will be the team’s confidence in the code that it can make it to the production at a higher level of quality.</p>
<p>So, continuous testing boosts the confidence of the team and encourages them to improve continuously.</p>
<p>Overall, if the team does not really neglect any of the test failures at any test phases or quality gates in the pipeline, definitely continuous testing will be a bonus towards achieving high-quality targets.</p>
<p>So to conclude on continuous testing, right from the unit tests that are run during the preliminary stage through the acceptance testing, performance testing and even certain manual tests that are going to be run are VERY VERY critical for defining continuous testing in the DevOps pipeline.</p>
<p><em>This completes our discussion on Part3 topics of continuous integration, continuous delivery, and continuous testing.</em></p>
<p><em><strong>In our upcoming tutorial, we will discuss more on</strong></em><em> <strong>Configuration management, release management, and application performance monitoring.</strong></em></p>
<h2>Continuous monitoring devops</h2>

<h3>Continuous monitoring devops</h3>
<p>[youtube]</p>
Continuous monitoring devops <a href="http://remmont.com">Latest current news</a> Continuous monitoring devops
<h4>Continuous monitoring devops</h4>
Continuous Testing in the DevOps pipeline - In this tutorial, we will learn about Continuous testing and Continuous testing pipeline in DevOps.
<h5>Continuous monitoring devops</h5>
Continuous monitoring devops <a href="http://remmont.com">Continuous monitoring devops</a> Continuous monitoring devops
SOURCE: <h6>Continuous monitoring devops</h6> <a href="https://dev-ops.engineer/">Continuous monitoring devops</a> Continuous monitoring devops
#tags#[replace: -,-Continuous monitoring devops] Continuous monitoring devops#tags#
Eduard Kabrinskiy
news today

[BirminghamKn]

Эдуард Кабринский - Sourcetree vsts - Kabrinskiy Eduard


<h1>Sourcetree vsts</h1>
<p>[youtube]</p>
Sourcetree vsts <a href="http://remmont.com">Latest news headlines today</a> Sourcetree vsts
<h1>Next up: Learn Sourcetree with Bitbucket</h1>
<p style="clear: both"><img src="https://sourcetreeapp.com/dam/jcr:1e84d84f-ce5e-45b6-b4c3-cc8247bbab9c/sourcetree_updated.png" /></p>
<h2>Step 1: Create a Git repository</h2>
<p>As our new Bitbucket space station administrator, you need to be organized. When you make files for your space station, you’ll want to keep them in one place and shareable with teammates, no matter where they are in the universe. With Bitbucket, that means adding everything to a repository. Let’s create one!</p>
<h3>Step 1: Create the repository</h3>
<p>Initially, the repository you create in Bitbucket is going to be empty without any code in it. That's okay because you will start adding some files to it soon. This Bitbucket repository will be the central repository for your files, which means that others can access that repository if you give them permission. You will also copy a version of that repository to your local system—that way you can update it from one repo, then transfer those changes to the other.</p>
<p style="clear: both"><img src="https://sourcetreeapp.com/dam/jcr:96af1ca2-3717-4fcf-bb99-f20143e98d1c/git-tutorial-basics-clone-repotorepocollaboration.png" /></p>
<p>Do the following to create your repository:</p>
<p style="clear: both"><ol>
From Bitbucket, click the + icon in the global sidebar and select <strong>Repository</strong>. Bitbucket displays the <strong>Create a new repository</strong> page. Take some time to review the dialog's contents. With the exception of the <strong>Repository type</strong>, everything you enter on this page you can later change. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:b2f5ac71-2847-495d-829e-a7600c82538f/create_new_repo3.png" /></ol></p>
<p>Enter BitbucketStationSupplies for the <strong>Name</strong> field. Bitbucket uses this <strong>Name</strong> in the URL of the repository. For example, if the user the_best has a repository called awesome_repo , the URL for that repository would be https://bitbucket.org/the_best/awesome_repo .</p>
<p>Keep the rest of the options as is unless you want to change them:</p>
<p><strong>Access level</strong> —Leave the <strong>This is a private repository</strong> box checked. A private repository is only visible to you and those with access. If this box is unchecked, anyone can see your repository.</p>
<p><strong>Include a README?</strong> —If you recently created your account, this defaults to a tutorial README. For the purposes of this tutorial, pick either of the <strong>Yes</strong> options, that way you'll start out with a file.</p>
<p>From <strong>Version control system</strong>, you can choose either <strong>Git</strong> or <strong>Mercurial</strong>. If you aren't sure which one to go with, keep <strong>Git</strong> as your option.</p>
<p>Click <strong>Create repository</strong>. Bitbucket creates your repository and displays its <strong>Source</strong> page.</p>
<h3>Step 2: Explore your new repository</h3>
<p>Take some time to explore the repository you have just created. To view the shortcuts available, press the <strong>?</strong> key on your keyboard.</p>
<p>Click <strong>+</strong> from the global sidebar for common actions for a repository. Scan through the links in the navigation sidebar to see what's behind each one, including the repository <strong>Settings</strong> where you'll update repository details and other settings. Click the <strong>Commits</strong> in the sidebar. If you included a README, you'll see one commit on that page.</p>
<p>Your repository is private and you have not invited anyone to the repository, so the only person who can create or edit the repository's content right now is you, the repository owner.</p>
<p style="clear: both"><img src="https://sourcetreeapp.com/dam/jcr:4ae0607f-6a58-4219-87fa-afb452fcf80f/explore_repository_git.gif" /></p>
<h2>Step 2: Copy your repository and add files</h2>
<p>Now that you have a place to add and share your space station files, you need a way to get to it from your local system. To set that up, you want to copy the Bitbucket repository to your system. Sourcetree refers to copying a repository as "cloning" it. When you clone a repository, you create a connection between the Bitbucket server and your local system.</p>
<p style="clear: both"><img src="https://sourcetreeapp.com/dam/jcr:b722211f-4b39-4c28-a9dd-9bed68a932ab/git-tutorial-basics-clone.png" /></p>
<h3>Step 1: Clone your repository to your local system</h3>
<p>Use Sourcetree to clone your repository to your local system without using the command line.</p>
<p><ol>
As you use Bitbucket more, you will probably work in multiple repositories. For that reason, it's a good idea to create a directory to contain all those repositories. So start by creating a directory on your local system and call it repos. </ol></p>
<p>From Bitbucket, go to your <strong>BitbucketStationSupplies</strong> repository.</p>
<p style="clear: both">Click the Clone button in the top right corner. Bitbucket displays the Clone this repository dialog. <img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:6fbea734-6103-4f8c-b407-1695a1d0f7ae/st_clone_an.gif" /></p>
<p>From the <strong>Clone this repository</strong> dialog, click <strong>Clone in Sourcetree</strong>.</p>
<p style="clear: both">From the <strong>Clone New</strong> dialog box, update the <strong>Destination Path</strong> to /repos/bitbucketstationsupplies . This destination path refers to the directory you just created with the folder for the repository. The <strong>Name</strong> field remains the same with the folder name of the repository. <img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:60e77b0a-a596-4936-9b83-be17c939d099/git_clone_st.png" /></p>
<p>Click the <strong>Clone</strong> button.</p>
<p>Congratulations! You've cloned your repository to your local system.</p>
<h3>Step 2: Create a file, add it locally, and push it to Bitbucket</h3>
<p>With the repository on your local system, you can start making a list of all the supplies you need for your space station. To do so, let's create a file for your supplies.</p>
<p>As you work on this section, the images may look slightly different, depending on whether you are working with a Git or Mercurial repository.</p>
<p style="clear: both">Double-click the bitbucketstationsupplies repository in Sourcetree and notice that there is nothing to commit from your local repository to the remote repository. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:7a1c8156-2cd7-44d5-859d-07e3d949b087/sourcetree_nothing.png" /></p>
<p>Use a text editor to add the following three lines: <br />space ice <br />cream nerf <br />darts telescope light shield</p>
<p style="clear: both">Save the file as supplies.txt to the bitbucketstationsupplies directory on your local system. The supplies.txt file now appears in Sourcetree since you created it in your local repository. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:2fa5b712-00a2-41cf-91cf-3e40be908ecc/sourcetree_added.png" /></p>
<p style="clear: both">Now is the point where you prepare a snapshot of the changes before committing them to the official history. From the options menu of the supplies.txt file, select <strong>Stage file</strong> (for a Git repository) or <strong>Add file</strong> (for a Mercurial repository). <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:47d850ec-c7f1-46a2-99f6-7796b1987aa5/files_stage_git.png" /> <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:31244996-001b-486c-b1bb-aa0c350f8a35/files_add_mer.png" /></p>
<p>Click the <strong>Commit</strong> button at the top to commit the file.</p>
<p style="clear: both">In the message box, enter "Initial commit." <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:87719c1b-18af-48af-a6d0-ddacddaded66/sourcetree_message.png" /></p>
<p style="clear: both">Click the <strong>Commit</strong> button under the box. Your new file is now committed to the project history. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:4ee697e7-42ac-42e7-b1ae-69b01c1e4f5d/sourcetree_committed.png" /> <br />Up until this point, everything you have done is on your local system and is invisible to your Bitbucket repository until you push those changes to your remote Bitbucket repository.</p>
<p style="clear: both">From Sourcetree, click the <strong>Push</strong> button to push your committed changes. Pushing lets you move one or more commits to another repository, which serves as a convenient way to publish contributions. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:cdaa95aa-909e-43eb-a612-bedf7427e82b/git_st_push.png" /></p>
<p>From the dialog box that appears, your next step depends on whether you are using Git or Mercurial:</p>
<p style="clear: both">Git–Under the <strong>Push?</strong> column, select the master branch to indicate that you are pushing that branch to origin and click <strong>OK</strong>. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:989227e7-1299-4ebb-b601-a43dce7e0ed9/git_st_pushto.png" /></p>
<p>Mercurial–Everything is automatic, so all you have to do is click <strong>OK</strong>.</p>
<p>Go to your <strong>BitbucketStationSupplies</strong> repository in Bitbucket.</p>
<p>If you click <strong>Commits</strong> in the sidebar, you'll see your commit in the repository. Bitbucket combines all the things you just did into that commit and shows it to you.</p>
<p style="clear: both">If you click <strong>Source</strong> in the sidebar, you'll see your file in the repository, the supplies.txt file you just added. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:2b68098a-f4af-4100-b60a-5680f2fab7c7/st_commits_source.gif" /></p>
<h2>Step 3: Pull changes from your repository</h2>
<p>Next on your list of space station administrator activities, you need to file out a request for new supplies. Let's set up a system for getting supplies to our Bitbucket space station. With just a bit more knowledge of Bitbucket and Sourcetree, we'll be supporting our space exploration for years to come!</p>
<h3>Step 1: Create a file in Bitbucket</h3>
<p>To add your supply request file, do the following:</p>
<p style="clear: both">From your <strong>BitbucketStationSupplies</strong> in Bitbucket, click <strong>Source</strong> to open the source directory. Notice you only have one file, supplies.txt , in your directory. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:36eff552-f752-4e01-ae50-bb945f7078bf/git+source+page+image.png" /></p>
<p><strong>A. Source page:</strong> Click the link to open this page.</p>
<p><strong>B. Branch selection:</strong> Pick the branch you want to view.</p>
<p><strong>C. More options button:</strong> Click to open a menu with more options, such as 'Add file'.</p>
<p><strong>D. Source file area:</strong> View the directory of files in Bitbucket.</p>
<p style="clear: both">From the <strong>Source</strong> page, click the <strong>More options</strong> button in the top right corner and select <strong>Add file</strong> from the menu. The <strong>More options</strong> button only appears after you have added at least one file to the repository. A page for creating the new file opens, as shown in the following image. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:45ecea9e-964d-47c3-8277-78ed718b75b3/mer_new_file_st.png" /></p>
<p><strong>A. Branch with new file:</strong> Change if you want to add file to a different branch.</p>
<p><strong>B. New file area:</strong> Add content for your new file here.</p>
<p>Enter supplyrequest in the <strong>filename</strong> field.</p>
<p>Select <strong>HTML</strong> from the <strong>Syntax mode</strong> list.</p>
<p>Add the following HTML code to the text area:</p>
<p>We are requesting additional supplies. Please send us the following:</p>
<p>Click <strong>Commit</strong>. The <strong>Commit message</strong> field appears with the message: supplyrequest created online with Bitbucket.</p>
<p>Click <strong>Commit</strong> under the message field.</p>
<p>You now have a new file in Bitbucket! You are taken to a page with details of the commit, where you can see the change you just made:</p>
<p style="clear: both"><img src="https://sourcetreeapp.com/dam/jcr:4b9a9b58-e923-4db7-9df2-32ee071c0b2e/git_new_file_committed.png" /></p>
<p>If you want to see a list of the commits you've made so far, click <strong>Commits</strong> in the sidebar.</p>
<h3>Step 2: Pull changes from a remote repository</h3>
<p>Now we need to get that supply request form onto your local system. The process is pretty straight forward, basically just the reverse of the push you used to get the supplies.txt file into Bitbucket.</p>
<p>To pull the file into your local repository, do the following:</p>
<p style="clear: both">Open your repository in Sourcetree, and click the <strong>Pull</strong> button. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:9a1e7bbe-4963-4f45-bd37-20274e92d15e/git_st_push-1.png" /> <br />A popup appears to indicate that you are merging the file from Bitbucket to your local repository. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:083cddee-16ba-4b29-b4e8-81e369417bca/hg-tutorial-basics-clone.png" /></p>
<p style="clear: both">Click <strong>OK</strong> from this box. Sourcetree updates with a description of the merged file. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:57fd5d3a-0d22-42b3-9d91-083506a5fcc1/git_postpull_st.png" /></p>
<p>Navigate to your repository folder on your local system and you'll see the file you just added.</p>
<p>Fantastic! Now, you have finished the basic DVCS workflow (clone, add, commit, push, and pull) between Bitbucket and your local system.</p>
<h2>Step 4: Use Sourcetree branches to merge an update</h2>
<p>After looking through the Intergalactic Mall Magazine, you see a pair of speakers that you really want for the space station. They are big enough to produce a good amount of sound and soft enough that the lack of gravity won't cause them to crash. The only problem is that they pretty pricey, and you need approval before you can officially add them to your list of supplies.</p>
<p>In the meantime, create a feature branch so that you can update the supply to your request list while you wait. Then when you have approval, you just merge the requests file from the feature branch into the main branch.</p>
<p>Branches are most powerful when you're working on a team. You can work on your own part of a project from your own branch, pull updates from Bitbucket, and then merge all your work into the main branch when it's ready. Our documentation includes more explanation of why you would want to use branches.</p>
<h3>Step 1: Create a branch and make a change</h3>
<p>Let's create a branch so that you can list the speakers in your supply requests file. Even though branches work differently between Git and Mercurial, you create them in a similar way from Sourcetree.</p>
<p style="clear: both"><ol>
<li>From Sourcetree, click the <strong>Branch</strong> button. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:f023d45b-d987-470e-870d-e02b80b04eed/git_st_push-3.png" /></li>
<li>Depending on whether you have a Git or Mercurial repository, you see a different popup for creating a new branch. From the <strong>New Branch</strong> or <strong>Create a new branch</strong> field, enter wish-list for the name of your branch. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:e3d4635f-e3f9-4f14-bfe8-81094cc99674/git_st_create_branches.png" /><br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:e20616eb-06b9-49fc-8e63-c7d39d55871c/mer_st_create_branches.png" /></ol></p>
<p>Click <strong>Create Branch</strong> or <strong>OK</strong>.</p>
<p style="clear: both">From Sourcetree, click the <strong>Show in Finder</strong> button. The directory on your system opens.<img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:be86396c-9793-4394-b083-9aa233550e4c/sourcetree_finder_git.png" /></p>
<p>From the directory folder, open the supplyrequest file with a text editor.</p>
<p>Making a change to the file by adding the following item to the list of supplies: <br />
anti-gravity speakers </p>
<p style="clear: both">Open the view in Sourcetree and notice that your repository now has uncommitted changes. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:19742546-28fd-424b-9c21-3e9d110000cc/sourcetree_updated-1.png" /> <br />From here, everything you do is the same as you did when you added the supplyrequest file and initially committed it.</p>
<p style="clear: both">If you have a Git repository, make supplyrequest.txt ready to commit by selecting <strong>Stage file</strong> from the options menu. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:99d5dddc-1c4f-4272-b587-045278ad162c/files_stage_git2.png" /></p>
<p>Click the <strong>Commit</strong> button at the top to commit the file.</p>
<p>In the message box, enter "Adding an item for my wish list."</p>
<p style="clear: both">Click the <strong>Commit</strong> button under the box. From Sourcetree, you see that the file has been updated on the wish-list branch. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:22bd8176-5c8c-4452-b737-f8eaf9052d35/sourcetree_othercommit.png" /></p>
<h3>Step 2: Merge file changes from a branch</h3>
<p>Your speakers were approved! Now it's time to update the main supply list with your wish-list item.</p>
<ol>
<li>First, you want to switch back to the main branch. From the left-side menu items in Sourcetree, hover your mouse over the right side of the <strong>Branches</strong> label so that the word <strong>Show</strong> appears. <br /><img src="https://sourcetreeapp.com/dam/jcr:c7ad127f-60e2-47a6-bd7a-a3aa286fa40f/show_branches-1.png" /></li>
<li>When <strong>Show</strong> appears, click it. Under the Branches heading, you will see the two branches for this repository, the main branch, and the wish-list branch. The main branch for a Git repository is called master . The main branch for a Mercurial repository is called default . <br /><img src="https://sourcetreeapp.com/dam/jcr:fa1e2757-484a-4042-9bff-0b39339b7641/branches_list.png" /></ol>
<p>Double-click the feature branch (in this case wish-list ) to switch to that branch.</p>
<p style="clear: both">Click the <strong>Merge</strong> button. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:252cf048-2fd2-4beb-8056-7b42c96c7379/git_st_push-4.png" /></p>
<p style="clear: both">From the popup that appears, make sure the commit on your wish-list branch is highlighted. You are indicating that you want to add the commit from this branch to the main branch. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:681b31b1-c798-4ea9-b8e9-5781f1ba5e6b/git_st_merging.png" /></p>
<p style="clear: both">If you have a Git repository, check this option at the bottom: <strong>Create a commit even if merge resolved via fast-forward. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:bf465778-28a0-4cf4-8f09-ef9ee7b097d6/st_merge_checkbox.png" /></strong></p>
<p style="clear: both">Click <strong>OK</strong>. You have updated the supplyrequest file in your main branch with your wish-list item. Sourcetree will look slightly different based on whether you have a Git or Mercurial repository. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:a44a2a5b-4916-4aa1-8da2-bab679fe91b0/mer_st_main_branch.png" /></p>
<p>If you have a Git repository, you are done. If you have a Mercurial repository, you will notice that you need to commit your changes. Click the <strong>Commit</strong> button at the top. The commit message defaults to a description with "Merge." Keep this message and go ahead and click <strong>Commit</strong>.</p>
<h3>Step 3: Push your change to Bitbucket</h3>
<p>From Sourcetree, click the <strong>Push</strong> button to push your committed changes.</p>
<p>From the dialog box that appears, click the <strong>OK</strong> button to push changes to your local repository.</p>
<p>Click the <strong>Overview</strong> page of your Bitbucket repository, and notice you can see your push in the <strong>Recent Activity</strong> stream.</p>
<p style="clear: both">Click <strong>Commits</strong> and you can see the commit you made on your local system. Notice that the change keeps the same commit code that it had on your local system. <br /><img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:9653a356-d264-4156-8696-384a794a1758/git_commitspush_st.png" /></p>
<p>Click <strong>Source</strong>, then click the supplyrequest file. You can see the last change to the file has the commit code you just pushed.</p>
<p style="clear: both">Click the file history list to see the committed changes for this file, as shown in the following image.<img style="float: left; margin: 0 10px 5px 0;" src="https://sourcetreeapp.com/dam/jcr:d6f6b375-cee6-43a4-ad6a-a28af61d84b7/git_sourcehistory_st.png" /></p>
<h2>You are done!</h2>
<p>That was intense! Maybe. Depends on how it compares to launching into space. Now that you know a lot more about Bitbucket, you are now prepared to run your space station's activities a lot better. Now, take a break and go do some star gazing.</p>
<p>Want to learn more about Bitbucket and Sourcetree? You can take on the challenge of updating a teammate's repository.</p>
<h2>Sourcetree vsts</h2>

<h3>Sourcetree vsts</h3>
<p>[youtube]</p>
Sourcetree vsts <a href="http://remmont.com">Latest national news in english</a> Sourcetree vsts
<h4>Sourcetree vsts</h4>
A Git GUI that offers a visual representation of your repositories. Sourcetree is a free Git client for Windows and Mac.
<h5>Sourcetree vsts</h5>
Sourcetree vsts <a href="http://remmont.com">Sourcetree vsts</a> Sourcetree vsts
SOURCE: <h6>Sourcetree vsts</h6> <a href="https://dev-ops.engineer/">Sourcetree vsts</a> Sourcetree vsts
#tags#[replace: -,-Sourcetree vsts] Sourcetree vsts#tags#
Эдуард Кабринский
new

[BirminghamKn]

Eduard Kabrinskiy - Azure devops repository permissions - Кабринский Эдуард


<h1>Azure devops repository permissions</h1>
<p>[youtube]</p>
Azure devops repository permissions <a href="http://remmont.com">News sites</a> Azure devops repository permissions
<h1>Azure Repos</h1>
<p>Get unlimited, cloud-hosted private Git repos for your project</p>
<h2>Free private Git repositories, pull requests, and code search</h2>
<p>Get unlimited private Git repository hosting and support for TFVC that scales from a hobby project to the world?s largest repository.</p>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/page/services/devops/repos/screenshot.jpg" /></p>
<h2>Support for any Git client</h2>
<p>Securely connect with and push code into your Git repos from any IDE, editor, or Git client.</p>
<h2>Web hooks and API integration</h2>
<p>Add validations and extensions from the marketplace or build your own using web hooks and REST APIs.</p>
<h2>Semantic code search</h2>
<p>Quickly find what you?re looking for with code-aware search that understands classes and variables.</p>
<h2>Kick off your next build from a Repos pull request</h2>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/page/services/devops/repos/collaborate.jpg" /></p>
<h3>Collaborate to build better code</h3>
<p>Perform more effective Git code reviews with threaded discussion and continuous integration for each change. Use forks to promote collaboration with inner source workflows.</p>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/page/services/devops/repos/automate.jpg" /></p>
<h3>Automate with built-in CI/CD</h3>
<p>Set up continuous integration/continuous delivery (CI/CD) to automatically trigger builds, tests, and deployments with every completed pull request using Azure Pipelines or your tools.</p>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/page/services/devops/repos/code-quality.jpg" /></p>
<h3>Protect your code quality with branch policies</h3>
<p>Keep code quality high by requiring code reviewer signoff, successful builds, and passing tests before pull requests can be merged. Customize your branch policies to maintain your team?s high standards.</p>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/page/services/devops/repos/integrations.jpg" /></p>
<h3>Use with your favorite tools</h3>
<p>Use Git and TFVC repositories on Azure Repos with your favorite editor and IDE.</p>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/shared/customers/cargill.png" /></p>
<blockquote><p>We can bring new products to market more quickly now that we use Azure DevOps.</blockquote></p>
<p>Cal Dornbush, Visual Studio Team Services Application Architect</p> </blockquote>
<h2>The DevOps Journey at Microsoft</h2>
<p>The road to DevOps adoption is not easy and at Microsoft we believe that the best way to navigate this challenging path is by following the footsteps of those who have already walked it. Explore the challenges and learnings of teams across Microsoft as they adopted a DevOps culture.</p>
<h2>Azure devops repository permissions</h2>

<h3>Azure devops repository permissions</h3>
<p>[youtube]</p>
Azure devops repository permissions <a href="http://remmont.com">Daily news</a> Azure devops repository permissions
<h4>Azure devops repository permissions</h4>
Get free private Git repositories and code collaboration in the cloud. Create Git pull requests and review code with Azure Repos, formerly on Visual Studio Team Services.
<h5>Azure devops repository permissions</h5>
Azure devops repository permissions <a href="http://remmont.com">Azure devops repository permissions</a> Azure devops repository permissions
SOURCE: <h6>Azure devops repository permissions</h6> <a href="https://dev-ops.engineer/">Azure devops repository permissions</a> Azure devops repository permissions
#tags#[replace: -,-Azure devops repository permissions] Azure devops repository permissions#tags#
Кабринский Эдуард
headline news

[BirminghamKn]

Eduard Kabrinskiy - Devops for salesforce - Эдуард Кабринский


<h1>Devops for salesforce</h1>
<p>[youtube]</p>
Devops for salesforce <a href="http://remmont.com">Top news</a> Devops for salesforce
<h1> Ivan's Tech blog </h1>
<p>Salesforce.com and all things Tech related. Specialising in technology architecture, cloud computing and DevOps. All views are my own. Twitter @ivanesalmeida</p>
<h3>Salesforce and DevOps Part 1 - My views</h3>
<ul>
<li>Get link</li>
<li>Facebook</li>
<li>Twitter</li>
<li>Pinterest</li>
<li>Email</li>
<li>Other Apps</li>
</ul>
<p>To get my blog up and running, I thought I'd start with a series regarding my current preferred topic: Salesforce and DevOps.</p>
<p>Let's start with a couple of conversation topics (bear with me if you know them already, comment if you don't agree, feel free!):</p>
<p style="clear: both"><img src="https://2.bp.blogspot.com/-_HwwjK_vSJw/W1sjEDYhqoI/AAAAAAAAyN8/4-zw0jk29scXRRHhnBu3BmNLpwJQZsxlQCLcBGAs/s320/Devops.svg.png" /></p>
<p style="clear: both"><img src="https://1.bp.blogspot.com/-zWzmDM59RgM/W1sjTqNpP9I/AAAAAAAAyOA/whK0hSIyC7g-L5-7ZGpZ23rNYUmlMHsGwCLcBGAs/s320/collaboration-illustration.jpg" /></p>
<p style="clear: both"><img src="https://3.bp.blogspot.com/-H9bpvXZwGRI/W1sjdIWJh_I/AAAAAAAAyOI/yyXlFbQZpn49Fud9U6f03mpPVtz9jC76ACLcBGAs/s1600/culture.png" /></p>
<ul>
<li>Salesforce being so "easy" to configure and customise with clicks and not code make people think that there's no need for what they see as convoluted processes. Have you encountered the question: Why should I do that when I can just do it straight there? Why do I need to pay for all that?</li>
<li>Thinking it's OK to just go and change things in production directly, because you can, without traceability</li>
<li>Historical lack of technical support and tools by Salesforce themselves. Things seem to be changing with SFDX, but it's still in the early stages</li>
<li>Salesforce, being multi-tenanted and proprietary technology, has to create their own ways for customising the client orgs, for which they started the metadata API long ago. I don't know for sure how many years they've been working on that, but it's interesting that there are still so many things that are not supported by it, making it complicated to automate all kinds of development at all times. They seem to be working on that as well, we'll see how fast and reliable that is. I'm optimistic, though, don't get me wrong</li>
<li>People working hands-on with Salesforce technologies, in my experience, have been divided into 3 groups: functional (BAs, configurators, admins, consultants and so on), technical (developers, architects and such) and testers (QA, functional testing, automated testing experts, for example). For the most part, DevOps has been driven by the technical group so far, and highly seen as obscure technical stuff and "coding" by others. This is mainly due to lack of knowledge, and technical people not being the best at sharing it and making it clear for everyone (I've been known to be guilty of that, sorry to say, but I'm working on it!)</li>
<li>For the reasons above, and others I'm not getting into, it's been historically hard to sell the implementation of DevOps. As it's not widely adopted, it's seen as expense that is not worth the trouble</li>
<li>Salesforce implementations don't always have the people it takes to lead a project with a DevOps culture, and these people are highly in demand, and are super expensive as well, which also makes it a hard sell sometimes</li>
</ul>
<p>After writing that list, things seem to be very bleak, but that's really not the case, as most of those are changing!</p>
<h2>Devops for salesforce</h2>

<h3>Devops for salesforce</h3>
<p>[youtube]</p>
Devops for salesforce <a href="http://remmont.com">News stories</a> Devops for salesforce
<h4>Devops for salesforce</h4>
Ivan's Tech blog Salesforce.com and all things Tech related. Specialising in technology architecture, cloud computing and DevOps. All views are my own. Twitter @ivanesalmeida Salesforce and
<h5>Devops for salesforce</h5>
Devops for salesforce <a href="http://remmont.com">Devops for salesforce</a> Devops for salesforce
SOURCE: <h6>Devops for salesforce</h6> <a href="https://dev-ops.engineer/">Devops for salesforce</a> Devops for salesforce
#tags#[replace: -,-Devops for salesforce] Devops for salesforce#tags#
Eduard Kabrinskiy
news headlines

[BirminghamKn]

Кабринский Эдуард - Devops 101 - Кабринский Эдуард


<h1>Devops 101</h1>
<p>[youtube]</p>
Devops 101 <a href="http://remmont.com">News headlines of the day</a> Devops 101
<h1>DevOps 101: What is a DevOps Platform?</h1>
<p style="clear: both"><img src="https://blog.xebialabs.com/wp-content/uploads/2018/10/devops-platform-1024x555.jpg" /></p>
<p>We?re excited to reveal an updated and vastly expanded edition of our popular <em>The Manager?s Guide to Continuous Delivery</em>, now called <em>The IT Manager?s Guide to DevOps: How to Drive the Business Value of Software Delivery</em>. To celebrate the new version, we?re using the XebiaLabs blog this week to highlight some of the new insights and advice coming your way from co-author, Tim Buntel. The following excerpt looks at how a DevOps platform supports the 5 stages of Continuous Delivery. You can download an advance copy of the complete ebook <strong>here.</strong></p>
<p>Note: Those attending the 2018 DevOps Enterprise Summit in Las Vegas will get the print version of the advance copy of the book. You can register for the event here and use the promo code <strong>XEBIALABS20</strong>.</p>
<h2>Introduction to a DevOps Platform</h2>
<p>In a DevOps organization, Continuous Delivery (CD) is used to create a constant flow of changes to production. The entire automated software production line is commonly referred to as the Continuous Delivery pipeline. The CD pipeline breaks the software delivery process into several stages, each of which verifies the quality of new features before moving them to the next stage until they finally are available to users. The pipeline provides feedback to the team and visibility into the flow of changes to everyone involved. To successfully scale DevOps in an enterprise, a set of components are leveraged to help teams achieve CD. This is called a DevOps platform.</p>
<p>While there may be slight variations from organization to organization, or within the type of software project, a typical DevOps platform facilitates CD through the following stages:</p>
<h2>1. The Initial Stages: Build Automation and Continuous Integration</h2>
<p>New features that the developers implement start their journey through the CD pipeline as code commits to a central code repository. The pipeline starts by building the binaries to create the deliverable(s) that are passed to the subsequent stages. Each developer?s code commits are integrated into the central code base on a continuous basis where they are built and unit tested. This is called Continuous Integration. It provides an early opportunity for feedback about the ?health? of the new application code. If something is wrong, the build will ?break,? and the cause is clearly identified.</p>
<p>The developer who introduced the problem code can commit a fix, and everyone can see the build ?go green? as it passes the phase.</p>
<p>Common tools you may hear mentioned:</p>
<h2>2. The Verification Stages: Test Automation</h2>
<p>The earlier problems are detected, the easier (and cheaper) it is to fix them. It is important that the pipeline verifies all relevant aspects?whether user functionality, security, performance, or compliance. Manual testing can identify some problems, but it is time consuming, costly, and error prone. High-performing DevOps teams use a combination of manual and automated testing to ensure an increasingly well-tested application as it moves through the pipeline.</p>
<p>Common tools you may hear mentioned:</p>
<blockquote><p style="clear: both"><img style="float: left; margin: 0 10px 5px 0;" src="http://xebialabsblog.wpengine.com/wp-content/uploads/2018/10/it-managers-guide.png" /><strong>FREE EBOOK</strong></blockquote></p>
<p>Whether you?re brand new to DevOps or looking to scale, this book helps you create a high-performing organization that drives business value up and time to market down. <strong>Read more.</strong></p></blockquote>
<h2>3. The Rollout Stage: Deployment Automation</h2>
<p>The final stage of the pipeline is deployment to production. Since the preceding stages have verified the overall quality of the system, this is a low-risk step. The deployment can be staged, with the new version initially released to a subset of the production environment and monitored before the complete roll out. Deployment is automated, allowing for reliable delivery of new functionality to users within minutes.</p>
<p>Common tools you may hear mentioned:</p>
<h2>4. The Live Stage: Operating, Monitoring, and the Feedback Loop</h2>
<p>The image of a pipeline is somewhat misleading since it implies a distinct end. In a DevOps platform, things that happen after the application is deployed to production provide feedback so that the entire cycle can begin again with fixes to problems, enhancements, or ideas for new features. So it?s really more of a loop than a pipeline.</p>
<p>At this stage, the DevOps platform is concerned with ensuring that users have a good experience. This means making sure the application is stable and fast, and that it?s being used in a way that adds value for the user. There are many tools to help with this. Some monitor running applications to alert and take action when a problem arises, some automate the process of scaling application instances up and down and reacting if instances become unavailable, and some provide a way to observe and interact with users while they are using the application.</p>
<p>Common tools you may hear mentioned:</p>
<h2>5. Orchestrating It All: Release Coordination and Automation</h2>
<p>Cross-functional DevOps teams include many participants in every stage of the pipeline, each with many tasks (both automated and manual) to be performed. Keeping track of it all can be challenging. Release coordination provides a top-level view of the entire pipeline. It defines the overall software delivery process and puts appropriate controls in place for each stage. This analysis highlights any inefficiencies or hot spots that can be improved. Tools can help identify bottlenecks, reduce errors, and lower the risk of release failures. You may hear such tools referred to as Application Release Automation, Application Release Orchestration, or Continuous Delivery Release Automation.</p>
<h2>Devops 101</h2>

<h3>Devops 101</h3>
<p>[youtube]</p>
Devops 101 <a href="http://remmont.com">Latestnews</a> Devops 101
<h4>Devops 101</h4>
A DevOps platform gives teams the intelligence, automation, and control necessary to perform DevOps at enterprise scale.
<h5>Devops 101</h5>
Devops 101 <a href="http://remmont.com">Devops 101</a> Devops 101
SOURCE: <h6>Devops 101</h6> <a href="https://dev-ops.engineer/">Devops 101</a> Devops 101
#tags#[replace: -,-Devops 101] Devops 101#tags#
Eduard Kabrinskiy
daily news

[BirminghamKn]

Кабринский Эдуард - Powerapps azure devops - Eduard Kabrinskiy


<h1>Powerapps azure devops</h1>
<p>[youtube]</p>
Powerapps azure devops <a href="http://remmont.com">Latest news online</a> Powerapps azure devops
<h1>PowerApps BuildTools for Azure DevOps</h1>
<p>For quite a long time I have been trying to automate the deployment of PowerApps solution/app. PowerApps build tools is still in <strong><strong>Preview</strong></strong> but this collection of Azure DevOps build tasks will help you eliminate all the manual intervention that is currently needed to manage the lifecycle of your application.</p>
<p>Normally, you would manually export your zip file from your development environment and import it into your production environment. You can now automate these tasks using Azure DevOps. To make use of these buildtools tasks you must install the extension from the Visual Studio market place into your Azure DevOps instance</p>
<p>This is an example of a very simple Build pipeline that publishes your zip file as artefact for deployment</p>
<p style="clear: both"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5tcz03c4--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/z41juybamk0qiu368mwf.png" /></p>
<p>Then, you can use these two PowerApps DevOps tasks in a Release pipeline to deploy to an environment</p>
<p style="clear: both"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--L3lJgsCb--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/gsq1nwq84rjtdeqbybz7.png" /></p>
<p>But that's not it. You can also automate the export of the zip file with this task</p>
<p style="clear: both"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--o-Uvmzgk--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/dxza99xcjzwlmkohgbtn.png" /></p>
<p>And you can take it even further, we know zip files are hard to track changes, so you can source control the contents of the zip files by using the unpack task</p>
<p style="clear: both"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--RFJKypIf--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/dyzd5ifus9jb24ibmmjm.png" /></p>
<p>This set of DevOps tasks will definitely help you manage the lifecycle of your PowerApps going forward, there are also tasks to automate common environment management functions that you can use.</p>
<p>If like me, you also like to get ahead of the game, go start automating your apps now </p>
<h2>Powerapps azure devops</h2>

<h3>Powerapps azure devops</h3>
<p>[youtube]</p>
Powerapps azure devops <a href="http://remmont.com">Latest news update</a> Powerapps azure devops
<h4>Powerapps azure devops</h4>
For quite a long time I have been trying to automate the deployment of PowerApps solution/app. PowerA... Tagged with powerapps, devops, deployment, azure.
<h5>Powerapps azure devops</h5>
Powerapps azure devops <a href="http://remmont.com">Powerapps azure devops</a> Powerapps azure devops
SOURCE: <h6>Powerapps azure devops</h6> <a href="https://dev-ops.engineer/">Powerapps azure devops</a> Powerapps azure devops
#tags#[replace: -,-Powerapps azure devops] Powerapps azure devops#tags#
Кабринский Эдуард
top news

[BurbankSige]

Кабринский Эдуард - Vsts build - Eduard Kabrinskiy


<h1>Vsts build</h1>
<p>[youtube]</p>
Vsts build <a href="http://remmont.com">News today</a> Vsts build
<h1>Articles</h1>
<p>If you have migrated over to VSTS (or TFS 2017) from TeamCity, you may have a noticed a useful feature missing.</p>
<p>Now VSTS defaults the build number format to a revision number in the format similar to as shown below. <br /></p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-30_09-30-54%20(1).png" /></p>
<h2>So whats the problem?</h2>
<p>This is fine if you are happy with an incrementing number across all projects. But we have found in the past we prefer an incrementing number for <em>each</em> project. TeamCity has this out of the box with the <strong>Build Counter</strong> variable.</p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-12_11-03-15%20(3).png" /></p>
<p>This useful feature allows us to version our projects with something like SemVer 2.0 to give us version numbers like 1.0.234, where the last number is incremented per build of a specific project.</p>
<p>All projects would start out with a 1.0.1 number and then increment from there. Projects build more frequently would have a higher number, projects only built occasionally would have a lower number.</p>
<p>I was puzzled that it is not available by default on VSTS, however we can add something very similar without too much effort.</p>
<p>I had seem some samples on the Internet that refer to modifying static text files to maintain project version numbers, but I would much prefer to use a project variable and use the VSTS REST API to update the counter on each build. This way all the metadata is kept together with the project and without any external file dependencies.</p>
<h2>How to implement a Build Counter in VSTS</h2>
<p>In your VSTS project, create a variable called <strong>ProjectBuildNumber</strong> and give it an initial value of 1</p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-29_23-18-27.png" /></p>
<p>In the <strong>Options</strong> section, set the Build number format to <strong>1.0.$(ProjectBuildNumber)</strong> </p>
<p>NOTE: This is just a sample, your numbering standard might be a little different.</p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-12_12-16-27.png" /></p>
<p>In your <strong>Tasks</strong> section of your Build definition, include a new step for running a PowerShell script.</p>
<p>NOTE: It is up to you if you want to use a script from a repository or an inline script, for this blog post we will use an inline script for simplicity.</p>
<p>Set the following on the PowerShell script screen:</p>
<p><ul>
<li>Set the Version to 2.*</li>
<li>Set the Display Name to something descriptive</li>
<li>Set the Type to Inline</li>
<li>For the Script content use this script.</li>
</ul>
</p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-29_22-41-48.png" /></p>
<p>Update the two fields at the top, the valueName is the name of the variable you added. This example uses ?ProjectBuildNumber?</p>
<p>The token is the PAT <em>(Personal Access Token)</em> you can generate from clicking your profile picture at the top right of the VSTS site and going to the Security section.</p>
<p>NOTE: It would be more ideal to use a system account PAT, rather than your own PAT, so that build process activities are always performed by system accounts and not tied in directly with user accounts.</p>
<p>Click the <strong>Save and Queue</strong> button. In the build logs, you will see the number being incremented from and the build number using the current value.</p>
<p style="clear: both"><img src="https://platform.deloitte.com.au/hubfs/MEX%20-%20Blog%20images/MEX%20-%20Author%20-%20Matt%20Corr/2017-11-29_23-22-16.png" /></p>
<p>Now each time you trigger or queue a build, the build number will be incremented.</p>
<h2>Vsts build</h2>

<h3>Vsts build</h3>
<p>[youtube]</p>
Vsts build <a href="http://remmont.com">The news</a> Vsts build
<h4>Vsts build</h4>
Discover how using the VSTS REST API we can implement a missing feature of VSTS to use for our project build numbers.
<h5>Vsts build</h5>
Vsts build <a href="http://remmont.com">Vsts build</a> Vsts build
SOURCE: <h6>Vsts build</h6> <a href="https://dev-ops.engineer/">Vsts build</a> Vsts build
#tags#[replace: -,-Vsts build] Vsts build#tags#
Eduard Kabrinskiy
news today

[BurbankSige]

Azure devops markdown - Эдуард Кабринский


<h1>Azure devops markdown</h1>
<p>[youtube]</p>
Azure devops markdown <a href="http://remmont.com">News headlines of the day</a> Azure devops markdown
<h1>Creating Azure DevOps WIKI Pages from within a pipeline - part 2</h1>
<p><strong>Contents</strong></p>
<p>This is part 2 of a blog post series about creating Azure DevOps WIKI pages from within a Pipeline.</p>
<p>If you have not read part 1, please do so first.</p>
<h1>Scenario</h1>
<p>The scenario for demonstrating the creation of an Azure DevOps WIKI pages from within a Pipeline is the creation of documentation (WIKI page) for each Azure Resource Deployment being made via an Azure DevOps Pipeline.</p>
<p>Below a screenshot of the end result, being documentation for an Azure Resource Deployment of an Azure Logic App.</p>
<p style="clear: both"><img src="https://stefanstranger.github.io/assets/2020-04-25-01.png" /></p>
<p>The goal is to have a similar Wiki document created for each of the Azure Resource Deployments being made via an Azure DevOps Pipeline.</p>
<h1>Solution</h1>
<h2>Documentation details</h2>
<p>The documentation contains the following sections:</p>
<p><ul>
<li>Title</li>
<li>Parameters</li>
<li>Variables</li>
<li>Resources</li>
<li>Deployment information</li>
<li>ARM Preview</li>
</ul>
</p>
<p>The following table shows the sources for each of above sections:</p>
<p> <table> <thead> <tr> <th>Section</th> <th>Source</th> </tr> </th> <tbody> <tr> <td>Title</td> <td>Metadata file</td> </tr> <tr> <td>Parameters</td> <td>ARM Template file</td> </tr> <tr> <td>Variables</td> <td>ARM Template file</td> </tr> <tr> <td>Resources</td> <td>ARM Template file</td> </tr> <tr> <td>Deployment information</td> <td>PSDocs template file</td> </tr> <tr> <td>ARM Preview</td> <td>ARM Template file</td> </tr> </tbody> </table> </p>
<h2>Metadata file</h2>
<p>This metadata file is something I re-used from the documentation of the PSDocs PowerShell Module.</p>
<h2>ARM Template</h2>
<p>For the deployment I used an ARM Template file to deploy an Azure Logic App which I used in a customer demo about Automation some time ago.</p>
<p><strong>Note:</strong> Not showing the parameter file because that was not used for the creation of documentation.</p>
<p>The ARM Template was iterated with the following code to retrieve the information I was looking for.</p>
<h2>ARM Preview</h2>
<p>For the ARM Preview part of the document I used Mermaid to create an diagram overview of the Resource Dependencies.</p>
<p>If you look at the ARM Template file above you see that Azure Resource Type Microsoft.Logic/Workflows has a dependency on Microsoft.Web/connections resources.</p>
<p style="clear: both"><img src="https://stefanstranger.github.io/assets/2020-04-25-03.png" /></p>
<p style="clear: both"><img src="https://stefanstranger.github.io/assets/2020-04-25-02.png" /></p>
<h3>Mermaid</h3>
<p>Azur DevOps Wiki supports Mermaid Diagrams.</p>
<p>Mermaid is a simple markdown-like script language for generating charts from text via JavaScript.</p>
<p>With some custom PowerShell code and the PowerShell Mermaid Module PSMermaid a very simple ARM Preview Diagram was created.</p>
<p>You can install the PowerShell Module with the following code:</p>
<p>For the creation of the ARM Preview Diagram I used the following PowerShell Functions. First we use the earlier shared Helper Function to parse the ARM Template file. The next helper Function New-MermaildResourceDiagram creates the Mermaid diagram code to be used in the Markdown document.</p>
<p>When you run the Function New-MermaidResourceDiagram you get the following output:</p>
<h2>PSDocs Template</h2>
<p>To create the Markdown document the following PSDocs Template is being used.</p>
<h2>Create Markdown deployment document and publishing script</h2>
<p>If we put everything together in one script to create the ARM Template Markdown document and publish the document to the Azure DevOps wiki the following code can be used.</p>
<h2>Azure DevOps Pipeline</h2>
<p>In the final step we are going to put everything together in an Azure DevOps Pipeline. The following steps need to be executed.</p>
<p><ol>
<li>Configure permissions on Azure DevOps wiki repository to publish document</li>
<li>Deploy the Azure Logic App</li>
<li>Create Markdown documentation of Azure Resource deployment and publish to wiki</li>
</ol>
</p>
<h3>Permissions on Azure DevOps wiki repository</h3>
<p>To have the deployment Markdown document being published to the Azure DevOps wiki (repository) the security on the Wiki needs to be configured. Confgure the Contribute setting to allow for the Project Collection Build Service.</p>
<p style="clear: both"><img src="https://stefanstranger.github.io/assets/2020-04-25-04.png" /></p>
<p style="clear: both"><img src="https://stefanstranger.github.io/assets/2020-04-25-05.png" /></p>
<h3>Yaml pipeline</h3>
<p>The yaml pipeline to execute above steps should look like this:</p>
<h2>Azure devops markdown</h2>

<h3>Azure devops markdown</h3>
<p>[youtube]</p>
Azure devops markdown <a href="http://remmont.com">Headlines</a> Azure devops markdown
<h4>Azure devops markdown</h4>
This is my personal blog. I work at Microsoft as a Consultant. You can find some of my open source projects on Github. I like to share my knowledge about Azure, PowerShell and DevOps
<h5>Azure devops markdown</h5>
Azure devops markdown <a href="http://remmont.com">Azure devops markdown</a> Azure devops markdown
SOURCE: <h6>Azure devops markdown</h6> <a href="https://dev-ops.engineer/">Azure devops markdown</a> Azure devops markdown
#tags#[replace: -,-Azure devops markdown] Azure devops markdown#tags#
https://ssylki.info/?who=car-and-driver ... t.com/news https://ssylki.info/?who=remmont.com/4520 https://ssylki.info/?who=mercury-insurance.remmont.com https://ssylki.info/?who=new-york-life- ... emmont.com https://ssylki.info/?who=apartment-list.remmont.com

[BirminghamKn]

Devops technologies - Kabrinskiy Eduard


<h1>Devops technologies</h1>
<p>[youtube]</p>
Devops technologies <a href="http://remmont.com">Latest breaking news</a> Devops technologies
<h1>DevOps</h1>
<p>Deliver innovation faster with simple, reliable tools for continuous delivery</p>
<p>Whether your DevOps implementation is just beginning or you?re looking to integrate with your existing toolchains and processes, building an end-to-end continuous delivery pipeline is faster and more secure with Azure DevOps technologies. Spend less time maintaining your toolset and more time focusing on customer value. Building, releasing, testing, and monitoring cloud and mobile applications is simple and reliable with DevOps technologies that enable you to continuously deliver innovation using any toolchain.</p>
<h2>Find the DevOps product you need</h2>
<table> <thead> <tr> <th style="width: 75%;">If you want to</th> <th style="width: 25%;">Use this</th> </tr> </th> <tbody> <tr> <td>Services for teams to share code, track work, and ship software</td> <td> Azure DevOps </td> </tr> <tr> <td>Create a full continuous integration and continuous deployment (CI/CD) pipeline with just a few clicks for any application in any language deployed on a variety of Azure services.</td> <td> Azure DevOps Projects </td> </tr> <tr> <td>Automatically build, test, distribute, deploy, and monitor iOS, Android, Windows, and macOS apps?all in one place</td> <td> Visual Studio App Center </td> </tr> <tr> <td>Set up labs for a classroom, trials, development, or testing</td> <td> Azure Lab Services </td> </tr> <tr> <td>Get the granular, up-to-date monitoring data you need?all in one place</td> <td> Azure Monitor </td> </tr> <tr> <td>Create cloud environments with quick setup, reusable templates, cost management, and integration with existing toolchains</td> <td> Azure DevTest Labs </td> </tr> </tbody> </table>
<h2>Use the DevOps tools you already know</h2>
<p>Keep using the tools you know?including Ansible, Chef, Jenkins, and Terraform?with Azure and get guidance and example architectures.</p>
<h2>Customers are doing great things with Azure DevOps products</h2>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/shared/customers/shell_m.png" /></p>
<h3>Top oil and gas firm accelerates software development to fuel global energy production</h3>
<blockquote><p>"Instead of telling people to wait for six months for a new feature, we can give it to them in a few weeks. Our lead cycles are getting much shorter, and we have business stakeholders involved so that our solutions are more aligned with business requirements."</blockquote></p>
<p>Johan Krebbers, IT Chief Technology Officer</p> </blockquote>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/shared/customers/icertis_m.png" /></p>
<h3>Icertis enhances security of cloud-based enterprise contract management solution</h3>
<blockquote><p>"The speed and agility of getting our product to market were very important reasons we went with the Microsoft cloud. Time-to-market has been significantly short, compared to what we would have achieved on other cloud platforms."</blockquote></p>
<p>Monish Darda, Cofounder and Chief Technology Officer</p> </blockquote>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/shared/customers/geico.png" /></p>
<h3>GEICO turbocharges insurance innovation in the cloud</h3>
<blockquote><p>"With DevOps and Azure, we're able to reduce our new-feature release cycle down to one week, and we think we can even speed that up."</blockquote></p>
<p>Fikri Larguet, Director of Cloud Services</p> </blockquote>
<p style="clear: both"><img src="https://azurecomcdn.azureedge.net/cvt-651ac13f7655ba1bd2a7669f8629318e228f2c132536db3a5733d3722666f31f/images/shared/services/devops/Devops-asset.png" /></p>
<h2>Learn how to scale DevOps practices throughout your organization</h2>
<p>Download the Enterprise DevOps 2020-2021 report to learn how top performing organizations have implemented DevOps across their businesses.</p>
<h2>Explore more DevOps technologies</h2>
<h3>Resource Manager </h3>
<p>Deploy resources as a group and easily repeat deployment tasks</p>
<h3>Azure Monitor </h3>
<p>Get the granular, up-to-date monitoring data you need?all in one place</p>
<h3>Security Center </h3>
<p>Unify security management and enable advanced threat protection across hybrid cloud workloads</p>
<h3>Log Analytics </h3>
<p>Transform your log data into insights and action</p>
<h3>Key Vault </h3>
<p>Safeguard cryptographic keys and other secrets used by cloud apps and services</p>
<h3>Microsoft DevOps Blog </h3>
<p>Get the latest DevOps updates from the Microsoft team</p>
<h3>DevOps tutorial </h3>
<p>Learn what DevOps is and see how to begin implementing it</p>
<h2>Devops technologies</h2>

<h3>Devops technologies</h3>
<p>[youtube]</p>
Devops technologies <a href="http://remmont.com">Latestnews</a> Devops technologies
<h4>Devops technologies</h4>
Deliver innovation faster with Azure DevOps technologies that make continuous delivery simpler, more reliable, and more secure.
<h5>Devops technologies</h5>
Devops technologies <a href="http://remmont.com">Devops technologies</a> Devops technologies
SOURCE: <h6>Devops technologies</h6> <a href="https://dev-ops.engineer/">Devops technologies</a> Devops technologies
#tags#[replace: -,-Devops technologies] Devops technologies#tags#
https://ssylki.info/?who=compare-auto-i ... emmont.com https://ssylki.info/?who=remmont.com/mi ... dos-news-2 https://ssylki.info/?who=mansions-for-sale.remmont.com https://ssylki.info/?who=remmont.com/th ... rs-careers https://ssylki.info/?who=pet-insurance.remmont.com

[BurbankSige]

Tfs and vsts - Эдуард Кабринский


<h1>Tfs and vsts</h1>
<p>[youtube]</p>
Tfs and vsts <a href="http://remmont.com">Breaking news today</a> Tfs and vsts
<h1>Work with VSTS (or TFS) Work Items from Excel without installing Team Explorer</h1>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/size/w100/2020/07/BrianRandell-Small-Head.png" /></p>
<h2>Brian A. Randell</h2>
<p>Husband. Dad of 2. Son. Brother. Developer. ALM/DevOps Consultant. MSFT MVP. Writer. Love fast cars & hard rocking music. ///M Power. Love cuddles with my kids.</p>
<p>More posts by Brian A. Randell.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/size/w100/2020/07/BrianRandell-Small-Head.png" />
</ul></p>
<h4>Brian A. Randell</h4>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/size/w2000/2017/08/bulk-modify-excel-blank-list.png" /></p>
<p><strong>TLDR; If you just want the step-by-step on how to work with Excel and work items <em>without</em> installing Team Explorer, jump down to the Non-Developer's Short Guide to Using Excel with TFS/VSTS Work Items on this page.</strong></p>
<p>For years, if you wanted to work with Team Foundation Server (TFS) Work Items from Excel, you had to install the Team Explorer package which basically gave you the Visual Studio Shell plus the extra bits to integrate with Office. However, starting with the 2015 release of TFS, Microsoft starting providing an installer package with just the bits you need to make Excel (and God forbid Microsoft Project) work with TFS or VSTS.</p>
<p><strong>That said, do you still need Excel integration?</strong></p>
<p>The web interface in TFS and Visual Studio Team Services (VSTS) has become rather amazing, so you won't often need to use Excel. For example, if you wanted to change a common field on multiple work items, you can select them in the UI (say a few Tasks on the Sprint Backlog, and select <strong>Edit</strong>:</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/BulkEditviaWebUI.png" /></p>
<p>This will open the <strong>Edit work items</strong> dialog where you can modify multiple fields at the same time as well as add <strong>Notes for History</strong>.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/EditWorkItems-Web.png" /></p>
<p>However, Excel provides two nice advantages.</p>
<p><ol>
<li>You can work offline. By pulling down a group of work items, you can work when you don't have Internet access to your TFS server or VSTS.</li>
<li>Excel can be faster when you're editing and making changes to lots of fields or copying in data from another source.</li>
</ol>
</p>
<p><em>In those cases, it makes sense to use Excel.</em></p>
<p>For developers who install Visual Studio, you're good to go. However, often there are non-developers on your team who need to work with lots of work items. For them it's easy to get the Excel features <em>without</em> installing Team Explorer or Visual Studio.</p>
<p>The basic steps are:</p>
<p>Install Office 2007 or later <strong>on Windows</strong> (Sorry no support macOS versions)</p>
<p>Download and install the Team Foundation Server Office? Integration 2017</p>
<p>Connect to our TFS instance or VSTS account</p>
<p>To download and install the <strong>Team Foundation Server Office Integration 2017</strong>, head over to the Visual Studio Downloads page and scroll down to the section labeled <strong>Team Foundation Server 2017 Update 2</strong>. You'll find both a <em>Web Installer</em> and an <em>ISO</em> download.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/DownloadOfficeIntegration.png" /></p>
<p>The Web Installer is great if you have good Internet where as the ISO file is great when you have multiple machines or bandwidth is at a premium and you only want to pay the download cost once.</p>
<p>Once you've got enough of the installer downloaded or you've mounted the ISO, run it and you'll get a simple install screen. You'll need to have local Administrator rights to install. Click <strong>Install</strong>, accept the UAC prompt and it will take a few moments depending on the speed of your computer and whetehr or not you downloaded the whole package.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/OfficeIntegrationSplash.png" /></p>
<p>Once you've installed the package, start Excel, and you should see a <strong>Team</strong> tab on the Ribbon.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/TeamTabExcel2016.png" /></p>
<p>On the Team tab, choose the <strong>New List</strong> command and the <strong>Connect to Team Foundation Server</strong> dialog will open. Use it to connect to your Team Project.</p>
<p style="clear: both"><img src="https://blog.brianrandell.com/content/images/2017/08/ConnecToTfsDialog.png" /></p>
<p>Once you're connected, you will see the <strong>New List</strong> dialog, where you can choose an existing <em>Work Item Query</em> or create a new <em>Input List</em>.</p>
<h2>Tfs and vsts</h2>

<h3>Tfs and vsts</h3>
<p>[youtube]</p>
Tfs and vsts <a href="http://remmont.com">The news</a> Tfs and vsts
<h4>Tfs and vsts</h4>
Work with VSTS (or TFS) Work Items from Excel without installing Team Explorer Brian A. Randell Husband. Dad of 2. Son. Brother. Developer. ALM/DevOps Consultant. MSFT MVP. Writer. Love
<h5>Tfs and vsts</h5>
Tfs and vsts <a href="http://remmont.com">Tfs and vsts</a> Tfs and vsts
SOURCE: <h6>Tfs and vsts</h6> <a href="https://dev-ops.engineer/">Tfs and vsts</a> Tfs and vsts
#tags#[replace: -,-Tfs and vsts] Tfs and vsts#tags#
https://ssylki.info/?who=money-lenders.remmont.com https://ssylki.info/?who=auto-connection.remmont.com https://ssylki.info/?who=houses-or-apar ... emmont.com https://ssylki.info/?who=remmont.com/lo ... nde-viajar https://ssylki.info/?who=remmont.com/1096