Re: Recent Edge upgrade breaks Matrix Plugin view

[Mark Waite]

I'm running Chrome 126.0.6478.62 and not seeing the issue any longer.  I 
did see it with a Chrome 125 version

On Monday, June 17, 2024 at 10:46:54 AM UTC-6 Mark Waite wrote:

> I saw something similar with Google Chrome 125 and then confirmed that it 
> was resolved with Google Chrome 126.  Check for a more recent release of 
> Microsoft Edge.
>
> On Monday, June 17, 2024 at 10:44:31 AM UTC-6 geoffroy...@gmail.com wrote:
>
>> Hello
>>
>> we are facing an annoying issue, where Matrix Jobs are not rendered 
>> correctly with latest Edge version:
>>
>>
>>- Version 125.0.2535.92 (Official build) (64-bit) works fine
>>- Version 126.0.2592.56 (Official build) (64-bit) display is broken
>>
>>
>> It will not show icons in the matrix table, leaving the table "empty"
>>
>> Not sure how to debug this, i don't see specific error messages in 
>> browser console (F12).
>>
>> Note is works fine with Firefox and Chrome, but our corporate setup is 
>> Edge-centric...
>>
>> Any recommendations how to investigate the issue?
>>
>> Regards
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ed73b21b-468c-41e2-9fa7-d236f37e1028n%40googlegroups.com.

Re: Recent Edge upgrade breaks Matrix Plugin view

[Mark Waite]

I saw something similar with Google Chrome 125 and then confirmed that it 
was resolved with Google Chrome 126.  Check for a more recent release of 
Microsoft Edge.

On Monday, June 17, 2024 at 10:44:31 AM UTC-6 geoffroy...@gmail.com wrote:

> Hello
>
> we are facing an annoying issue, where Matrix Jobs are not rendered 
> correctly with latest Edge version:
>
>
>- Version 125.0.2535.92 (Official build) (64-bit) works fine
>- Version 126.0.2592.56 (Official build) (64-bit) display is broken
>
>
> It will not show icons in the matrix table, leaving the table "empty"
>
> Not sure how to debug this, i don't see specific error messages in browser 
> console (F12).
>
> Note is works fine with Firefox and Chrome, but our corporate setup is 
> Edge-centric...
>
> Any recommendations how to investigate the issue?
>
> Regards
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/340f249c-04a4-4b3b-9c54-366fd0406826n%40googlegroups.com.

Re: Issue with Jenkins and GitLab Integration

[Mark Waite]

On Saturday, April 27, 2024 at 3:46:30 PM UTC-6 erick@gmail.com wrote:

Subject: Issue with accessing GitLab repository from Jenkins

Problem Description:
We have configured Jenkins to access a GitLab repository hosted at 
`192.168.0.24:Berechit/easyformer.git`, but we are encountering 
authentication errors when attempting to retrieve changes from this 
repository. Despite several checks, we have been unable to resolve the 
issue.

Verified Elements:
- Correct configuration of SSH keys in GitLab and Jenkins.
- Permissions on the GitLab repository have been checked and appear to be 
correct.
- SSH keys have been manually tested from the Jenkins container and appear 
to be functioning correctly.
- Jenkins logs indicate an authentication error when attempting to retrieve 
changes from the repository.
WARNING: Unknown parameter(s) found for class type 
'jenkins.plugins.git.GitStep': credentials The recommended git tool is: 
NONE No credentials specified

That message likely means that your pipeline includes the step:

git credential: 'abc' url: 'your-git-repo-url'

The "credential" parameter is not a valid parameter for the "git" step.  
Use the Pipeline syntax snippet generator to use the correct parameter 
name. The Git client plugin documentation page includes a 90 second video 
that shows how to use the generator

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/910f6025-7cff-424d-b6df-5a4ca26d0fe8n%40googlegroups.com.

Re: Pipeline script from git - credentials?

[Mark Waite]

On Tuesday, April 16, 2024 at 5:36:58 AM UTC-7 you wrote:

Hi,

we are currently transforming all our SCMs to git. That worked for the jobs 
that rely on a global library and just have a function-call in the pipeline 
that's directly set in the job configuration.

However I have a couple of auxiliary jobs that are configured as 'Pipeline 
script from git'
Here I am experiencing some problems I am not used to from the old SCM:
- the selection 'credentials' is empty even though there are a couple of 
credentials in and escpecially one I use from a 'checkout' step from my 
library
- when I add new credentials with the button 'add' one line below the 
selection still does not show anything.
- the newly added credentials are shown in the global credentials 
administration list and I am not allowed it another time 

Is there a known bug in this area or is there something I am doing wrong?


You are probably seeing a limitation of the git plugin.  It accepts ssh 
private key credentials for git connections over ssh (either ssh:// or 
git@hostname:) and it accepts username / password credentials for git 
connections over HTTP (either http:// or https://). If your credential is a 
secret text or some other form of credential, the git plugin won't show it 
in the dropdown list because it only supports those two types of 
credentials.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/af180528-7f4d-4ccc-b9e7-750d91e63c4fn%40googlegroups.com.

Re: Jenkins not able to launch the slave due to unrecognizable JAVA_HOME

[Mark Waite]

On Monday, April 15, 2024 at 7:09:03 AM UTC-7 Sai wrote:

Hi,

I have the below machine config

*(Master Jenkins)*
OS RedHat Enterprise Linux 7.6
openjdk version "11.0.22" 2024-01-16 LTS
path: /usr/lib/jvm/java-11-openjdk-11.0.22.0.7-1.el7_9.x86_64/bin/java


The Jenkins project stopped supporting RHEL 7 in Nov 2023.  RHEL 7.9 is the 
most recent release of RHEL 7.  You're running RHEL 7.6, an outdated 
version of an unsupported operating system.  It might work, but the Jenkins 
project no longer tests or verifies that operating system 
 


* (Slave Jenkins)*
RHEL VERSION=7.9 (Maipo)
openjdk version "12.0.2" 2019-07-16
path: /etc/java/jdk-12.0.2+10/bin/java


Jenkins has never supported Java 12.  I don't recall anyone ever doing any 
Jenkins testing or Jenkins development with Java 12.  Java 12 is also not 
supported by the OpenJDK project.

Jenkins currently supports Java 11, Java 17, and Java 21.  

The installation location that you are listing for Java 12 is unexpected.  
Applications (like Java) are not intended to be installed in the "/etc" 
directory.  If you install Java 11 on the agent operating system using 
either Eclipse Temurin packages or operating system packages, it will not 
place Java in "/etc".

Your options include:

   - Install Java 11 on the agent and plan for future operating system 
   upgrades to replace RHEL 7 with something that is supported
   - Continue attempts with Java 12 on the agent after assuring that Java 
   12 is actually installed.  You'll be running an unsupported, untested 
   Jenkins configuration with an unsupported Java version
   - Install Java 17 on the controller and on the agent  and plan for 
   future operating system upgrades to replace RHEL 7 with something that is 
   supported
   - Install Java  21 on the controller and on the agent  and plan for 
   future operating system upgrades to replace RHEL 7 with something that is 
   supported


but still jenkins not recognizing JAVA path

so could anyone please help as it is urgent

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1c69941b-9fcf-4eae-a7cf-00e3e305009bn%40googlegroups.com.

Re: Websocket support

[Mark Waite]

On Wednesday, April 3, 2024 at 12:45:05 PM UTC-6 Carlos Sanchez wrote:

Hi, 

Trying to use websockets with the Kubernetes plugin I get "WebSocket 
support is not enabled in this Jenkins installation" 
I couldn't find much documentation but looking through the code [1] I 
assume this is only supported in jetty10 and app server support is needed?

Thanks

[1] https://github.com/jenkinsci/jenkins/tree/master/websocket



Websocket support works with the Jetty 10 that is bundled inside Jenkins.  
It does not work with other containers (like Tomcat or WildFly).  The "Other 
Servelt Containers" page 
<https://www.jenkins.io/doc/book/installing/servlet-containers/> says:

> In particular, support for WebSocket agents is only implemented for the 
Jetty servlet container. 
 
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/99df2c9f-d713-4426-802f-81abd7f8b732n%40googlegroups.com.

Re: Multibranch Pipeline with Git-plugin - no PR support ?

[Mark Waite]

On Tuesday, January 9, 2024 at 3:22:29 AM UTC-7 Torsten wrote:

Hi, 

my Jenkins Multibranch jobs are currently based on Bitbucket, using the " 
cloudbees-bitbucket-branch-source" plugin. I was using a configuration with 
- Discover branches
- *Discover pull requests from origin* 
resulting in multiple tab views to run builds for Branches and PR´s.

Now we need to migrate the git repositories to Github and I´m running into 
2 issues:

1.) Github plugin seems to only support User/pwd authentication - but I´m 
restricted to use ssh-key(s) only.


That is a serious limitation that your organization has placed on you.  It 
will limit many uses of GitHub in Jenkins and elsewhere.  The GItHub API is 
only accessible over HTTP.  The HTTP authentication requires username / 
password authentication with a GitHub personal access token or other form 
of token.  The HTTP authentication does not accept private keys as far as I 
know.

Without access to the GitHub API, you're severely limited on the types of 
operations that can be performed.  The GitHub branch source plugin and the 
GitHub organization folder plugin use the GitHub API to perform many of 
their operations.  The GitHub API is what makes those plugins such an 
improvement over the Git plugin.  The same is true for the Bitbucket branch 
source plugin.

I assume that you were allowing HTTP authenticated requests with 
Bitbucket.  Similar requests are needed for GitHub.  The best choice is to 
persuade your organization that they need to allow token based 
authentication with GitHub.
 

