[JIRA] (JENKINS-55886) JCasC cannot configure TLS for Active Directory

2019-02-06 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons commented on  JENKINS-55886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JCasC cannot configure TLS for Active Directory   
 

  
 
 
 
 

 
 I tried and it does work, thanks Gordon Franke! I did not notice the tlsConfiguration moved from activeDirectory level to domain level. I suppose this can be closed then.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55886) JCasC cannot configure TLS for Active Directory

2019-01-31 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55886  
 
 
  JCasC cannot configure TLS for Active Directory   
 

  
 
 
 
 

 
Change By: 
 Edgars Didrihsons  
 

  
 
 
 
 

 
 The issue appeared after updating active-directory plugin to 2.11 which is a security update. Downgrade to  active-directory:2.10 resolves the issue. Jenkins startup fails due to JCasC complaining about invalid configuration element: tlsConfiguration{code:java}Caused by: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class hudson.plugins.active_directory.ActiveDirectorySecurityRealm : tlsConfiguration.Available attributes : bindName, bindPassword, cache, captchaSupport, customDomain, domain, domains, environmentProperties, groupLookupStrategy, internalUsersDatabase, removeIrrelevantGroups, server, site, startTls{code}If TLS is not configured it defaults to (Unsecure) Trust all Certificates option.    
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55886) JCasC cannot configure TLS for Active Directory

2019-01-31 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55886  
 
 
  JCasC cannot configure TLS for Active Directory   
 

  
 
 
 
 

 
Change By: 
 Edgars Didrihsons  
 

  
 
 
 
 

 
 The issue appeared after updating active-directory plugin to 2.11 which is a security update.  Downgrade to  Jenkins startup fails due to JCasC complaining about invalid configuration element: tlsConfiguration{code:java}Caused by: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class hudson.plugins.active_directory.ActiveDirectorySecurityRealm : tlsConfiguration.Available attributes : bindName, bindPassword, cache, captchaSupport, customDomain, domain, domains, environmentProperties, groupLookupStrategy, internalUsersDatabase, removeIrrelevantGroups, server, site, startTls{code}If TLS is not configured it defaults to (Unsecure) Trust all Certificates option.    
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55886) JCasC cannot configure TLS for Active Directory

2019-01-31 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55886  
 
 
  JCasC cannot configure TLS for Active Directory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 active-directory-plugin, configuration-as-code-plugin  
 
 
Created: 
 2019-01-31 08:26  
 
 
Environment: 
 jenkins:2.150.2  configuration-as-code-support:1.5  configuration-as-code:1.5  active-directory:2.11   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Edgars Didrihsons  
 

  
 
 
 
 

 
 The issue appeared after updating active-directory plugin to 2.11 which is a security update. Jenkins startup fails due to JCasC complaining about invalid configuration element: tlsConfiguration 

 

Caused by: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class hudson.plugins.active_directory.ActiveDirectorySecurityRealm : tlsConfiguration.
Available attributes : bindName, bindPassword, cache, captchaSupport, customDomain, domain, domains, environmentProperties, groupLookupStrategy, internalUsersDatabase, removeIrrelevantGroups, server, site, startTls 

 If TLS is not configured it defaults to (Unsecure) Trust all Certificates option.    

[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1

2018-11-13 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons commented on  JENKINS-50840  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Powershell script execution broken in powershellHelper.ps1   
 

  
 
 
 
 

 
 How is this Fixed when I still encounter it today with Jenkins 2.138.3 and durable-task-plugin 1.27 ? Adding Out-String does help though so thanks for that.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents

2018-08-02 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52847  
 
 
  durable-task plugin v1.23 misbehaves on BusyBox agents   
 

  
 
 
 
 

 
Change By: 
 Edgars Didrihsons  
 

  
 
 
 
 

 
 After upgrade of durable-task-plugin from 1.22 to 1.23 it no longer works on alpine based containers. Downgrading to 1.22 reverts to the expected behavior.I managed to trigger this on a fresh jenkins/jenkins:lts-alpine container with only recommended plugins installed and following pipeline:{ {}}{ code:java}node { sh 'sleep 120; echo Hello World'}{code}{{Expected result: Hello World is echoed after 120 second delay}}{{Actual result:}}{code:java}Started by user testRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/busybox[Pipeline] {[Pipeline] sh[busybox] Running shell scriptps: unrecognized option: pBusyBox v1.28.4 (2018-05-30 10:45:57 UTC) multi-call binary.Usage: ps [-o COL1,COL2=HEADER]Show list of processes -o COL1,COL2=HEADER Select columns for display+ sleep 120wrapper script does not seem to be touching the log file in /var/jenkins_home/workspace/busybox@tmp/durable-f130160e(JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300)  [Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -1Finished: FAILURE{code}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents

2018-08-02 Thread edgars.didrihs...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Edgars Didrihsons created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52847  
 
 
  durable-task plugin v1.23 misbehaves on BusyBox agents   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2018-08-02 07:29  
 
 
Environment: 
 Jenkins:2.121.2-alpine running on Docker version 18.03.1-ce, build 9ee9f40  durable-task-plugin:1.23  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Edgars Didrihsons  
 

  
 
 
 
 

 
 After upgrade of durable-task-plugin from 1.22 to 1.23 it no longer works on alpine based containers. Downgrading to 1.22 reverts to the expected behavior. I managed to trigger this on a fresh jenkins/jenkins:lts-alpine container with only recommended plugins installed and following pipeline: {{}} 

 

node {
 sh 'sleep 120; echo Hello World'
}
 

 Expected result: Hello World is echoed after 120 second delay Actual result: 

 

Started by user test
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/busybox
[Pipeline] {
[Pipeline] sh
[busybox] Running shell script
ps: unrecognized option: p
BusyBox v1.28.4 (2018-05-30 10:45:57 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

 -o COL1,COL2=HEADER Select columns for display
+ sleep 120
wrapper script does not seem to be touching the log file in