[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-10 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez commented on  JENKINS-50525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
 Jae Gangemi 1.5.0 or 1.5.1 ?  
 

  
 
 
 
 

 
 
 

 
 
 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-49795) Bad serialization of ParametersAction.parameterDefinitionNames

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: content/_data/changelogs/lts.yml http://jenkins-ci.org/commit/jenkins.io/30d3398d9e8183dc78d522e0643e6a1b1d491de2 Log: Add JENKINS-49795  
 

  
 
 
 
 

 
 
 

 
 
 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-50460) Builds marked as failed - Dr Memory plugin (JEP-200)

2018-04-10 Thread pin...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Piotr Bogdanski commented on  JENKINS-50460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds marked as failed - Dr Memory plugin (JEP-200)   
 

  
 
 
 
 

 
 Another update: I was wrong in my understanding of the issue earlier. Looks like the exception from description is thrown just after build run, not during jenkins server restart.   
 

  
 
 
 
 

 
 
 

 
 
 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-50663) Deadlock on jenkins startup

2018-04-10 Thread k...@vandewiele.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kpop commented on  JENKINS-50663  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on jenkins startup   
 

  
 
 
 
 

 
 Same here, workaround by Giuseppe Iannello allowed Jenkins to start again.  
 

  
 
 
 
 

 
 
 

 
 
 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)

2018-04-10 Thread s...@viessmann.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Skiba commented on  JENKINS-28335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)   
 

  
 
 
 
 

 
 I added this issue as a project idea for GSoC 2018 but I hope that this issue will be fixed before summer. I don't think that a student will take this project but hope dies last   
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread bingsh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bing Shiao created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50709  
 
 
  Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Bing Shiao  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2018-04-10 07:59  
 
 
Environment: 
 pipeline-maven-plugin-3.5.1  Jenkins ver. 2.107.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bing Shiao  
 

  
 
 
 
 

 
 When project type is 'pom', attached artifacts are being skipped entirely from  XmlUtils.listGeneratedArtifacts().  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 

[JIRA] (JENKINS-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread bingsh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bing Shiao started work on  JENKINS-50709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bing Shiao  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-47254) Support for building tags for Bitbucket Server/Cloud

2018-04-10 Thread mgau...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-47254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
 Eduard Weiss, can you review Antonio's feedback on your PR #113 please? It will be nice if we succeed to have this feature ready. Thanks for your involvement.  
 

  
 
 
 
 

 
 
 

 
 
 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)

2018-04-10 Thread andrew.paul.g...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray commented on  JENKINS-28335  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)   
 

  
 
 
 
 

 
 I find it amazing that there are still these massive glaring gaps in functionality (esp for Git) in critical functions all over declarative pipeline.   They're supposed to be the future but not there yet.  
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread bingsh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bing Shiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50709  
 
 
  Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
Change By: 
 Bing Shiao  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread bingsh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bing Shiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50709  
 
 
  Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
Change By: 
 Bing Shiao  
 
 
Attachment: 
 Screen Shot 2018-04-10 at 1.12.31 AM.png  
 

  
 
 
 
 

 
 
 

 
 
 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-50601) SSH plugin cannot negotiate

2018-04-10 Thread zac...@gmx.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zack Snyder commented on  JENKINS-50601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSH plugin cannot negotiate   
 

  
 
 
 
 

 
 Devin Nusbaum Any update here?  
 

  
 
 
 
 

 
 
 

 
 
 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-50287) Make as-it-is checkout only files initally

2018-04-10 Thread n...@x2systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Neil Sleightholm edited a comment on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 In my case this has introduced a problem, I want a clean workspace to be updated to infinity and then my build process will remove some files and I want this to be the "as-it-is" state. This defect has now broken this behaviour - can I request that this change is regressed? [~ifernandezcalvo] - is it possible to get this reverted?  
 

  
 
 
 
 

 
 
 

 
 
 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-30744) multibranch issues if branch contains /

2018-04-10 Thread m...@thois.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thijs Borst commented on  JENKINS-30744  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: multibranch issues if branch contains /   
 

  
 
 
 
 

 
 Varun Reddy No, we've adjusted the way we name our branches, which is a pain.  
 

  
 
 
 
 

 
 
 

 
 
 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-50663) Deadlock on jenkins startup

2018-04-10 Thread cobe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Obexer commented on  JENKINS-50663  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on jenkins startup   
 

  
 
 
 
 

 
 FYI: Apparently a fixed Sonar plugin is already published: https://plugins.jenkins.io/sonar?why-is-this-caching-so-damn-bad Fix: https://github.com/jenkinsci/sonarqube-plugin/commit/735513927f6b3811cf9ced1a38681913639b6ab0    
 

  
 
 
 
 

 
 
 

 
 
 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-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50669  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value   
 

  
 
 
 
 

 
 Code changed in jenkins User: Baptiste Mathus Path: src/main/java/io/jenkins/plugins/essentials/logging/EssentialsLoggingConfigurer.java http://jenkins-ci.org/commit/essentials-plugin/5f42dc4e3cca1981dc7c5636b4139731c0d16ec4 Log: JENKINS-50669 reflective access shim  
 

  
 
 
 
 

 
 
 

 
 
 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-50710) essentials plugin Jenkinsfile should trigger a full evergreen build with the change

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50710  
 
 
  essentials plugin Jenkinsfile should trigger a full evergreen build with the change   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 R. Tyler Croy  
 
 
