Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / relevance/relevance_rails issues and pull requests
#64 - private key in config not being used in some circumstances
Issue -
State: open - Opened by muness over 12 years ago
#63 - Retrying apt-get shenanigans.
Pull Request -
State: closed - Opened by aredington over 12 years ago
#62 - Elastic CI: Use Jenkins configuration to set git name and email
Issue -
State: closed - Opened by sumbach over 12 years ago
#61 - Elastic CI: Automatically converge build slaves when they are provisioned
Issue -
State: closed - Opened by sumbach over 12 years ago
#60 - Elastic CI: Automatically generate, test, and bless build slave AMI
Issue -
State: closed - Opened by sumbach over 12 years ago
#59 - Elastic CI: Add Jenkins job to create fresh build slave AMI
Issue -
State: closed - Opened by sumbach over 12 years ago
#58 - Elastic CI: Add smoke tests for new build slave
Issue -
State: closed - Opened by sumbach over 12 years ago
#57 - Elastic CI: Automate creation of build slave AMI
Issue -
State: closed - Opened by sumbach over 12 years ago
#56 - Defect: Conflicting Rails versions caused generation to fail
Issue -
State: closed - Opened by karnowski over 12 years ago
- 4 comments
Labels: ready-for-qa
#55 - Defect: Only saw "relevance_file" generator when adding to existing app
Issue -
State: closed - Opened by karnowski over 12 years ago
- 2 comments
#54 - CI: add retry to handle "no candidate" for ruby errors
Issue -
State: closed - Opened by karnowski over 12 years ago
Labels: in-progress
#53 - Add Linode support
Issue -
State: closed - Opened by rsanheim over 12 years ago
#52 - README in generated app is not accurate.
Issue -
State: closed - Opened by mtnygard over 12 years ago
#51 - App generation fails using RVM 1.12.0 or higher
Issue -
State: closed - Opened by karnowski over 12 years ago
Labels: ready-for-showcase
#50 - Elastic CI: Build AMI image for Elastic CI build slave
Issue -
State: closed - Opened by sumbach over 12 years ago
- 1 comment
Labels: in-progress
#49 - Elastic CI: Spike: Investigate issue where Amazon EC2 Jenkins plugin exceeds specified instance cap
Issue -
State: closed - Opened by sumbach over 12 years ago
#48 - Elastic CI: Improve “Amazon EC2” Jenkins plugin
Issue -
State: closed - Opened by sumbach over 12 years ago
#47 - Elastic CI: As a devops, I can add a new CI build slave to ci.thinkrelevance.com
Issue -
State: closed - Opened by sumbach over 12 years ago
Labels: in-progress
#46 - Build Fraa Jaad
Issue -
State: closed - Opened by aredington over 12 years ago
- 5 comments
Labels: discussion-needed
#45 - add ruby 1.8.7 support
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 2 comments
#44 - Xvfb should be available to all CI builds
Issue -
State: closed - Opened by sumbach over 12 years ago
#43 - Add parameterized nightly builds
Issue -
State: closed - Opened by sumbach over 12 years ago
- 1 comment
#42 - Provide an alternative to ssh-agent for specifying SSH public keys
Issue -
State: closed - Opened by sumbach over 12 years ago
#41 - Output from Chef should print to local console
Issue -
State: closed - Opened by sumbach over 12 years ago
- 1 comment
Labels: ready-for-qa
#40 - fix bundle install not installing into the new gemset
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#39 - Spike: Investigate integrating with appscrolls
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#38 - add relevance user to elzar
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#37 - Spike: Understand Jenkins' capabilities for off-machine & concurrent builds
Issue -
State: closed - Opened by karnowski over 12 years ago
- 4 comments
#36 - Do not run Rails apps as a user with passwordless sudo
Issue -
State: closed - Opened by aredington over 12 years ago
- 1 comment
#35 - provision_config generator detects default database for existing apps
Issue -
State: closed - Opened by cldwalker over 12 years ago
#34 - relevance_rails --help should print its own help
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#33 - check for a clean repo in generators that run git commands
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#32 - fail fast in generators for shell commands i.e. git
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#31 - Abort early if rvm current doesn't return an rvm version
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#30 - detect and enforce a reasonable rvm version
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 3 comments
#29 - make elzar a gem dependency
Issue -
State: closed - Opened by cldwalker over 12 years ago
#28 - make rails g provision_config easier to use for existing app users
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#27 - Investigate Rails 3 generators regarding non-zero exit codes
Issue -
State: closed - Opened by karnowski over 12 years ago
#26 - Provide rake task that provisions and generates cap config
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#25 - have elzar's ruby match the ruby version in relevance_rails
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 3 comments
#24 - Add working Cap files for existing Rails apps
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#23 - Add more libraries to elzar
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
Labels: ready-for-qa
#22 - Add a nightly CI provision test builds
Issue -
State: closed - Opened by karnowski over 12 years ago
#21 - As a user, I can add Elzar and its recipes to an existing rails app
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#20 - Defect: Mac devs can't deploy to ec2 with bundle package
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#19 - Add test to ensure that `relevance_rails new` command fails fast
Issue -
State: closed - Opened by ldenman over 12 years ago
- 2 comments
#18 - Defect: relevance_rails reports rails version
Issue -
State: closed - Opened by karnowski over 12 years ago
- 1 comment
#17 - Defect: Fail fast on EC2 provision
Issue -
State: closed - Opened by karnowski over 12 years ago
- 1 comment
#16 - Defect: ancient rubygems version when using Ruby 1.9
Issue -
State: closed - Opened by karnowski over 12 years ago
- 1 comment
#15 - Defect: `rails g provision_config` does not warn when ssh agent identity not found
Issue -
State: closed - Opened by ldenman over 12 years ago
- 4 comments
#14 - fix local development of relevance_rails rails apps
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#13 - Add a CI build for unit tests
Issue -
State: closed - Opened by karnowski over 12 years ago
- 1 comment
#12 - development generator should live in the gem
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#11 - generator only generates code
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 2 comments
#10 - Support PostgreSQL
Issue -
State: closed - Opened by aredington over 12 years ago
- 3 comments
Labels: ready-for-showcase
#9 - Acceptance test deployment environments
Issue -
State: closed - Opened by aredington over 12 years ago
- 2 comments
#8 - Test outcome of chef convergence
Issue -
State: closed - Opened by aredington over 12 years ago
#7 - Provide documentation on ~/.relevance_rails/aws_config.yml for users of the gem
Issue -
State: closed - Opened by mtnygard over 12 years ago
- 1 comment
#6 - Defect: Allow multiple generators
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
#5 - allow provisioning of multiple servers
Issue -
State: closed - Opened by cldwalker over 12 years ago
#4 - allow relevance_rails to work in non-rvm environments i.e. rbenv
Issue -
State: closed - Opened by cldwalker over 12 years ago
- 1 comment
Labels: ready-for-showcase
#3 - Support Ruby 1.9
Issue -
State: closed - Opened by aredington over 12 years ago
- 4 comments
#2 - Automate Deployment Environment Management
Issue -
State: closed - Opened by aredington over 12 years ago
- 3 comments
#1 - Enable all employees access to provisioned machines
Issue -
State: closed - Opened by aredington over 12 years ago
- 1 comment