I was about to ask this question - but have managed to find a solution.
Adding question anyway in the hope that it might help others.
AND because I was initially scared to do anything with wizard in case jenkins config got wiped .. or something. So despite seeing the wizard I went all around the houses moving config files, editing different settings before finally finding the very easy solution!
Upgrade from jenkins.war 2.263.3 to 2.375.1 gave some trouble.
Jenkins with workflow and pipelines.
PROBLEM:
Dashboard shows "[user] is missing the Overall/Administer permission"
You can actually use menus and see jobs to some extent but various parts of GUI are not working.
SOLUTION:
Try to login as admin user.
Instead of Dashboard showing the jenkins setup wizard was showing.
Click in the wizard to skip setup and get rid of it.
After that Dashboard shows ok for the admin user and also for other users.
Another thing to watch with this jump upgrade - ssl library has changed and jenkins internal .ssh/config had to have some changes to control legacy ssh keys.
Login as admin user.
Instead of Dashboard showing the jenkins setup wizard was showing.
SOLUTION:
Click in the wizard to skip setup and get rid of it.
After that Dashboard shows ok for the admin user and also for other users.
I want to do automatic build in Jenkins when code gets pushed into the Gitlab.
For the same doing webhooks configuration in Gitlab, but getting error :
Url is blocked: Requests to the local network are not allowed.
Even not able to do the activity mentioned in the image :
I am not able to go to the admin area.
if you have the gitlab server locally
from doc
This behavior can be overridden by enabling the option “Allow requests to the local network from web hooks and services” in the “Outbound requests” section inside the Admin Area > Settings (/admin/application_settings/network):
url to the entire article here
Use the root login and check the outbound option, you should be good.
Let me know if you get any other error.
I had faced the same issue yesterday, but all good now.
I am trying to use bitbucket docker image as documented in the below link.
https://bitbucket.org/atlassian/docker-atlassian-bitbucket-server
I progressed to
bring up the container.
hit the url and create admin user.
But it does not log me in.
The message is invalid userId/password.
The reset wont work because being a container, the mail service is not set up.
I cannot proceed past this and it is frustrating.
Any help is appreciated.
I have a problem with one of my coworkers is not able to see the build icon next to each job. I already tried to make the permissions in Manage Jenkins -> Configure Settings -> Project-based Matrix Authorization Strategy to be the same as mine but I can see the icon and my coworker can't, so any help would be appreciated.
I'm attaching a picture so everyone knows what I'm talking about. It's the red square box that my co-worker is not able to see.
Ensure that your colleague has the Job->Build permission for those jobs, log out, clear cache in browser for jenkins, log in. It's possible their browser has an old version of the page cached or their client hasn't responded to a permissions change yet?
I setup travis-ci for a new rails project, but for some reason the build status is always shown as unknown in my README. I have googled a bit and not been able to find any solutions. Although I have had some similar symptoms as others. E.g., all of my builds show they are still building, but if you look at the individual builds they are passed or failed.
BTW, should this be reported as a travis-ci issue?
I ran in to the same issue. I was able to address the issue by adding the branch parameter to the image url:
This url did not work
https://travis-ci.org/kandadaboggu/iprofiler.png
This url worked
https://travis-ci.org/kandadaboggu/iprofiler.png?branch=master
.com will not work here, as per latest. This works for me
## Travis-Build
[](https://travis-ci.org/sananand007/genTspsolver)
Travis-Build
I use the Travis badge in our project's README in Github and I had the same issue. It turned out I did not have the correct settings in Travis.
From your Travis dashboard, go to More options => Settings. For me, I needed to turn on "Build pushed branches." After that, I clicked More options => Trigger build, and triggered a build.
Once Travis ran (and passed), I went back to Github and hard refreshed the page. The Travis badge had updated to green, or "build: passing".
In my case, the links I used were based on travis-ci.org when as of May 2018, all links should use travis-ci.com
See this announcement
This registered unknown
https://travis-ci.org/jlboat/FastaUtils.png?branch=master
This registered passing
https://travis-ci.com/jlboat/FastaUtils.png?branch=master
My issue was just that I this was my first build on travis-ci.org after I made my app public instead of private. I just had to wait for the image to be updated to reflect the new build status, which took a couple minutes. It is a free service on the .org rather than the paid service on the travis-ci.com so we have to wait on the shared resources to create the build status image.
In my case, the issue resolved by opening the image url on browser. You can get the image url from the Status Image popup by clicking build status badge on your project dashboard. The build status changed immediately after the image url fully loaded on the browser. For example click me
Follow a simple rule: use link of your travis repository dashboard.
In my case it's https://travis-ci.com/<username>/<repository>