Idea Transcript
Sign In
This is Luciano Silva's Typepad Profile.
Join Now!
Join Typepad and start following Luciano Silva's activity
Already a member? Sign In
Luciano Silva Apex, NC Travel aficionado, Software Developer, Cloud Foundry Solutions Architect Recent Activity
Running tasks with Docker images from an S3 bucket Pipeline tasks can be executed with images stored in repositories other than a Docker registry as previously described in another blog entry. However, the drawback of that article's proposed solution is the fact that the rootfs of the image needs to be available and stored uncompressed. Enter S3 resource's untar... Continue reading Posted Jul 31, 2017 at The CI Lounge
Sign in or register to follow
View all »
Followers 3
The CI Lounge
The problem The environment where Concourse is deployed requires workers to have an HTTP/HTTPS proxy configuration in order to access external artifacts from the internet. The solution Deploy Concourse workers with the appropriate proxy configuration for the groundcrew job. - name: worker ... jobs: - name: groundcrew release: concourse properties:... Continue reading Posted Jul 14, 2017 at The CI Lounge
View all »
Blogs and Sites
Comment
Around The Web lmpsilva lmpsilva
0
How to integrate Concourse pipelines with Vault Concourse 3.3.1+ supports credential management integration with HashiCorp's Vault and eliminates the need to feed credentials to pipelines via plain-text parameter files. This integration requires configuration updates to both Vault and Concourse servers as described further below. From a pipeline definition standpoint, the usage of credentials from Vault is very... Continue reading Posted Jul 11, 2017 at The CI Lounge
Tripezio
0
How to configure Concourse with an HTTP/HTTPS proxy
Following 1
0 Favorites
Comment
Comment
0
Concourse Pipeline Patterns: Parameterized Tasks In the same fashion as a method or a function in programming languages, Concourse pipeline tasks can be executed with parameterized variables, inputs and outputs. That allows for the reuse of common task definitions, for example, "package release" or "deploy application", in multiple contexts and in multiple executions for distinct... Continue reading Posted Mar 30, 2017 at The CI Lounge
Comment
0
Concourse Pipeline Patterns: Time-Triggered Pipelines Time-triggered CI pipelines are very common for tasks that require to be executed on a regular basis (hourly, daily, monthly,...), such as systems backup, automated application builds and tests, cleanup of data storage, etc. In Concourse, time triggered pipelines can be implement with the time resource, which produces a new... Continue reading Posted Mar 27, 2017 at The CI Lounge
Comment
0
Concourse Hacks: running tasks and resources without a Docker registry For cases when the access to Docker Hub is not available from the subnet which Concourse is deployed to AND the deployment of an internal Docker Registry may take long or be difficult for any reason, there is a workaround to run Concourse pipelines on that environment: run tasks and... Continue reading Posted Mar 24, 2017 at The CI Lounge
Comment
0
Concourse CI Pipeline Patterns: Gated Pipelines Gated CI pipelines provide control for administrators and release managers on when a given software release is deployed to a tightly protected environment (e.g. production). The execution of jobs that perform certain tasks (e.g. deployment) targeting the downstream environment beyond the "gate" step is done only upon either an approval... Continue reading Posted Mar 21, 2017 at The CI Lounge
Comment
0
A simple File Resource for Concourse Very often, especially during pipeline development time, your pipeline scripts may require the download of a file that is not yet in S3, github, nor Artifactory, but it is actually available in a URL-addressable public repository, such as a download mirror website or an internal file repository. For those cases... Continue reading Posted Feb 28, 2017 at The CI Lounge
Comment
0
Preview Concourse pipelines in ATOM If you use the ATOM editor for coding Concourse pipelines, then there is a great tool available to preview pipelines directly from the editor's user interface: the concourse-vis plugin by danhigham. The plugin allows you to visualize an entire CI pipeline, to pan and zoom into specific sections of it... Continue reading Posted Dec 16, 2016 at The CI Lounge
Comment
0
Google Cloud Storage integration with Concourse Concourse pipelines can be integrated with Google Cloud Storage (GCS) to store/retrieve build artifacts to/from GCS buckets. The sample pipeline provided below uses the GCS resource for Concourse in its implementation. Hints are also given on how to configure a GCS bucket for integration with a Concourse pipeline in the... Continue reading Posted Dec 14, 2016 at The CI Lounge
Comment
0
Azure Blobstore integration with Concourse pipelines This article provides an example of the integration of Azure Blobstore containers with Concourse pipelines. The example uses the Azure Blobstore resource to save a build artifact to an Azure Blobstore container and then retrieve it back later. This pipeline illustrates the implementation of the "only build packages once" pattern... Continue reading Posted Dec 7, 2016 at The CI Lounge
Comment
0
Pivotal Cloud Foundry usage report producer pipeline Pivotal Cloud Foundry (PCF) provides a set of accounting report APIs that can be used to retrieve and compile applications and services usage data of all organizations and spaces of a PCF deployment. This sample Concourse pipeline leverages the PCF accounting report API along with the standard open source Cloud... Continue reading Posted Nov 17, 2016 at The CI Lounge
Comment
0
Artifactory integration with Concourse pipelines A best practice in continuous integration pipelines is to "only build packages once" and then consume that same version of the produced artifacts in later steps of the pipeline (e.g. app deployment, functional/integration tests). In order to implement this pattern in a pipeline, integration with artifacts repositories are commonly used.... Continue reading Posted Nov 16, 2016 at The CI Lounge
Comment
0
Insert build metadata into user notifications in Concourse Metadata about running builds, such as build ID, job or pipeline name, is available as environment variables for get or put operations in Concourse. Such information is very useful to provide to pipeline users when notifying them about their builds' success or failure. The list of available variables is listed... Continue reading Posted Oct 20, 2016 at The CI Lounge
Comment
0
Sending emails with file attachments from Concourse pipelines A CI pipeline in Concourse may be required to send notification emails containing one or more attachments to its users and subscribers. An example of a use case is of a pipeline that produces files and/or reports that need to be sent directly to users instead of being stored in... Continue reading Posted Oct 6, 2016 at The CI Lounge
Comment
0
Sean, here are some ways to serialize concourse pipelines. - If the pipelines are relatively simple and managed by the same team/people, they could be defined in a single pipeline definition file, visualized individually on the concourse UI by using the groups feature and then use the "trigger/passed" job parameters for one group job to trigger the next. - If the pipelines are defined and managed separately, then you could serialize them using a common resource to trigger them (e.g. github repo), where the first one updates the resource after it is done and which will then trigger the next pipeline. A pool resource (https://github.com/concourse/pool-resource) could also be used to control the "lock"/"unlock" of the common resource. Commented Oct 3, 2016 on PCF Backup using CFOps at The CI Lounge
Running local tasks while developing your CI pipeline in Concourse When developing relatively complex pipelines for Concourse, tasks definitions and scripts are typically defined in individual files (e.g. YML and .sh), separate from the main pipeline definition YML file. While this is a great structure for a CI pipeline in production, it creates a pain point for the developer of... Continue reading Posted Sep 20, 2016 at The CI Lounge
Comment
0
PCF Backup using CFOps This article provides an example of a Concourse CI pipeline that performs automated nightly backups of a complete Pivotal Cloud Foundry deployment by using the CFOps backup tool. The pipeline also demonstrates the integration of backup scripts with a shared file storage system via scp in order to store the... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
2
Blue-Green application deployment with Concourse This is an example of a Concourse pipeline that builds, tests and deploys a Node.js sample application using theBlue-Green deployment methodology. The steps automated in the pipeline are as follows: Retrieve the application's source code from GitHub The pipeline is automatically triggered upon a code update/check-in event in the GitHub... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
0
Application CI pipeline targeting multiple CF spaces This is an example of a Concourse pipeline that performs the following tasks for a sample Golang application: builds (compiles) the binary artifact unit tests it deploys it to a Cloud Foundry staging space load tests it deploys it to a Cloud Foundry production space Each step is configured to... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
0
Concourse pipelines with a local Docker Registry A typical question that surfaces from customers planning to adopt and deploy Concourse on their production environments is “How do I run Concourse tasks on a protected or internetless environment where no access to Docker Hub is available?”. The typical short answer from experts or from the Concourse documentation is... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
0
Deploy a Private Docker Registry with Bosh A bosh release is available for Docker Registry at https://github.com/cloudfoundrycommunity/docker-registry-boshrelease and can be used to deploy a private docker registry using Bosh. The sample provided requires a Bosh 2.0 deployment (Cloud Config-based). The sample manifest will deploy a Docker Registry with the following VM/jobs topology: [PROXY_VM] | | [REGISTRY_VM1] [REGISTRY_VM2]... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
0
Deploying Concourse on Bosh-lite The quickest way to install and run a local copy of Concourse is by using the provided Vagrant image as mentioned in Concourse’s documentation page. However, in certain cases, one may have the need to experiment with the Boshdeployed version of Concourse in a local machine prior to moving it... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
0
Concourse deployment with a Bosh 1.x manifest Concourse's installation documentation provides only samples on how to install Concourse using a Bosh 2.0-style deployment manifests, i.e. manifests that rely on the Bosh 2.0 Cloud Config concept. In some instances though, customers may want to install Concourse on a new or existing Bosh Director where a Bosh 1.0 compliant... Continue reading Posted Sep 16, 2016 at The CI Lounge
Comment
Luciano Silva is now following The Typepad Team Sep 16, 2016
More... Subscribe to Luciano Silva’s Recent Activity
Typepad © 2003-2018 Typepad, Inc. All Rights Reserved. Terms of Service Privacy Policy
0