Concourse Documentation. Now that youre all set up and have a Concourse running, its time to see what this thing can do. As per tradition, there is a pretty useless Hello, world This will at least show the basics of fly, which you can read more about in great detail at The Fly CLI, so its still worth a read. Once youve got your Concourse all set up, youll want to download the Fly CLI from your instance via the web UI. The Nutanix Bible A detailed narrative of the Nutanix architecture, how the software and features work and how to leverage it for maximum performance. You can find the download links by browsing to the main page If youre on Linux or OS X, you will have to chmod x the downloaded binary and put it in your PATH. This can be done in one fell swoop with install pathtofly usrlocalbinfly. Throughout this page well assume youve spun up the Concourse Lite VM, but if youve set up Concourse in some other way, everything still applies just use your URL instead of http 1. Once you have fly, youll want to target your local Virtual. Box like so fly t lite login c http 1. This will save the target as lite, which well use for all later commands that we want to run against the local box by using the same t flag. Out of the box, Concourse doesnt have any Configuring Pipelines configured. Thats boring. Here, have this YAML Hello, worldDump that into a file called hello. If you refresh the main page, you should now see the worlds tiniest pipeline Newly configured pipelines are paused by default indicated by the blue bar along top of the page, to prevent them from running freely when youre not sure what they do yet. MetadataTouch_3.png' alt='Metadata Touch Keygen' title='Metadata Touch Keygen' />What is Subversion Why does it exist Subversion is an opensource, centralized version control system. See Our Vision on our front page to know why Subversion. Full software with working keygen and patch, ProShow Producer version 5. Build 3310. To unpause it, you can either reveal the pipelines sidebar via the button in the top left and press, or run fly t lite unpause pipeline p hello world. You can always fetch the current configuration of a pipeline by running fly t lite get pipeline p hello world. This pipeline configuration so far describes a single job, whose plan has a single task. There are no resources for this job to automatically trigger so well have to give it a helping hand. Click the job and then press the button in the top right. The task boots up, prints Hello, world, and completes successfully Lets spice things up a bit. A pipeline with a single job with no resources isnt very interesting, so lets add a simple resource in the form of a timed trigger, using the Time resource. Hey ListenRun the following to reconfigure the existing pipeline fly t lite set pipeline p hello world c navi pipeline. Your pipeline should now look like this Every minute, the every 1m resource will yield a new version. This resource is used in a get step in the navi job, which sets trigger to true, so as a result the job will run every minute. Now may be a good time to start learning about the different types of resources or start looking at Tutorials. It can be hard to learn a new tool without having something you want to accomplish. These tutorials will at least guide you through particular use cases to show you how youd use Concourse in real world scenarios. You may also want to just dive right in to some living, breathing Concourse pipelines. These arent accompanied by documentation explaining them, but it may be useful just to see some real world use cases Welcome, Cadet. This walkthrough assumes youve already got a Concourse set up and ready to go. If you dont, the most important thing is that you dont panic and go through the installation guide before coming back here. First, lets get you a copy of your training materials. Fork this repository on Git. Hub into your own account. This will give you somewhere to keep your work. Next, clone your fork down to your local machine by running this command git clone https github. This is a simple Ruby project that will let you get a feel for flying. Lets check everything is working by running the tests locally. If everything is working then you should see a few green dots on the screen to let you know that the tests are passing. If something failed then make sure to fix it and get the tests green before continuing. For example, if youre missing the bundle executable then youll need to run gem install bundler. Ok, weve got a project. We want a pipeline. Its important to build a pipeline up gradually rather than attempting to do the whole thing at once. Lets start at the start by running those unit tests we just ran in Concourse. Download fly from your Concourse. You can find a download link on your Concourse installation main page. They will either be at the bottom right or in the middle if you dont have any pipelines yet. HOMEbin. HOMEDownloadsfly HOMEbin. Make sure that HOMEbin is in your path. You should now be able to run fly help to see if everything is working. Ok, lets target and log in to our Concourse. URL. The t flag is the name well use to refer to this instance in the future. The c flag is the concourse URL that wed like to target. Depending on the authentication setup of your Concourse it may prompt you for various credentials to prove you are who you say you are. Right, lets try running the current project in Concourse. Huh. Well then, lets give it that flag with a file that it wants. Path. Flag path build. Alright, so we need a file called build. Lets create it under the flight school directory. Surprise, surprise looks like we cant just give it an empty file. Andy Williams Midi Files. We need to write a task definition. A task definition describes a unit of work to Concourse so that it can execute it. Lets go through this line by line The platform simply states that we would like this task to run on a Linux worker. The imageresource section declares the image to use for the tasks container. It is defined as a resource configuration. The inputs section defines a set of things that we need in order for our task to run. In this case, we need the flight school source code in order to run the tests on it. The final run section describes how Concourse should run the task. By default Concourse will run your script with a current working directory containing all of your inputs as subdirectories. Ok, lets save that in build. Total Received Xferd Average Speed Time Time Time Current. Dload Upload Total Spent Left Speed. Ok, so what happened here. We started a build, uploaded the flight school input, and then tried to run the flight schoolcitest. Which isnt there. Oops Lets write that. This is basically the same commands we ran above in order to run the tests locally. The new bits at the start set up a few things. The binbash is a shebang line that tells the operating system that when we execute this file we should run is using the binbash interpreter. The set e x line is setting a few bash options. Namely, e make it so the entire script fails if a single command fails which is generally desirable in CI. By default, a script will keep executing if something fails. The x means that each command should be printed as its run also desirable in CI. Lets give this new script a whirl. Total Received Xferd Average Speed Time Time Time Current. Dload Upload Total Spent Left Speed. This error message means that the script we told it to run is not executable. Lets fix that. Running again gives us fly t ci execute c build. Total Received Xferd Average Speed Time Time Time Current. Dload Upload Total Spent Left Speed.