Hi All,
Noobie question here, just installed Jenkins:lts-apline (really great implementation btw) and during the setup process the Jenkins URL is presented to me to edit. By default it's http://localhost:8080/ how can I change this and/or expose Jenkins to my local network, or even through my router so that git hooks can be implemented?
Thanks in advance
I was hoping to setup a Dockerfile that would contain the base settings and config for my CI tasks like installing PHPUnit PHPab CS etc as well as he toolchain to execute on push builds. This would enable me to destroy the container at will and rebuild to the fully functioning test setup. Sorry if my terminology has muddied the water
8 replies
however when i ran the command docker run jenkins/jenkins
or trying to set a specific using docker run -p 8181:8181 jenkins/jenkins
or trying to set a specific using docker run -p 8181:8181 jenkins/jenkins
i was not able to reach the jenkins web site with neither port 8080 or 8181, can you let me know why ? i am running the ubuntu vm on virtual box
Hello everyone I am Harshad Dabhade
And I am very interested in Jenkins.
I wanted to contribute to a project where a plugin to automate polling of image changes and security scans, need to be developed but I am not getting the Github repository, of this project can anyone help me out.
And I am very interested in Jenkins.
I wanted to contribute to a project where a plugin to automate polling of image changes and security scans, need to be developed but I am not getting the Github repository, of this project can anyone help me out.
so this channel is for "jenkins docker packaging and plugins". I don't think your question (and you didn't really ask one) is related to that. There is a tutorial on making plugins - https://www.jenkins.io/doc/developer/tutorial/
Hello @viveksahu26 , their is dedicated for newcomers channel - https://gitter.im/jenkinsci/newcomer-contributors - to ask any questions you have. Also you may start contributing at https://www.jenkins.io/participate/
Hello,
I'm trying to setup a multi-environment Jenkins instances orchestrated by Swarm. And i'm looking for customizing the UI including .svg logos in header and login screen.
I'm using the theme plugin with a css file under userContent to differentiate the environments by colors and that works just fine since it's isolated from the war content.
the jenkins logo is embedded in jenkins.war. If i want to update the logo per environment i need to overwrite the file once the war/ dir is inflated inside the jenkins_home then restart. This is annoying knowing that when i upgrade the version (most recent file of war/images/jenkins-header-v2.svg replaces the manipulated one when the new war explodes).
So as a workaround and since i'm also manipulating the scripts (jenkins.sh & install-plugins.sh) i included a step to run the java -jar jenkins.war then kill it once the war explodes, replace the files and then run the same command in background with a complete list of JAVA_OPTS and JENKINS_OPTS this time.
This automates the process and i don't have to manually replace the logos.
I don't feel like this is the best solution but i couldn't find any other lead. note that extracting the war kind of distorts the Manifest file and makes it impossible to run the app without rebuilding it which means more scripting.
I'm curious to know if there are folks out there doing something similar.
I'm trying to setup a multi-environment Jenkins instances orchestrated by Swarm. And i'm looking for customizing the UI including .svg logos in header and login screen.
I'm using the theme plugin with a css file under userContent to differentiate the environments by colors and that works just fine since it's isolated from the war content.
the jenkins logo is embedded in jenkins.war. If i want to update the logo per environment i need to overwrite the file once the war/ dir is inflated inside the jenkins_home then restart. This is annoying knowing that when i upgrade the version (most recent file of war/images/jenkins-header-v2.svg replaces the manipulated one when the new war explodes).
So as a workaround and since i'm also manipulating the scripts (jenkins.sh & install-plugins.sh) i included a step to run the java -jar jenkins.war then kill it once the war explodes, replace the files and then run the same command in background with a complete list of JAVA_OPTS and JENKINS_OPTS this time.
This automates the process and i don't have to manually replace the logos.
I don't feel like this is the best solution but i couldn't find any other lead. note that extracting the war kind of distorts the Manifest file and makes it impossible to run the app without rebuilding it which means more scripting.
I'm curious to know if there are folks out there doing something similar.
3 replies
jenkinsci/docker#985 has broken publishing of docker images, publish.sh needs a rework to handle the new directory structure
Just need my internet to be fixed...should be tomorrow
since the new release went out today, people are noticing the docker images are not released
so we might want to update twitter or something
users list maybe?
Hey all! I'm new to using Jenkins and have a question that I haven't had luck answering elsewhere. So I am using the blueocean image of jenkins in docker. My container is working properly and I was able to configure connections with github and deployment with publish over ssh. Now it's time to share this with my coworkers and I'm wondering if there is a way to keep all of my configurations so they don't have to go through the manual setup (and probably make errors). If i build a new image from my container it won't contain all of the internal configurations correct? Do I understand correctly that I need to add them into volumes? Thanks for helping a newbie!
@HannahKeith You can use a volume for JENKINS_HOME (in the image it is /var/jenkins_home). Then all of the config would be written to that directory on the host. You would need to share that directory with your coworkers and give them the correct volume mapping for that. Does that answer the question?
detecting if the file is there or not is easy, but detecting if its the fixed version is hard
@halkeye
$ jenkins-plugin-cli --version
2.1.0
you need at least 2.1.1, shouldn't be a hard check?
The "Installing - Docker" section now uses Jenkins plugin manager CLI to install the Blue Ocean plugin and all its dependencies rather than relying on the blueocean image. https://www.jenkins.io/doc/book/installing/docker/ . Same for the tutorials like maven https://www.jenkins.io/doc/tutorials/build-a-java-app-with-maven/ , Python https://www.jenkins.io/doc/tutorials/build-a-python-app-with-pyinstaller/ , and Node https://www.jenkins.io/doc/tutorials/build-a-node-js-and-react-app-with-npm/ . Still an issue in the Node.js tutorial with access to the resulting demo site, but that seemed less valuable than being able to switch from the blueocean image to the official Jenkins image.
https://stackoverflow.com/a/37939589 will probably work if can assume there no extra fields
@timja \o/ do i need to make a PR to update the image?
. /usr/loca/bin/jenkins-support && versionLT ver1 ver2
maybe?
I'm pretty partial to the simple one at https://github.com/jenkinsci/helm-charts/pull/117/files#diff-f43ba057eb61e2b6fe86125c6edcdc0b2f7a9f47d3f2687394b4918a1882a56aR212 but i'll take a deeper look after work