New UI now available for opt-in!
Thanks @rsshilli for chiming in. We agree with all 5 of these points. #1 is being addressed as we speak, and have designs made for #3. #5 is something we must and will address before forcing this UI...
View ArticleTriggering Jobs w/ Api - Build parameters missing
That’s odd. Were they not in the job or not in the response?
View ArticleNew UI now available for opt-in!
Thanks for the quick reply! I also forgot: When I click on an artifact (and I often have to click on one for each test that failed), they open in the same tab now, instead of opening in new tabs like...
View ArticleNew UI now available for opt-in!
Hi @rsshilli happy to help! Thanks for that last data point. We make a point in the new UI to not open new tabs whenever possible as most developers prefer to choose for themselves where a new tab...
View ArticleTriggering Jobs w/ Api - Build parameters missing
This announcement went out this week: https://circleci.com/blog/introducing-circleci-api-v2/ You can now trigger pipeline first class and use parameters that can be resolved at trigger time (meaning...
View ArticleTest timings can't be found
I’m seeing the same thing on an Elixir app. Timings/parallelization was working fine until a few weeks ago. What version of CI are you using? We’re using v2 (not v2.0) and not workflows, and I think...
View ArticleOn macOS runners: WARNING: terminal is not fully functional
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
View ArticleCircleCi don`t connect with my vps
Hi. I have a problem and I cant find error in my code. My circleci I don't want to make a connection with my vps.Its error message: #!/bin/bash -eo pipefail ssh -T root:51.91.252.150 <...
View ArticleCircleCi don`t connect with my vps
This looks very similar to this issue: Getting an error when trying to deploy using SCP Please perform the troubleshooting steps discussed there, and double check your firewall rules.
View ArticleHow to get timings from jasmine/protractor
The test results feature requires a valid Junit Style XML file. It is possible that the output of your program does not conform to this schema. I wrote a validation tool that you can try here:...
View ArticleNo space left on device iii
Hi there, today our builds started failing: failed to register layer: Error processing tar file(exit status 1): write /usr/local/bundle/gems/mysql2-0.4.10/ext/mysql2/mysql2.so: no space left on device
View ArticleCircleCi don`t connect with my vps
Thank you for help.I read all article. But I have turn off my firewall.And I don`t know where I have problem.
View ArticleRun workflow with delay
Hey, Is there an option to set a job to run 24 hours after another job is done? I have a job that deploys to the staging environment, and a job that deploys to the production environment. The...
View ArticleClik here to view.
CircleCi don`t connect with my vps
One immedaite problem that I see is this: devsymfony: root:51.91.252.150 This is not a valid syntax for SSH. It should be root@ not root:
View ArticleRun workflow with delay
Hello, Welcome to our community! There is no built in way to schedule jobs like this right now. Note that you can schedule recurring jobs[1], but it follows the cron model (i.e. run at X time). There...
View ArticleNo space left on device
Could you provide more information about your build? Which executor you are using? If docker, which image?
View ArticleWindows image with CMake
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
View ArticleConditional expression documentation?
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
View ArticleCan no longer build docker images (returned a non-zero code: 239)
i am experiencing the same issue. Were you able to find the cause? seems a bunch of node images were updated 4 days ago, id say the issue is there somewhere
View ArticleCan no longer build docker images (returned a non-zero code: 239)
ok hope this helps, but managed to fix our issue. we used docker:stable-dind in the ci which then runs node:12-alpine (dockerfile). the issue was using: npm install -g -s --no-progress yarn@1.9.4 when...
View Article