[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin

2019-07-29 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu commented on  JENKINS-52889  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: new lines in secret is substituted by spaces when reading via Vault plugin   
 

  
 
 
 
 

 
 Hee Won Kim you should iclude the actual shell script lines you are running.   I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03 and you can fix that by setting IFS= as per https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution   BUT its easier to just embed it in double quotes so that: if I do this it is replaced by spaces 

 

 echo $FOO > .foo 

 but if I do this instead it works 

 

 echo "$FOO" > .foo 

 then the newlines are preserved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin

2019-07-29 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu edited a comment on  JENKINS-52889  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: new lines in secret is substituted by spaces when reading via Vault plugin   
 

  
 
 
 
 

 
 [~saillinux] you should  iclude  include  the actual shell script lines you are running. I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash [http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03]and you can fix that by setting {{IFS=}} as per [https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution] BUT its easier to just embed it in double quotes so that:if I do this it is replaced by spaces{code:java} echo $FOO > .foo{code}but if I do this instead it works{code:java} echo "$FOO" > .foo{code}then the newlines are preserved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS

2018-05-18 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu commented on  JENKINS-51430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS   
 

  
 
 
 
 

 
 This is a puppet-jenkins issue. I'll open the PR there.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS

2018-05-18 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51430  
 
 
  Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-05-18 17:14  
 
 
Environment: 
 Jenkins 2.73.3  CentOs 7  Openjdk version 1.8  
 
 
Labels: 
 systemd service  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Samuel Beaulieu  
 

  
 
 
 
 

 
 How to reproduce: Run in a systemd OS like CentOS 7 with /etc/sysconfig/jenkins 

 

JENKINS_JAVA_OPTIONS=-Dhudson.model.DirectoryBrowserSupport.CSP="default-src 'self';" 

 As per https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy   Error message in journalctl 

 

Error: Could not find or load main class 'self';"
 

   Investigation This is because the last line of the systemd script /usr/lib/jenkins/jenkins-run is 

 

$JAV

[JIRA] (JENKINS-33358) Groovy and PermGen memory leak

2017-03-21 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu commented on  JENKINS-33358  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Groovy and PermGen memory leak   
 

  
 
 
 
 

 
 Reporting successful fix with the new groovy version. We updated an affected instance on Java 8, LTS version 2.7.4 to the non-LTS 2.48 and have been running the server for a week. The memory is under control now. +1 in bringing this into LTS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

2016-05-24 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Has anyone time to test with the new version of the swarm plugin (2.1)? https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [swarm-plugin] (JENKINS-34718) Get a new release of swarm client plugin

2016-05-10 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34718 
 
 
 
  Get a new release of swarm client plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 swarm-plugin 
 
 
 

Created:
 

 2016/May/10 9:29 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.642.2 
 
 
 

Labels:
 

 plugin release swarm 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Samuel Beaulieu 
 
 
 
 
 
 
 
 
 
 
It would be good to get a new release of the swarm client plugin. The last release is the 2.0 from 3 Aug 2015 especially to pick up the remoting version bumps in LTS. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-33940) Throttle plugin "per project" doesn't work with Matrix jobs

2016-04-13 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu edited a comment on  JENKINS-33940 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Throttle plugin "per project" doesn't work with Matrix jobs  
 
 
 
 
 
 
 
 
 
 I'm using Jenkins ver. 1.642.2Matrix Project Plugin 1.6.Throttle Concurrent Builds Plug-in 1.8.4And none of the throttling is working for 'matrix' multi-configuration type jobs.I've turned on the logs for 'ThrottleQueueTaskDispatcher' but there isn't much logged there anywayEdit: I was able to get the 'category' throttling to work  as above  if I set the {{"Manage Jenkins" > "Configure System" > (heading) "Throttle Concurrent Builds"}} to a lower number than the job config. If its a higher number than the job config then it does not throttle them (eg system label = 10 and job config = 1 will not throttle to 1) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-33940) Throttle plugin "per project" doesn't work with Matrix jobs

2016-04-13 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu edited a comment on  JENKINS-33940 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Throttle plugin "per project" doesn't work with Matrix jobs  
 
 
 
 
 
 
 
 
 
 I'm using Jenkins ver. 1.642.2Matrix Project Plugin 1.6.Throttle Concurrent Builds Plug-in 1.8.4And none of the throttling is working for 'matrix' multi-configuration type jobs.I've turned on the logs for 'ThrottleQueueTaskDispatcher' but there isn't much logged there anyway Edit: I was able to get the 'category' throttling to work if I set the {{"Manage Jenkins" > "Configure System" > (heading) "Throttle Concurrent Builds"}} to a lower number than the job config. If its a higher number than the job config then it does not throttle them (eg system label = 10 and job config = 1 will not throttle to 1) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-33940) Throttle plugin "per project" doesn't work with Matrix jobs

2016-04-13 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu edited a comment on  JENKINS-33940 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Throttle plugin "per project" doesn't work with Matrix jobs  
 
 
 
 
 
 
 
 
 
 I'm using Jenkins ver. 1.642.2Matrix Project Plugin 1.6.Throttle Concurrent Builds Plug-in 1.8.4And none of the throttling is working for 'matrix' multi-configuration type jobs. I've turned on the logs for 'ThrottleQueueTaskDispatcher' but there isn't much logged there anyway 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-33940) Throttle plugin "per project" doesn't work with Matrix jobs

2016-04-13 Thread the.samuel.beaul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Beaulieu commented on  JENKINS-33940 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Throttle plugin "per project" doesn't work with Matrix jobs  
 
 
 
 
 
 
 
 
 
 
I'm using  Jenkins ver. 1.642.2 Matrix Project Plugin 1.6. Throttle Concurrent Builds Plug-in 1.8.4 
And none of the throttling is working for 'matrix' multi-configuration type jobs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.