Components: 
 essentials, essentials-plugin  
 
 
Created: 
 2018-04-10 08:55  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 Right now, the essentials-plugin changes are tested only using the standard buildPlugin.  We should have that, but then run at least the make container-check with the changed plugin to see if this does not break anything. Note: I'm not doing that right now since 1) we have more pressing matters, and 2) possibly this will be superseded by a larger picture way of achieving this: we want any Jenkins Essentials change to be checked against evergreen tests and many many others, so maybe it's better and simpler to just see this plugin like any other one. Any opinion R. Tyler Croy?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
   

[JIRA] (JENKINS-50710) essentials plugin Jenkinsfile should trigger a full evergreen build with the change

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50710  
 
 
  essentials plugin Jenkinsfile should trigger a full evergreen build with the change   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 Right now, the essentials-plugin changes are tested only using the standard {{buildPlugin}}. We should have that, but then run at least the {{make container-check}} with the changed plugin to see if this does not break anything.Note: I'm not doing that right now since 1) we have more pressing matters, and 2) possibly this will be superseded by a larger picture way of achieving this: we want *any* _Jenkins Essentials_ change to be checked against evergreen tests and many many others, so maybe it's better and simpler to just see this plugin like any other  _Essentials_  one.Any opinion [~rtyler]?  
 

  
 
 
 
 

 
 
 

 
 
 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 email

[JIRA] (JENKINS-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50669  
 
 
  Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Sprint: 
 Essentials - Milestone  1  2  
 

  
 
 
 
 

 
 
 

 
 
 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-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50669  
 
 
  Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Labels: 
 essentials essentials-triggered  technical-debt  
 

  
 
 
 
 

 
 
 

 
 
 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-50711) plugin doesn't work with ssh link to git repo

2018-04-10 Thread admin-s...@ukr.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Serg Pr created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50711  
 
 
  plugin doesn't work with ssh link to git repo   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Boguslaw Klimas  
 
 
Components: 
 git-parameter-plugin  
 
 
Created: 
 2018-04-10 09:01  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Serg Pr  
 

  
 
 
 
 

 
 I have an error: "Command "/usr/bin/git ls-remote -h g...@gitlab.site.com:name/project.git" returned status code 128: stdout: stderr: /tmp/ssh5744210594072786682.sh: line 6: ssh: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.   As a result, I have a build error:  ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. If I fill the field "Default value" to "master" instead of "**" - I don't have Revision error in build process, but "Git Parameter Plugin's" error above, still exist and I can't choose the branch. I use: Git Parameter Plug-In: 0.9.1 Git plugin: 3.8.0 Git client plugin: 2.7.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-47399) Using of ssh url with new version of git-parameter plugin

2018-04-10 Thread admin-s...@ukr.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Serg Pr commented on  JENKINS-47399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using of ssh url with new version of git-parameter plugin   
 

  
 
 
 
 

 
 building job least once - doesn't help. Log attached.parameter-plugin-bug.txt    
 

  
 
 
 
 

 
 
 

 
 
 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-47399) Using of ssh url with new version of git-parameter plugin

2018-04-10 Thread admin-s...@ukr.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Serg Pr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47399  
 
 
  Using of ssh url with new version of git-parameter plugin   
 

  
 
 
 
 

 
Change By: 
 Serg Pr  
 
 
Attachment: 
 parameter-plugin-bug.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-50711) plugin doesn't work with ssh link to git repo

2018-04-10 Thread admin-s...@ukr.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Serg Pr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50711  
 
 
  plugin doesn't work with ssh link to git repo   
 

  
 
 
 
 

 
Change By: 
 Serg Pr  
 
 
Attachment: 
 parameter-plugin-bug.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtilsTest.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-include-attached-artifacts.log http://jenkins-ci.org/commit/pipeline-maven-plugin/4ffd21589f13de17a891eb1cdc242104254748d6 Log: Merge pull request #142 from bingshiao/JENKINS-50709 JENKINS-50709 Missing attached artifacts in pom typed project Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/1913c238dc6c...4ffd21589f13  
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated  JENKINS-50709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50709  
 
 
  Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-50709) Missing attached artifacts in pom typed project

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50709  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing attached artifacts in pom typed project   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bing Shiao Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtilsTest.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-include-attached-artifacts.log http://jenkins-ci.org/commit/pipeline-maven-plugin/b269fcc2fc0f8dd7b03613bd4f8f469bdee3f3ea Log: JENKINS-50709 Missing attached artifacts in pom typed project  
 

  
 
 
 
 

 
 
 

 
 
 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-25858) java.io.IOException: Unexpected termination of the channel

