21–30 of 72 posts
Some of people also use their CI tools for running arbitrary one-off scripts (like deploys). Is this possible with Concourse? Currently we have a few Jenkins jobs that just execute a fab task that then does the actual work.
This looks awesome! I hope to transition to it, handling Jenkins configurations is a huge pain. Some of people also use their CI tools for running arbitrary one-off scripts (like deploys). Is this possible with Concourse? Currently we have a few Jenkins jobs that just execute a fab task that then does the actual work.
This looks awesome! I hope to transition to it, handling Jenkins configurations is a huge pain. Some of people also use their CI tools for running arbitrary one-off scripts (like deploys). Is this possible with Concourse? Currently we have a few Jenkins jobs that just execute a fab task that then does the actual work.
For anyone else that got excited about having a Jenkins alternative, this project seems to be only about containers and not other workloads that VMs could tackle, such as running browser or desktop-based software tests. At least that's my understanding after giving the documentation a cursory glance. Could someone familiar with the project please confirm (or hopefully correct) this?
I find these approaches better than risking test pollution, especially when it comes to building VMs and spinning up desktop apps.
Earlier quoted context omitted.
Using the `fly` CLI allows you to know what changes are being made when you update the pipeline (it shows a diff), and when your configuration is invalid (or when the update fails for another reason).
I get the exact same features from my configuration manager, as long as there is a command I can run to validate the configuration file(s).
Things that we've done so far with Concourse:
* A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel
* A job, that based on the completion of a build will upload the resulting artifact to Github and tag the release with a new version, auto generated release notes and checksums
* Travis.ci style github pull request analysis
* A security feed monitor that notifies us when a part of our application is vulnerable and when it is, kicks off a build and sends an email notification
* Automatically updates submodules and gems for git repos and runs specs and tests against the updated artifact.
These tasks were not difficult to implement. Every pipeline for Concourse is explicitly defined in its configuration file [2], which we version control. There is never any reconfiguring or rebuilding "snowflake" servers when we re-deploy our Concourse VMs. They rebuild identically based on the config files.
[1] - http://buildpacks-ci.cfapps.io (Chrome friendly, Firefox not)
Are there any plans to support OS X workers? This would be extremely helpful for Mac and iOS apps.
Concourse uses the Garden API to manage containers. Houdini is a "no-op" implementation that just tells Garden "yep, I've got your container right here".
Earlier quoted context omitted.
No, i think raziel2p understands. If you're using a configuration management tool like Puppet or Ansible, by far the easiest way to manage a piece of software is through a configuration file on disk that the configuration management tool can manage directly: it's easy to see the current state, and to make changes. Anything that requires a tool or an API requires you to interpose some sort of update mechanism between…
Ah, gotcha. So if I'm following this line correctly, it'll need someone to write a wrapper that detects updates to .yml files and invokes fly?
http://docs.ansible.com/ansible/playbooks_intro.html#handler...
The handler could use the command module to run fly:
Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1]) Things that we've done so far with Concourse: * A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel * A job, that based on the completion of a build will…