Issues
- 1
- 1
Adding Elestio as deployment option
#1928 opened by kaiwalyakoparkar - 5
Remove Almalinux image or upgrade it to Java 17
#1894 opened by lemeurherve - 10
Remove Java 11 images on weekly release line
#1890 opened by basil - 3
new Jenkins version not released for jdk11
#1927 opened by grayudu - 6
No plugins installed
#1896 opened by tanrax - 2
versionLT in jenkins-support doesn't treat newer version of workflow-cps as newer
#1880 opened by PiersRBME - 5
Djenkins.install.runSetupWizard=false is not working as expected
#1866 opened by githubofkrishnadhas - 2
docker start container failed
#1850 opened by Zhenbin24 - 10
- 8
Add ARM64 Support for Alpine JDK 11 and 17 - Inbound Agent
#1844 opened by Slyrc - 2
- 1
The repository 'https://packagecloud.io/github/git-lfs/debian bookworm InRelease' is not signed.
#1840 opened by ld-singh - 2
CVE-2024-23897 still exists in latest LTS version jenkins/jenkins:2.440.1-lts-jdk11
#1834 opened by jayclover - 5
`jenkins-plugin-cli` reports `War not found, installing all plugins: /usr/share/java/jenkins.war`
#1803 opened by dominykas - 2
- 0
JenkinsProject
#1802 opened by DanielMbah - 4
Windows - There should be a set of weekly and LTS short tags not including Jenkins version in their names
#1783 opened by lemeurherve - 0
After Jenkins docks with ldap, the first login the next day will display a password error. The second login will be successful, and submitting the pipeline using Jenkins' API will fail. Jenkins logs indicate that the connection to ldap has timed out
#1786 opened by MybatisYang - 3
every update failes from downloading `plugins/ssh-slaves`
#1585 opened by ccppoo - 5
windowsservercore-2019 image not updated
#1736 opened by Jonny-vb - 2
`windowsservercore-2019` images use `windowsservercore-1809` as base image
#1775 opened by lemeurherve - 16
First unlock jenkind
#1624 opened by kazek127 - 2
The master Jenkins of the latest LTS JDK17 version reports an error when using SSH to connect to a slave node
#1689 opened by zhangsg1234 - 2
latest with jdk17 & almalinux
#1768 opened by drhae - 0
Set JDK17 as the default JDK for Windows image
#1772 opened by lemeurherve - 2
- 0
The directory separator used in the Windows build script is dependent on the OS
#1763 opened by lemeurherve - 13
- 3
Ship production build of Java 21 from Eclipse Temurin
#1737 opened by basil - 3
Upgrade curl to >=8.4.0 to fix CVE-2023-38545
#1740 opened by hartmut-co-uk - 4
CVE-2023-38039, CVE-2023-38408, CVE-2023-38039, CVE-2023-38039, CVE-2023-44487
#1742 opened by srikavya-kola - 3
- 6
apt fails on fips-enabled hosts
#1694 opened by mkim37 - 6
apt-get update fails with signatures couldn't be verified because the public key is not available
#1695 opened by akandimalla - 16
Latest alpine image uses unsupported JRE
#1690 opened by Bitals - 4
Can not install plugin
#1681 opened by wg-peng - 5
- 6
Use Debian bookworm base image instead of bullseye to decrease unfixed vulnerability count
#1686 opened by gokhansengun - 2
Allow container build immediately after publication to repo.jenkins-ci.org
#1671 opened by MarkEWaite - 1
- 2
Problem with "sign in" in the docker Desktop
#1664 opened by Zhamemo - 1
Centos7: download Temurin's binaries instead of relying on their docker image
#1642 opened by gounthar - 4
Error while trying to build image
#1615 opened by LuizDMM - 5
- 3
- 1
I want to replace the "002" in "/kaniko/executor -f ./src/Luck.Walnut.Api/Dockerfile -c . --destination=registry.cn-hangzhou.aliyuncs.com/luck-walunt/walunt-devflow:002" with the values of the parameters BRANCH_NAME and VERSION_NAME, but I have tried several ways such as "$params.BRANCH_NAME", '$params.BRANCH_NAME', '${params.BRANCH_NAME}', etc., and none of them can be recognized correctly. What should I do to correctly replace the value?
#1618 opened by KawhiWei - 5
manifest not found
#1565 opened by aizzycb - 7
images are all lts - no weekly images
#1567 opened by PiersRBME - 1
Fail to start docker in jenkins
#1568 opened by jessemoe