2018-04-10 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vassilena Treneva commented on  JENKINS-25858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.IOException: Unexpected termination of the channel   
 

  
 
 
 
 

 
 Using Jenkins ver. 2.113 with SSH Slaves plugin 1.26. All our UNIX, Windows and OSX slaves are using SSH connection.  We are seeing a lot of these. Is it the same issue?     Slave JVM has not reported exit code. Is it still running? ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)      ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) ERROR: Socket connection to SSH server was lost java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at com.trilead.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41) at com.trilead.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52) at com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79) at com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108) at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:232) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:706) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) at java.lang.Thread.run(Thread.java:748) Slave JVM has not reported exit code before the socket was lost [04/05/18 17:10:24] [SSH] Connection closed.  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-50712) branchSources in MultibranchWorkflowJob asking for vulnerable signature approvals when running in sandbox

2018-04-10 Thread alexeygrigo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexey Grigorov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50712  
 
 
  branchSources in MultibranchWorkflowJob asking for vulnerable signature approvals when running in sandbox   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2018-04-10 10:02  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Alexey Grigorov  
 

  
 
 
 
 

 
 Hi team I have 2 examples where I have parametrized build which supposed to create a pipelines. But when running in sandbox it failing and asking for approvals of : method groovy.lang.GroovyObject getProperty java.lang.String method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object which are highlighted red as dangerous by jenkins here are examples  

 
multibranchPipelineJob("${JENKINS_PROJECT_NAME}/CI Build") {
branchSources {
github {
scanCredentialsId("${GIT_CREDENTIALS_ID}")
repoOwner("${GITHUB_REPO_OWNER}")
repository("${GITHUB_REPO_NAME}")
}
}
}
 

 

 
ERROR: Scripts not permitted to use method groovy.lang.GroovyObject getProperty java.lang.String (javaposse.jobdsl.dsl.helpers.workflow.GitHubBranchSourceContext.GIT_CREDENTIALS_ID)
 

 I think problem here is usage of DELEGATE_FIRST mode without whitelisting (if it even possible to whitelist) second example  

 
 

[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally

2018-04-10 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 maybe we can add an option to set the value of `--set-depth` when you select `as-it-is`  
 

  
 
 
 
 

 
 
 

 
 
 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-50712) branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox

2018-04-10 Thread alexeygrigo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexey Grigorov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50712  
 
 
  branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox   
 

  
 
 
 
 

 
Change By: 
 Alexey Grigorov  
 
 
Summary: 
 branchSources in MultibranchWorkflowJob  and PipelineJob  asking for vulnerable signature approvals when running in sandbox  
 

  
 
 
 
 

 
 
 

 
 
 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-26521) timeout step should support breaking on inactivity, not just a fixed duration

2018-04-10 Thread henrik.ko...@emc.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Koren commented on  JENKINS-26521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timeout step should support breaking on inactivity, not just a fixed duration   
 

  
 
 
 
 

 
 Andrew Bayer when do you think that this change will be resolved  thanks   
 

  
 
 
 
 

 
 
 

 
 
 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-50287) Make as-it-is checkout only files initally

2018-04-10 Thread n...@x2systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Neil Sleightholm commented on  JENKINS-50287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make as-it-is checkout only files initally   
 

  
 
 
 
 

 
 That would be perfect.  
 

  
 
 
 
 

 
 
 

 
 
 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-50460) Builds marked as failed - Dr Memory plugin (JEP-200)

2018-04-10 Thread pin...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Piotr Bogdanski commented on  JENKINS-50460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds marked as failed - Dr Memory plugin (JEP-200)   
 

  
 
 
 
 

 
 I was able to workround this issue, as suggested here, by adding below in jenkins.xml file:     

 

-Dhudson.remoting.ClassFilter=net.praqma.drmemory.DrMemoryResult,net.praqma.drmemory.DrMemoryResult$ErrorSummary,net.praqma.drmemory.errors.InvalidHeapArgument,net.praqma.drmemory.DrMemoryError$StackTrace,net.praqma.drmemory.DrMemoryError$Note 

      
 

  
 
 
 
 

 
 
 

 
 
 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-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Sonar Team  
 
 
Attachments: 
 jenkins.log, Screen Shot 2018-04-10 at 17.47.30.png  
 
 
Components: 
 sonar  
 
 
Created: 
 2018-04-10 10:33  
 
 
