[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-10-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 

  
 
 
 
 

 
 ... Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when  multiple external SVN Legacy SCM libs are loaded by the Jenkinsfile *and* the *Local module directory* indicates preservation/overriding of the parent directory. (Ie, when the dot default is not used and a working copy root directory for each lib is created under the {{@libs}} directory.Configuration of global and folder specific libraries as shown in the attachments. The Jenkinsfile script begins{ quote code }  @Library('pipeline_global_helpers') _@Library('pipeline_branch_build')import com.foo.bar.Application{ quote code }Running the pipeline makes it as far as checking out or updating the local working copies in the {{@libs/pipeline_global_helpers}} and {{@libs/pipeline_branch_build}} in the pipeline workspace on the master, but execution aborts thereafter with the stack trace{ quote code:none }  ERROR: Library pipeline_branch_build expected to contain at least one of src or vars directoriesorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: Loading libraries failed1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1073) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE  { quote code }The libraries both have {{src}} and {{vars}} subdirectories and cause no error if used individually if checked out with *Local module directory* set to the default dot (no working copy root directory). I have also avoided the error once or twice when overriding/preserving the working copy root directory when loading a single external library, but not reliably. Ultimately the above error recurs.Checking out straight into the {{@libs}} directory is good for the single-library use

[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-10-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38517  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
 External libraries mandate that src/ etc. be at the root of a “repository”, which in the case of Subversion would be a “version” folder such as {…/trunk/}}, so it is correct to fail. Possibly it could fail with a more helpful error message, though I am not sure that is feasible—would have to look at what the API offers in this case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Change By: 
 Brian Ray  
 
 
Attachment: 
 firefox_2016-09-26_13-10-08.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Change By: 
 Brian Ray  
 
 
Attachment: 
 firefox_2016-09-23_13-52-40.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...

2016-09-26 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38517  
 
 
  Multiple shared libs throw "ERROR: Library  expected to contain at least one of src or vars directories" when ...   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 firefox_2016-09-23_13-52-40.png, firefox_2016-09-23_13-54-51.png, firefox_2016-09-23_13-57-54.png  
 
 
Components: 
 subversion-plugin, workflow-cps-global-lib-plugin  
 
 
Created: 
 2016/Sep/26 8:04 PM  
 
 
Environment: 
 LTS 2.7.4   scm-api 1.3  subversion 2.6  worfklow-cps-global-lib 2.3   Zulu OpenJDK 8.17.0.3-win64 (1.8.0_102-b14)  Win 7 Pro master--error does not involve agents  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Brian Ray  
 

  
 
 
 
 

 
 ... multiple external SVN Legacy SCM libs are loaded by the Jenkinsfile and the Local module directory indicates preservation/overriding of the parent directory. (Ie, when the dot default is not used and a working copy root directory for each lib is created under the @libs directory. Configuration of global and folder specific libraries as shown in the attachments. The Jenkinsfile script begins 

@Library('pipeline_global_helpers') _ 
@Library('pipeline_branch_build') import com.foo.bar.Application
 Running the pipeline makes it as far as checking out or updating the local working copies in the @libs/pipeline_global_helpers and @libs/pipeline_branch_build in the pipeline workspace on the master, but execution