2.) Git plugin supports ssh-key(s) for authentication, but seems not to 
support "Discover pull-requests from origin".
(https://www.jenkins.io/doc/book/pipeline/multibranch/)

The Git plugin only supports "*Discover other refs*"

Is there a way to handle the PR´s in any way with the Git plugin ?


The git plugin uses command line git or JGit and limits itself to the 
concepts that are available from command line git.  Command line git does 
not have the concept of a pull request.  Command line git understands refs 
and branches.

If you can find the refspec that GitHub uses to store pull requests, you 
might be able to detect those pull request branches and create jobs for 
those pull request branches.  However, that is a much worse experience than 
the experience you'll have if you use the GitHub branch source plugin and 
the GitHub organization folder plugin and let them manage the creation and 
deletion of branches 

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/228e2f47-1ce3-4cec-ab07-0b382d6358c8n%40googlegroups.com.

Re: This node is offline because it uses an old

[Mark Waite]

On Thursday, February 8, 2024 at 11:47:29 PM UTC-7 dheinric wrote:

Am Donnerstag, dem 08.02.2024 um 08:20 -0800 schrieb tzach solomon:

"This node is offline because it uses an old" 


Old what?


An old agent.jar (or the deprecated term for agent, in the case of the 
older plugin version used by Tzach).  That is a message from the Versions 
Node Monitors plugin <https://plugins.jenkins.io/versioncolumn/>.  

The plugin provides a configuration option that allows administrators to 
disconnect agents that use a non-matching version of Jenkins remoting.  
However, disconnecting the agent  when a non-matching version of Jenkins 
remoting is often too aggressive.  Many administrators would rather have 
the same options provided by the plugin for JVM version.  The JVM version 
checks in the plugin can disconnect if the JVM major version on the agent 
is older than the JVM version on the controller (default mode) or if the 
JVM version on the agent is older than the JVM version on the controller 
(paranoid mode) or if the JVM version on the agent does not exactly match 
the JVM version on the controller (paranoid++ mode).

JENKINS-63607 <https://issues.jenkins.io/browse/JENKINS-63607> and 
JENKINS-72688 <https://issues.jenkins.io/browse/JENKINS-72688> track the 
issue.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/28220643-a706-490e-9fc9-e9201487430dn%40googlegroups.com.

Re: Debian update overwrites environment settings

[Mark Waite]

On Tuesday, January 2, 2024 at 12:22:51 PM UTC-7 Jochen wrote:


Hi,

I am using the Jenkins Debian packages from

https://pkg.origin.jenkins.io/debian/

to install, and update Jenkins. In general, I'm quite happy with that. 
There is one exception, though:

My setup requires changing of two environment variables, JENKINS_PORT, and 
JAVA_HOME. Right now, I have configured those by editing jenkins.service. 
In other words, I am advising systemd to set the proper values.

The problem with that: Any update of Jenkins (of which there are quite a 
few, thankfully) replaces the jenkins.service file, thus overwriting my 
changes. In other words: After each update, I need to reapply my changes to 
jenkins.service.

Is there any better location for those values, that survives updates?


There is a better location for those values and it will survive updates.  
The "Managing systemd services" 
<https://www.jenkins.io/doc/book/system-administration/systemd-services/> 
page describes the "systemctl edit jenkins" command that creates a local 
copy of the overrides file .  That copy is preserved across upgrades.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/179c8dc8-96ed-4376-986a-2ff5920401a1n%40googlegroups.com.

Re: Unable to Save Project

[Mark Waite]

On Monday, December 4, 2023 at 2:29:11 PM UTC-7 Eric wrote:

I've started going through the plugins that have issues and pretty quickly 
ran into the "conditional buildstep" plugin.  I can't disable this plugin 
because I use it.  Do you have any suggestions?

Thanks,
Eric


The conditional build step plugin was fixed in 1.4.0 
<https://plugins.jenkins.io/conditional-buildstep/releases/#version_1.4.0> 
for configuration form modernization.  The most recent release is 1.4.3.

If you haven't updated to latest releases of the plugins, that's certainly 
the first step.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c943b414-c6db-4031-9681-6e232ac1c71dn%40googlegroups.com.

Re: Unable to Save Project

[Mark Waite]

On Monday, December 4, 2023 at 1:40:26 PM UTC-7 Eric wrote:

Hi All!  I have a project that I am unable to make changes to.  I can't 
even make a comment in a field then save it down.  I can't even save it 
down without a comment.  It throws up a screen saying "Oops!  A problem 
occurred while processing a request."  Not sure where the physical log is, 
it's not in /var/log/jenkins/jenkins.log.  So I go to Manage Jenkins/System 
Log/All Jenkins Logs.  It has a big stack trace for the attempted save, 
I'll paste it below.  Any idea what my issue is?  Thanks!

Error while serving http://ipAddress:8080/job/ProjectName/configSubmit 
java.lang.IllegalArgumentException: The frontend sent an unexpected list of 
classes 


That almost always means that one or more of the plugins that are active on 
your system has not been updated for the configuration form modernization 
that happened in Jenkins 2.277.1.

You'll need to find and remove the plugins that have not been updated.  A 
detailed guide is available 
at https://community.jenkins.io/t/migrating-jenkins/894/5 

Mark Waite 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e1d0bbf2-663d-4f5a-9cb9-592cd11e1e90n%40googlegroups.com.

Re: Combine a multi-branch, and a multi-configuration project

[Mark Waite]

On Tuesday, November 14, 2023 at 7:26:38 AM UTC-7 jochen wrote:


Hi,

is it possible to combine multi-branch pipeline, and a multi-config project?

Or, in other words: I have a multi-branch pipeline project, which uses a 
fixed JDK, and a fixed Maven version. What I would like to have, would be a 
matrix of builds for every branch with different JDK's, and Maven versions.


How about a matrix build with declarative Pipeline as described 
in https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/

If you use scripted Pipeline, then you could consider a matrix build with 
scripted Pipeline as described 
in 
https://www.jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/

Darin Pope created a video that illustrates the ideas 
in https://www.youtube.com/watch?v=HsvO2nDlDSI

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f3e801e9-cb5a-43ed-b56a-c9fac950f2can%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

Two diagrams have been added to the Jenkins Enhancement Proposal 
<https://github.com/jenkinsci/jep/blob/cd176912ed8797ddee1066be59b1a68fb9b6bc77/jep//README.adoc>.
  
One diagram shows a single Java version (Java 25) to highlight the 
lifecycle of a single Java version in the Jenkins community.  The other 
diagram shows the transition across multiple Java versions.  The pull 
request <https://github.com/jenkinsci/jep/pull/400> includes the 
discussions.

The duration of the alert period that precedes the transition from one 
minimum Java version to the next minimum Java version is still being 
discussed.  The current implementation in Jenkins core provides begins 
notifying 18 months before the change and then notifies again 9 months 
before the change.  James Nord feels that it would be better to notify 12 
months before the change and refresh 6 months before the change.  The pull 
request conversation 
<https://github.com/jenkinsci/jep/pull/400#discussion_r1360372868> has the 
details.

Tim Jacomb (a JEP editor) has agreed that the proposal is ready to be 
assigned a JEP number and to enter "Draft" state.  I'll plan to do that 
within the next few days.

Assigning a JEP number does not prevent us from correcting or improving the 
JEP.  Changes, corrections, and improvements are allowed to draft JEPs.

Mark Waite

On Saturday, October 14, 2023 at 5:56:17 AM UTC-6 Mark Waite wrote:

> I've created a Jenkins Enhancement Proposal based on this draft.  Comments 
> are welcomed at https://github.com/jenkinsci/jep/pull/400 
>
> On Monday, September 25, 2023 at 7:20:07 AM UTC-6 Mark Waite wrote:
>
>> Java releases are delivered every 6 months with a long term support 
>> release every two years as announced in a September 2021 blog post 
>> <https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.
>>   
>> The release cadence is described in more detail in another blog post 
>> <https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
>> The OpenJDK project and Eclipse Temurin project both support their long 
>> term support releases with security patches for six years.
>>
>> The two year release cadence with a six year support life means that 
>> three Java LTS releases are officially supported at any point in time by 
>> the OpenJDK project and the Eclipse Temurin project.  Jenkins developers 
>> would like to generally support two Java LTS releases rather than three LTS 
>> releases in order to reduce overhead from supporting Java releases.
>>
>> In order to limit Java support to two LTS releases, I propose that the 
>> Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
>> supported for two years, then becomes the minimum required Java version for 
>> two years, then is unsupported for two years.  In the last two years, new 
>> Jenkins releases will not run on that oldest supported Java version.
>>
>> A diagram 
>> <https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
>>  
>> is provided to describe the transition from our current model to the 
>> “2+2+2” model.
>>
>> The diagram shows that as part of the transition, Java 17 will be the 
>> minimum required Java version for only 12 months and Java 21 will be the 
>> minimum required version for only 18 months.  Java 25 and later will be the 
>> minimum required version for 24 months.
>>
>> The “2+2+2” pattern balances the needs of large scale Jenkins users for 
>> predictability and stability and the needs of Jenkins developers for less 
>> maintenance overhead.
>>
>> After a week or two of discussion in the Jenkins developer mailing list 
>> and the Jenkins user mailing list, I plan to submit this as a Jenkins 
>> Enhancement Proposal.
>>
>> More details are available in the Google Doc 
>> <https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
>> .
>>
>> Thanks,
>> Mark Waite
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/14286a26-6d79-4f0e-9f44-ff196f3ad2d0n%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

I've created a Jenkins Enhancement Proposal based on this draft.  Comments 
are welcomed at https://github.com/jenkinsci/jep/pull/400 

On Monday, September 25, 2023 at 7:20:07 AM UTC-6 Mark Waite wrote:

> Java releases are delivered every 6 months with a long term support 
> release every two years as announced in a September 2021 blog post 
> <https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.
>   
> The release cadence is described in more detail in another blog post 
> <https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
> The OpenJDK project and Eclipse Temurin project both support their long 
> term support releases with security patches for six years.
>
> The two year release cadence with a six year support life means that three 
> Java LTS releases are officially supported at any point in time by the 
> OpenJDK project and the Eclipse Temurin project.  Jenkins developers would 
> like to generally support two Java LTS releases rather than three LTS 
> releases in order to reduce overhead from supporting Java releases.
>
> In order to limit Java support to two LTS releases, I propose that the 
> Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
> supported for two years, then becomes the minimum required Java version for 
> two years, then is unsupported for two years.  In the last two years, new 
> Jenkins releases will not run on that oldest supported Java version.
>
> A diagram 
> <https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
>  
> is provided to describe the transition from our current model to the 
> “2+2+2” model.
>
> The diagram shows that as part of the transition, Java 17 will be the 
> minimum required Java version for only 12 months and Java 21 will be the 
> minimum required version for only 18 months.  Java 25 and later will be the 
> minimum required version for 24 months.
>
> The “2+2+2” pattern balances the needs of large scale Jenkins users for 
> predictability and stability and the needs of Jenkins developers for less 
> maintenance overhead.
>
> After a week or two of discussion in the Jenkins developer mailing list 
> and the Jenkins user mailing list, I plan to submit this as a Jenkins 
> Enhancement Proposal.
>
> More details are available in the Google Doc 
> <https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
> .
>
> Thanks,
> Mark Waite
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f27aef92-86db-46f8-be60-32cc1d0ad4ebn%40googlegroups.com.

Re: doesn’t have label

[Mark Waite]

On Thursday, October 12, 2023 at 7:55:50 AM UTC-6 you wrote:

Mark Waite schrieb am Mittwoch, 11. Oktober 2023 um 20:07:29 UTC+2:

I've sometimes seen something like that when working with the static agents 
that I have connected to my controller.  I workaround the problem by adding 
a "junk" label to any one of the agents.  After saving the junk label, I 
configure the agent again to remove the "junk" label and that seems to 
cause jobs to again recognize agent labels.


 

Affected by https://issues.jenkins.io/browse/JENKINS-71937?  Should be 
fixed in latest weekly (2.427).


Possibly, though I've used my workaround for many months and that issue was 
only introduced in in Jenkins 2.426.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6af46a77-b69d-4a13-a086-219164763e3bn%40googlegroups.com.

Re: doesn’t have label

[Mark Waite]

I've sometimes seen something like that when working with the static agents 
that I have connected to my controller.  I workaround the problem by adding 
a "junk" label to any one of the agents.  After saving the junk label, I 
configure the agent again to remove the "junk" label and that seems to 
cause jobs to again recognize agent labels.

On Wednesday, October 11, 2023 at 10:39:22 AM UTC-6 alok.d...@gmail.com 
wrote:

> We recently got into an issue where Jenkins master is failed to 
> schedule/distribute builds even though a lot of build agents are sitting 
> idle. We noticed this problem with both ec2 fleet and ec2 (on-demands) 
> plugins. 
>
> Most of the jobs are stuck in the queue with the following message but 
> nodes with the required labels are up in the UI. 
>
> Anyone has experienced similar behavior? Any suggestions to fix this? 
> Thanks. 
> Still waiting to schedule task Waiting for pending items to get a node 
> assigned ‘aws-dev-deploy-6’ doesn’t have label ‘docker’ ‘aws-dev-deploy-8’ 
> doesn’t have label ‘docker’ ‘aws-prod-deploy-5’ doesn’t have label ‘docker’ 
> ‘aws-prod-deploy-6’ doesn’t have label ‘docker’ ‘aws-prod-deploy-7’ doesn’t 
> have label ‘docker’ ‘i-09a2be6382fc26e24’ doesn’t have label ‘docker’ 
> ‘i-0a0347c44f3325130’ doesn’t have label ‘docker’ ‘i-0a2dd9e65b696c5a2’ 
> doesn’t have label ‘docker’ ‘j1-android i-03006f1500a1a0c49’ doesn’t have 
> label ‘docker’ ‘j1-docker i-009e0ccbd3a9616d3’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-00327f98f2b84ccd0’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-007332676d8b4a5f6’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-07a579dbf80a63d27’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-07c99149550e0be53’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-08c0f86b1dfeb58c0’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-0a55498b644f1a18a’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-0b4f913462a670fa3’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-0ca4a73a0bb975df6’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-0dd7e76088df5c56d’ doesn’t have label ‘docker’ 
> ‘j1-jenkinsfilerunner i-0ee7610539156599c’ doesn’t have label ‘docker’ 
> ‘j1-linux i-0058f862d193df3ea’ doesn’t have label ‘docker’ ‘j1-linux 
> i-00656f1ae9f80073a’ doesn’t have label ‘docker’ ‘j1-linux 
> i-012491b4a3876bef0’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0177b40a2676cc70a’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0285a836ca10ea06a’ doesn’t have label ‘docker’ ‘j1-linux 
> i-03bf1b363f722977e’ doesn’t have label ‘docker’ ‘j1-linux 
> i-03dcba2eed6a02624’ doesn’t have label ‘docker’ ‘j1-linux 
> i-03eafa4b54936f82e’ doesn’t have label ‘docker’ ‘j1-linux 
> i-04077c54f1352eaec’ doesn’t have label ‘docker’ ‘j1-linux 
> i-059e9e4d333245344’ doesn’t have label ‘docker’ ‘j1-linux 
> i-08559e6d9be2dab5c’ doesn’t have label ‘docker’ ‘j1-linux 
> i-08dfca6d3b1176a11’ doesn’t have label ‘docker’ ‘j1-linux 
> i-090bee3bdf40db6ea’ doesn’t have label ‘docker’ ‘j1-linux 
> i-09a71e57be1518373’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0a06b985fea4aeef7’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0b868611590a750a6’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0e5597e6c71593762’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0f8bd2f10aaf9aa11’ doesn’t have label ‘docker’ ‘j1-linux 
> i-0fd49a3eeb2c6d1a1’ doesn’t have label ‘docker’ 
>  Help us localize this page 
> 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a9ae96c2-e4a9-4256-9a6b-5b061d48b170n%40googlegroups.com.

Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

Java releases are delivered every 6 months with a long term support release 
every two years as announced in a September 2021 blog post 
<https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.  
The release cadence is described in more detail in another blog post 
<https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
The OpenJDK project and Eclipse Temurin project both support their long 
term support releases with security patches for six years.

The two year release cadence with a six year support life means that three 
Java LTS releases are officially supported at any point in time by the 
OpenJDK project and the Eclipse Temurin project.  Jenkins developers would 
like to generally support two Java LTS releases rather than three LTS 
releases in order to reduce overhead from supporting Java releases.

In order to limit Java support to two LTS releases, I propose that the 
Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
supported for two years, then becomes the minimum required Java version for 
two years, then is unsupported for two years.  In the last two years, new 
Jenkins releases will not run on that oldest supported Java version.

A diagram 
<https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
 
is provided to describe the transition from our current model to the 
“2+2+2” model.

The diagram shows that as part of the transition, Java 17 will be the 
minimum required Java version for only 12 months and Java 21 will be the 
minimum required version for only 18 months.  Java 25 and later will be the 
minimum required version for 24 months.

The “2+2+2” pattern balances the needs of large scale Jenkins users for 
predictability and stability and the needs of Jenkins developers for less 
maintenance overhead.

After a week or two of discussion in the Jenkins developer mailing list and 
the Jenkins user mailing list, I plan to submit this as a Jenkins 
Enhancement Proposal.

More details are available in the Google Doc 
<https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
.

Thanks,
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cfd37f66-a56b-4a78-bff0-cd7469e5c284n%40googlegroups.com.

Re: How does one deploy to webdav server?

[Mark Waite]

On Monday, August 28, 2023 at 7:26:00 AM UTC-6 Kari Cowan wrote:

No, it's a protocol, WinSCP will use it if selected.

Project files (mostly MarkLogic XQuery) for the DB are stored in GitHub, so 
I'd like a more automated way to pull from GH and deploy to the DB server 
handling those.   


The most common way to handle that type of deployment with Jenkins is to 
perform the deployment from a command line script written in your choice of 
scripting languages, then run that script from an "sh" step in a Jenkins 
Pipeline.

That makes it easier to develop and debug and gives you the choice of 
scripting language that best suits your needs, interests, and skills.

If you find a Jenkins plugin that does WebDAV deployment (I am not aware of 
one), it then requires that you do your development and debugging from 
inside the Jenkins job, using the features provided by the plugin and 
limited by the features of the plugin.  That tends to slow your progress 
and make you more dependent on the plugin and its maintainer.

Jesse Glick gave a DevOps World talk that described the technique several 
years ago if you'd like more details.  https://youtu.be/Zeqc6--0eQw is the 
talk

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e5260268-ad7c-4d09-8cb5-80f925ee3a57n%40googlegroups.com.

Re: is docker pipeline plugin maintained?

[Mark Waite]

On Wednesday, August 23, 2023 at 2:04:20 PM UTC-6 valerio wrote:

Hi,

With my team we've started using docker pipeline plugin within jenkins and 
it seems working cool!
The plugin main page (https://plugins.jenkins.io/docker-workflow/) states 
it's up for adoption

* Does it mean the plugin is not maintained anymore?
* If yes, is there any maintained plugin alternative to docker pipeline to 
run commands inside docker container within a scripted jenkins pipeline?

Thanks a lot for your support,
Valerio


 A plugin that is up for adoption has no active maintainer.  Plugins that 
are up for adoption tend to be less well maintained than plugins that are 
not up for adoption.

Commands can be run inside a Docker container from a scripted Jenkins 
Pipeline by using sh steps that perform docker commands.  The Docker 
pipeline plugin is a good choice for simple use cases.  It is used in the 
Jenkins tutorials.  I think it is a reasonable choice to use.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a60464b4-afe0-4e39-9fc1-5705da351c9dn%40googlegroups.com.

Re: Jenkins Python Job

[Mark Waite]

On Thursday, August 10, 2023 at 9:45:48 AM UTC-6 Mari wrote:

Hi All,

I have a job running on Jenkins server, which builds python script. The 
script has to display a bar chart as final output.
The build agent I am using on Jenkins appears to have python installed. I 
confirmed this by adding a build step as python3 —version and the result 
was: Python 3.6.8.

Why then do I have this error showing. Do I need to install a plugin? 

Kind regards 
Mari





Traceback (most recent call last)
File "newjenkins.py", line 7, in 
import matplotlib.pyplot as plt
File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py", line 97, in 

_backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup()
File "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py", 
line 25, in pylab_setup
globals(),locals(),[backend_name])
File 
"/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_gtkagg.py", 
line 10, in 
from matplotlib.backends.backend_gtk import gtk, FigureManagerGTK, 
FigureCAnvasGTK, \
File "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_gtk.py", 
line 13, in 
import gtk, gdk = gtk.gdk
File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 64, 
in 
_init()
File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 52, 
in _init
_gtk.init_check()
RuntimeError: could not open display


That output indicates that the program is choosing to run Python 2 packages 
(like gtk) with Python 3.  You probably need Python 3 packages to run with 
Python 3.6.8. 

Installing a plugin won't help.  Python 2 reached end of life in 2020, per 
https://www.python.org/doc/sunset-python-2/

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/74a3b800-028f-47ce-b915-086046be13ecn%40googlegroups.com.

Re: Regarding unable to start jenkins

[Mark Waite]

On Sunday, August 6, 2023 at 9:21:41 PM UTC-6 Ashok Reddy wrote:

Hi , 

I am able to see the error, which I have already shared. 
What else shall I need to provide information in order to help me out to 
fix this issue?


You're trying to persuade other people to give their time to help you.  
You're more likely to persuade them to give their time to help you if you 
follow the detailed instructions in "How to report an issue" 
<https://www.jenkins.io/participate/report-issue/>.  You haven't followed 
those detailed instructions.

Read and follow those detailed instructions.  Yes, there are many steps in 
those instructions.  Yes, it is a lot of work for you to follow those steps.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c5e5d982-6a17-425a-9a1c-eaeee97b39fcn%40googlegroups.com.

Re: Regarding unable to start jenkins

[Mark Waite]

On Sunday, August 6, 2023 at 7:36:59 PM UTC-6 Ashok wrote:

Hi All, 

Can someone help me to fix this issue?


Not really, at least not without your providing more details as were 
requested by Kris Stern earlier.

There are many users that run Jenkins on macOS and start it with the 
command `java -jar jenkins.war`.  They don't see the problem that you are 
seeing.  There must be something different about your environment than the 
environment of other users that are running on macOS.

Since you've not provided any details of the differences, it is unlikely 
that anyone will be able to help you fix the issue.  Without those details, 
you are hoping that someone has seen your exact issue, will guess that is 
the issue, and will tell you the answer, without knowing enough details to 
confirm that your issue matches their issue.

The "How to report an issue" page 
<https://www.jenkins.io/participate/report-issue/> provides excellent 
guidance on the type of information that is needed when you're trying to 
persuade others to donate their time to help you.  Others are much more 
likely to help with guesses on the diagnosis of your issue when you provide 
the necessary details.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9fdb6155-f11a-4f14-a69f-3f7ca75282f3n%40googlegroups.com.

Re: java.lang.NoSuchMethodError: No such DSL method 'withKubeConfig' found among steps [approveReceivedEvent,

[Mark Waite]

On Friday, July 21, 2023 at 8:08:26 AM UTC-6 Gizem wrote:

Hi, 

I have the same issue. I have installed kubernetes-cli; even i uninstalled 
and installed the pugin again. Still does not work for me. 

Could you please help me? Best regards

On build log: 

Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 
04309c70-2416-4c88-a8c6-283c2f844814 java.lang.NoSuchMethodError: No such 
DSL method 'kubernetesDeploy' found among steps

 


Unfortunately, you do not have the same issue.  The message "no such DSL 
method 'withKubeConfig'" can be solved by installing the Kubernetes CLI 
plugin.  You've done that.  The message "no such DSL method 
'kubernetesDeploy'" cannot be solved by installing any plugin that is known 
to the Jenkins Pipeline steps reference 
<https://www.jenkins.io/doc/pipeline/steps/>.  There is no active plugin 
that provides the method "kubernetesDeploy".

A 'kubernetesDeploy' step was provided by the Kubernetes Continuous Deploy 
plugin but that plugin has been suspended from distribution due to an 
unresolved remote code execution vulnerability.  Refer 
to https://www.jenkins.io/security/advisory/2022-08-23/#SECURITY-2448 for 
the details.

You'll need to find another way perform the desired operation rather than 
using that Pipeline step.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5bb79b7a-271d-4091-a9c8-49dc3cbc965bn%40googlegroups.com.

Re: git job weirdness (in Changes)

[Mark Waite]

On Tuesday, July 4, 2023 at 3:09:57 AM UTC-6 David Balazic wrote:

I created a new job with the same settings, except: 
- the original job (with the issues) had GIT settings to ave disk space, 
ase described in the thread "git plugin, use --single-branch option to save 
disk space?" on this list on may 26 2023 
- the new job had default GIT options 

With the new job, the second issue (all files listed as added) is not 
present. 
So it is a bug in git-client with the nondefault options? 

For the record, the different settings in the old job regarding git are: 

- Advanced / "Refspec" is not blank (as per default), but: 
+refs/heads/my_branch:refs/remotes/origin/ my_branch 
- "Additional Behaviours" has an "Advanced clone behaviours" item with 
values: 
"Honor refspec on initial clone" enabled 
"Shallow clone" enabled 


Shallow clone causes git to request only the depth of commits specified.  
Changelog history is computed from the history in the local copy of the 
repository.  If the history in the  local copy of the repository   is 
shallow, then it is entirely possible that the history does not exist in 
that local copy.
 

The third issue (file list look) is still present in the new job, while the 
first (changes list) was not tested as only one commit was done between 
latest en previous build. 

Regards, 
David 

From: 'David Balazic' via Jenkins Users 
Sent: Tuesday, 20 June 2023 10:17 
To: 'David Balazic' via Jenkins Users 
Subject: git job weirdness (in Changes) 

Hi! 

I have set up a job in Jenkins v2.387.2 with sources from git and a maven 
build step. 

Last time I committed and pushed two changes into the repo. (one push after 
both commits) The Jenkins job detected the change and started a build. 

Issues: 
- the changes page in Jenkins ( /view/foo/job/my_job/changes ) shows only 
the second change (the commit message and the author). 
Clicking the "detail" link opens 
/view/foo/job/my_job/4/changes#1234_the_hash where again only the second 
commit is mentioned. 
The files on disk (in the workspace) have the correct content (from both 
commits). 

- on the above details/summary page, there is a list of many files from the 
repo/working tree with the plus icon prepended 
It seems almost every file in the repo (in the branch I checked out) is 
listed. 
This is the same for a previous build too, which was also triggered by SCM 
change and has one file actually changed. 
And the build before that. 
This job has 4 builds, and the 3 after the initial build all have this 
issue of all files being listed, instead only the changed ones. 

- on the details/summary page, the "changed" files listed are in black, 
slightly bold font, but when hovering the mouse over each , that line turns 
blue and underlined (similar to links), clicking on it has no effect. 

Questions: 
- why are not both changes (or in general: all changes since previous 
build) listed? 
- why are all files listed, not just the changed ones? 
- why the blue underlined text? 


Regards, 
Lep pozdrav, 
David Balažic 


The information in this email is confidential and may be legally 
privileged. It is intended solely for the addressee. Any opinions expressed 
are mine and do not necessarily represent the opinions of the Company. 
Emails are susceptible to interference. If you are not the intended 
recipient, any disclosure, copying, distribution or any action taken or 
omitted to be taken in reliance on it, is strictly prohibited and may be 
unlawful. If you have received this message in error, do not open any 
attachments but please notify the Endava Service Desk on (+44 (0)870 423 
0187), and delete this message from your system. The sender accepts no 
responsibility for information, errors or omissions in this email, or for 
its use or misuse, or for any act committed or omitted in connection with 
this communication. If in doubt, please verify the authenticity of the 
contents with the sender. Please rely on your own virus checkers as no 
responsibility is taken by the sender for any damage rising out of any bug 
or virus infection. 

Endava plc is a company registered in England under company number 5722669 
whose registered office is at 125 Old Broad Street, London, EC2N 1AR, 
United Kingdom. Endava plc is the Endava group holding company and does not 
provide any services to clients. Each of Endava plc and its subsidiaries is 
a separate legal entity and has no liability for another such entity's acts 
or omissions. 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bc75a2c6-5ca8-40dd-9ea4-e8d0edd9d13an%40googlegroups.com.

Re: git plugin, use --single-branch option to save disk space?

[Mark Waite]

On Friday, May 26, 2023 at 7:23:39 AM UTC-6 David Balazic wrote:

Thanks but I already tested those:

 

Refspec: refs/heads/main

Honor refspec on initial clone: enabled

Shallow clone: enabled

Shallow clone depth: 1

 

 

They download a little less : 1.8 GB

 

The credit goes to the shallow clone option. The Honor refspec option does 
not seem to make any difference. Even the commands seem to be unaffected by 
it.

Maybe the refspec option is missing from the GUI? The example on the web 
has it.

 


Not missing from the GUI, just hidden by default behind the "Advanced" 
button on the Repositories configuration of the page.  Click the Advanced 
button and it will show two more fields, a "Name" field and a "Refspec" 
field.
 
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/833aaac1-5ba2-408f-9e02-926bfc9a747fn%40googlegroups.com.

Re: git plugin, use --single-branch option to save disk space?

[Mark Waite]

On Friday, May 26, 2023 at 5:46:34 AM UTC-6 David Balazic wrote:

Hi! 

With the git plugin, is there a way to clone a repo with the 
--single-branch option? 

We have a freestyle job wit a Git source code, where we specify the branch 
as: refs/heads/main 
And when the build is done, the cloned repo (the .git folder) is very big, 
about 2.6 GB. 
We use a command line git implementation (gitforwindows.org 2.40.1). 

Using command line to clone gives this values: 

git clone --branch main https://server.example.com/foo/bar "C:\tmp\git 
test\test_xxx_branch_main" 
git clone --single-branch --branch main https://server.example.com/foo/bar 
"C:\tmp\git test\test_xxx_branch_main_single" 

The first creates a 2.6 GB .git folder, while the second a 70 MB sized .git 
folder. 
They both also have about 120 MB of working tree files. 

So about 2.4 GB is "wasted" due to unneeded cloned branches. 

Is there a way to make the Jenkins git plugin to clone only the required 
branches? 


Yes, you can match the behavior of the --single-branch argument to git 
clone with the Jenkins git plugin.

Configure a refspec that matches a single branch in the remote 
configuration section.
Enable "Honor refspec on initial clone"

Those options are described in a git plugin Pipeline example 
<https://github.com/jenkinsci/git-plugin#checkout-with-a-narrow-refspec>.

If you don't need the history of the repository in your job, you can reduce 
the size even further by using a shallow clone that only retrieves the most 
recent commit.

That option is also described in a git plugin PIpeline example 
<https://github.com/jenkinsci/git-plugin#checkout-with-a-shallow-clone-to-reduce-data-traffic>
.

You can reduce disc use even further if you have a copy of the remote 
repository already available on the agent.  Then you can use a reference 
repository.  Reference repositories are generally not helpful when using 
shallow clone, since the reference repository may not include many of the 
changes in the shallow clone.

A 10-15 minute video <https://youtu.be/jBGFjFc6Jf8?t=6434> discussing 
various performance improvement options is also available if you prefer 
video.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d9b55add-c0ae-4440-ae86-0354d5082fb9n%40googlegroups.com.

Re: Signature verification failed in update site

[Mark Waite]

On Sunday, May 21, 2023 at 7:42:07 AM UTC-6 Samir wrote:

When I run jenkins with ZAP plugin, I get the following errors on Build.

I tried changing java.security file and removing MD5 from 
jdk.certpah.disabledAlgorithms,
Also changed RSA keySize to < 512 as also changed the command line to remove
certificate checking. But nothing helps. Can you please suggest what I 
could be doing wrong?

It used to work all right some time back but this error pops up now.

regards,
Samir

May 21, 2023 6:29:12 PM hudson.model.UpdateSite updateData
SEVERE: ERROR: Signature verification failed in update site 
default (show details)java.security.cert.CertPathValidatorException: 
signature check failed


As far as I can tell, that message has no relation to the Zap plugin.  That 
is a message from the verifySignature method of the  JSONSignatureValidator 
in Jenkins core that is checking the validity of the data received from the 
Jenkins update center.

Changing Java security settings is unlikely to help with that message.

You may have misconfigured the URL of the Jenkins update center in "Manage 
Jenkins" -> "Plugins" -> "Advanced Settings" in the ""Update Site" field.  
See https://updates.jenkins.io/ for the standard value that should be there.

If the URL of the Jenkins update center is configured correctly, then it is 
possible that there is a network device between the Jenkins controller and 
the Jenkins update center that is damaging or blocking the necessary data.  
The network experts at your organization are probably the best people to 
consult to see if they have a proxy configured or some other form of 
network blocking.

You could enable a system logger from the "System log" page to view the 
logs of the jenkins.util.JSONSignatureValidator class.  The logging 
statements in the source code may help you identify the issue in your local 
enviornment.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1307fe4b-9643-4aa4-be8a-b4f32567a6dbn%40googlegroups.com.

Re: Jenkins is not starting up after upgrade to Version: 2.387.3

[Mark Waite]

On Thursday, May 4, 2023 at 6:29:18 AM UTC-6 Ravindra wrote:

I can't access the UI anymore , is there any way I can do it without the UI 
?


I think that you may have misunderstood what I wrote.  The most important 
part of what I wrote is the first paragraph that says:


> Check earlier in the log file and you'll probably find a reason why those 
plugins did not load.  Some other plugin may have failed to load or a 
dependency was not satisfied or some other issue was stated in the log file.


Performing the other actions is secondary to understanding what caused the 
plugins to fail to load.  Read the log file.  If the log file contents are 
not clear to you, then upload the log file to some public location where 
you can share the link with others so that they can read the log file if 
you don't understand the details of what it is saying.  GitHub gist or some 
other snippet hosting service would be a good place to put the log file for 
review by others.  If the log file contains sensitive information, you'll 
want to remove that sensitive information before you upload it.

Alternatively, you can use the Ubuntu package manager to install the older 
version.  However, that won't provide you the critical information that you 
need.  The critical information that you need is, "Why did the plugins fail 
to load?"  That information is in the log file.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/09f6f60e-3d49-4624-8801-d6f292dfc26fn%40googlegroups.com.

Re: Jenkins is not starting up after upgrade to Version: 2.387.3

[Mark Waite]

On Thursday, May 4, 2023 at 5:11:53 AM UTC-6 Ravindra wrote:

Hi  Folks , 

I upgrade Jenkins to Version: 2.387.3 on ubuntu using package Manager .

now its crashed and not stating up , from the logs i found below errors : 

* - Failed to load: Pipeline: Shared Groovy Libraries 
(workflow-cps-global-lib 2.17)*

*- Failed to load: Jenkins Git client plugin (git-client 3.5.1)*

*- java.io.IOException: Failed to load: NodeJS Plugin (nodejs 1.3.9)*


Please suggest how to fix this .


Check earlier in the log file and you'll probably find a reason why those 
plugins did not load.  Some other plugin may have failed to load or a 
dependency was not satisfied or some other issue was stated in the log file.

Based on the version numbers of those plugins, you may have missed the 
instructions in previous upgrade guides that state that you need to upgrade 
plugins to their most recent releases and you need to remove deprecated 
plugins.

The workflow cps global lib plugin 2.17 is deprecated and should be 
uninstalled.  Replace it 
with https://plugins.jenkins.io/pipeline-groovy-lib/

The git client plugin 3.5.1 was released 2.5 years ago.  Upgrade it to git 
client plugin 4.2.0

NodeJS plugin 1.3.9 was released 2.5 years ago.  Upgrade it to nodejs 
plugin 1.6.0

Based on those three versions, there are probably other plugin versions 
that need to be upgraded.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a50b69a5-33ff-4017-9682-5a8246685f62n%40googlegroups.com.

Re: Not able to delete deprecated plugins

[Mark Waite]

On Wednesday, April 26, 2023 at 11:58:49 AM UTC-6 you wrote:

Hi Guys, 

I am not able to delete deprecated plugs. I am getting below errors. Please 
suggest how can I remove below plugin

Failed to load: Gitlab Hook Plugin (gitlab-hook 1.4.2) - Plugin is missing: 
ruby-runtime (0.12)


Thanks for asking.  The Ruby runtime plugin is deprecated.  It does not 
support Java 11 or Java 17.  Plugins that depend on the Ruby runtime plugin 
are deprecated.  They do not support Java 11 or Java 17.  Current versions 
of Jenkins require either Java 11 or Java 17.

Remove the gtilab-hook plugin file (gitlab-hook.jpi) and folder 
(gitlab-hook) from the plugins directory in your Jenkins home directory.  
Remove any other plugins that are on the list in the "Deprecating non-Java 
plugins" blog post 
<https://www.jenkins.io/blog/2021/12/22/deprecated-ruby-runtime/>.

Thanks,
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c745fab0-77c3-4bab-b249-3d9507c086ffn%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

[Mark Waite]

On Thursday, April 6, 2023 at 6:56:31 AM UTC-6 dheinric wrote:

Am Donnerstag, dem 06.04.2023 um 05:33 -0700 schrieb Mark Waite:

I'd rather not include extra instructions for Debian 10, Debian 11, Ubuntu 
18, and Ubuntu 20, especially when those instructions involve creating 
directories as the root user and assuring those directories have correct 
ownership and permissions.


People knowing that page might then (falsely) assume that the key will be 
managed by a package after initial setup if it is to be placed into 
/usr/share/keyrings. OTOH, creating the directory is just one more line, 
like

sudo sh -c "test -d /etc/apt/keyrings || mkdir -m 0755 /etc/apt/keyrings"

We'll discuss further in the retrospective to see which path we take to 
reduce the problems for Debian and Ubuntu administrators on the next GPG 
key rotation.


Why wait (until next rotation)? Why not create a package which places the 
current key into /usr/share/keyrings and add that as a dependency to the 
main Jenkins package? This is how Element or PostgreSQL (to name a few) 
already do it. Would have the benefit that no documentation change would be 
needed.


Agreed that if the decision from the retrospective and investigation is to 
implement an additional package as a dependency to the main Jenkins 
package, then there is no need to wait until the next key rotation.  The 
bigger challenge is having someone implement that package and perform the 
necessary testing to confirm that it is well behaved on Debian 10, Debian 
11, Ubuntu 18, Ubuntu 20, and Ubuntu 22.  If that effort takes enough time 
that Debian 12 releases before it is done, then Debian 12 will also need to 
be tested.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20c19a0a-2846-4d99-9c76-83ea7c06e368n%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

[Mark Waite]

On Thursday, March 30, 2023 at 11:40:34 PM UTC-6 dheinric wrote:

Am Donnerstag, dem 30.03.2023 um 10:44 -0700 schrieb Mark Waite:

> Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long as 
the new PGP public key has been installed by following the instructions in 
the Linux installation page 
<https://urldefense.com/v3/__https://www.jenkins.io/doc/book/installing/linux/*long-term-support-release__;Iw!!Obbck6kTJA!f96PpN88GsBnP_-4CebJqPJTmS-WwRlEKHPbu3Ll2zayOh71wSktbHrVoIT6-fnkQQZ4x5_7PR-uc88RLWO2PeyX4lw$>


Please note that these instructions contain a small mistake. The key should 
be downloaded to "/etc/apt/keyrings", unless it is later managed by a 
package, which is not the case here (see 
https://wiki.debian.org/DebianRepository/UseThirdParty) 
<https://wiki.debian.org/DebianRepository/UseThirdParty>. Would be great if 
that could be corrected (or, as recommended by Debian, a package be provided 
for 
managing the keyring after the initial setup).


I'm hesitant to change those instructions based on the comment in the 
https://wiki.debian.org/DebianRepository/UseThirdParty page where it says:

> In releases older than Debian 12 and Ubuntu 22.04, /etc/apt/keyrings does 
not exist by default. It SHOULD be created with permissions 0755 if it is 
needed and does not already exist.

I'd rather not include extra instructions for Debian 10, Debian 11, Ubuntu 
18, and Ubuntu 20, especially when those instructions involve creating 
directories as the root user and assuring those directories have correct 
ownership and permissions.

We'll discuss further in the retrospective to see which path we take to 
reduce the problems for Debian and Ubuntu administrators on the next GPG 
key rotation.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a7198085-868c-46cf-bc35-a59d05cdebden%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

[Mark Waite]

On Thursday, March 30, 2023 at 11:13:20 AM UTC-6 Alan Sparks wrote:

Tried to build a Jenkins image here this morning and getting signing errors 
on the repo:

W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://pkg.jenkins.io/debian-stable binary/ Release: The following 
signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project
W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
 The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
Project
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

I see a post on the Jenkins blog about the key changing, but it says April 
5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
doesn't seem to work, nor does the new one.  I'm using the same repo 
configuration:
deb https://pkg.jenkins.io/debian-stable binary/

What has changed?


The GPG private key that signs the Jenkins 2.387.1 deb file expired March 
30, 2023.  A comment 
<https://community.jenkins.io/t/new-linux-repository-signing-keys-for-jenkins-2-397-and-2-387-2/6509>
 
to the blog post 
<https://www.jenkins.io/blog/2023/03/27/repository-signing-keys-changing/> 
says:

> Users installing Jenkins LTS 2.387.1 after March 31, 2023 may see a 
warning or an error noting that the PGP key has expired.

> Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long as 
the new PGP public key has been installed by following the instructions in 
the Linux installation page 
<https://www.jenkins.io/doc/book/installing/linux/#long-term-support-release>
You're correct that the old key does not work (because it has expired) and 
that the new key does not work with the old releases (because they were not 
signed with the new key). 

The new key works with new releases (like Jenkins 2.397 released March 28, 
2023 and Jenkins 2.387.2 that will be released April 5, 2023).

If you need to install Jenkins LTS with the Linux installer between now and 
April 5, your choices include:

   - Override the package manager to ignore the expired PGP key
   - Use a container image like jenkins/jenkins:2.387.1-jdk11 
   
<https://hub.docker.com/layers/jenkins/jenkins/2.387.1-jdk11/images/sha256-005fcb5c3017ef120d0d9d8d8925e9248ff6e2cf2b5e18b527b01459c7b2b3f4>
   - Install the war file without the Linux installer

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a46275a2-3ee3-405d-9142-5bc2d325119cn%40googlegroups.com.

Re: Contexts/environments?

[Mark Waite]

On Sunday, January 29, 2023 at 8:38:58 PM UTC-7 Victor Sudakov wrote:
Any ideas or thoughts on this? 

On 27.01.2023 16:42, Victor Sudakov wrote: 
> Dear Colleagues, 
> 
> Some CI/CD tools support the concept of contexts or environments. In each 
> environment/context, you define a set of variables or secrets with 
> different values, and refer to the contexts from the pipeline. For 
example, 
> for Github Actions you can create the "main" and "dev" environments and 
> then mention them in your pipeline: 


I've used folders as a way to provide additional context for a job.  If one 
folder is for dev and another is for main, the environment variables on the 
main folder can be different than the environment variables on the dev 
folder.  Credentials can be assigned to the folder as well.  If the same 
credential ID is used in both contexts, the job should be able to reference 
credentials from the folder.

 
> jobs: 
> build: 
> runs-on: ubuntu-latest 
> environment: ${{ github.ref_name }} 
> steps: 
> - name: Test secrets 
> run: something 
> env: 
> SUPER_SECRET: ${{ secrets.TEST_SECRET }} 
> 
> and the value of secrets.TEST_SECRET will be different for different 
> branches. 
> 
> Do you know of a plugin for Jenkins with a similar functionality for its 
> Multibranch Pipelines? 
> 
> Jenkins has the concept of "credential domains", can they be used for 
this 
> purpose (like referring to a credential domain from the environment{} 
block for 
> example)? 
> 
-- 
Victor Sudakov 
Systems Administrator 
Streamline - Property Management Software 
Website: www.streamlinevrs.com 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bbc6dd83-232a-445c-bed9-672728b1047bn%40googlegroups.com.

Re: Another way to uninstall a plugin?

[Mark Waite]

On Tuesday, January 10, 2023 at 6:32:25 PM UTC-7 Peter wrote:
Getting rid of the WMI plugin warning implies updating to 2.386 for 
me. See https://issues.jenkins.io/browse/JENKINS-70301 


That's correct.  I've proposed that as an LTS candidate for Jenkins 2.375.3 
that will release in about 4 weeks.  If it is not accepted for 2.375.3, 
then it will be in the next LTS baseline  that will be delivered in 8 weeks.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/21ac678c-f583-416d-8802-d9e98881c6acn%40googlegroups.com.

Re: Another way to uninstall a plugin?

[Mark Waite]

Removing plugins from Docker containers has some complications that are 
specific to the way plugins are managed in Docker containers.  We have a 
work in progress pull request that is developing the detailed description 
of the various scenarios to remove plugins from a container.

The technique that I've used has been to remove the contents of 
${JENKINS_HOME}/plugins as the last step in my Dockerfile version that is 
removing a plugin so that on the next startup of that container, the 
current set of plugins will be copied from the "${REF}" directory into the  
${JENKINS_HOME}/plugins directory.  I don't know if that's the best way, 
but that's one way that has worked for me.

On Sunday, January 8, 2023 at 5:31:34 PM UTC-7 zil...@gmail.com wrote:

> No it's not the WMI Windows Agents plugin since we're totally a Linux shop.
>
> I'll try your suggestion of "hovering" the "Uninstall" button. Thanks
>
> On Tuesday, January 3, 2023 at 12:36:46 PM UTC-5 db...@cloudbees.com 
> wrote:
>
>> On Tue, Jan 3, 2023 at 4:49 PM zil...@gmail.com  wrote:
>>
>>> Thanks. It's a deprecated plugin. I'm trying to uninstall all the 
>>> indicated deprecated plugins, but they just keep coming back after a 
>>> restart. They are disabled though.
>>>
>>
>> Is it WMI Windows Agents Plugin?
>>
>> Plugins getting re-installed is expected behavior if they're a plugin 
>> whose functionality was split ("detached") from Jenkins core in the 
>> past, as is the case with that one. It's the only such plugin currently 
>> deprecated as well.
>>
>> The only real solution is for all other plugins you have installed to 
>> declare a core dependency of 1.547 or newer, so none of them cause the 
>> detached plugin to be installed automatically again. Check the popup that 
>> appears when hovering the "uninstall" button for candidates, or check the 
>> URL /pluginManager/api/json?tree=plugins[shortName,requiredCoreVersion] in 
>> Jenkins to learn which installed plugins have a ~9 year old core dependency 
>> and should be modernized.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c78595f-4ad5-4acc-8037-6f4ca928b240n%40googlegroups.com.

Re: Docker container stops on a Jenkins restart?

[Mark Waite]

https://www.jenkins.io/blog/2022/05/27/docker-image-new-lifecycle/ says 
that beginning with Jenkins 2.332.3 the docker container lifecycle has 
changed.

add the flag --restart=on-failure 
 to 
the docker run <…​> jenkins/jenkins command

On Sunday, January 1, 2023 at 11:21:23 AM UTC-7 zil...@gmail.com wrote:

> I used to not have this issue with the older Jenkins version that this 
> installation replaced.
>
> I updated to Jenkins v2.346.3 and I start it as a Docker container like 
> this
> $ docker run --rm -d -p 8080:8080 -v 
> /mnt/jenkins_master/jenkins_home:/var/jenkins_home --name jenkins_master 
> --memory=24g 
> 1234567890.dkr.ecr.eu-north-1.amazonaws.com/jenkins_master:2.346.3
>
> Now when I got to my browser to restart Jenkins
> myJenkins.domain.com/restart 
>
> the container dies? Why, and how do I prevent this? I don't see any logs 
> indicating why.
>
> TIA, Chris
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/91bcaad6-bbad-4ca0-92ff-4859f1c64867n%40googlegroups.com.

Re: Save and Apply button do nothing on copied job

[Mark Waite]

It could be a known tables to divs issue in one of the plugins you have 
installed.  If that plugin is used in the job, it could stop save and apply 
when other jobs are still able to save and apply.

See the detailed steps 
at https://community.jenkins.io/t/migrating-jenkins/894/5

If those steps don't work, then you can open an issue on issues.jenkins.io, 
provide the list of plugins installed and their exact versions and see if 
someone is willing to try to duplicate the problem.

On Saturday, December 31, 2022 at 6:57:44 PM UTC-7 zil...@gmail.com wrote:

> I can Save and Apply on other jobs, just not this copied one.
>
> Chris
>
> On Saturday, December 31, 2022 at 8:12:35 PM UTC-5 zil...@gmail.com wrote:
>
>> I have updated all the plugins.
>>
>> Chris
>>
>> On Saturday, December 31, 2022 at 8:10:50 PM UTC-5 zil...@gmail.com 
>> wrote:
>>
>>> Jenkins 2.346.3 run as a docker container.
>>>
>>> I copied a Freeform job and called it test-workspace
>>>
>>> When I configure the test-workspace job, I click either the Save or 
>>> Apply buttons, but NOTHING happens - no logs, no feedback, no error, no 
>>> green bar flash on top of page. NADA!
>>>
>>> I disabled ruby-runtime since it was failing the app to come up.
>>>
>>> Is this a bug?
>>>
>>> TIA,
>>> Chris
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7e931589-56a8-4db5-9511-6931cfa7f843n%40googlegroups.com.

Re: *** buffer overflow detected ***: java terminated

[Mark Waite]

On Monday, December 5, 2022 at 1:02:18 PM UTC-7 Madhu Muchukota wrote:

> Thanks Mark 
>
> All I'm doing is just triggering/running a multi branch pipeline job from 
> the controller UI.
>
> I will be happy to share more information needed from my end. 
>
>
Unfortunately, somehow you have a failure mode that is different than the 
100,000+ Jenkins controllers around the world that are running with Java 
11.  I don't have any suggestions about what could be different.

Things that you could explore:

   - Does the same failure happen
  - on a different computer running the same configuration?
  - on a different computer running without Tomcat?
  - on the same computer running without Tomcat?
  - Were there recent upgrades to any components?
  - Core upgrade
  - Plugin upgrades
  - Operating system upgrades
   - Were there any recent system configuration changes?
  - Were settings increased on the system make it more secure or to 
  better defend it?
   

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7d818b09-f66f-4681-8163-2c1b26070e88n%40googlegroups.com.

Re: *** buffer overflow detected ***: java terminated

[Mark Waite]

On Monday, December 5, 2022 at 10:29:49 AM UTC-7 Madhu Muchukota wrote:

> Thanks Ivan and Dirk.
>
> My java version was jdk-11.0.16+8 and I updated this to the latest one in 
> JAVA 11 this morning which is jdk-11.0.17+8 and I still see the same error.
>
> Tomcat is of version 9.0.0.0
> Jenkins is of version 2.375.1
>
>
The message that you're seeing indicates that the Java process was killed 
by the operating system when the Java process performed an unsafe operation 
(buffer overflow).  The Java virtual machine works very hard to prevent 
Java programs from being able to perform unsafe operations.  There are some 
areas where Java allows unsafe operations (Java Native Interface, Java 
Native Runtime project <https://github.com/jnr>), but those are exceptional 
cases.  In almost all cases, buffer overflow failures should not happen in 
a Linux Java process.

If you can provide instructions so that others can duplicate the problem, 
the OpenJDK team and others are likely very interested in the conditions 
that cause the failure.

If your goal is to avoid the issue rather than investigate why it is 
failing, you might try running Jenkins without Tomcat.  If that still shows 
the issue, then you might try bisecting your most recent plugin updates to 
see if one of the recent plugin updates is associated with the change of 
behavior.

A process killed by buffer overflow is very rare in the Jenkins world and 
in the Java world.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b2444171-95b2-45ed-8e9a-146407bc41dcn%40googlegroups.com.

Re: GIT plugin - notifyCommit Token

[Mark Waite]

On Friday, December 2, 2022 at 8:52:26 AM UTC-7 Madhu Muchukota wrote:

> Hi Team, 
>
> We recently upgraded Jenkins and as a part of this, plugins too got 
> upgraded.
>
> We use Service Hooks in Azure DevOps and after the upgrade, we are seeing 
> GIT notifyCommit is failing with HTTP status code 401.
>
> Upon troubleshooting, I came to know that the Jenkins Git Plugin that got 
> upgraded to the latest version needs notifyCommit token and I don't have 
> any option to pass that notifyCommit token on my Azure DevOps service hook 
> subscription page.
>
> Did anyone run into the same issue? and is there any property through 
> which I can disable this notifyCommit token option?
>
>
The git plugin documentation 

 
says 

The token parameter is required by default as a security measure, but can 
be disabled by the following system property 
:
hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL

It has two modes:

   - 
   
   disabled-for-polling - Allows unauthenticated requests as long as they 
   only request polling of the repository supplied in the url query parameter. 
   Prohibits unauthenticated requests that attempt to schedule a build 
   immediately by providing a sha1 query parameter.
   - 
   
   disabled - Fully disables the access token mechanism and allows all 
   requests to notifyCommit to be unauthenticated. *This option is insecure 
   and is not recommended.*
   

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/34f1422f-8df5-48a7-91b8-52a99a96a25fn%40googlegroups.com.

Re: The following installed plugins are deprecated: WMI Windows Agents Plugin

[Mark Waite]

On Wednesday, November 23, 2022 at 6:46:44 AM UTC-7 Christoph wrote:

> But - wait a second. As soon as I found out one or more culprits depending 
> on WMI windows agents these should immediately be declared deprecated, 
> right? 
> And you can declare the dependency.
> Otherwise you'll run in trouble when there are still active installations 
> and WMI won't be shipped any longer.
>
>
As far as I can tell from a search of the 1800+ plugins that I have cloned 
locally, I find only 1 plugin with an explicit dependency on the WMI 
Windows Agents plugin.  That plugin is  Multi-slave config plugin 
 - last released 8 
years ago.

If that plugin is installed, it will need to be removed.
 

> I'll file issues when I know more...
>
> BR,
> Christoph
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2e8cd077-c124-41ab-be01-447b81679a69n%40googlegroups.com.

Re: The following installed plugins are deprecated: WMI Windows Agents Plugin

[Mark Waite]

Hover over the "uninstall button" for the WMI Windows Agents plugin in the 
Jenkins plugin manager and a pop-up will appear that lists the installed 
plugins that have an implied dependency on the plugin.  Those plugins need 
to be removed or they need to be adopted and upgraded so that their minimum 
Jenkins version is a recent Jenkins version.

An implied dependency on the WMI Windows Agents plugin is described in the 
"What's this?" page that pops up from the "Implied" section of the WMI 
Agents Plugin dependencies page 
<https://plugins.jenkins.io/windows-slaves/#dependencies>.

It says:

> Features are sometimes detached (or split off) from Jenkins core and 
moved into a plugin. Many plugins, like Subversion or JUnit, started as 
features of Jenkins core.

> Plugins that depend on a Jenkins core version before such a plugin was 
detached from core may or may not actually use any of its features. To 
ensure that plugins don't break whenever functionality they depend on is 
detached from Jenkins core, it is considered to have a dependency on the 
detached plugin if it declares a dependency on a version of Jenkins core 
before the split. Since that dependency to the detached plugin is not 
explicitly specified, it is *implied*.

> Plugins that don't regularly update which Jenkins core version they 
depend on will accumulate implied dependencies over time

The last statement is what is happening.  One or more of the installed 
plugins can be run on a Jenkins core version before WMI Windows Agents 
plugin was split from Jenkins core.  Those plugins need to either be 
removed or upgraded.  See the list of plugins in the "Implied" section of 
the dependencies page for WMI Windows Agents plugin 
<https://plugins.jenkins.io/windows-slaves/#dependencies>.  If one or more 
of those installed plugins is critical to you, you can adopt the plugin 
<https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> 
and use the "Improve a Plugin" tutorial 
<https://www.jenkins.io/doc/developer/tutorial-improve/update-base-jenkins-version/>
 
to upgrade the minimum required Jenkins version of the plugin.

Mark Waite
On Wednesday, November 23, 2022 at 1:16:53 AM UTC-7 
christop...@googlemail.com wrote:

> Hi,
>
> I have what we call a "hen-egg-problem" to solve a deprecation warning in 
> latest LTS:
> Jenkins warns about deprecation of the WMI Windows agent plugin
> When I want to disable that plugin for a test I get a warning, it might be 
> unsafe to disable the plugin because other plugins might depend on it.
> And indeed, when it is disabled I can't start any jobs through the UI.
>
> Is there any way to get out of this situation? Otherwise that deprecation 
> warning does not make much sense to me.
>
> Thank!
> Christoph
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d83620e7-e6b2-4af9-ad63-b270cacac6d4n%40googlegroups.com.

Re: git checkouts always set to controller user, causing problems with latest git

[Mark Waite]

I suspect that you'll find that something is misconfigured in your agent 
definition rather than an issue in the checkout step.

I think you'll be able to see that if you:

   1. Create a file in the workspace from inside the Pipeline
   2. Check the permissions of the created file

I suspect you'll see that the permissions are the same as the permissions 
generated by the checkout scm task.

This is the Pipeline script that I used to confirm it:

pipeline {
agent {
label '!windows' // sh step not available on windows
}
stages {
stage('Hello') {
steps {
   writeFile file: 'a-test-file.txt', text: 'Some text inside 
the file'
   sh 'ls -altr a-test-file.txt'
}
}
}
}
On Friday, October 28, 2022 at 5:32:48 AM UTC-6 ice...@googlemail.com wrote:

> In our setup we  run the agents  a separate user via ssh ( contoller: 
> jenkins, agent: jenkinsworker).
>
> In a pipeline we  checkout some code:
> ```
> node(agent) {
>checkout git+ssh://.
>   }
> ```
> This  results in the workdir and all git files belonging to the user 
> jenkins,  not jenkinsworker.
>
> Trying to do a commit (with the need to run a commit-msg hook) fails to 
> run the hook unless I explicitly allow the directory as  safe and correct 
> the hook path (it is set to /dev/null if the directory belongs to an other 
> user ).
>
> I would have  expected the workdir to be owned  by the agent user.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d2943e1e-4caa-47ca-8a30-007d14358107n%40googlegroups.com.

Re: jenkins issue

[Mark Waite]

On Monday, October 10, 2022 at 6:19:34 AM UTC-6 Pooja wrote:

> in jenkins am getting below error
> New release '22.04.1 LTS' available. Run 'do-release-upgrade' to upgrade 
> to it.
>

That message is displayed when you're running an older version of Ubuntu, 
like 20.04 or 18.04.  They are trying to encourage you to upgrade so that 
you can remain on a supported operating system version.
 

>  fatal: could not read Username for 'https://github.com': No such device 
> or address
>

https://stackoverflow.com/questions/40274484/fatal-could-not-read-username-for-https-github-com-device-not-configured
 
indicates that usually means you're not using a credential with an HTTPS 
private git repository.  A credential is required and the credential has 
not been provided or is no longer valid.

 Use --update-env to update environment variables
>

Sorry, I don't recognize that message

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f80d74f9-adc5-4f70-a488-9a858a09dfb1n%40googlegroups.com.

Re: Jenkins Won't start after latest ugrade

[Mark Waite]

Yet another technique, quoting from the link that I included earlier:

> Make sure the default JVM is the newly installed version. If it is not, 
run systemctl edit jenkins and set either the JAVA_HOME environment 
variable or the JENKINS_JAVA_CMD environment variable

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/787a7314-9be4-42ca-9e88-5e8e4ade8a75n%40googlegroups.com.

Re: Jenkins Won't start after latest ugrade

[Mark Waite]

On Wednesday, September 14, 2022 at 2:26:09 PM UTC-6 Eric Fetzer wrote:

Thanks for the response Mark.  I don't want to backgrade, so jenkins won't 
> run.  Can you give me a clue as to where the filepath is to java in 
> Jenkins.  Just upgrading didn't solve the problem and the vid is too slow 
> for me.  He seems to talk a lot about working in the tool.  I'm command 
> line RHEL 7.
>
>
I believe that the command you want is described on the Red Hat Customer 
Portal <https://access.redhat.com/solutions/6232511>.

# alternatives --config java

Naturally, there are many different scenarios and complications where that 
command is the wrong choice.  For most people, the simplest choice is to 
switch the system path to Java and that is what alternatives will do.

If that is not what you prefer, then you can configure a specific Java path 
through

# systemctl edit jenkins
 
The Jenkins documentation includes a guide to managing services with systemd 
<https://www.jenkins.io/doc/book/system-administration/systemd-services/>.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7724e4c7-62f1-4c2a-bb4e-d8f39e1f565bn%40googlegroups.com.

Re: Jenkins Won't start after latest ugrade

[Mark Waite]

See 
https://www.jenkins.io/doc/administration/requirements/upgrade-java-guidelines/ 
for instructions and a video describing the steps

On Wednesday, September 14, 2022 at 10:06:19 AM UTC-6 slide wrote:

> The latest weekly releases dropped support for Java 8, so you will need to 
> update to Java 11 at a minimum. You may need to look if there is a separate 
> yum package for Java 11 (e.g., if Java 8 is still the default in your OS, 
> then yum update java may not update to Java 11, it may just update to the 
> latest Java 8).
>
> On Wed, Sep 14, 2022 at 8:59 AM eric@gmail.com  
> wrote:
>
>> Here's what I did:
>>
>> yum update jenkins
>>
>> Here's what's happening trying to get version info after upgrade.  Also 
>> won't start with systemctl start jenkins.
>>
>> [root@nd645bd001 ~]# /bin/jenkins -version
>> Sep 14, 2022 10:56:24 AM executable.Main verifyJavaVersion
>> SEVERE: Running with Java class version 52, which is older than the 
>> Minimum required version 55. See 
>> https://jenkins.io/redirect/java-support/
>> java.lang.UnsupportedClassVersionError: 52.0
>> at executable.Main.verifyJavaVersion(Main.java:145)
>> at executable.Main.main(Main.java:109)
>>
>> Jenkins requires Java versions [17, 11] but you are running with Java 1.8 
>> from /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.342.b07-1.el7_9.x86_64/jre
>> java.lang.UnsupportedClassVersionError: 52.0
>> at executable.Main.verifyJavaVersion(Main.java:145)
>> at executable.Main.main(Main.java:109)
>>
>> Seems I need to upgrade java, but jenkins doesn't control java.  Please 
>> advise.  Should I just yum update java?
>>
>> Thanks,
>> Eric
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/63ddfcc2-b01e-4f44-8c6e-9ee40f923905n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Website: http://earl-of-code.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/987308da-c629-4352-996b-a87d1b195066n%40googlegroups.com.

Re: HTTPS - works okay, but 2 problems

[Mark Waite]

On Tuesday, September 13, 2022 at 7:26:12 PM UTC-6 John wrote:

> Hello,
>
> We are running Jenkins 2.368 on a Rocky 8 Linux server. I was asked to 
> implement SSL onto our Jenkins service, and have done that using a 
> keystore. (I only deal with the server itself as a sysadmin, I do not use 
> Jenkins myself for CI purposes.)
> This all seems to work okay, but I have noticed two issues:
>
> 1) Despite changing the '/etc/sysconfig/jenkins' file setting the 
> JENKINS_PORT to -1 and setting the JENKINS_HTTPS_PORT to 8443, port 8080 is 
> still listened upon by Jenkins. Using the 'lsof' command from a console 
> shows that both ports 8080 and 8443 are listening. The 'System Information' 
> page within Jenkins shows that it is also present on the supplied java 
> command-line (as the --httpPort option). How do we fully disable the use of 
> port 8080?
>
>
If you installed Jenkins 2.368 on Rocky 8 Linux with the yum command, then 
Jenkins should be configured with "systemctl edit jenkins" instead of 
editing the '/etc/sysconfig/jenkins' file.  

The "Managing systemd services 
<https://www.jenkins.io/doc/book/system-administration/systemd-services/> 
page provides more details.
 

> 2) The keystore password is exposed in the 'ps' command output, and in the 
> 'System Information' page found when I log into Jenkins and look under the 
> 'Manage Jenkins' page. This is obviously not secure. Perhaps the password 
> should be stored as part of the Jenkins configuration rather than just 
> passed onto the command-line from the sysconfig file?
>  Is there another way to hide the password?
>
>
I'm not sure on that one.  You may need to replace the ExecStart with the 
specific command line arguments that you want to use.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a159ca1c-1369-4382-bcad-59ce56d59f6en%40googlegroups.com.

Re: Problems upgrading from 2.263 to 2346.2

[Mark Waite]

On Tuesday, September 13, 2022 at 5:31:07 PM UTC-6 Robert wrote:

> Currently I see this in the system log
>
> It appears whenever you look at a job from the dashboard and it needs to 
> show it’s build history.
>
> Kind of puzzling why this happens for some jobs and not others.
>
> The jobs appear under a Folder.
>
> java.lang.NoSuchMethodError: com.google
> .common.util.concurrent.MoreExecutors.sameThreadExecutor()com/google/common/util/concurrent/ListeningExecutorService
>
>
The instructions in the upgrade guides for the intervening versions between 
2..263 and 2.346.2 will help with this issue.  Your upgrade crosses several 
major changes in Jenkins.  The upgrade guides provide critical instructions.

Specifically, be sure that you have upgraded all the plugins to their most 
recent releases.
 

> this all is in a stack where it looks like it’s calling getLastBuild on 
> LazyBuildMixIn
>
> deeper down it’s doing 
> AbstractFolder.getBuildHealthReports(AbstractFolder.java:925)
>
> It’s using idk 1.8.0_121 on the controller
>
>
Please upgrade to a newer version of Java 8.  Eclipse Temurin provides JDK 
1.8.0_345 at no charge.  Other Java providers (Red Hat, Azul, Amazon) also 
provide similar versions at no charge.

Even better to upgrade to a Java 11 version.  The Jenkins project no longer 
support Java 8 on the controller.  See 
the https://www.jenkins.io/blog/2022/06/28/require-java-11/ for the 
announcement from June 2022.
 

> It’s noticeable that
>
> Some jobs are able to show their build history
>
> Some jobs cannot and error with 
>
> “A problem occurred while processing the request”
>
> I’m using Folders plugin 6.4
>
>
Folders plugin was released 4 years ago.  Upgrade the plugins.
 
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/714ee0b6-1b29-456a-8ae5-75b23e830b4en%40googlegroups.com.

Re: Highest Jenkins Version usable with Java 8

[Mark Waite]

On Friday, September 2, 2022 at 7:42:09 AM UTC-6 Randall wrote:

> Hi All,
>
> I am stuck with Java 8 on one platform and cannot upgrade. What is the 
> latest Jenkins version I can use? (Docker is not involved).
>

 Jenkins 2.346.3 <https://www.jenkins.io/changelog-stable/#v2.346.3> is the 
most recent Jenkins LTS.  It supports Java 8.

Jenkins 2.356 <https://www.jenkins.io/changelog/#v2.356> is the last 
Jenkins weekly release that supports Java 8.  It was released 

The Jenkins 2.361.1 LTS that is scheduled to release Sep 7, 2022 will not 
support Java 8.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ce68f6ab-3a6b-42c9-ae78-1dac0f992581n%40googlegroups.com.

Re: Edit pipeline in BlueOcean

[Mark Waite]

On Tuesday, August 30, 2022 at 7:54:23 AM UTC-6 Anderson Cruz wrote:

> Hello everyone,
>
> I'm running a Jenkins 2.346.1 LTS with Role Based Strategy and facing the 
> issue describe here 
> https://issues.jenkins.io/browse/JENKINS-48219?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab
>
> [image: a722e38a-6e17-461a-9f5f-e393482eefdf.png]
> Non-admin users cannot click on BlueOcean Pencil to edit pipeline. Just do 
> not show/render on their screen. I've tried the permissions manually on 
> config.xml but did not work as well.
>
> Any suggestions?
>

I think you'll need to guide your users to edit their Pipelines with their 
preferred text editor rather than using the Pipeline editor that is 
provided with Blue Ocean.

The issue report <https://issues.jenkins.io/browse/JENKINS-48219> seems 
unlikely to be fixed based on the note in the Blue Ocean pipeline editor 
documentation <https://www.jenkins.io/doc/book/blueocean/pipeline-editor/> 
that says:

> Blue Ocean will not receive further functionality updates. Blue Ocean 
will continue to provide easy-to-use Pipeline visualization, but it will 
not be enhanced further. It will only receive selective updates for 
significant security issues or functional defects.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f17d4bec-57a8-46d3-b770-737234140f6an%40googlegroups.com.

Re: JDK parameter plugin

[Mark Waite]

On Monday, August 29, 2022 at 11:20:25 AM UTC-8 you wrote:

> There is a STored XSS vulnerability for the JDK Parameter plugin.We use 
> this plugin to specify the JDK version for our Builds compilation. Is there 
> any plans to upgrade the plugin or can I use the any other plugin ? TIA


The JDK parameter plugin <https://plugins.jenkins.io/JDK_Parameter_Plugin/> was 
last released 9 years ago.  There have only been three pull requests to the 
plugin since the 1.0 release 9 years ago.  I've seen no mention from anyone 
of any plan to fix that vulnerability or to modernize the plugin. 

If the plugin matters to your employer, you could ask your employer to 
allow you or one of your colleagues to maintain the plugin.  That would 
meet your need for the plugin and would help the other 4000+ installations 
of the plugin.

A five part video series on modernizing a Jenkins plugin 
<https://www.youtube.com/watch?v=Fev8KfFsPZE> is available.  There is also 
a 3 part video series that illustrates how to fix a security vulnerability 
<https://www.youtube.com/watch?v=D-b9WWx1Xes>.  If you prefer a written 
tutorial, see the "Modernizing a Jenkins plugin" 
<https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit?usp=sharing>google
 
doc.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/360900ca-d0f9-4f6b-a00e-1dc6d3dfc65dn%40googlegroups.com.

Re: Error installing plugins for Jenkins 2.346.2

[Mark Waite]

On Friday, August 5, 2022 at 9:00:12 AM UTC-6 Sunil wrote:

> These are the steps I followed as per the documentation: 
> wget -O /etc/yum.repos.d/jenkins.repo \ 
> https://pkg.jenkins.io/redhat-stable/jenkins.repo 
> rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key 
> yum upgrade 
> # Add required dependencies for the jenkins package 
> yum install java-11-openjdk 
> yum install jenkins 
> systemctl daemon-reload 
>
> systemctl enable jenkins 
> systemctl start jenkins 
> systemctl status jenkins 
>
> Is there a way to upload plugins through the console? I am able to 
> download the plugins using wget. Is there a way for me to install the 
> downloaded plugin? 
>
 
https://stackoverflow.com/questions/19540289/how-to-fix-the-java-security-cert-certificateexception-no-subject-alternative
 
suggests that exception is related to SSL certificates.  Maybe the yum 
upgrade needs to be followed by a restart of the computer?

https://blog.devgenius.io/rhel-centos-7-fix-for-lets-encrypt-change-8af2de587fe4
 
discusses more about certificate updates and CentOS 7.  Be sure that the 
ca-certificates package is installed and is the most recent release.

The Jenkins plugin installation manager tool 
(https://github.com/jenkinsci/plugin-installation-manager-tool/) can 
download plugins and their dependencies from a command line.  However, 
since it is a Java tool and you're seeing a Java exception, I suspect that 
it will report the same exception.

The plugin manager page in Jenkins will accept uploads as either files or 
as URLs.  However, the upload page does not automatically download 
dependent plugins.  Much better to fix whatever issues causes your computer 
to not allow Java to access SSL secured web sites.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/674e0657-ee8f-4993-a79b-bede98a807c9n%40googlegroups.com.

Re: Error installing plugins for Jenkins 2.346.2

[Mark Waite]

On Friday, August 5, 2022 at 8:35:12 AM UTC-6 Sunil wrote:

I am running into errors installing plugins on a new Jenkins 
> installation on Linux.
>

 

> java.security.cert.CertificateException: No subject alternative DNS 
> name matching updates.jenkins.io found. 
>
>
Have you updated the operating system packages to the most recent 
releases?  We've seen issues in the past where a user installed the 
operating system and was unable to use current SSL certificates because 
their operating system had not been updated with the most recent packages.

# yum update

I actually prefer "yum upgrade" 
but 
https://unix.stackexchange.com/questions/55777/in-centos-what-is-the-difference-between-yum-update-and-yum-upgrade
 
warns that "yum update" may be the better choice for most users.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f584711c-0204-400e-81d4-0d079fadcaa6n%40googlegroups.com.

Re: jenkins endpoints

[Mark Waite]

On Monday, July 25, 2022 at 8:14:02 PM UTC-6 maanideep wrote:

> Hi,
>
> could someone please get me Jenkins REST API endpoint for project build .
>
> https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-PROJECTS
> please help
>
> something similar to this
>

See the "REST API" link at the bottom right side of the Jenkins page for 
the job.  There is a link "REST API".  When that link is clicked, it opens 
a page that describes many different portions of the REST API for that job.

For 
example, 
https://ci.jenkins.io/job/Plugins/job/elastic-axis-plugin/job/master/api/ 
will show the REST API for the Elastic Axis plugin job on ci.jenkins.io 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/93811d6a-1c91-4e18-8ba3-d445ecd82131n%40googlegroups.com.

Re: Plugin update on Jenkins 2.346.2 broken

[Mark Waite]

On Monday, July 18, 2022 at 9:13:57 AM UTC-6 Alan Sparks wrote:

> I tried this morning to run a plugin update on my test instance running 
> 2.346.2, and it broke very badly.  It came back up with 40+ plugins 
> disabled, and reports of cyclic dependencies.
>
>  
>
> For instance:
>
> Cycle detected: Plugin:sshd -> Plugin:mina-sshd-api-core -> 
> Plugin:ssh-credentials -> Plugin:credentials -> 
> Plugin:configuration-as-code -> Plugin:commons-text-api -> 
> Plugin:commons-lang3-api -> Plugin:sshd
>
>  
>
> Jenkins log:
>
> 2022-07-18 14:20:16.845+ [id=30]SEVERE  
> hudson.PluginManager$1$3$2$1#reactOnCycle: found cycle in plugin 
> dependencies: (root=Plugin:sshd, deactivating all involved) Plugin:sshd -> 
> Plugin:mina-sshd-api-core -> Plugin:ssh-credentials -> Plugin:credentials 
> -> Plugin:configuration-as-code -> Plugin:commons-text-api -> 
> Plugin:commons-lang3-api -> Plugin:sshd
>
>  
>
> I know that these plugins were updated:
>
> mina-sshd-api-common
>
> mina-sshd-api-core
>
>  
>
> I can’t get any of the critical plugins re-enabled.  Is this a known issue?
>

Yes, it was reported a few hours ago 
as https://issues.jenkins.io/browse/JENKINS-69034

Workaround is to not install the latest releases of those two plugins.  
Revert to the previous versions of those plugins.

Mark Waite 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f97f3933-33a9-42f7-84ce-7972cd2e955en%40googlegroups.com.

Re: Unable to sign up to accounts.jenkins.io

[Mark Waite]

On Friday, June 17, 2022 at 6:10:29 AM UTC-6 Josef wrote:

> Hi,
> I am currently unable to sign up to accounts.jenkins.io (
> https://accounts.jenkins.io/signup).
> I successfully posted the singn-up form, but have received no confirmation 
> e-mail.
>
> When I do another sign-up attempt, I get an error message informing me 
> that my userid/e-mail already exist.
>
> I also tried password reset, but with the same result: no e-mail received.
>
> This prevents me to start a feature request in the issue tracker (I am 
> ready to create a pull request, and want to stick to the rules).
>
> Could anyone please help?
>

Could you provide the username or the email address you used to register in 
a new issue at https://github.com/jenkins-infra/helpdesk ?  That will allow 
the infra team to assist you.

Thanks,
Mark Waite 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a61cbfd8-549b-4a0c-80c6-5b85d922963an%40googlegroups.com.

Re: Jenkins running as a service restarts by itself after upgrade from 2.303.2 to 2.319.3

[Mark Waite]

On Friday, June 10, 2022 at 2:06:48 PM UTC-6 Chris wrote:

> As I've already mentioned (maybe it was not very clear - so just to 
> remind):
>
> 1. OS is Red Hat Linux 7.9
>
> 2. I can't see any valid jenkins package in the system: ‘rpm -qa | grep -i 
> jenkins’ command doesn’t show anything 
>
> 3. Running ‘yum list | grep -i jenkins’ shows only these 3 packages:
>
> python2-jenkins.noarch 0.4.16-2.el7 1cvmware_EPEL_EPEL_7Server
>
> python2-jenkins-job-builder.noarch
>
> python36-jenkins.noarch 0.4.16-2.el7 1cvmware_EPEL_EPEL_7Server
>
>
> What else should I check - do you have any suggestions ?
>
Since there is no Jenkins package installed, the system must have a 
jenkins.war file that someone in your organization used to create their own 
service to run the Jenkins war file.   Your choices include:

   - Adapt your custom systemd service to match the systemd implementation 
   in the Jenkins RPM package.  If there are future changes to the Jenkins 
   systemd implementation, you'll need to update your service definition to 
   match those changes
   - Replace your custom systemd service that is running jenkins.war with 
   the standard Jenkins RPM package

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/702ee36e-7955-4bef-8f39-34bf53ca7ffen%40googlegroups.com.

Re: Jenkins running as a service restarts by itself after upgrade from 2.303.2 to 2.319.3

[Mark Waite]

On Friday, June 10, 2022 at 7:12:40 AM UTC-6 fcenedese wrote:

> At 08:16 10.06.2022, you wrote: 
>
> >Hi, 
> > 
> >I upgraded Jenkins (running as a service) from version 2.235.5 to 2.303.2 
> (by just replacing .war file and restarting the service), which seemed to 
> work pretty stable. Before doing it, I upgraded Java from OpenJDK 8 to 
> OpenJDK 11, which was the prerequisite for Jenkins upgrade. I tried to 
> upgrade even to 2.319.3 or to 2.332.3 and I was able to log in to GUI with 
> my AD credentials after upgrade, however there are some issues which cause 
> Jenkins to restart by itself from time to time when using these 2 releases, 
> so for now I downgraded it back to 2.303.2.
>

One issue might be related to the technique you used to perform the upgrade 
to Jenkins 2.332.3.  Unfortunately, you haven't provided enough information 
for others to know if you made that mistake or not.

If the original installation used a Linux package (deb or rpm), then you 
failed to upgrade correctly when you upgraded by replacing the war file.  
Please use the Linux package manager to upgrade if you used the Linux 
package manager for the initial installation.

Please review the changelog and the upgrade guide for the releases.  
Specifically note in the Jenkins 2.332.1 changelog 
<https://www.jenkins.io/changelog-stable/#v2.332.1> that the Jenkins Linux 
installers switched from System V init to systemd.  Note in the Jenkins 
2.332.1 upgrade guide <https://www.jenkins.io/changelog-stable/#v2.332.1> that 
the Jenkins Linux installers switched from System V init to systemd.  There 
is also a blog post 
<https://www.jenkins.io/blog/2022/03/25/systemd-migration/> that describes 
the details needed for an issue report 
<https://www.jenkins.io/blog/2022/03/25/systemd-migration/#reporting-issues> 
that will allow others to help with the issue.

Note that the Linux installer change did not affect Jenkins 2.319.3, so if 
you were seeing restarts in Jenkins 2.319.3, then it was not related to the 
change from System V init to systemd.

If the original installation used the Windows installer, then you are 
making a large enough jump in versions that you should probably install 
with the latest Windows installer rather than replacing the war file.

Another issue might be related to possible bug in Jenkins that is reported 
as Java 11 requiring more memory that Java 8 for a similar configuration.  
Unfortunately, you haven't provided enough information for others to know 
if that is the issue or not.  One confirmed instance of that report is the 
metaspace 
memory leak report <https://issues.jenkins.io/browse/JENKINS-63766> in 
JENKINS-63766 <https://issues.jenkins.io/browse/JENKINS-63766>.  If that is 
the specific issue, then updating plugins to most recent versions should 
resolve it.

If it is none of those things, then you'll need to provide more details 
that help isolate the cause of the issue.
 

> >The question is why is this happening ? 
>
> I can't offer an explanation or even a solution but we too had that 
> problem of Jenkins restarting. As consequence I downgraded from 
> Jenkins 2.332.3. It may have been rather a problem with Java 11 
> but I don't remember exactly. Currently we're using Jenkins 
> version 2.319.3 (on Ubuntu) with openJDK 8 and that is stable. 
> Of course we'd welcome a solution to this problem as well. 
>
>
Since Jenkins weekly will end support of Java 8 in June 2022 and Jenkins 
LTS will end support of Java 8 in September 2022, it is in your best 
interest to provide enough information so that others can understand and 
assist with the issue you're seeing.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/877d8fb6-20f4-4125-aca0-85380ac1a14en%40googlegroups.com.

Re: How to uninstall Pipeline: Deprecated Groovy Libraries

[Mark Waite]

Releases are available that remove the dependency.

On Tuesday, May 24, 2022 at 3:54:42 PM UTC-6 alan.l...@microfocus.com wrote:

>  
>
> Thanks for that answer.  I’ll watch for those releases.
>
> -Alan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0e3a24e8-f1d1-4a32-82ef-569680382925n%40googlegroups.com.

Re: Git Source Code Management Oddity

[Mark Waite]

On Monday, May 23, 2022 at 11:57:28 AM UTC-6 Eric wrote:

> Also note that I AM using the "with credentials" from the plugin.
>
>
I don't understand that statement.

If you're using the `withCredentials` wrapper in a Pipeline, then you don't 
need to use the thing that the git plugin calls the "Git Publisher post 
build step".  Perform the push of the plugin from a shell, batch, or 
powershell step inside a `withCredentials` wrapper.  Much easier to manage 
a `withCredentials` wrapper with shell commands than to wrestle with the 
`Git publisher post build step`.

Mark Waite
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1b95410b-a81f-4a70-83e6-70e5cec86e3an%40googlegroups.com.

Re: How to uninstall Pipeline: Deprecated Groovy Libraries

[Mark Waite]

On Tuesday, May 24, 2022 at 3:27:28 PM UTC-6 Alan Sparks wrote:

> So this plugin (Pipeline: Deprecated Groovy Libraries) is now marked 
> deprecated and I’m trying to remove it.  But I don’t seem to see how.
>
>  
>
> When I check, I have “Pipeline: Groovy Libraries” already installed.  But 
> If I go to uninstall the deprecated one, it tells be I have dependencies on 
> “Pipeline: Declarative” and “GitLab”.   I need both of those.
>
>  
>
> I don’t see a procedure on the plugin info page how to work around the 
> dependencies.  Can someone point me to how to uninstall this plugin?  
> Thanks.
>
>  
>
You'll need to wait for the two plugins to be released with an update to 
their dependencies so that they do not depend on the deprecated plugin.  

The "Pipeline: Declarative" change 
<https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/530> 
was merged about 2 hours ago and is likely to be released very soon.

The GitLab plugin does not have a pull request 
<https://github.com/jenkinsci/gitlab-plugin/pulls> submitted for it yet.  
Once the pull request has been submitted and merged, then you'll need to 
update to that version.  Then you'll be able to remove the deprecated 
plugin.

Mark Waite

>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5863a3ff-e0bb-4eba-b6f4-b2babc5a0ff2n%40googlegroups.com.

Re: Git Source Code Management Oddity

[Mark Waite]

On Thursday, May 19, 2022 at 8:42:29 AM UTC-6 Eric Fetzer wrote:

> OK, I've been having some major issues with Git source code management in 
> Jenkins.  So I have several repositories I pull from to do builds.  I use 
> my same credentials to pull from each.  If the pull succeeds, I push a tag 
> at it.  I was noticing certain tags were failing saying it already existed 
> even though it didn't exist.  Well, it didn't exist in THAT repository.  
> But it did exist in one of the other repositories.  I tested by creating 
> these tags in git command line and pushing them and it worked fine.  Anyone 
> have a clue what could be happening here?  The jenkins task goes to my 
> repository's url with my credentials selecting from the branch I tell it.  
> It's set to clean before check out.  It does all of this fine.  It has a 
> Git Publisher post build step to push my tag only if the checkout succeeds 
> with the box checked to create new tag.  This works UNLESS that same tags 
> exists in any of the projects I run this checkout task against.  Can anyone 
> think of a reason for this odd behavior?  Thanks!!!


I don't know if the git publisher in the git plugin is able to handle 
checkout from multiple repositories.  It may not be that sophisticated.

You may need to switch to use the "with credentials" feature that was added 
in Google Summer of Code 2021 to allow you to perform the push of the tag 
yourself rather than using the git publisher.  Docs on the "with 
credentials" feature are available 
at https://plugins.jenkins.io/git/#plugin-content-credential-binding 
(Pipeline) and https://plugins.jenkins.io/git/#plugin-content-git-bindings 
(freestyle) 

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ef07f787-0884-49a9-9ea3-960b6eeb021fn%40googlegroups.com.

Re: Log location and WEBROOT changed after Jenkins upgrade

[Mark Waite]

On Monday, May 2, 2022 at 1:14:45 PM UTC-6 you wrote:

> Hello,
> I recently upgraded Jenkins from 2.263.4/2.303.3 to 2.332.2 on three 
> CentOS 7 machines, using the official jenkins.io packages from the 
> redhat-stable repository.
> While Jenkins (since years!) always saved its log as /var/log 
> /jenkins/jenkins.log, now it sends all log messages to syslog 
> (/var/log/message) instead.
> Was this an expected change?
>
>
Yes, that is an expected change.

The Jenkins 2.332.2 upgrade guide notes that Jenkins has switched from 
System V init to systemd.  Read more about it 
at https://www.jenkins.io/doc/upgrade-guide/2.332/

The Jenkins 2.332.2 changelog notes that Jenkins has switched from System V 
init to systemd.  Read more about it 
at https://www.jenkins.io/changelog-stable/#v2.332.1

The "What's new in Jenkins 2.332.2 livestream" notes that Jenkins has 
switched from System V init to systemd.  Learn more about it 
at https://youtu.be/JO0BSpVjUJ8

The "Managing systemd services" page in the Jenkins documentation gives 
more information about managing systemd services with Jenkins.  
See https://www.jenkins.io/doc/book/system-administration/systemd-services/

The "Managing the systemd service on CentOS 7.9" video by Darin Pope 
provides more information 
at https://youtu.be/MkokjTQ2ngc?list=PLvBBnHmZuNQJeznYL2F-MpZYBUeLIXYEe
 

> What's more, I also noticed that a "%C" directory has been created in 
> Jenkins' home which only contains a jenkins/war subdir and the contents I 
> list below.
>
> In the systemd service definition 
> (/usr/lib/systemd/system/jenkins.service) indeed I now see:
>
> 
> # Location of the exploded WAR
> Environment="JENKINS_WEBROOT=%C/jenkins/war"
>
> # Location of the Jenkins log. By default, systemd-journald(8) is used.
> #Environment="JENKINS_LOG=%L/jenkins/jenkins.log"
> 
>
> I tried performing a clean install on a fresh VM and the result is the 
> same.
> Is this a bug in the official Jenkins packages?
> I suppose %C and %L were meant to be something else...
> Can I safely change this configuration?
>
>
Yes, you can change that configuration.  
Per 
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Specifiers 
, the '%C' should be expanded by systemd to be the system cache directory.  
On my Red Hat Enterprise Linux 8 that is /var/cache.

Based on https://issues.jenkins.io/browse/JENKINS-68313, it appears that 
the CentOS 7 implementation of systemd does not support the '%C' 
specifier.  Replace it with the text for the cache directory on your 
operating system.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2d7e8855-30d9-4422-8c6e-52e8fcb0f07bn%40googlegroups.com.

Re: Alternative for Multiple SCM plugin

[Mark Waite]

On Tuesday, April 19, 2022 at 9:19:00 AM UTC-6 adharsh wrote:

> Hi, 
> Thanks for the reply.
> Having 100's of pipeline projects in Jenkins may lead to performance and 
> disk space issues on Jenkins controller right. Correct me if I am wrong.
>


I run thousands of Pipeline projects on my Jenkins and have not see 
performance issues.  Jobs do use disc space, but that happens whether they 
are Pipeline or Freestyle.  It is a mistake to avoid Pipeline jobs because 
you're worried about performance and disk space issues with hundreds of 
jobs. 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/daf1a935-e6b6-4060-ab34-3b1ee6ace88fn%40googlegroups.com.

Re: Jenkins project response to Russian invasion of Ukraine

[Mark Waite]

I failed to attach the alternative image.  Here it is 

On Wednesday, April 6, 2022 at 12:39:21 PM UTC-6 Mark Waite wrote:

> The Jenkins project has posted a statement of support for Ukraine on its 
> home page at https://www.jenkins.io/ .  The statement says:
>
> We stand with the people of Ukraine. Please assist humanitarian efforts 
> for the Ukrainian people and those affected by the military invasion of 
> Ukraine by supporting international aid organizations, including the 
> International 
> Committee of the Red Cross <https://www.icrc.org/>
>
> Two pull requests have been opened proposing a more visible message.
>
> PR-5027 <https://github.com/jenkins-infra/jenkins.io/pull/5027> - Site 
> preview <https://deploy-preview-5027--jenkins-io-site-pr.netlify.app/> 
> (Cossack 
> with "Stop the war" on a flag)
>
> PR-5030 <https://deploy-preview-5030--jenkins-io-site-pr.netlify.app/> - Site 
> preview <https://deploy-preview-5030--jenkins-io-site-pr.netlify.app/> 
> (Butler 
> with open eyes and "Stop the war" flag)
>
> We'd like more community opinions on those two alternatives.  Respectful 
> comments on the pull requests or upvotes on the existing comments in the 
> pull requests will help us understand which of the two is preferred by the 
> community.  You're also welcome to reply to this message with your 
> preferences.
>
> Please adhere to the Jenkins code of conduct 
> <https://www.jenkins.io/project/conduct/> in all comments and 
> interactions in the Jenkins community.
>
> Thanks,
> Mark Waite - Jenkins Documentation Officer
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/31f878d0-6d45-4554-9462-4cd12d23a74fn%40googlegroups.com.

Jenkins project response to Russian invasion of Ukraine

[Mark Waite]

The Jenkins project has posted a statement of support for Ukraine on its 
home page at https://www.jenkins.io/ .  The statement says:

We stand with the people of Ukraine. Please assist humanitarian efforts for 
the Ukrainian people and those affected by the military invasion of Ukraine 
by supporting international aid organizations, including the International 
Committee of the Red Cross <https://www.icrc.org/>

Two pull requests have been opened proposing a more visible message.

PR-5027 <https://github.com/jenkins-infra/jenkins.io/pull/5027> - Site 
preview <https://deploy-preview-5027--jenkins-io-site-pr.netlify.app/> (Cossack 
with "Stop the war" on a flag)

PR-5030 <https://deploy-preview-5030--jenkins-io-site-pr.netlify.app/> - Site 
preview <https://deploy-preview-5030--jenkins-io-site-pr.netlify.app/> (Butler 
with open eyes and "Stop the war" flag)

We'd like more community opinions on those two alternatives.  Respectful 
comments on the pull requests or upvotes on the existing comments in the 
pull requests will help us understand which of the two is preferred by the 
community.  You're also welcome to reply to this message with your 
preferences.

Please adhere to the Jenkins code of conduct 
<https://www.jenkins.io/project/conduct/> in all comments and interactions 
in the Jenkins community.

Thanks,
Mark Waite - Jenkins Documentation Officer

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6f3b3543-5fce-41fa-8584-435af2c51040n%40googlegroups.com.

Re: About the Spring4Shell vulnerability (CVE-2022-22965)

[Mark Waite]

On Tuesday, April 5, 2022 at 8:20:29 AM UTC-6 Tomonari Katsumata wrote:

> Hello 
>
> I'm the one who recently started using these JenkinsPlugins. 
> - generic-webhook-trigger 1.67 
> - kubernetes 1.19.3 
> - pipeline-model-definition 1.6.0 
> - git 4.2.2 
> - git-client 3.2.1 
> - scmskip 1.0.1 
> - openshift-sync 1.0.45 
> - gitlab-plugin 1.5.13 
> (I use Jenkins 2.204.2) 
>
>
No one has analyzed that Jenkins core version or those plugin releases to 
see if they are vulnerable.  No one will analyze those versions.

You may not be affected by Spring4Shell but you *are* *affected* by *many* 
Jenkins security advisories.  
See https://www.jenkins.io/security/advisories/ for the Jenkins core 
security advisories that may apply to that old Jenkins core version.

As a sampling, the security advisories include:

   - https://www.jenkins.io/security/advisory/2022-02-09/
   - https://www.jenkins.io/security/advisory/2022-01-12/
   - https://www.jenkins.io/security/advisory/2021-11-04/
   - https://www.jenkins.io/security/advisory/2021-10-06/
   - https://www.jenkins.io/security/advisory/2021-06-30/
   - https://www.jenkins.io/security/advisory/2021-04-20/
   - https://www.jenkins.io/security/advisory/2021-02-19/
   
I only gathered security advisories for the last year.  Your Jenkins 
version is two years old.

Since you care enough about security to ask about Spring4Shell, you 
certainly care enough to resolve all those security advisories by upgrading 
Jenkins core and the Jenkins plugins that you use.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/61fd52ce-b8f5-4e5b-8f20-1ba83b701bb0n%40googlegroups.com.

Re: JMeter Performance plugin having XXE vulnerability

[Mark Waite]

On Monday, April 4, 2022 at 9:32:56 AM UTC-6 Arun Suresh wrote:

> JMeter performance plugin is listed with vulnerability: 
> https://plugins.jenkins.io/performance/ 
> So currently its not safe to use this plugin(
> https://www.jenkins.io/security/advisory/2021-11-12/#SECURITY-2394).
>
> Can you please help us to fix this issue. Currently I'm facing issue that 
> I don't find any other alternative plugin also to use since this plugin 
> currently have this vulnerability. 
> Due to this vulnerability, currently security guidelines is not allowing 
> us to use this plugin. Will be extremely helpful if you can support us 
> here. 
>
> The current maintainers were informed of the vulnerability before it was 
published without a fix.  They did not have the capacity to fix it.  I 
assume they still do not have the capacity to fix it.

You are welcome to adopt the plugin and fix the issue.  It would be a good 
way for your employer to get the fix they need and a good way for them to 
contribute to the Jenkins community.  The "Contributing to Open Source" 
<https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit?usp=sharing>
 
workshop from DevOps World 2021 provides a series of steps that you could 
take to prepare to adopt the performance plugin.  There is a five part 
video series <https://www.youtube.com/watch?v=Fev8KfFsPZE> linked in that 
document that introduces the concepts and illustrates the tasks to consider 
as you adopt a plugin.

As another alternative, you could push the JMeter results to a different 
location (a web server somewhere inside your company) and guide people to 
read the results from that web server.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8806fe7d-850f-4ac0-9a2f-fb3901acef21n%40googlegroups.com.

Re: How to create web service health check using jenkins pipeline?

[Mark Waite]

On Thursday, March 31, 2022 at 9:37:40 AM UTC-6 misteek wrote:

> Hi all,
>
> New to jenkinsfile/groovy world. 
>
> Can someone please let me know how to create a jenkins pipeline health 
> check to check if multiple websites are running. 
>
> If any of the sites are down or http response code is not 200 an email 
> notification should be sent.
>
> For every website to be checked should I create separate "stages" in the 
> pipeline or is there a better way?
>

I think that what you're describing is a "test" to confirm the web sites 
are running.  One way to implement that is to create the web site checker 
as tests that output their results in JUnit format, then use the JUnit 
plugin to display the results in Jenkins.

That allows you to run the tests outside Jenkins and see multiple results 
inside Jenkins.

For example, you could write the test in Python and output the result to a 
junit format with as 
described 
https://stackoverflow.com/questions/11241781/python-unittests-in-jenkins

Another example, you could write the test in Javascript with jest, as 
described 
in 
https://stackoverflow.com/questions/54294612/how-to-publish-jest-test-results-in-jenkins

You could write the test in Java and output the result to junit format as 
done in the tutrorial 
https://www.jenkins.io/doc/tutorials/build-a-java-app-with-maven/#add-a-test-stage-to-your-pipeline

Each of those techniques have the benefit that you write the test locally, 
run it locally, then use Jenkins to execute the same test as you run 
locally.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9c68d983-688f-4a8d-a191-ca22d386ffb5n%40googlegroups.com.

Re: cron trigger limited to one branch in the Jenkinsfile

[Mark Waite]

On Monday, March 14, 2022 at 2:44:52 AM UTC-6  François wrote:

> no one knows how to limit a cron to a branch in a Jenkinsfile ?
>
>
See 
https://github.com/jenkinsci/packaging/blob/5707f90ede196076fcd1308e517c90d52e0e9d99/Jenkinsfile#L6
 
for one technique to consider.  It makes the cron property conditional 
based on if the current branch is the primary branch in the repository.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/61d65321-8e41-4bf6-a760-de9bd0ca89c1n%40googlegroups.com.

Re: Plugin update "Jenkins (2.323) or higher required"

[Mark Waite]

On Tuesday, March 8, 2022 at 4:44:32 AM UTC-7 Stefan wrote:

> Hi,
>
> We are using the LST cycle but this gives issues when I try to update 
> plugins.
> My use case:
>
> Ansible playbook updates the linux server (and jenkins LST if available)
> After that I use an ansible playbook to (
> https://github.com/wcm-io-devops/ansible-jenkins-facts) look for plugins 
> where "hasUpdate = true" and then update the plugin.
>
>
I think you may be using the wrong tool to update your Jenkins plugins.

https://www.jenkins.io/blog/2022/02/10/last-plugin-version-not-installable/ 
describes the same type of failure you're seeing.

I think you want to call the plugin installation manager tool 
<https://github.com/jenkinsci/plugin-installation-manager-tool> to update 
your plugins.  It takes a Jenkins version number as an argument and will 
not offer a plugin update if the plugin does not support that Jenkins 
release.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6499bd77-7c7a-4008-8bac-c7902efa57d3n%40googlegroups.com.

Re: java.io.IOException: Could not copy remoting.jar into '/var/lib/jenkins' on agent

[Mark Waite]

On Saturday, January 29, 2022 at 8:45:46 AM UTC-7 michael wrote:

>
> I'm running out of options. 
>
>
The Java version you're running is quite old.  You might try an experiment 
with a recent Java version (like 11.0.14 or 8u322) in case there is 
something in that old Java version that prevents it.

Since the Java version is outdated, it may be that the operating system 
where you're running it is also using an outdated set of CA certificates.  
You might try updating the CA  certificates and the other operating system 
packages on the machine.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/15de6aad-9a5c-440e-ace9-67cf5c41898dn%40googlegroups.com.

Re: error

[Mark Waite]

On Saturday, January 1, 2022 at 10:50:41 AM UTC-7 Muni wrote:

> thank you 
> but i got again another error
>
> + ssh -o StrictHostKeyChecking=no ubu...@172.31.2.250 sudo docker rm -f 
> javawebappcontainer
> Warning: Permanently added '172.31.2.250' (ECDSA) to the list of known 
> hosts.ubu...@172.31.2.250: Permission denied (publickey).
> + true[Pipeline] sh 
> <http://18.217.55.199:8080/job/java-web-app-docker/17/console#>+ ssh -o 
> StrictHostKeyChecking=no ubu...@172.31.2.250 sudo docker run -d -p 8080:8080 
> --name javawebappcontainer 
> bhaskar77/java-web-app-docker:17ubu...@172.31.2.250: Permission denied 
> (publickey).[Pipeline] }
>
>
What have you done to diagnose the cause of the message?

What is the Pipeline script statement that is being run when that message 
appears?

What alternatives have you attempted and what were the results?

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/be46bc65-fa38-4829-9165-ae416e6b12d8n%40googlegroups.com.

Re: error

[Mark Waite]

Posting the same question twice to the same mailing list is not helpful to 
your desire to be helped by others.  The people that might help you are 
more likely to be annoyed by multiple posts and more likely to ignore 
future requests for help.

On Saturday, January 1, 2022 at 10:57:10 AM UTC-7 munibh...@gmail.com wrote:

> hi team i got error
> + ssh -o StrictHostKeyChecking=no ubu...@172.31.2.250 sudo docker rm -f 
> javawebappcontainer Warning: Permanently added '172.31.2.250' (ECDSA) to 
> the list of known hosts. ubu...@172.31.2.250: Permission denied 
> (publickey). + true [Pipeline] sh 
>  + ssh -o 
> StrictHostKeyChecking=no ubu...@172.31.2.250 sudo docker run -d -p 
> 8080:8080 --name javawebappcontainer bhaskar77/java-web-app-docker:17 
> ubu...@172.31.2.250: Permission denied (publickey). [Pipeline] } $ 
> ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 9444 
> killed; [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [Pipeline] 
> // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: 
> script returned exit code 255 Finished: FAILURE
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6c73005a-9dbe-4673-8ce5-071ae6e4b220n%40googlegroups.com.

Re: error

[Mark Waite]

On Saturday, January 1, 2022 at 10:35:59 AM UTC-7 you wrote:

> im getting error
>
> java.lang.NoSuchMethodError: No such DSL method 'Stage' found among steps 
> [] 
>

If you're trying to use define a Pipeline stage, the keyword is 'stage', 
not 'Stage'.  As far as I know, the domain specific language keywords are 
case sensitive.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ffd3154a-d75d-4423-a741-16a34af41c41n%40googlegroups.com.

Re: How to find out plugins depending on Matrix-Auth-Plugin

[Mark Waite]

On Friday, December 24, 2021 at 7:51:29 AM UTC-7 Riccardo Foschia wrote:

> Hi Jenkins Users, 
>
> from the change log of Matrix-Auth-Plugin (see 
> https://github.com/jenkinsci/matrix-auth-plugin/blob/master/CHANGELOG.md 
> ): 
>
> "If you use any plugins with a dependency on this plugin, make sure 
> they're compatible with this release before upgrading." 
>
> How do I find those plugins that depend on Matrix-Auth-Plugin? 
>
>
https://plugins.jenkins.io/matrix-auth/#dependencies lists the plugins that 
require matrix auth in the "Required" section.  Those are:

*Required*
Azure AD 
Create Job Advanced 
Job and Node ownership 
OpenShift Login 
Role-based Authorization Strategy 

SSH2 Easy 
Seed Jenkins 

It also lists plugins that have an optional dependency on matrix auth.  
Those are:

*Optional*
Build Failure Analyzer 
View Job Filters 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/41e41ee2-3f19-45cf-9459-ff12aff8cfafn%40googlegroups.com.

Re: Error permission denied when clone remote repo

[Mark Waite]

On Wednesday, December 22, 2021 at 3:28:20 PM UTC-7 Emanuel wrote:

> I install Jenkins in Ubuntu 20.04 and create my first task in my 
> localhost, to clone a test repository en my localhost.
>
> [image: Captura de pantalla de 2021-12-22 17-55-20.png]
>
> when i try to build i see this error "stderr: /home/emanuel/git-test/.git: 
> permission denied"
>
>  

> Running as SYSTEM
> Building in workspace /home/emanuel/git-test
> The recommended git tool is: NONE
> No credentials specified
> Cloning the remote Git repository
> Cloning repository https://github.com/pilchita/test-jenkins.git
>  > git init /home/emanuel/git-test # timeout=10
> ERROR: Error cloning remote repo 'origin'
> hudson.plugins.git.GitException: Could not init /home/emanuel/git-test
>
 

> Caused by: hudson.plugins.git.GitException: Command "git init 
> /home/emanuel/git-test" returned status code 1:
> stdout:
> stderr: /home/emanuel/git-test/.git: Permiso denegado
>
>
Command line git attempted to perform the command "git init  
/home/emanuel/git-test" and was not allowed to write to that location as 
the user that is running the Jenkins controller process.  

Jenkins runs as the user 'jenkins' when installed with the package manager 
on Ubuntu and Debian.  The user 'jenkins' does not have permission to write 
to '/home/emanuel'.

Let Jenkins control its own directories by using the default workspace 
assigned to Jenkins.  Don't assign it to write to /home/emanuel when its 
default is writing to a different location.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4568f64b-c439-49eb-9efe-bccc247c55e7n%40googlegroups.com.

Re: New Log4Shell (CVE-2021-44228) probe for Jenkins Health Advisor plugin by CloudBees

[Mark Waite]

On Tuesday, December 14, 2021 at 9:23:51 AM UTC-7 Arnaud Héritier wrote:

> Hi community,
>
> If you are using the Jenkins Health Advisor plugin by CloudBees ( 
> https://plugins.jenkins.io/cloudbees-jenkins-advisor/ ) we just added a 
> probe to detect when the Controller JVM has a log4j artifact impacted by 
> #Log4Shell (CVE-2021-44228) in its open file descriptors.
>
> If you see it reporting a problem not listed under 
> https://issues.jenkins.io/issues/?jql=labels%20%3D%20CVE-2021-44228 
> please report it.
>
>
I'm a very happy user of the Jenkins Health Advisor.  Highly recommended as 
a way to get email advice from Jenkins experts.  
See https://www.youtube.com/watch?v=p_suN31OIAg for a video introduction to 
Health Advisor.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/790d0a61-7266-4e9a-9620-5d2c4db32782n%40googlegroups.com.

Re: Unable to Install or Update - Debian/Ubuntu

[Mark Waite]

On Friday, December 10, 2021 at 12:58:32 PM UTC-7 you wrote:

>  After adding the key and repository, I receive the following:
>
> Ign:4 https://pkg.jenkins.io/debian-stable binary/ InRelease
> Err:5 https://pkg.jenkins.io/debian-stable binary/ Release
>   Certificate verification failed: The certificate is NOT trusted. The 
> certificate chain uses expired certificate.  Could not handshake: Error in 
> the certificate verification. [IP: 151.101.2.133 443]
>

That may indicate that the base operating system has not been updated and 
so is not ready for the Let's Encrypt SSL certificate that is used on 
pkg.jenkins.io.

Update the operating system packages to the latest package versions.  
See https://www.debian.org/doc/manuals/debian-faq/uptodate.en.html for 
guidance on Debian.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/28c55af3-7c38-4434-938a-6ee6b0642527n%40googlegroups.com.

Re: Master issue after LTS 2.319.1

[Mark Waite]

On Sunday, December 5, 2021 at 1:37:51 PM UTC-7 senthilkum kear wrote:
 

> Do you have any links which suggest running controller and agent on the 
> same machine? whatever I searched I am getting only two VM instructions. It 
> will be great if you could point me to the correct documents. 
> Appreciate your response.
>
>
Same virtual machine is not significantly different from multiple virtual 
machines.  Create a user account for the agent, create a private key / 
public on the account, add the public key to the authorized_keys file, 
configure the agent with the host key of the agent and with the private key 
of the account, and you're ready to run.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f685a0df-58d9-4449-98b8-bba43208e2b3n%40googlegroups.com.

Re: Master issue after LTS 2.319.1

[Mark Waite]

On Saturday, December 4, 2021 at 7:25:03 AM UTC-7 senthilkumar wrote:

> Hi Team,
> After the upgrade Jenkins is suggesting two things, the master node is 
> changed to built-in and you can't run jobs on the master node. 
>
> This is not an issue when we have a bigger Jenkins environment, like one 
> master and multiple agents. But the issue comes when we have a small 
> footprint. For example, we have a couple of Jenkins environments where we 
> have only one master(inbuilt node now) and less than 10 jobs. How we can 
> modify this to comply with the latest security changes?
>
> - Have one master and run all jobs?
> - Have one master with zero executors and have one agent on the same 
> machine?
> - Have one master and one agent on different VM or machines? - This way we 
> are increasing the footprints.
>

Please use 'controller' rather than 'master'.  It's more inclusive.

A controller with zero executors and an agent on the same machine is likely 
the best "small footprint" approach of the three you offered.   Use a 
separate account for the agent process and use file system permissions to 
prevent the agent process from reading the contents of the JENKINS_HOME 
directory.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/66321260-c1e1-4248-982c-d281426fbc11n%40googlegroups.com.

Re: Jenkins master after LTS 2.319.1

[Mark Waite]

On Saturday, December 4, 2021 at 7:25:03 AM UTC-7 senthilkumar wrote:

> Hi All,
> This question is already asked, but the current LTS version pushing us to 
> use agent due to the security issue. so what will be the further steps. 
>
> Currently we have multiple teams using Jenkins. We have single node 
> Jenkins and master and agent node Jenkins. Those running on master and 
> agent its not an issue. But some teams using only one Jenkin machine as 
> their footprint is very less. Their setup is single VM, only one master 
> node and has less than 10 jobs. For those what is the suggestion? Can we 
> run the jobs on master(In-built node) now or we need to create a agent?  if 
> agent then I have to maintain two VMs or I can have the master and agent on 
> same VM?
>
>
Please use the term 'controller' rather than 'master'.  It's a more 
inclusive term.

You can host an agent on the same virtual machine that runs the 
controller.  Use a separate account for the agent so that you can use file 
system permissions to prevent the agent from reading the contents of the 
JENKINS_HOME directory.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9ed3de43-6e68-47e2-82b6-b1f94252e9c5n%40googlegroups.com.

Re: Jenkins stable 2.319.1?

[Mark Waite]

On Wednesday, December 1, 2021 at 11:28:45 AM UTC-7 Alan Sparks wrote:

> I guess I'm paranoid.  I guess the release came out before the changelog.  
> Sorry for the interruption.
>
>
It is good to be a little paranoid about long term support releases being 
correct.  Thanks for checking.

Dates for the long term support releases are visible on the Jenkins 
calendar at https://www.jenkins.io/events/ 

Release candidates are announced on this mailing list about two weeks 
before the release.  The 2.319.1 release candidate 
<https://groups.google.com/g/jenkinsci-dev/c/plwMqtme6DA/m/MOEjFsEQAAAJ> 
and release was handled by Cathy Chan as release lead 
<https://groups.google.com/g/jenkinsci-dev/c/IPpiXyKgCCM/m/qrBMxBqaAAAJ> 
(Thanks Cathy!).

Changelog and upgrade guide don't become available until after the release 
has been delivered.

Mark Waite
 

> On Wednesday, December 1, 2021 at 11:24:43 AM UTC-7 Alan Sparks wrote:
>
>> I got a notice on Jenkins of a new stable release 2.319.1.  And it’s in 
>> the //pkg.jenkins.io/debian-stable repo.  But see no changelog for it 
>> and didn’t see a pre-notice in announcements.   Is this real?
>>
>> -Alan
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/50b3625c-12e0-4b0b-a912-794bba2ea211n%40googlegroups.com.

Re: Error updating plugins from Jenkins

[Mark Waite]

On Friday, November 19, 2021 at 12:35:36 PM UTC-7 you wrote:

> Mark,
>
> Thank you for your response.
>
> Yes I'm running Linux. (sorry for missing this information)
>
> I suspected the Let's Encrypt certificates earlier, so I've already added 
> ISRG Root X1 (the issuer of Let's Encrypt) to the cacerts file.
> Nevertheless I just replaced my cacerts file with the one in the most 
> recent java 8 release, restarted jenkins but did not help. The first plugin 
> was downloaded successfully, the second failed as before.
>
> Actually what I don't understand is how downloading the very first plugin 
> succeeds. It's consistently the first plugin which succeeds and the others 
> fail.
> If downloading the other plugins fail due to a missing/expired Let's 
> Encrypt certificate, the first one should also fail. It should not be able 
> to connect to updates.jenkins.io at all.
>
>
If there are multiple Jenkins mirrors that are roughly the same distance to 
you, then the mirrorbits response from https://get.jenkins.io might 
redirect the second request to a different HTTP server than the first 
request.  However, if you confirmed that they are all working, that seems 
unlikely to be the cause.
 

> Also, I have a standalone application which I use to check the HTTP 
> redirects  and certificates, and this never fail to download the plugins 
> (the URLs are taken from Jenkins log), even though I use the very same jre 
> instance on the very same machine.
>

I assume that curl or wget from that machine will successfully 
retrieve https://updates.jenkins.io/latest/antisamy-markup-formatter.hpi 
and https://updates.jenkins.io/latest/ant.hpi 
and https://updates.jenkins.io/latest/adoptopenjdk.hpi.  If not, then the 
issue is related to something outside of Java (like the ca-certs file).
 

> My application use HttpsUrlConnection to download the files. I don't know 
> whether Jenkins use the same or some framework.
>
> The other thing I don't see is how the "CN=Kubernetes Ingress Controller 
> Fake Certificate, O=Acme Co" comes into the picture. According to the logs 
> (see my original e-mail) the SSL handshake fails on this certificate, but I 
> don't really see which server this certificate comes from.
>
>
I thought that certificate could be reported when a request is made to the 
IP address of an HTTP server hosted in Kubernetes.  The Kubernetes server 
needs the hostname in order to use the correct SSL certificate (or 
something like that).
 

> I've also checked the mirrorlist as you suggested. All mirrors listed in 
> the response look good, that is have a valid certificate chain according to 
> my cacerts file.
>

Unfortunately, I'm out of ideas if one of those do not resolve the issue.

Mark Waite 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8ab8f80e-cc61-4ec9-a4f4-5581f4876adan%40googlegroups.com.

Re: Error updating plugins from Jenkins

[Mark Waite]

I think that the output 
of https://updates.jenkins.io/latest/antisamy-markup-formatter.hpi?mirrorlist 
will show that your location may be served by multiple Jenkins mirrors.

You can then check each of the mirrors to identify if one of them is 
responding with an incorrect SSL certificate.

It could also be that the JDK on your Jenkins controller or the 
ca-certificates package on your Jenkins controller are too old to recognize 
the September 2021 updates to Let's Encrypt root certificates.  I suspect 
that Java 11.0.1+13-LTS on the controller likely indicates that the 
ca-certificates package is also similarly out of date (assuming you're 
running Linux).  Update the packages on your controller so that you have 
the latest security fixes for Java and for the operating system.

Mark Waite

On Friday, November 19, 2021 at 10:26:26 AM UTC-7 you wrote:

> Hello,
>
> When I try updating plugins, the very first plugin gets downloaded 
> successfully, but the subsequent ones fail to download.
>
> [image: Jenkins.png]
> According to *Details* the SSL handshake fails due to a certificate error:
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cec5c693-b8b8-480e-9bad-262f16e401fdn%40googlegroups.com.

Re: Java 11 is the recommended version to run Jenkins on

[Mark Waite]

Good point.  More details on the transition to Java 11 are included in the 
2.303.1 
upgrade guide 
.
  
The upgrade guide includes a list of plugins known to be incompatible with 
Java 11.

On Wednesday, November 3, 2021 at 8:44:00 AM UTC-6 Daniel wrote:

> Somewhere it states that not all plug-ins support Java 11 also.
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9209f0b5-cb47-48d2-a068-f3d2e1d9f3cen%40googlegroups.com.

Re: Java 11 is the recommended version to run Jenkins on

[Mark Waite]

Jenkins continues to support Java 8.  We recommend Java 11.

See https://www.jenkins.io/blog/2021/08/17/docker-images-use-jdk-11-by-default/ 
for more details on the rationale for that transition.

On Wednesday, November 3, 2021 at 8:24:47 AM UTC-6 s.p...@gmail.com wrote:

> After I upgraded Jenkins to 2.303.2, I'm seeing an alert as below. J. I 
> think Java 11 is OpenJDK and we are using java 1.8.0_301. Is Java 1.8 no 
> longer supported ? Any inputs are really appreciated. TIA
>
> "Java11 is the recommended version to run Jenkins on; please consider 
> upgrading."
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/30b4e059-f436-4645-9777-3289efd4a487n%40googlegroups.com.

Re: Pipeline: Nodes and Processes incompatibility?

[Mark Waite]

On Wednesday, October 6, 2021 at 8:54:26 AM UTC-6 Fritz Elfert wrote:

>
> Hi, 
>
> I am looking at the Plugin Manager im my jenkins 2.303.1 installation and 
> it 
> shows this warning for the Pipeline: Nodes and Processes plugin: 
>
> Warning: The new version of this plugin is marked as incompatible with the 
> installed version. This is usually the case because its behavior changed, 
> or because it uses a different settings format than the installed version. 
> Jobs using this plugin may need to be reconfigured, and/or you may not be 
> able to cleanly revert to the prior version without manually restoring old 
> settings. Consult the plugin release notes for details. 
>
> I currently have 2.39 installed and the warning is for 2.40 
>
> Despite looking at the obvious place: (github releases in this case) it is 
> unclear to me, what exactly is incompatible.



The GitHub release page for 2.40 

 
has the following text at the very top:

The NODE_NAME environment variable value set for the built-in node inside 
node blocks now matches the behavior of other job types: On Jenkins 2.306 
and earlier, the behavior is unchanged (master). On Jenkins 2.307 and 
later, the variable will be built-in or master, depending on whether the 
instance was upgraded from a previous release or newly installed, and 
whether the migration was applied. See 
https://www.jenkins.io/redirect/built-in-node-migration/


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a48ed28f-62af-4f16-9d00-18174ba046a6n%40googlegroups.com.

Re: Help! I am trying to upgrade from 2.263.1 to 2.303.1

[Mark Waite]

I use Amazon Linux 2 for agents with no issue. I've never heard of a
problem that was specific to Amazon Linux 2.

On Tue, Oct 5, 2021, 3:23 PM Iván Fernández Calvo 
wrote:

> I do not think so the issue seems related to the upgrade not the OS.
>
> El 5 oct 2021, a las 21:09, Daniel Burns 
> escribió:
>
> Thank you.  I wanted to at least respond.  This is in DEV so I can
> definitely try different things.  Using what you stated, I can mimic PROD
> and create a new DEV server with a fresh OS.  I assume there are no issues
> with using AWS Amazon Linux 2, instead of RHEL Linux?
>
> Thank you.
>
> On Sunday, October 3, 2021 at 6:13:09 AM UTC-5 kuisat...@gmail.com wrote:
>
>> It is not clear what it is the current issue you want to resolve, so my
>> suggestion is to start again the first case you expose.
>>
>> >On my first try, I thought I had upgraded, but I did not realize that
>> the version of WAR file was the same (2.263.1) I upgraded the plugins, then
>> realized that it had not been upgraded to 2.303.1, so then I put the new
>> WAR file in place.  I was able to log in just fine, but one of the most
>> important pipelines I have did not work.  I makes a call out to Gitlab and
>> I update Gitlab at the same time.
>>
>> Before upgrading the production environment try to upgrade the same
>> system but in another machine:
>>
>> * In a new machine
>> * Copy the JENKINS_HOME folder to the new server in the same place
>> * Remove the folder JENKINS_HOME/nodes/* (we do not want to use the
>> production Agents)
>> * Start Jenkins in the new machine
>> * Upgrade the plugins
>> * Stop Jenkins
>> * Update the war
>> * Start Jenkins
>> * Create a new Agent that fit the requirements of your important pipeline
>> * Test the pipeline
>>
>> At this point you'd have the same issue you face at the beginning, to try
>> to troubleshoot it you need to check
>> * Check the Jenkins logs from the start to the execution of the pipeline,
>> we are looking for exceptions
>> * Check the console log of the pipeline to see which error is causing the
>> pipeline to not work
>> * check the logs of the Agent in case we are error there
>> * Check the manage Jenkins and check there is no warning or error at the
>> top of the page
>>
>> If you provide the exceptions you found we could help you to point to a
>> specific fix.
>> My guess is that you have a problem with a plugin version, it could be
>> that it conflicts with another,
>> or your pipeline needs a specific version of a plugin.
>>
>> El viernes, 1 de octubre de 2021 a las 19:51:26 UTC+2,
>> daniel...@vistracorp.com escribió:
>>
>>> I put a new WAR in place and restart and normally, no issues at all.
>>>
>>> I have RedHat 6 running on an AWS EC2.
>>>
>>> On my first try, I thought I had upgraded, but I did not realize that
>>> the version of WAR file was the same (2.263.1) I upgraded the plugins, then
>>> realized that it had not been upgraded to 2.303.1, so then I put the new
>>> WAR file in place.  I was able to log in just fine, but one of the most
>>> important pipelines I have did not work.  I makes a call out to Gitlab and
>>> I update Gitlab at the same time.
>>>
>>> I went backwards to snapshots I made of the two servers before I
>>> upgraded.  Validated that the pipeline works, then upgraded Gitlab fully
>>> tested and the pipeline worked.  So I narrowed the issue to Jenkins.  I
>>> tried the upgrade again, without updating the plugins first.  This time, I
>>> got an error on login page, If I clicked on Login, it gives me a prompt to
>>> put my ID and password, upon hitting enter it gives me a 403 crumb error.
>>> We use A/D to validate credentials.
>>>
>>> I have tried several times, even trying to go down to the LTS right
>>> after the 2.263 release same issue.  At this point I am assuming I have a
>>> plugin problem.
>>>
>>> I tried to look at the log and even created the logging.properties file
>>> but I don't see anything glaringly obvious there either.
>>>
>>> Can someone assist, suggest something?
>>>
>>> Thank you
>>> Daniel
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/apYDcjRLRCk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/27ac518f-d42d-4104-b68c-3c05ca1db282n%40googlegroups.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: Cannot update Jenkins on Debian due to certification problem

[Mark Waite]

Be sure that the ca-certificates package on your Debian distribution is 
current.  An older root certificate for Let's Encrypt expired Sep 30, 
2021.  
See https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ 
for more info

If you're running a Debian version that is no longer maintained (like 
Debian "wheezy") you may need to update your operating system or perform 
other more manual operations to recognize the root certificate.

On Tuesday, October 5, 2021 at 6:32:33 AM UTC-6 Riccardo Foschia wrote:

> Hi all,
>
> I'm trying to update a Jenkins installation on Debian to the current 
> version 2.314 using
>
> apt-get update
> apt-get install jenkins
>
> but calling apt-get update gives me the following error so apt-get 
> install fails also:
>
> Fehl:8 https://pkg.jenkins.io/debian binary/ Release
> server certificate verification failed. CAfile: 
> /etc/ssl/certs/ca-certificates.crt CRLfile: none
> 
> E: The repository 'https://pkg.jenkins.io/debian binary/ Release' does 
> no longer have a Release file.
> N: Updating from such a repository can't be done securely, and is 
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user 
> configuration details.
>
> The error for me looks like
> https://issues.jenkins.io/browse/INFRA-1725
> https://issues.jenkins.io/browse/INFRA-2685
>
> Is there currently an issue with SSL certificate for 
> https://pkg.jenkins.io? Or is there another problem? What can I do?
>
> Thanks in advance and kind regards,
> Riccardo
>
> -- 
>
> META-LEVEL Software AG
> Lyonerring 1
> 66121 Saarbrücken
> Deutschland
> Tel: +49 - 681 / 99687-0
> Fax: +49 - 681 / 99687-99 <+49%20681%209968799>
> Mail: in...@meta-level.de
> Web: www.meta-level.de
>
> Rechtsform: Aktiengesellschaft
> Sitz: Saarbrücken
> HR B Nr. 13 380 Amtsgericht Saarbrücken
> USt-IdNr. DE 1 38 17
> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
> Vorsitzender des Aufsichtsrats: Reinhard Kuhn
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a21bb3b7-de54-430e-9d3f-160406f9ae91n%40googlegroups.com.

Re: Question on Jenkins

[Mark Waite]

On Wednesday, September 29, 2021 at 10:37:26 AM UTC-6 Priya wrote:

> We use perforce 
>

Same instructions apply.  Ask the person who defined the job originally to 
tell you how its SCM was configured.  Configure it that way again.

Alternately, retrieve the config.xml file for that job definition from a 
backup and use the version from a backup.

P.S. Providing insufficient information and making others extract that 
information from you by one question at a time is a painful process and 
causes many contributors to stop answering questions.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/50eaf440-7b4c-4829-a165-8bb13526f58bn%40googlegroups.com.

Re: Question on Jenkins

[Mark Waite]

Ask the people who configured that job originally to tell you the SCM 
configuration information.

If it was using a Git repository, you'll need a URL for that repository.  
Usually those repository URL's are of the form 
https://git.example.com/someone/some-repo.git or 
g...@git.example.com:someone/some-repo.git.

There are many tutorials that will show you how to configure SCM for a 
Jenkins job.  I created one in 2014 that I called "Jenkins in 5 minutes".  
Badly out of date, but illustrates the 
concepts. https://www.youtube.com/watch?v=NovHZZwlCfk

On Wednesday, September 29, 2021 at 10:30:08 AM UTC-6 priya.r...@gmail.com 
wrote:

> How do I do this?
>
>
>- No SCM configured - usually Jenkins jobs have an SCM configured.  
>Choose the SCM you prefer for that job and configure it
>
>
>
> On Tue, Sep 28, 2021 at 5:38 PM Mark Waite  wrote:
>
>>
>>
>> On Tuesday, September 28, 2021 at 1:21:15 AM UTC-6 priya wrote:
>>
>>> Hi
>>>
>>> I stopped and started Jenkins since the server hosting it had an issue : 
>>>
>>> But now when I click on Configure I see the following:
>>>
>>> Snapshot attached.How do I fix this?
>>>
>>
>> You'll need to provide a better description of what you expected to see 
>> as compared to what you see.  In that screen shot, I see:
>>
>>- Jenkins 2.164.1 - a Jenkins version that was released in 2019.  
>>Multiple security advisories have been issued since that release.  If 
>>you're expecting security fixes, then upgrade to 2.303.1
>>- No SCM configured - usually Jenkins jobs have an SCM configured.  
>>Choose the SCM you prefer for that job and configure it
>>- Build discarder may not be configured with limits.  If you want to 
>>limit the amount of build history you retain, assign values to the build 
>>discarder
>>
>>  
>>
>>> --
>>> Thanks
>>> Priya
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/aa8bba3e-4f81-473b-bb3a-be674d24994dn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/aa8bba3e-4f81-473b-bb3a-be674d24994dn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/809f34de-6ed3-47ef-8989-0958eed1b7b4n%40googlegroups.com.

Re: Question on Jenkins

[Mark Waite]

On Tuesday, September 28, 2021 at 1:21:15 AM UTC-6 priya wrote:

> Hi
>
> I stopped and started Jenkins since the server hosting it had an issue : 
>
> But now when I click on Configure I see the following:
>
> Snapshot attached.How do I fix this?
>

You'll need to provide a better description of what you expected to see as 
compared to what you see.  In that screen shot, I see:

   - Jenkins 2.164.1 - a Jenkins version that was released in 2019.  
   Multiple security advisories have been issued since that release.  If 
   you're expecting security fixes, then upgrade to 2.303.1
   - No SCM configured - usually Jenkins jobs have an SCM configured.  
   Choose the SCM you prefer for that job and configure it
   - Build discarder may not be configured with limits.  If you want to 
   limit the amount of build history you retain, assign values to the build 
   discarder

 

> --
> Thanks
> Priya
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/aa8bba3e-4f81-473b-bb3a-be674d24994dn%40googlegroups.com.

Re: Pull changes when a tag is created

[Mark Waite]

If you're running the default command line git version on CentOS 7, it does 
not accept partial globs in the refspec.  The command line git 
documentation for refspec says:

Since Git 2.6.0 you can use partial globs in the pattern to match multiple 
branches, so this works:
fetch = +refs/heads/qa*:refs/remotes/origin/qa*

If you're running a command line git version before 2.6.0, your partial 
glob won't work.

On Wednesday, September 22, 2021 at 11:50:30 AM UTC-8 jayarama...@gmail.com 
wrote:

> Hello,
>
> I wanted to trigger a Jenkins build when a new tag is created but I'm not 
> having any luck with it. 
>
> Just to be sure I mentioned it, I don't have access to modify the repo 
> since it's a public repo.
>
> The following configuration is what I used in the "Git" Source Code 
> Management
> Repo URL: https://github.com/apache/tomcat.git
> Refspec: +refs/tags/8.5.*:refs/remotes/origin/tags/8.5.*
> Branch Specifier: **/tags/**
> Build Trigger: Poll SCM (with no schedule)
>
> Is there something I'm doing wrong?
>
> I can't do WebHooks which is unfortunate I think
>
> Any insights would be appreciated. 
>
> [image: SCM.jpg]
>
> [image: Triggers.jpg]
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5e70f3cf-6ffd-4ba2-a6f0-4a83c217d7a1n%40googlegroups.com.

Re: Jenkins Credentials

[Mark Waite]

On Saturday, September 18, 2021 at 4:45:43 AM UTC-6 Nikolas wrote:

>
> Hi, recently I'm not able to login anymore in JIRA neither in 
> https://ci.jenkins.io/
>
> I have try to reset the password but no email arrives. Since there is no 
> contact specified for these case I had post here.
> I'm the mantainer of xunit/nodejs plugin. Could someone of the Jenkins 
> infrastructure help me to login again so I can responde to the JIRA issue 
> and perform release again?
>
> My login is nfalco
> https://issues.jenkins.io/secure/ViewProfile.jspa?name=nfalco
>

 The Jenkins project Confluence instance was attacked 
<https://www.jenkins.io/blog/2021/09/04/wiki-attacked/>.  Out of an 
abundance of caution, we reset the passwords of all jenkins.io accounts.  
We notified maintainers through the email address registered with their 
jenkins.io account.  I suspect you may not have seen that email based on 
the email address currently associated with your G-mail account.

Send an email message to mark.earl.waite at gmail.com and we'll get your 
password reset.

Thanks,
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/85ce900c-f373-4f24-b459-2cdbcfdd2b35n%40googlegroups.com.

Re: Execute shell script from jenkins

[Mark Waite]

Your Jenkins controller is running on Windows.  Windows uses batch and 
powershell for its command line scripting.

If you want to run a shell script, add an agent on an operating system that 
supports bash.  That could be a Linux Docker based agent running in Docker 
on your Windows computer.  It could be an agent on a Linux computer.  It 
could be an agent on macOS, FreeBSD, or OpenBSD.

In any case, you should add agents to your controller so that you are not 
running jobs on the controller.

Mark Waite

On Thursday, August 12, 2021 at 9:00:28 AM UTC-6 you wrote:

> Hello everyone,
>
> How can I execute shell scripts from jenkins? 
>
> I have the below code in "Execute Shell" command
> ""
> #!/bin/bash
> echo "hello"
>
> Received the following Error Msg  in the console.
>
> Running as SYSTEM Building on master in workspace 
> C:\Users\crnat\.jenkins\workspace\ssh-task-test [ssh-task-test] $ /bin/bash 
> C:\Users\crnat\AppData\Local\Temp\jenkins563122492098989130.sh The system 
> cannot find the file specified FATAL: command execution failed 
> java.io.IOException: CreateProcess error=2, The system cannot find the file 
> specified at java.lang.ProcessImpl.create(Native Method) at 
> java.lang.ProcessImpl.(Unknown Source) at 
> java.lang.ProcessImpl.start(Unknown Source) Caused: java.io.IOException: 
> Cannot run program "/bin/bash" (in directory 
> "C:\Users\crnat\.jenkins\workspace\ssh-task-test"): CreateProcess error=2, 
> The system cannot find the file specified at 
> java.lang.ProcessBuilder.start(Unknown Source) at 
> hudson.Proc$LocalProc.(Proc.java:252) at 
> hudson.Proc$LocalProc.(Proc.java:221) at 
> hudson.Launcher$LocalLauncher.launch(Launcher.java:996) at 
> hudson.Launcher$ProcStarter.start(Launcher.java:508) at 
> hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:144) at 
> hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at 
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:803)
>  
> at hudson.model.Build$BuildExecution.build(Build.java:197) at 
> hudson.model.Build$BuildExecution.doRun(Build.java:163) at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) 
> at hudson.model.Run.execute(Run.java:1906) at 
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at 
> hudson.model.ResourceController.execute(ResourceController.java:97) at 
> hudson.model.Executor.run(Executor.java:429) Build step 'Execute shell' 
> marked build as failure Finished: FAILURE
>
>
> Thanks,
> Poo
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a48954e6-e1c7-48c1-8605-caf7479c2228n%40googlegroups.com.

Re: cross-platform shell plugin 0.10 not stopping jobs on clients

[Mark Waite]

I just checked and confirmed what you reported.  A Unix based agent does
not kill the process that was created by the XShell plugin, even though the
Jenkins job stops.

A shell step does kill the process that was created.

Process did seem to be killed on a Windows agent with XShell.

Work around is to switch from XShell to the shell step.  Please submit a
bug report to issues.jenkins.io.

Mark Waite

On Fri, Aug 6, 2021 at 4:25 PM Anne Hammond  wrote:

> Xshell plugin, or cross-platform shell plugin, 0.10 is not stopping jobs
> on the clients under jenkins 2.289.2 when the job is aborted from the
> jenkins dashboard.
>
> There are some previous posts about Xshell where it worked in 1.586 (is
> this the jenkins version?), and in 1.565.2-1.586.
>
> This worked until we upgraded jenkins from 2.107.3 to 2.289.2.
>
> Any advice for how to fix this, or to post more information here so that
> it can be fixed in jenkins, appreciated.
>
> Thank you!
>
> Anne
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d8f530b2-eb2a-4536-ac80-709c6a71c3b2n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d8f530b2-eb2a-4536-ac80-709c6a71c3b2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF%2BpEY5Dj-A42Fd4y9YL_2eGx9wNZ73uBvirFMbMN6brQ%40mail.gmail.com.

Re: Even distribution of jobs

[Mark Waite]

On Sat, Jul 10, 2021 at 6:18 AM Fabian Cenedese  wrote:

> At 20:23 07.07.2021, Jonathan Mackenzie wrote:
>
> >I am running 2.192 and I can see it in the plugin manager. Clicked the
> 'Available' tab then typed 'scoring' in the filter box and it showed right
> up.
>
> It may have been with your version but it isn't offered anymore with the
> current jenkins. Either it's not compatible anymore and was therefore
> removed or there's a problem with the list of available plugins.
>
>
Or there's a problem locally for you.  I see that plugin as available to
download with Jenkins 2.289.2 in my local installation.  I see that plugin
as available to download with Jenkins 2.289.2 on ci.jenkins.io as well.

Mark Waite


> bye  Fabi
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/20210710121829.088F046E360B%40macserver.private
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFkntrFgO%2B99QwpWVBm%2BNVQDfcBHAwtTYU7uvt_oDsCRg%40mail.gmail.com.