Environment: 
 OS: Ubuntu 16.04 LTS. (4.4.0-116-generic #140-Ubuntu)  JRE/JDK: 1.8.0_131  Jenkins Master: 2.114  Web Browser: Chrome 65.0.3325.181  Jenkins Installation: sudo apt install jenkins  SonarQube Scanner: upgrade from 2.6.1 -> 2.7  
 
 
Labels: 
 sonar sonarqube plugin startup  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: https://plugins.jenkins.io/sonar.   The Jenkins shows: Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for.    The /var/log/jenkins/jenkins.log has been attached: jenkins.log   Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists $ sudo /etc/init.d/jenkins stop Correct java version found [ ok ] Stopping jenkins (via systemctl): jenkins.service. appadmin@Jenkins:~$ ps aux | grep jenkins jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/

[JIRA] (JENKINS-50713) Timestamper URL paths are incorrect in README examples

2018-04-10 Thread royar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Arnon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50713  
 
 
  Timestamper URL paths are incorrect in README examples   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Steven G Brown  
 
 
Components: 
 timestamper-plugin  
 
 
Created: 
 2018-04-10 10:33  
 
 
Environment: 
 Timestamper 1.8.9  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Arnon  
 

  
 
 
 
 

 
 In the wiki, you describe the timestamp paths as the following:   

 
Examples:

/timestamps
By default, display the elapsed time in seconds with three places after the decimal point.
/timestamps?time=HH:mm:ss&appendLog
Display the system clock time and append the line from the log.
/timestamps?elapsed=HH:mm:ss.S&appendLog
Display the elapsed time and append the line from the log.
/timestamps?time=HH:mm:ss&elapsed=HH:mm:ss.S
Display both the system clock time and the elapsed time.
/timestamps?currentTime&time=HH:mm:ss
Display the current time on the Jenkins master. 

   These paths are incorrect. When sending a request to /timestamps?time=HH:mm:ss&appendLog for example:   

 
< HTTP/1.1 302 Found
< Server: nginx/1.10.2
< Date: Tue, 10 Apr 2018 10:31:27 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Content-Type-Options: nosniff
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET, POST, PUT, DELETE
< Access-Control-Allow-Headers: Authorization
< Set-Cookie: JSESSIONID.10fc358a=node01

[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Change By: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png |width=500 ! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{{$ sudo /etc/init.d/jenkins stop}}{{Correct java version found}}{{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}}{{appadmin@Jenkins:~$ ps aux | grep jenkins}}{{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://www.myjenkins.com -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}}{{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://www.myjenkins.com -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}}{{Correct java version found}}{{[ ok ] Starting jenkins (via systemctl): jenkins.service.}}{{$ ps aux | grep j

[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Change By: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.]   The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png|width= 500 1000 ! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{{$ sudo /etc/init.d/jenkins stop}}{{Correct java version found}}{{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}}{{appadmin@Jenkins:~$ ps aux | grep jenkins}}{{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid  --  –  /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/]  -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}}{{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/]  -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}}{{Correct java version found}}{{[ 

[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Change By: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.]  The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for.  !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists  { quote} { { $ sudo /etc/init.d/jenkins stop}} {{Correct java version found}} {{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}} {{appadmin@Jenkins:~$ ps aux | grep jenkins}} {{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}} {{Correct java version found}} {{[ 

[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Change By: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.]  The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for.  !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{quote} {{ $ sudo /etc/init.d/jenkins stop }}   {{ Correct java version found }}   {{ [ ok ] Stopping jenkins (via systemctl): jenkins.service. }}   {{ appadmin@Jenkins:~$ ps aux | grep jenkins }}   {{ jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 }}   {{ jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 }}   {{ $ sudo /etc/init.d/jenkins start }}   {{ Correct j

[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread marslo.j...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marslo Jiao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50714  
 
 
  SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
Change By: 
 Marslo Jiao  
 

  
 
 
 
 

 
 SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.]  The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for.  !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists   { quote noformat }  $ sudo /etc/init.d/jenkins stop Correct java version found [ ok ] Stopping jenkins (via systemctl): jenkins.service.  appadmin jenkins @Jenkins:~$ ps aux | grep jenkins jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/]  -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/]  -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080   $ sudo /etc/init.d/jenkins start Correct java version found [ ok ]

[JIRA] (JENKINS-50663) Deadlock on jenkins startup

2018-04-10 Thread henr...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 henryju commented on  JENKINS-50663  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on jenkins startup   
 

  
 
 
 
 

 
 Fixed in 2.7.1 Ticket on our side: https://jira.sonarsource.com/browse/SONARJNKNS-294  
 

  
 
 
 
 

 
 
 

 
 
 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-50715) Pipeline fails with NPE due to Blue Ocean favorites

2018-04-10 Thread renatosilvar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Renato Rosa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50715  
 
 
  Pipeline fails with NPE due to Blue Ocean favorites   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-04-10 10:49  
 
 
Environment: 
 Jenkins version: 2.114  Blue Ocean version: 1.4.2  
 
 
Labels: 
 blueocean  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Renato Rosa  
 

  
 
 
 
 

 
 This was a new branch, and this was the first time it was built in a multi-branch pipeline. 

 
[Pipeline] End of Pipeline
 java.lang.NullPointerException
 at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:109)
 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127)
 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
 at hudson.security.ACL.impersonate(ACL.java:290)
 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor

[JIRA] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)

2018-04-10 Thread b...@praqma.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bue Petersen commented on  JENKINS-50460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds marked as failed - Dr Memory plugin (JEP-200)   
 

  
 
 
 
 

 
 We are happy to accept PRs solving the problem, but right now I don't have bandwidth to get the problem fixed. If it is simple and related to remoting, we might know what the problem is and then it is not complex to fix. In that case we could maybe supply a fix within some weeks.      
 

  
 
 
 
 

 
 
 

 
 
 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-50460) Builds marked as failed - Dr Memory plugin (JEP-200)

2018-04-10 Thread b...@praqma.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bue Petersen commented on  JENKINS-50460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds marked as failed - Dr Memory plugin (JEP-200)   
 

  
 
 
 
 

 
 Mads Nielsen - this is the know remoting problem, we're going to fix for other of our plugins - right?  
 

  
 
 
 
 

 
 
 

 
 
 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-50460) Builds marked as failed - Dr Memory plugin (JEP-200)

2018-04-10 Thread b...@praqma.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bue Petersen commented on  JENKINS-50460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds marked as failed - Dr Memory plugin (JEP-200)   
 

  
 
 
 
 

 
 Oh, sorry for the spam. Yes he says - we will supply a fix during next week.  
 

  
 
 
 
 

 
 
 

 
 
 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-50716) Include scm/tag in flattened POM

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


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50716  
 
 
  Include scm/tag in flattened POM   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 plugin-pom  
 
 
Created: 
 2018-04-10 11:15  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 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 uns

[JIRA] (JENKINS-50663) Deadlock on jenkins startup

2018-04-10 Thread k...@vandewiele.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kpop commented on  JENKINS-50663  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on jenkins startup   
 

  
 
 
 
 

 
 On my setup, Sonar 2.7.1 fixes the startup issue. Thank you henryju for the quick fix!  
 

  
 
 
 
 

 
 
 

 
 
 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-50717) Documentation update for polling

2018-04-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50717  
 
 
  Documentation update for polling   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Labels: 
 P4_C  
 

  
 
 
 
 

 
 
 

 
 
 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-50717) Documentation update for polling

2018-04-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50717  
 
 
  Documentation update for polling   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Paul Allen  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-04-10 11:24  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Paul Allen  
 

  
 
 
 
 

 
 Split out Polling and triggered builds into a seperate doc and update filters.  Add hinds on 'Build' before polling when updating pipeline poll filters.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  

[JIRA] (JENKINS-50027) Polling build filters in jenkinsfile broken or need guidance on what code should be

2018-04-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-50027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ready for release.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50027  
 
 
  Polling build filters in jenkinsfile broken or need guidance on what code should be   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-50634) Triggered probe option

2018-04-10 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen started work on  JENKINS-50634  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT

2018-04-10 Thread atay...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Taylor reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 See my last comment since I think it is still an issue  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-20427  
 
 
  Build Parameter variable in branch name causes polling to detect false changes in GIT   
 

  
 
 
 
 

 
Change By: 
 Alex Taylor  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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, v

[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector

2018-04-10 Thread ulid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Max M commented on  JENKINS-40109  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector   
 

  
 
 
 
 

 
 I am as well getting the same ErrorCollector NotSerializable exception; however, a standalone call like this: 

 

$ groovy CI/erroring_script.groovy
$
 

 (outside of Jenkins) does not show any compilation errors! In Jenkins, OTOH, this same file causes stacktraces like this: 

 

an exception which occurred:
	in field org.codehaus.groovy.control.MultipleCompilationErrorsException.collector
	in object org.codehaus.groovy.control.MultipleCompilationErrorsException@5c35f1cb
	in field com.cloudbees.groovy.cps.Outcome.abnormal
	in object com.cloudbees.groovy.cps.Outcome@3bd3307c
	in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome
	in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@5ea1a9f6
	in field com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution.body
	in object com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution@1d84ca28
	in field org.jenkinsci.plugins.workflow.cps.CpsThread.step
	in object org.jenkinsci.plugins.workflow.cps.CpsThread@57923e5c
	in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread
	in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@1509e249
	in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0
	in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@66aabd0b
	in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress
	in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@4ece610f
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
	in object com.cloudbees.groovy.cps.impl.TryBlockEnv@164ca394
	in field com.cloudbees.groovy.cps.impl.CallEnv.caller
	in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@5e76c9db
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
	in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@147a91d1
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
	in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1e88ca58
	in field com.cloudbees.groovy.cps.impl.CpsClosureDef.capture
	in object com.cloudbees.groovy.cps.impl.CpsClosureDef@34f25659
	in field com.cloudbees.groovy.cps.impl.CpsClosure.def
	in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@15439a64
	in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures
	in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@89104e8
	in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@89104e8
Caused: java.io.NotSerializableException: org.codehaus.groovy.control.ErrorCollector
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
	at org.jboss.marshalling.river.River

[JIRA] (JENKINS-50075) Unit Test for IssuesFilter

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unit Test for IssuesFilter   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ullrich Hafner Path: src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeCategoryTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeFileTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeModuleTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludePackageTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeTypeTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeCategoryTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeFileTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeModuleTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludePackageTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeTypeTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IssuesFilterTestUtil.java http://jenkins-ci.org/commit/analysis-core-plugin/853db77f4fb2bcfbc565b346a995b8c5dec094fe Log: Merge pull request #98 from frankchrisg/hm-edu-testing Add JUnit tests for IssuesFilter and subclasses for task JENKINS-50075. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/aa3a8b4d9ec1...853db77f4fb2  
 

  
 
 
 
 

 
 
 

 
 
 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/op

[JIRA] (JENKINS-50082) Unit Test of LocalizedPriority and EnvironmentResolver

2018-04-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-50082  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50082  
 
 
  Unit Test of LocalizedPriority and EnvironmentResolver   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-50075) Unit Test for IssuesFilter

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unit Test for IssuesFilter   
 

  
 
 
 
 

 
 Code changed in jenkins User: Frank Christian Geyer Path: src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeCategoryTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeFileTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeModuleTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludePackageTest.java src/test/java/io/jenkins/plugins/analysis/core/model/ExcludeTypeTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeCategoryTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeFileTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeModuleTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludePackageTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IncludeTypeTest.java src/test/java/io/jenkins/plugins/analysis/core/model/IssuesFilterTestUtil.java http://jenkins-ci.org/commit/analysis-core-plugin/4b6faee021c7bdb2cbbdcb911315d3bc9b8aa6f6 Log: Add JUnit tests for IssuesFilter and subclasses for task JENKINS-50075.  
 

  
 
 
 
 

 
 
 

 
 
 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-50075) Unit Test for IssuesFilter

2018-04-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50075  
 
 
  Unit Test for IssuesFilter   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-50074) Mockito Test for ByIdResultSelector

2018-04-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-50074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50074  
 
 
  Mockito Test for ByIdResultSelector   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-50069) Unit Test for IssuesRecorder.Descriptor

2018-04-10 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-50069  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50069  
 
 
  Unit Test for IssuesRecorder.Descriptor   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-50294) Design (JEP) Essentials Instance Client Health Checking

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50294  
 
 
  Design (JEP) Essentials Instance Client Health Checking   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Summary: 
 Design (JEP)  how to determine the "health level" of Jenkins   Essentials Instance Client Health Checking  
 

  
 
 
 
 

 
 
 

 
 
 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-50490) Provide lightweight checkout capability for Mercurial

2018-04-10 Thread k...@vandewiele.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kpop commented on  JENKINS-50490  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide lightweight checkout capability for Mercurial   
 

  
 
 
 
 

 
 This is also described in the official documentation https://www.mercurial-scm.org/wiki/TipsAndTricks#Create_links_to_snapshots_of_files_and_tarballs  
 

  
 
 
 
 

 
 
 

 
 
 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-50294) Design (JEP) Essentials Instance Client Health Checking

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-50294  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Design (JEP) Essentials Instance Client Health Checking   
 

  
 
 
 
 

 
 Early draft review thread on the developer ML : https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/jenkinsci-dev/9YNUJyE5WGE   
 

  
 
 
 
 

 
 
 

 
 
 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-50294) Design (JEP) Essentials Instance Client Health Checking

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated  JENKINS-50294  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50294  
 
 
  Design (JEP) Essentials Instance Client Health Checking   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-49471) Add option for suppressing notifications to Bitbucket

2018-04-10 Thread benoit.gue...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 benoit guerin closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49471  
 
 
  Add option for suppressing notifications to Bitbucket   
 

  
 
 
 
 

 
Change By: 
 benoit guerin  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-40921) Build Periodically setting for multibranch pipelines needs clarification

2018-04-10 Thread jenk...@macwinnie.me (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Winter commented on  JENKINS-40921  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build Periodically setting for multibranch pipelines needs clarification   
 

  
 
 
 
 

 
 May I ask, why the mentioned solution – to remove the option – was the chosen one? My use-case would be to run the build of some multibranch projects every x hours. The Job is to build multiple versions of docker images of one tool based on their base image. The base image could have changed while the relevant SCM source did not and so the multibranch pipeline does not fit my needs. Or did I miss sth? Thank you!  
 

  
 
 
 
 

 
 
 

 
 
 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-49805) Prototype error telemetry logging with a Java Util Logger configuration

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus started work on  JENKINS-49805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-49805) Prototype error telemetry logging with a Java Util Logger configuration

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-49805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prototype error telemetry logging with a Java Util Logger configuration   
 

  
 
 
 
 

 
 So I'm going to close this, as I just checked we do implement the JEP. 
 
JENKINS-50164 still blocks the implementation of some part of the "data segregation" part of the JEP, but will be enough already to track it. I'll adjust the image once it's approved & merged. 
I also filed https://github.com/jenkinsci/jep/pull/80 to add some clarifications about log rotation expectations after a discussion with R. Tyler Croy, and an overlook for the name field I had forgotten to put in the JSON logs 
  
 

  
 
 
 
 

 
 
 

 
 
 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-49805) Prototype error telemetry logging with a Java Util Logger configuration

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49805  
 
 
  Prototype error telemetry logging with a Java Util Logger configuration   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-49811) Define Evergreen Error service API

2018-04-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus started work on  JENKINS-49811  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-50714) SonarQube Scanner 2.7 blocks Jenkins start

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50714  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SonarQube Scanner 2.7 blocks Jenkins start   
 

  
 
 
 
 

 
 Would it be possible to get a threaddump from the instance?  
 

  
 
 
 
 

 
 
 

 
 
 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-50701) Jenkin Dynatrace SAAS Integration issue

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50701  
 
 
  Jenkin Dynatrace SAAS Integration issue   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 _unsorted  
 
 
Component/s: 
 jenkinslint-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-50701) Jenkin Dynatrace SAAS Integration issue

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50701  
 
 
  Jenkin Dynatrace SAAS Integration issue   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Victor Martinez Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-50701) Jenkin Dynatrace SAAS Integration issue

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50701  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkin Dynatrace SAAS Integration issue   
 

  
 
 
 
 

 
 Apparently JIRA component was missing for the plugin. Fixed it  
 

  
 
 
 
 

 
 
 

 
 
 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-50701) Jenkin Dynatrace SAAS Integration issue

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to dynatrace  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50701  
 
 
  Jenkin Dynatrace SAAS Integration issue   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev dynatrace  
 

  
 
 
 
 

 
 
 

 
 
 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-50701) Jenkin Dynatrace SAAS Integration issue

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50701  
 
 
  Jenkin Dynatrace SAAS Integration issue   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 dynatrace-dashboard-plugin  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-50598) Add support of running JTH with custom WAR

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support of running JTH with custom WAR   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/539cbe295a6782f6cde65cdf7962e6dbb07defb1 Log: Merge pull request #102 from oleg-nenashev/jth/2.38 [JENKINS-50598,JENKINS-50590] - Update JTH to 2.38 Compare: https://github.com/jenkinsci/plugin-pom/compare/624a61e2d84b...539cbe295a67  
 

  
 
 
 
 

 
 
 

 
 
 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-50590) Adding a crumb to a WebRequest removes all existing parameters

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Adding a crumb to a WebRequest removes all existing parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/539cbe295a6782f6cde65cdf7962e6dbb07defb1 Log: Merge pull request #102 from oleg-nenashev/jth/2.38 [JENKINS-50598,JENKINS-50590] - Update JTH to 2.38 Compare: https://github.com/jenkinsci/plugin-pom/compare/624a61e2d84b...539cbe295a67  
 

  
 
 
 
 

 
 
 

 
 
 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-50598) Add support of running JTH with custom WAR

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support of running JTH with custom WAR   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/45c3ffaa5eceddc25ffdf0eab7850ac34c902701 Log: [JENKINS-50598,JENKINS-50590] - Update JTH to 2.38  
 

  
 
 
 
 

 
 
 

 
 
 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-50590) Adding a crumb to a WebRequest removes all existing parameters

2018-04-10 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Adding a crumb to a WebRequest removes all existing parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/45c3ffaa5eceddc25ffdf0eab7850ac34c902701 Log: [JENKINS-50598,JENKINS-50590] - Update JTH to 2.38  
 

  
 
 
 
 

 
 
 

 
 
 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-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector

2018-04-10 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40109  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector   
 

  
 
 
 
 

 
 Max M - any chance you could attach your script that's failing?   
 

  
 
 
 
 

 
 
 

 
 
 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-50700) Fix maven-hpi-plugin to use hudson.util.VersionNumber

2018-04-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50700  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix maven-hpi-plugin to use hudson.util.VersionNumber   
 

  
 
 
 
 

 
 would be great  
 

  
 
 
 
 

 
 
 

 
 
 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-50642) intermittent JenkinsRule test timeout failure

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


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: intermittent JenkinsRule test timeout failure   
 

  
 
 
 
 

 
 

the jenkins-jdk-8 branch likely will fail for the same reason
 I guess you mean MarkEWaite:require-jdk-8. That is on 2.60.x—already quite old! May as well just base it on the current LTS (2.107.x) IMO.  
 

  
 
 
 
 

 
 
 

 
 
 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-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-10 Thread jgang...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jae Gangemi commented on  JENKINS-50525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
 both  
 

  
 
 
 
 

 
 
 

 
 
 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-50525) Error When Provisioning Slave: mountPath: Required value

2018-04-10 Thread jgang...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jae Gangemi commented on  JENKINS-50525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error When Provisioning Slave: mountPath: Required value   
 

  
 
 
 
 

 
 i tried mounting in a host volume just to see if that populate the field but i still got the same error.  
 

  
 
 
 
 

 
 
 

 
 
 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-49389) Completed pipeline jobs queued against master

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49389  
 
 
  Completed pipeline jobs queued against master   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Labels: 
 maybe-fixed-by-durability-megafix  
 

  
 
 
 
 

 
 
 

 
 
 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-50213) SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SEVERE io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor Could not find execution for run   
 

  
 
 
 
 

 
 Vivek Pandey this one looks like the root cause is failure to persist some key piece of data (maybe a dirty restart occurred at a very bad time).  Blue Ocean should accept the occasional null FlowExecution because that is a legitimate state that can arise from some forms of critical runtime failure.   
 

  
 
 
 
 

 
 
 

 
 
 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-49389) Completed pipeline jobs queued against master

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-49389  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Completed pipeline jobs queued against master   
 

  
 
 
 
 

 
 John Arnold I just released a big update to workflow-cps (v 2.47) and workflow-job (v 2.18) that fixes a large variety of related issues. Could you please install these updates and let us know if they resolve the issues here? Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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-50663) Deadlock on jenkins startup

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


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50663  
 
 
  Deadlock on jenkins startup   
 

  
 
 
 
 

 
 While a Sonar plugin change may have triggered this bug, it looks more like a core issue to me. The deadlock is between GuiceFinder and ExtensionList, but possibly OldDataMonitor.report should not be acquiring a lock either since it is involved at a low level in initialization—perhaps it could queue up reports until after startup has completed, or at least extensions have been prepared, or perhaps data could become a static WeakHashMap reference.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 core  
 
 
Labels: 
 deadlock threads  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 
 

[JIRA] (JENKINS-45585) WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-45585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build   
 

  
 
 
 
 

 
 Released with v2.18 of workflow-job  
 

  
 
 
 
 

 
 
 

 
 
 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-49746) Regex returns more matches than it should if errors are close together

2018-04-10 Thread barn...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish commented on  JENKINS-49746  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regex returns more matches than it should if errors are close together   
 

  
 
 
 
 

 
 Alex Earl, did you find a solution for this issue yet? It is still causing very large emails to be sent from our Jenkins server.  
 

  
 
 
 
 

 
 
 

 
 
 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-45585) WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-45585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45585  
 
 
  WorkflowRun.onLoad need not eagerly load the FlowExecution of a completed build   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-50348) Why does "Pipeline: Groovy" require "Support Core"?

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing b/c Andrew has explained the reason for the dependency  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50348  
 
 
  Why does "Pipeline: Groovy" require "Support Core"?   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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 ht

[JIRA] (JENKINS-49930) Add editor ATH coverage for setting and changing environment variables

2018-04-10 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz started work on  JENKINS-49930  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-49930) Add editor ATH coverage for setting and changing environment variables

2018-04-10 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz assigned an issue to Karl Shultz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49930  
 
 
  Add editor ATH coverage for setting and changing environment variables   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Assignee: 
 Karl Shultz  
 

  
 
 
 
 

 
 
 

 
 
 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-47913) 'Script' text box is not visible.

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47913  
 
 
  'Script' text box is not visible.   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 
 

 
 
 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-49930) Add editor ATH coverage for setting and changing environment variables

2018-04-10 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-49930  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add editor ATH coverage for setting and changing environment variables   
 

  
 
 
 
 

 
 PR up.  
 

  
 
 
 
 

 
 
 

 
 
 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-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile

2018-04-10 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-49928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add editor ATH coverage for changing agent settings in a Jenkinsfile   
 

  
 
 
 
 

 
 PR up.  
 

  
 
 
 
 

 
 
 

 
 
 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-47913) 'Script' text box is not visible.

2018-04-10 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ravi H K My understanding is that those plugins are were originally somewhat special and weren't used in the normal way exactly. Anyway, that approach is no longer suggested, and I'm not surprised that the direct HPI install doesn't generate a working system – I think that those HPI dependencies may not actually do anything anymore without special build configuration (though would hesitate to remove them completely without confirming more deeply).  Currently the suggested way to add JS dependencies is located here: https://github.com/jenkinsci/js-samples/blob/master/step-04-externalize-libs/HOW-IT-WORKS.md#configure-node-build-to-externalize-dependencies – I believe this is how the JS dependencies are actually added in plugins.  Someone more familar with the guts of how our JS dependencies work may feel free to correct me here though – I mostly do backend stuff at the moment. Tom FENNELLY is that right or am I completely off base here?  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47913  
 
 
  'Script' text box is not visible.   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together

2018-04-10 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-49746  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regex returns more matches than it should if errors are close together   
 

  
 
 
 
 

 
 I have not, been hammered at work and haven't had time to look into it more.  
 

  
 
 
 
 

 
 
 

 
 
 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.


  1   2   3   >