[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories

2020-02-03 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in https://github.com/jenkinsci/github-branch-source-plugin/pull/274  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51519  
 
 
  GitHub Organization should allow skipping archived repositories   
 

  
 
 
 
 

 
Change By: 
 Nik Reiman  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-60835) Publish information about currently running builds via API

2020-01-22 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60835  
 
 
  Publish information about currently running builds via API   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 swarm-plugin  
 
 
Created: 
 2020-01-22 09:16  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nik Reiman  
 

  
 
 
 
 

 
 When using slave.jar, build nodes publish information about currently running builds via the Jenkins API. I'm not super well-versed in the API internals, but as far as I can tell, this involves publishing extra information for each executor. Otherwise, Jenkins replaces this with a PlaceholderTask, which doesn't contain any information about what is actually building, and the API consumer can only see if the executor is idle or not. Effectively, this means that API calls such as [{{get_running_builds}} in the python-jenkins API|]https://python-jenkins.readthedocs.io/en/latest/api.html#jenkins.Jenkins.get_running_builds return an empty list, which is not terribly useful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-44720) Git Submodules parallel jobs

2019-02-08 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman updated  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed and will be released with git plugin version 4.0.0 / git-client plugin version 3.0.0  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-44720  
 
 
  Git Submodules parallel jobs   
 

  
 
 
 
 

 
Change By: 
 Nik Reiman  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-44720) Git Submodules parallel jobs

2018-08-06 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman commented on  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Submodules parallel jobs   
 

  
 
 
 
 

 
 PR to git-client-plugin has been merged, corresponding PR to git-plugin is here: https://github.com/jenkinsci/git-plugin/pull/612  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-06 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman updated  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44720  
 
 
  Git Submodules parallel jobs   
 

  
 
 
 
 

 
Change By: 
 Nik Reiman  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-06 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman assigned an issue to Nik Reiman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44720  
 
 
  Git Submodules parallel jobs   
 

  
 
 
 
 

 
Change By: 
 Nik Reiman  
 
 
Assignee: 
 Nik Reiman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-06 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman started work on  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nik Reiman  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-02 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman commented on  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Submodules parallel jobs   
 

  
 
 
 
 

 
 PR is here: https://github.com/jenkinsci/git-client-plugin/pull/348  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-02 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman commented on  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Submodules parallel jobs   
 

  
 
 
 
 

 
 This issue is also important to me, as at my company we have a very large git repo with over 30 submodules. Cloning speeds, even with reference repositories, are quite slow (especially on Windows). We're talking ~10 minutes just for the checkout step, but I have done some basic tests and we estimate we can get this down to just a minute or two with a combination of reference repositories and the --jobs argument. Mark Waite I am sympathetic towards your workload and understand that you have other priorities. I've done some Java development in the past, and I poked around the git-plugin and git-client-plugin source code. I think I've come up with a solution, but I'll probably need some help getting it merged since it's my first contribution to any Jenkins plugin. Your help and patience would be appreciated! Let's continue this discussion at GitHub, where I will submit a pull request soon.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-44720) Git Submodules parallel jobs

2018-08-02 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman edited a comment on  JENKINS-44720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Submodules parallel jobs   
 

  
 
 
 
 

 
 This issue is also important to me, as at my company we have a very large git repo with over 30 submodules. Cloning speeds, even with reference repositories, are quite slow (especially on Windows). We're talking ~10 minutes just for the checkout step, but I have done some basic tests and we estimate we can get this down to just a minute or two with a combination of reference repositories and  the --jobs argument  updating submodules in parallel .[~markewaite] I am sympathetic towards your workload and understand that you have other priorities. I've done some Java development in the past, and I poked around the git-plugin and git-client-plugin source code. I think I've come up with a solution, but I'll probably need some help getting it merged since it's my first contribution to any Jenkins plugin. Your help and patience would be appreciated!Let's continue this discussion at GitHub, where I will submit a pull request soon.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-51519) GitHub Organization should allow skipping archived repositories

2018-05-24 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51519  
 
 
  GitHub Organization should allow skipping archived repositories   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2018-05-24 09:31  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nik Reiman  
 

  
 
 
 
 

 
 It would be nice if the GitHub Organization plugin had an option to filter out repositories which are archived (and hence read-only). The user can blacklist these manually, but this can be a bit of a chore with larger organizations.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

   

[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8

2018-02-13 Thread nik.rei...@ableton.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nik Reiman commented on  JENKINS-41316  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8   
 

  
 
 
 
 

 
 Ditto here, 1.15 has caused a bunch of our container-related builds to fail. Looking at the diff of https://github.com/jenkinsci/docker-workflow-plugin/pull/116/files, it seems that the "detection" is looking for `cat` commands, which we are not using within `docker.image.inside`. Sadly the `–entrypoint ""` workaround also does not work in our case and we have reverted to 1.14 for now. Is there another JIRA issue already to track this regression, or should this one be re-opened?  
 

  
 
 
 
 

 
 
 

 
 
 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.