I had tried to use CircleCI to run some tests on my spring project.I have added the config.yml as required, but since I found some of my builds fails. I delete the config.yml and unfollow the git repository to use a different template for the config.yml. But, now CircleCI won’t detect the new .circleci directory even though it is on the GitHub repository. .circleci on GitHub
This concerns an incident with CircleCI, as can be found on their website:
And on their Twitter channel:
So UI requests were temporarily disabled, but the issue has been resolved a few hours later.
Related
Relevant setup information: gradle 4+, relatively new installation of Artifactory (Pro 6+), artifactory gradle plugin version 4+
When attempting to run the build command on a local development environment in both Eclipse Photon and IntelliJ (late 2017 version), I run into dozens and dozens of 403 errors when making a HEAD request for dependencies. But, if I login to Artifactory through a web browser as the user that gradle is using and go to the exact same URL, it has no problem reaching the resource that gradle failed to reach. The problem occurs with every user on Artifactory, even one with admin privileges. The jars I'm looking for are part of a virtual repository with dependencies both internal to the artifactory installation and external. Finally, the build used to work just fine a month ago, and nothing I can think of has changed to permissions.
tl;dr only when logging in from gradle and using Artifactory plugin, a virtual Artifactory repo returns 403 errors on nearly every dependency for every user
This question: Docker pull from artifactory fails with credentials issue seemed close, but is using docker+jenkins (I'm not) and has no answers.
When I finally dug into the system logs, I found many lines like this one: "Rejected artifact download request: User XYZ is not permitted to deploy 'SOME JAR' into 'SOME CACHE JAR'"
It appears that users must have DEPLOY permissions in order to download an artifact that will be cached (behavior of virtuals/remotes.) This may also explain why the build used to work - the cached jars wouldn't have needed updates a month ago when I'd just added the remote and downloaded everything.
Adding deploy permissions to my user for the relevant repositories fixed the issue.
I need a little (maybe a lot more than a little) direction in combining these two services to work together. I have added the COVERALLS_REPO_TOKEN enviornment variable in the CircleCI settings online. I also have a .coveralls.yml file that has the following:
service_name: circleci
repo_token: the automated generated token
The CircleCI documentation does point this out, but I this leaves me confused. The repo is enabled on Coveralls, but from then on it is not very clear.
Anyone know of a solution?
I have cross-posted this question to the CircleCI Discourse forum.
For a java, gradle project that generates code coverage reports using jacoco, along with adding COVERALLS_REPO_TOKEN environment variable, I had to use the gradle coveralls plugin
In CircleCI, I see the below logs after using the gradle plugin:
> Task :coveralls
service name: circleci
service job id: null
repo token: present (not shown for security)
[message:Job #39.1, url:https://coveralls.io/jobs/XXXjobId]
I didn't have to add the .coveralls.yml file
I need to configure CI pipeline in my TFS with source repo in GitLab, I have updated the Trigger section as below and checked in the code, but the build was not triggered, is there any configuration required in the GitLab repo? Please advice hot to achieve this.
I would troubleshoot your problem by checking the following in this order:
when triggering the build manually, does the source code downloading from the GitLab repository successfully work?
if yes, then:
did you created and pushed the develop branch on the repository?
You need to publish your locally created 'develop' branch on the remote repository, e.g. >git push -u origin develop
if no, then there are issues on the "Services" entry you created on TFS for accessing your GitLab repository:
check whether you are using HTTPS in the URL;
to enable HTTPS access to your repository, remember to set a password on your GitLab account, then use that password along with your username (email address) on the "Services" endpoint set up on TFS;
p.s. also, check which 'Connection' is selected in the Repository section of your build definition: it should be the one pointing to your GitLab repo :-)
I have changed the Poling interval to 180 seconds and it worked.
I have been trying to deploy from a GitHub repository to Heroku. For pushing my changes to GitHub I am using Mac UI Client for GitHub.
Now in the heroku app setup, I changed at https://dashboard.heroku.com/apps/myapp/settings . Here I made changes in option GitHub Rep (Link your app to a GitHub repository to see commit diffs in the activity log.). I added as my github-user/repository-name
Now when i use myappname.heroky.com I am redirected to a default page which says :
Heroku | Welcome to your new app! Refer to the documentation if you
need help deploying.
In the documentation it is all commands which is going over me since i use Github UI tool.
Any idea if this can be deployed w/o using the commands?
I am asking this particular thing, since last time I used AppHarbor and it simply pulled my github rep w/o any hiccups.
Adding your GitHub repo to the Heroku app settings will not set up automatic deployments. It just allows Heroku to provide commit information in the app logs.
To achieve what you are looking for, you need to set up continuous deployment (or "CD"). The easiest way to do this is with a continuous integration (or "CI") solution.
One common CI server is Jenkins, though that will require you to set it up manually. Nowadays, there are several automated CI/CD services you can take advantage of, including Travis, CircleCI, Codeship, Snap. All of them have options to automatically deploy to Heroku after building your app (which can be trigger by a push to GitHub).
I can't seem to get Github integration working with my application on AppHarbor. I don't see any errors in the build details, it's just a blank txt in the details... and it never switches to active with the status staying as the red no circle.
I followed the instructions on configuring my github repository with slug and token in the service hooks. The application deploys fine when I push directly to app harbor git.
Is there a trick or a gotcha that I might be forgetting?
If it's a private repository you have to add the apphb user on Github as a collaborator.
For future references, another thing to note is, that it only push the code when it gets commited. Therefor, if you commit, then set up github, you will need to commit again in order to get it pushed.