Hi, we have been using the Alpine version of PostgreSQL for a while. Our production environment has upgraded to v11.7 and I wanted to update the CircleCI version to the same.
There is no Alpine version of 11.7 available… do they usually trail in the release date/time? Or is there another reason a 11.7-Alpine is not available?
Also, is there way
(Newbie here, so trying to learn and understand).
Heya @OisinMoran - we can turn off this feature per-project if you submit a support ticket 
We are working to improve this feature with self-service opt-out.
I am trying to decide if we need a paid account or not. Are the number of projects limited or just the build minutes on the free tier? How about the number of users, is that limited? Thanks for any advice!
So I am having a hard time figuring out how to fix a failing test right now. I recently made a new branch on my project where I wrote a ruby migration that sets a column in one of my postgres tables to auto-increment. I’ve run my tests locally and everything is working fine. When I pushed my code though the circleCI tests fail and I keep getting this particular error
rails aborted!
ActiveRecord::StatementInvalid: SQLite3::SQLException: near "(": syntax error: CREATE TABLE "place_destinations" ("id" serial NOT NULL PRIMARY KEY, "place_id" integer, "destination_id" integer, "hyperlocal_destination_id" integer DEFAULT nextval('hyperlocal_destination_id_seq'::regclass))
this is the migration
def up
execute <<-SQL
CREATE SEQUENCE hyperlocal_destination_id_seq START 1;
ALTER SEQUENCE hyperlocal_destination_id_seq OWNED BY place_destinations.hyperlocal_destination_id;
ALTER TABLE place_destinations ALTER COLUMN hyperlocal_destination_id SET DEFAULT nextval('hyperlocal_destination_id_seq');
SQL
end
My schema.rb for this column looks like this and was generated by the rails
t.integer "hyperlocal_destination_id", default: -> { "nextval('hyperlocal_destination_id_seq'::regclass)" }
And this is what the config.yml looks like
version: 2
jobs:
build:
docker:
# Find other images @ https://circleci.com/docs/2.0/circleci-images/
- image: circleci/ruby:2.6.2-node
environment:
RAILS_ENV: test
PGHOST: 127.0.0.1
PGUSER: root
- image: circleci/postgres:9.6.2-alpine
environment:
POSTGRES_USER: root
POSTGRES_DB: circle-test_test
working_directory: ~/repo
steps:
- checkout
# Download and cache dependencies
- restore_cache:
keys:
- v1-dependencies-{{ checksum "Gemfile.lock" }}
# fallback to using the latest cache if no exact match is found
- v1-dependencies-
- run:
name: install dependencies
command: |
bundle install --jobs=4 --retry=3 --path vendor/bundle
- save_cache:
paths:
- ./vendor/bundle
key: v1-dependencies-{{ checksum "Gemfile.lock" }}
# Database setup
- run: bundle exec rake db:create
- run: bundle exec rake db:schema:load
# run tests!
- run:
command: bundle exec rake test
when: always
# collect reports
- store_test_results:
path: test/reports
- store_artifacts:
path: /tmp/test-results
destination: test-results
any help would be appreciated!
I have a project that I cannot get to build on CircleCI. All tests pass locally. If the build fails, and I rerun the build with ssh, I can connect and run all of the commands successfully, and all tests pass in the ssh session.
The build is failing at bundle exec rake db:create
I’ve tried rearranging my require statements in config/application.rb to no avail. Any ideas?
Here is the full backtrace:
bundle exec rake db:create --trace
rake aborted!
/usr/local/lib/ruby/2.4.0/uri.rb:99: warning: already initialized constant URI::VERSION_CODE
/usr/local/lib/ruby/2.4.0/uri.rb:99: warning: previous definition of VERSION_CODE was here
/usr/local/lib/ruby/2.4.0/uri.rb:100: warning: already initialized constant URI::VERSION
/usr/local/lib/ruby/2.4.0/uri.rb:100: warning: previous definition of VERSION was here
NameError: uninitialized constant URI::Generic
Did you mean? URI::Generic
/usr/local/lib/ruby/2.4.0/uri/ftp.rb:23:in `<module:URI>'
/usr/local/lib/ruby/2.4.0/uri/ftp.rb:13:in `<top (required)>'
/usr/local/lib/ruby/2.4.0/uri.rb:107:in `require'
/usr/local/lib/ruby/2.4.0/uri.rb:107:in `<top (required)>'
/usr/local/lib/ruby/2.4.0/uri/rfc2396_parser.rb:13:in `require'
/usr/local/lib/ruby/2.4.0/uri/rfc2396_parser.rb:13:in `<top (required)>'
/usr/local/lib/ruby/2.4.0/uri/common.rb:13:in `require'
/usr/local/lib/ruby/2.4.0/uri/common.rb:13:in `<top (required)>'
/usr/local/lib/ruby/2.4.0/uri/generic.rb:12:in `require'
/usr/local/lib/ruby/2.4.0/uri/generic.rb:12:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/core_ext/object/json.rb:6:in `require'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/core_ext/object/json.rb:6:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/core_ext/object.rb:13:in `require'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/core_ext/object.rb:13:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/configuration.rb:4:in `require'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/configuration.rb:4:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/railtie/configuration.rb:3:in `require'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/railtie/configuration.rb:3:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/railtie.rb:223:in `require'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/railtie.rb:223:in `config'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails/railtie.rb:127:in `config'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/i18n_railtie.rb:11:in `<class:Railtie>'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/i18n_railtie.rb:10:in `<module:I18n>'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/i18n_railtie.rb:9:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/railtie.rb:4:in `require'
/usr/local/bundle/ruby/2.4.0/gems/activesupport-5.2.4.1/lib/active_support/railtie.rb:4:in `<top (required)>'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails.rb:17:in `require'
/usr/local/bundle/ruby/2.4.0/gems/railties-5.2.4.1/lib/rails.rb:17:in `<top (required)>'
Turns out this was a issue with the Bintray API - they had introduced some changes to prevent denial of service attacks, and these were blocking the requests from CircleCI.
I have the same problem, but worked around using a script that posts the non-public artifact links to a Slack channel.
Cool!
Yet another workaround is to click on one of the other tabs, say Parameters, and then edit the URL, changing #build-parameters to #artifacts.
Hey @justin.kay!
Welcome to CircleCI Discuss!
Users on the free plan have access to Windows and Linux build VMs, and can run 1 job at a time. The build credits are limited to 2,500 per week.
The performance plan grants access to larger resources, more build credits, optimization, and autoscale features. More information can be found on our Pricing and Plans page.
If you are building an open source project, get additional benefits such as 400,000 free credits per month. You can find more information on our CI for Open Source page.
Hello Vinoth!
Thanks for writing into CircleCI discuss!
Now I have 2 Organisations listed in CicleCI(One is on my Github username & other is on my exact Github org name)
Your Github account and organization will both show as an organization on CircleCI. This is normal behavior.
Under my User Profile, I cannot see Admin settings visible so that I cannot add anyone from my current team.
Could you write into our support team so we can take a closer look as to why this might be happening?
Hello sxh!
Welcome to CircleCI Discuss!
It appears an Orb is being used in this case, if the Orb defines the variable type as integer, it won’t be able to accept an environment variable. The parameter type for a parameter you’d like to assign as an environment variable is env_var_name.
If you are using someone else’s Orb, you can grab the source code using the CLI command circleci orb source namespace/orbname, make any changes and republish under your namespace.
Thanks for the info!
The Go orb v1.0.0 was released yesterday. https://circleci.com/orbs/registry/orb/circleci/go
I am trying to setup android emulator and launch after it, using the commands -
But the problem is when I am running the config.yml file on circleci its showing , emulator out of date Below is the attached error description, and I am using windows 10, eclipse ide, java language, appium, android mobile app-
#!/bin/bash -eo pipefail
cd {ANDROID_HOME}/emulator;ls
export LD_LIBRARY_PATH={ANDROID_HOME}/emulator/lib64:${ANDROID_HOME}/emulator/lib64/qt/lib
emulator -avd test -skin 1440x2560 -memory 2048 -no-window -noaudio -no-boot-anim -no-window -accel on
LICENSE emulator lib64 resources
NOTICE.csv emulator-check mksdcard source.properties
NOTICE.txt emulator64-crash-service package.xml
android-info.txt goldfish-webrtc-bridge qemu
bin64 lib qemu-img
emulator: WARNING: encryption is off
emulator: INFO: VideoFrameSharer.cpp:76: Initialized handle: videmulator5554
emulator: INFO: WebRtcBridge.cpp:263: Launching: /opt/android/sdk/emulator/goldfish-webrtc-bridge --daemon --logdir /tmp/android-unknown --port 41219 --handle videmulator5554 --turn
emulator: INFO: WebRtcBridge.cpp:273: Launched /opt/android/sdk/emulator/goldfish-webrtc-bridge --daemon --logdir /tmp/android-unknown --port 41219 --handle videmulator5554 --turn , pid:3393
emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: /home/circleci/.android/emulator-grpc.cer security will be disabled.
E0305 15:48:38.883310735 3383 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {“created”:"@1583423318.883291099",“description”:“SO_REUSEPORT unavailable on compiling system”,“file”:"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc",“file_line”:169}
Started GRPC server at 127.0.0.1:8554
Your emulator is out of date, please update by launching Android Studio:
I cant the perform the above actions, because I am running automated test acses and unable to see the emulator in run time, i can see only the screenshots and looks like by passing these details it is opening a tablet ui instead of mobile version, Please help
This is starting to roll out at the moment, it’s per-project so you may see scheduled pipelines for some projects and not others for the next few days, until we hit a 100% roll out (modulo any need to roll back).
-Gordon
@bcardiff were you able to certify your orb(s)?
Almost. We got the Partner label at https://circleci.com/orbs/registry/orb/manastech/crystal . The certified label is reserved only for CircleCI authored orbs.
The Partner labeled orbs do appear on searches directly at https://circleci.com/orbs/registry/, but they require the opt-in to use of third-party orbs… Which, is not ideal since that setting allows too much IMO
allow all members of my organization to publish dev orbs, use uncertified orbs, and use third-party orbs (not supported by CircleCI) in project configuration
The Xcode 11.4 Beta 3 image has just been released and can be selected as follows:
macos:
xcode: 11.4.0
The main changes in this image, from the Xcode 11.3.1 image, are:
/Applications/Xcode-11.4.beta.3.app
Runtime changes:
Potentially breaking changes:
Moving forward, Xcode images will no longer ship with Python 2. Homebrew have recently removed the Python 2 formula in favour of Python 3. For more information, including how you can maintain your own tap for Python 2, please see the PR for the Python 2 formula deletion.
Minor software changes:
The full manifest of installed software can be found here.
We have enabled few workflows which block until the user confirms. I was wondering if this holding time ever expires and if it accrues for CircleCI credits.
For those wondering, I solved this myself in the end. I added this:
- run: sudo apt-get update
- run: sudo apt-get install -y python-pip python-dev
- run: sudo pip install --upgrade awscli
- run: aws --version