[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline

2020-05-04 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon commented on  JENKINS-62140  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow use of remote file for non-multibranch pipeline   
 

  
 
 
 
 

 
 Is it though? In multipipeline, git is configured through the "branch sources" section, while the build configuration configures where Jenkinsfile can be found on all branches. But it doesn't allow you to configure to fetch Jenkinsfile in a separate repository.   That's this use-case I would like to be supported by the pipeline jobs. When using "Pipeline from SCM", you need to configure one (or multiple) git repository, with one containing your Jenkinsfile. If Jenkinsfile and code to build are present in 2 separate repositories, you need 2 repositories, triggers apply to both, Jenkinsfile itself need to adapt itself to having both repositories, it's quite intrusive whereas I'd looking for something seamless like Jenkinsfile was in the same repository as the code.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline

2020-05-01 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon commented on  JENKINS-62140  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow use of remote file for non-multibranch pipeline   
 

  
 
 
 
 

 
 Indeed, pipeline jobs. I haven't found why it is hidden on purpose, but it looks like it could be useful too. Isn't a pipeline job basically a multibranch job with only one branch? In my case I want to use a Jenkinsfile with a repository I cannot modify for a single job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline

2020-05-01 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-62140  
 
 
  Allow use of remote file for non-multibranch pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Aytunc BEKEN  
 
 
Components: 
 remote-file-plugin  
 
 
Created: 
 2020-05-01 19:03  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Laurent Goujon  
 

  
 
 
 
 

 
 Remote file plugin hides itself from the pipeline reference dropdown for non-multibranch jobs, but this would be a great addition too and this restriction should probably be relaxed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-51123) Deadlock in CpsFlowExecution

2018-05-03 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon commented on  JENKINS-51123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock in CpsFlowExecution   
 

  
 
 
 
 

 
 Hopefully the issue can be fixed by changing the order of operations. Here's my attempt at it: https://github.com/jenkinsci/workflow-cps-plugin/pull/225  
 

  
 
 
 
 

 
 
 

 
 
 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-51123) Deadlock in CpsFlowExecution

2018-05-03 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51123  
 
 
  Deadlock in CpsFlowExecution   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jstack.txt  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2018-05-04 03:49  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Laurent Goujon  
 

  
 
 
 
 

 
 It seems that a deadlock has been introduced in some recent changes to workflow-cps-plugin. The whole jstack has been attached to the report, but two threads are waiting on each other: 
 
the first thread is calling CpsFlowExecution#subsumeHead, got the lock on the instance, and then trying to acquire the r/w lock on the node storage 
the second thread is calling CpsFlowExecution#getNode, got the r/w lock on the storage, and then is calling close which tries to get the instance lock 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-40174) Missing authentication during git checkout and git-lfs

2016-12-01 Thread laurent.gou...@online.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent Goujon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40174  
 
 
  Missing authentication during git checkout and git-lfs   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-client-plugin  
 
 
Created: 
 2016/Dec/01 10:49 PM  
 
 
Environment: 
 Jenkins 2.27  Git Plugin: 3.0.0  Git Client Plugin: 2.0.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Laurent Goujon  
 

  
 
 
 
 

 
 One of our repository is using git-lfs to store large objects. When trying to doing a checkout of the branch, Jenkins fails to clone the repository when the git-lfs filter is getting the objects. 

 
Cloning the remote Git repository
Cloning repository ssh://g...@github.com/foo/repo.git
 > git init /jenkins/workspace/foo/repo # timeout=10
Fetching upstream changes from ssh://g...@github.com/foo/repo.git
 > git --version # timeout=10
using GIT_SSH to set credentials SSH Key to access github
 > git fetch --tags --progress ssh://g...@github.com/foo/repo.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url ssh://g...@github.com/foo/repo.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url ssh://g...@github.com/foo/repo.git # timeout=10
Fetching upstream changes from ssh://g...@github.com/foo/repo.git
using GIT_SSH to set credentials SSH Key to access github
 > git fetch --tags --progress ssh://g...@github.com/foo/repo.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision