[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22

2020-02-21 Thread jenk...@siigna.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Bouché commented on  JENKINS-61131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: vsphere-cloud: Credentials selection is broken in UI since 2.22   
 

  
 
 
 
 

 
 Also seeing this on LTS 2.204.2 with plugin 2.22.  Downgrading to 2.21 allows credential selection.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.204653.1582040133000.4672.1582331340193%40Atlassian.JIRA.

[JIRA] (JENKINS-53917) choice parameter no longer supports choices in pipeline

2018-10-05 Thread jenk...@siigna.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Bouché commented on  JENKINS-53917  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: choice parameter no longer supports choices in pipeline   
 

  
 
 
 
 

 
 Downgrading to structs 1.15 resolves the error.  
 

  
 
 
 
 

 
 
 

 
 
 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-53917) choice parameter no longer supports choices in pipeline

2018-10-05 Thread jenk...@siigna.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Bouche updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53917  
 
 
  choice parameter no longer supports choices in pipeline   
 

  
 
 
 
 

 
Change By: 
 Steve Bouche  
 

  
 
 
 
 

 
 Current releases of all plugins, notably Struct 1.16, result in the {{choice}} parameter no longer having a legal {{choices}} argument. [https://github.com/jenkinsci/structs-plugin/pull/41] perhaps?Reproduce: {{docker run -p 8080:8080 jenkins/jenkins:2.138.1}}, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.Originally reported on IRC by ctcpme  ([~siigna]) :{noformat}[2018-10-05 07:58:19]i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this?[2018-10-05 08:02:23]  <@danielbeck>  ctcpme are you on structs plugin 1.16?[2018-10-05 08:02:38]yes[2018-10-05 08:03:51]  <@danielbeck>  ctcpme is there a way for you to ignore the error, if so, what happens?[2018-10-05 08:04:41]i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails.  {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-53234) swarm-client fails to connect with 500 error while using Azure AD Plugin

2018-08-24 Thread jenk...@siigna.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Bouche created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53234  
 
 
  swarm-client fails to connect with 500 error while using Azure AD Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-ad-plugin  
 
 
Created: 
 2018-08-24 23:56  
 
 
Environment: 
 Jenkins 2.121.1  Jenkins Swarm client 3.13  Azure AD Plugin 0.3.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Steve Bouche  
 

  
 
 
 
 

 
 Connecting the swarm-client to Jenkins while security is set to Jenkins’ own user database is successful. Attempting to connect the swarm-client to Jenkins while security is set to Azure Active Directory is unsuccessful. 

 

$ java -jar swarm-client-3.13.jar -username USER_UPN -password USER_API_TOKEN -master http://JENKINS
Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client main
INFO: Client.main invoked with: [-username USER_UPN -password PASS -master http://JENKINS]
Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client run
INFO: Discovering Jenkins master
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.SwarmClient discoverFromMasterUrl
SEVERE: Failed to fetch slave info from Jenkins, HTTP response code: 500
Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client run
SEVERE: RetryException occurred
hudson.plugins.swarm.RetryException: Failed to fetch slave info from Jenkins, HTTP response code: 500
at hudson.plugins.swarm.SwarmClient.discoverFromMasterUrl(SwarmClient.java:233)
at