munged workspace folder names?

[Robert Nicholson]

Is this a feature of Jenkins where it appears to munge the job name when 
generating the folder name under workspace?

Does this apply to GitHub organization jobs only?

I show where the folder name under itbox/workspaces on my slave is missing the 
first character of the job name.

and earlier I can see it’s actually preprinted characters to the full job name.

Is this how discard builds works by munging the folder name like this?

This is with jenkins 2.346.2

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/E81028CF-44E1-4D23-A8FB-9396BEBD838E%40gmail.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: HTTPS - works okay, but 2 problems

[James Nord]

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)

/James

On Wed, 14 Sept 2022 at 17:35, John Horne  wrote:

> Thanks for that. I looked through bug reports and found someone else
> saying that port 8080 remained open. It was you (I think) that replied to
> him/her that the RPM version does not use the sysconfig file. Creating a
> systemd override to disable port 8080 worked fine.
>
> As to the second problem - it's still a problem. I remembered from other
> work that multiple 'ExecStart's are not allowed for certain types. So need
> to use 'ExecStart=' and then on the following line put the actual ExecStart
> I wanted. However, this invokes /usr/bin/jenkins which ultimately runs java
> with all the options passed to it. So no matter what I do in the systemd
> override file for ExecStart, it always ends up with a java command being
> run with the keystore password as one of the options being shown.
> I need to think about this a bit more.
>
> John.
> On Wednesday, 14 September 2022 at 03:33:17 UTC+1 Mark Waite wrote:
>
>> On Tuesday, September 13, 2022 at 7:26:12 PM UTC-6 John wrote:
>>
>>> Hello,
>>>
>>> We are running Jenkins 2.368 on a Rocky 8 Linux server. I was asked to
>>> implement SSL onto our Jenkins service, and have done that using a
>>> keystore. (I only deal with the server itself as a sysadmin, I do not use
>>> Jenkins myself for CI purposes.)
>>> This all seems to work okay, but I have noticed two issues:
>>>
>>> 1) Despite changing the '/etc/sysconfig/jenkins' file setting the
>>> JENKINS_PORT to -1 and setting the JENKINS_HTTPS_PORT to 8443, port 8080 is
>>> still listened upon by Jenkins. Using the 'lsof' command from a console
>>> shows that both ports 8080 and 8443 are listening. The 'System Information'
>>> page within Jenkins shows that it is also present on the supplied java
>>> command-line (as the --httpPort option). How do we fully disable the use of
>>> port 8080?
>>>
>>>
>> If you installed Jenkins 2.368 on Rocky 8 Linux with the yum command,
>> then Jenkins should be configured with "systemctl edit jenkins" instead of
>> editing the '/etc/sysconfig/jenkins' file.
>>
>> The "Managing systemd services
>> 
>> page provides more details.
>>
>>
>>> 2) The keystore password is exposed in the 'ps' command output, and in
>>> the 'System Information' page found when I log into Jenkins and look under
>>> the 'Manage Jenkins' page. This is obviously not secure. Perhaps the
>>> password should be stored as part of the Jenkins configuration rather than
>>> just passed onto the command-line from the sysconfig file?
>>>  Is there another way to hide the password?
>>>
>>>
>> I'm not sure on that one.  You may need to replace the ExecStart with the
>> specific command line arguments that you want to use.
>>
>> Mark Waite
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6ac178e4-4b63-470f-90ce-8e96568c9629n%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/CAPzq3peWUiTVfeUU0CcJrrAT41Spn4u2rDiKePnfCF-1r5H3jw%40mail.gmail.com.