[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread tobias.h...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Herrmann Hinz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55654  
 
 
  infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
Change By: 
 Tobias Herrmann Hinz  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread jaros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 aleksey savitskiy commented on  JENKINS-55654  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
 The same here with Bitbucket OAuth plugin. After success authentification on bitbucket site system redirects me to securityRealm/finishLogin url, wich which will fail and the loop starts again. plugin version 0.8 jenkins version 2.150.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49042) Update Robot Framework logo to new one

2019-01-17 Thread aleksi.sim...@eficode.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksi Simell closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49042  
 
 
  Update Robot Framework logo to new one   
 

  
 
 
 
 

 
Change By: 
 Aleksi Simell  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-43752) Not able to use git, sh, pwd etc in active choice parameter script

2019-01-17 Thread jens.haup...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 J H edited a comment on  JENKINS-43752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to use git, sh, pwd etc in active choice parameter script   
 

  
 
 
 
 

 
 I have the same Problem. Is there  anythinh  anything  new?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-43752) Not able to use git, sh, pwd etc in active choice parameter script

2019-01-17 Thread jens.haup...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 J H commented on  JENKINS-43752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to use git, sh, pwd etc in active choice parameter script   
 

  
 
 
 
 

 
 I have the same Problem. Is there anythinh new?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55561) Stages within stage thoriwng error

2019-01-17 Thread shiv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shivu R H commented on  JENKINS-55561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stages within stage thoriwng error
 

  
 
 
 
 

 
 Thank you Vivek Pandey and Andrew Bayer for your paying attention. Vivek Pandey I'm having older versions -  
 
Jenkins (2.107.1) 
Pipeline: Declarative(1.2.7) 
 Seems to be I need to upgrade to avail the nesting at sub stages.   Andrew Bayer I tried this snippet.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55561) Stages within stage thoriwng error

2019-01-17 Thread shiv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shivu R H updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55561  
 
 
  Stages within stage thoriwng error
 

  
 
 
 
 

 
Change By: 
 Shivu R H  
 

  
 
 
 
 

 
 I'm trying to build pipeline using declarative pipeline by referring [pipeline syntax |https://jenkins.io/doc/book/pipeline/syntax/].From  *  [this|https://jenkins.io/doc/book/pipeline/syntax/#parallel] * , I'm getting the following -{code:java}WorkflowScript: 31: Unknown stage section "stages". Starting with version 0.5, steps in a stage must be in a steps block. @ line 31, column 17.   stage('Branch C') {   ^WorkflowScript: 31: No "steps" or "parallel" to execute within stage "Branch C" @ line 31, column 17.   stage('Branch C') {   ^2 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310){code}also from [this |https://jenkins.io/doc/book/pipeline/syntax/#sequential-stages-example] -{code:java}Running in Durability level: MAX_SURVIVABILITYorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 14: Unknown stage section "stages". Starting with version 0.5, steps in a stage must be in a steps block. @ line 14, column 9.   stage('Sequential') {   ^WorkflowScript: 14: No "steps" or "parallel" to execute within stage "Sequential" @ line 14, column 9.   stage('Sequential') {   ^2 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310){code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-55671) interactive shell script console in jenkins pipeline

2019-01-17 Thread narakeshec...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rakesh Nagarajan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55671  
 
 
  interactive shell script console in jenkins pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-01-18 05:21  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Rakesh Nagarajan  
 

  
 
 
 
 

 
 I am having a shell script, Which executes the sh file and in the mid of the script, it will print some values and  will ask for (Yes/No) confirmation.   I need to give yes or no value (or any sort of value) to the shell script through jenkins to the mid of the shell script.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 


[JIRA] (JENKINS-55670) Add support of sonar vulnerabilities

2019-01-17 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55670  
 
 
   Add support of sonar vulnerabilities   
 

  
 
 
 
 

 
Change By: 
 Radi Berkovich  
 
 
Summary: 
  Add  support of  sonar vulnerabilities  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55670) Add sonar vulnerabilities

2019-01-17 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55670  
 
 
   Add sonar vulnerabilities   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-01-18 05:20  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-17 Thread bruno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Medeiros commented on  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
 Same problem for OpenID Connect support: JENKINS-55668  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-17 Thread bruno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Medeiros edited a comment on  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
 Same problem for OpenID Connect support: JENKINS- 55668 55669  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55669) Auth plugin doesn't work after upgrade to Jenkins 2.150.2

2019-01-17 Thread bruno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Medeiros updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55669  
 
 
  Auth plugin doesn't work after upgrade to Jenkins 2.150.2   
 

  
 
 
 
 

 
Change By: 
 Bruno Medeiros  
 

  
 
 
 
 

 
 Keycloak plugin is broken after 2.150.2 update, as described here is this other OpenID Connect plugin:[https://github.com/jenkinsci/oic-auth-plugin/issues/54] Also seems related to:https://issues.jenkins-ci.org/browse/JENKINS-55668  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55669) Auth plugin doesn't work after upgrade to Jenkins 2.150.2

2019-01-17 Thread bruno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Medeiros created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55669  
 
 
  Auth plugin doesn't work after upgrade to Jenkins 2.150.2   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 D. Lauer  
 
 
Components: 
 keycloak-plugin  
 
 
Created: 
 2019-01-18 04:19  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Bruno Medeiros  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21311  
 
 
  Queue item cancellation via REST api works but returns a 404   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly queue rest stapler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33053) Trigger jobs in build pipeline plugin using REST api

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou commented on  JENKINS-33053  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Trigger jobs in build pipeline plugin using REST api   
 

  
 
 
 
 

 
 There is a GSoC 2019 project that proposes to wrap a java jenkins-rest library in the form of a Jenkins plugin, would that be a viable solution? If you are interested please reach out on https://gitter.im/jenkinsci/gsoc-sig  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55332) Parallel branch no longer prefixing log lines

2019-01-17 Thread royce_1...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Royce Shen closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55332  
 
 
  Parallel branch no longer prefixing log lines   
 

  
 
 
 
 

 
Change By: 
 Royce Shen  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55262  
 
 
  Missing content-type on serverStatuses REST API   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-20451) Add Copy Artefacts info to the xml Rest API

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20451  
 
 
  Add Copy Artefacts info to the xml Rest API   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31011) Provide REST API for enabling and disabling Jenkins jobs

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31011  
 
 
  Provide REST API for enabling and disabling Jenkins jobs   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 api  newbie-friendly  rest  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-20321) Chaining Jobs via REST Callback

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou commented on  JENKINS-20321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Chaining Jobs via REST Callback
 

  
 
 
 
 

 
 You can trigger builds and wait for them to complete using the REST API. See an example in the cdancy/jenkins-rest wiki.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26795) Configuration methods are not exported in REST API

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26795  
 
 
  Configuration methods are not exported in REST API   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-15624) Rest API for view manipulation

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-15624  
 
 
  Rest API for view manipulation   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48162) QUERY via REST API

2019-01-17 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48162  
 
 
  QUERY via REST API   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55586) Credentials-binding plugin still masking deleted credentials in log

2019-01-17 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator commented on  JENKINS-55586  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials-binding plugin still masking deleted credentials in log   
 

  
 
 
 
 

 
 Jasmine Jack, I'm not using JJB at all, I created my job by hand with a Jenkinsfile script.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55608) Log audit event for build start

2019-01-17 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar assigned an issue to David Olorundare  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55608  
 
 
  Log audit event for build start   
 

  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
Assignee: 
 Latha Sekar David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55608) Log audit event for build start

2019-01-17 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar assigned an issue to Latha Sekar  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55608  
 
 
  Log audit event for build start   
 

  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
Assignee: 
 David Olorundare Latha Sekar  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55608) Log audit event for build start

2019-01-17 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar assigned an issue to Latha Sekar  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55608  
 
 
  Log audit event for build start   
 

  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
Assignee: 
 Latha Sekar  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55268) Multibranch pipelines cannot have different "Named Branch" configurations when created by the organization plugin

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55268  
 
 
  Multibranch pipelines cannot have different "Named Branch" configurations when created by the organization plugin   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 git jenkins multi-branch organization pipeline  pipeline-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55517  
 
 
  Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 pipeline-triaged plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55220  
 
 
  Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 pipeline-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-55629  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
 Vijay K Can't reproduce. I tried latest Jenkins 2.150.2 with bitbucket-branch-source 2.4.0 and bitbucket 1.8, I can see Bitbucket in the drop down and it can be configured just fine. Can you check if you have these plugins installed and loaded correctly? Also, any error during jenkins startup? 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Priority: 
 Blocker Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55630) Support declarative pipelines

2019-01-17 Thread benjamin.musc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Muschko commented on  JENKINS-55630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support declarative pipelines   
 

  
 
 
 
 

 
 Thanks for your response. I should have mentioned that I am using `dep` for package management. 

 

pipeline {
agent any
tools {
go 'go-1.11'
}
stages {
stage('Prepare') {
steps {
sh 'go version'
sh 'curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh'
sh 'dep ensure'
}
}
stage('Build') {
steps {
sh 'go build'
}
}
}
}
 

 When trying to run `dep ensure` I get the following error message: 

 

+ dep ensure
/Users/bmuschko/.jenkins/workspace/link-verifier is not within a known GOPATH/src
 

 That's why I came to the conclusion that I needed a custom workspace. Do you have another idea on how to work around the issue? Things are probably easier with `vgo` as your project source doesn't necessarily have to reside in `$GOPATH/src`.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-17 Thread mar...@jitbase.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Courtois created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55668  
 
 
  Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Jenkins Oauth issue.png  
 
 
Components: 
 bitbucket-oauth-plugin  
 
 
Created: 
 2019-01-17 23:54  
 
 
Environment: 
 Jenkins 2.150.2  bitbucket-oauth-plugin 0.8  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Martin Courtois  
 

  
 
 
 
 

 
 Since I updated Jenkins with 2.150.2 version, I can't authentificate Jenkins with bitbucket-oauth-plugin 0.8. I'm in kind of redirect loop between bitbucket.org and my jenkins instance (attached) If I downgrade Jenkins to 2.150.1, it's working If I re-update to Jenkibs to 2.150.2, it's NOT working  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

[JIRA] (JENKINS-53562) Add remote root directory configuration

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-53562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add remote root directory configuration   
 

  
 
 
 
 

 
 This functionality was added in 1.0.6 together with windows images..    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52708) Fail to create agents with GPU attached

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak edited a comment on  JENKINS-52708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fail to create agents with GPU attached   
 

  
 
 
 
 

 
 GPUs can be attached (without modifying plugin code) by using templates functionality introduced in 1. 8. 0. 8.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52716) Allow selecting subnetworks different than "default" for the default VPC

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak edited a comment on  JENKINS-52716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow selecting subnetworks different than "default" for the default VPC   
 

  
 
 
 
 

 
 You can use any network via templates functionality introduced in 1. 8. 0. 8.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52251) Support GCE feature 'deploying-containers'

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak edited a comment on  JENKINS-52251  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support GCE feature 'deploying-containers'   
 

  
 
 
 
 

 
 That feature can probably be achieved by using templates introduced in 1. 8. 0. 8.  [~schultemarkus] Can you confirm..  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container

2019-01-17 Thread ay...@cornell.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ahmed Kamel commented on  JENKINS-55527  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds fail randomly when running sh in container   
 

  
 
 
 
 

 
 Got it. Thanks for posting these. I'll watch the issue over on github.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread j...@jackivy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Ivy commented on  JENKINS-55654  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
 We use LTS and when I updated to 2.150.2 we started getting an infinite redirect back and forth between Jenkins and login.microsoft.com when using the Azure AD plugin for authentication.  I had to roll back to 2.150.1.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52716) Allow selecting subnetworks different than "default" for the default VPC

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-52716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow selecting subnetworks different than "default" for the default VPC   
 

  
 
 
 
 

 
 You can use any network via templates functionality introduced in 1.8.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52708) Fail to create agents with GPU attached

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-52708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fail to create agents with GPU attached   
 

  
 
 
 
 

 
 GPUs can be attached (without modifying plugin code) by using templates functionality introduced in 1.8.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52251) Support GCE feature 'deploying-containers'

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-52251  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support GCE feature 'deploying-containers'   
 

  
 
 
 
 

 
 That feature can probably be achieved by using templates introduced in 1.8.0.   Markus Schulte Can you confirm..  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-01-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 

  
 
 
 
 

 
 The Job Config History plugin contains several fields that should be able to be configured with "Configuration as Code". These fields are normally configured under "Manage Jenkins". The fields can be viewed  at  [ here| https://plugins.jenkins.io/jobConfigHistory] under "Interdependencies with other Plugins".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-01-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Ewelina Wilkosz  
 
 
Components: 
 configuration-as-code-plugin, jobconfighistory-plugin  
 
 
Created: 
 2019-01-17 23:31  
 
 
Labels: 
 jcasc-compatibility  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Austin Dewey  
 

  
 
 
 
 

 
 The Job Config History plugin contains several fields that should be able to be configured with "Configuration as Code". These fields are normally configured under "Manage Jenkins". The fields can be viewed here under "Interdependencies with other Plugins".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
  

[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-17 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 Eric Blackwell Rachel Yen Thats exactly what Im telling about.. Thats was one of main reasons to add templates in our company.   At template level you can choose image family instead of image instead of image itself, and every time you create new image in that family it will automatically use it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-17 Thread eric.blackw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blackwell commented on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 I bet more people would use it if it was available. Is pretty handy.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55630) Support declarative pipelines

2019-01-17 Thread ch...@orr.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr commented on  JENKINS-55630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support declarative pipelines   
 

  
 
 
 
 

 
 Can you show the Declarative Pipeline that you tried already and are having trouble with? The Go-related environment variables should already be exported during a Pipeline build, and so this Pipeline works fine to install Go and be able to run it: 

 

pipeline {
  agent any
  tools {
go '1.11'
  }
  stages {
stage('Build') {
  steps {
sh 'go version'
sh 'git clone https://github.com/bmuschko/link-verifier'
dir('link-verifier') {
  sh 'go build …'
}
  }
}
  }
}  

 Does that cover what you're trying to do?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error

2019-01-17 Thread yixi...@medallia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yixiao Lin commented on  JENKINS-25046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cookie header too long, causing a 413 HTTP error   
 

  
 
 
 
 

 
 Bump this issue. We use Jenkins enterprise and use the operation center to manage the masters. With more masters, we run into this issue quite frequently.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41196) Pluggable core component

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-41196  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pluggable core component   
 

  
 
 
 
 

 
 I believe this story is largely replaced by Custom WAR Packager anyway (https://github.com/jenkinsci/custom-war-packager). This tool allows quickly building Custom WARs so that users can pick up Remoting/Stapler updates for their own baselines if they do not want to upgrade due to various reasons. Not a 100% solution, but it definitely helps in this use-case  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55654  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
 CC Wadeck Follonier Daniel Beck    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server

2019-01-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-55356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Some workflow jobs fail after restart on Java 11 server   
 

  
 
 
 
 

 
 That directory exists and looks like a typical workspace. it does contain a directory named .@tmp which was a surprise for me. That directory contains 3 files that with names that start with 'jenkins-gitclient-permission'. I assume some form of temporary file, but don't recognize them as anything specific.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55654  
 
 
  infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 OAuth jenkins keycloak oidc  regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55666) Configure Dependabot for the Vanilla image of Jenkinsfile Runner

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55666  
 
 
  Configure Dependabot for the Vanilla image of Jenkinsfile Runner   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2019-01-17 22:40  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 We already have some test automation for Jenkinsfile Runner. It would be great if we could setup an automatic update flow for the Vamnilla version so that we could try out the CI flows and the test frameworks for JFR  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-55663) Extend the Jenkinsfile Runner user documentation

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55663  
 
 
  Extend the Jenkinsfile Runner user documentation   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 It would be great to extend the documentation and to add the following info: * brief overview of the archirecture * clarify flavors of JFR (Vanilla and Custom War Packager) * document usage of Java 8 and Java 11 images  * Dependabot Example reference      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55663) Extend the Jenkinsfile Runner user documentation

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55663  
 
 
  Extend the Jenkinsfile Runner user documentation   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 documentation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55664) Create Developer documentation for Jenkinsfile Runner

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55664  
 
 
  Create Developer documentation for Jenkinsfile Runner   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2019-01-17 22:38  
 
 
Labels: 
 documentation  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
   Acceptance criteria: 
 
There is a CONTRIBUTING.md file with the contribution guidelines 
There is a DEVELOPER.md with a brief overview of the JFR architecture 
    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

[JIRA] (JENKINS-55665) Allow promotion of individual matrix builds

2019-01-17 Thread gsm...@d3engineering.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Smith created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55665  
 
 
  Allow promotion of individual matrix builds   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 matrix-project-plugin, promoted-builds-plugin  
 
 
Created: 
 2019-01-17 22:38  
 
 
Environment: 
 matrix-project 1.13  promoted-builds 3.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gabriel Smith  
 

  
 
 
 
 

 
 I would like to be able to promote individual sub-builds within a matrix configuration project. Currently, only the overall build of a matrix configuration can be promoted.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-55663) Extend the Jenkinsfile Runner user documentation

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55663  
 
 
  Extend the Jenkinsfile Runner user documentation   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Summary: 
 Extend the Jenkinsfile Runner  user  documentation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55663) Extend the Jenkinsfile Runner documentation

2019-01-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55663  
 
 
  Extend the Jenkinsfile Runner documentation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2019-01-17 22:36  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 It would be great to extend the documentation and to add the following info: 
 
brief overview of the archirecture 
clarify flavors of JFR (Vanilla and Custom War Packager) 
document usage of Java 8 and Java 11 images 
    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed

2019-01-17 Thread sylvain.lebeau...@z-battle.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sylvain LEBEAUPIN updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55618  
 
 
  When using spot instances, requests 3-4 nodes when one is needed   
 

  
 
 
 
 

 
Change By: 
 Sylvain LEBEAUPIN  
 
 
Attachment: 
 jenkins.ec2.142.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed

2019-01-17 Thread sylvain.lebeau...@z-battle.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sylvain LEBEAUPIN commented on  JENKINS-55618  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When using spot instances, requests 3-4 nodes when one is needed   
 

  
 
 
 
 

 
 I have exactly the same issue with the version 1.42 In my settings, I set only 1 executor (advanced section) of a spot instance. Work fine with the previous version 1.40.1. Since the update to 1.42: 
 
I view only 1 slave (good); 
several spot instances are started (~4-5 argh); 
jenkins logs display several provisioning every 10s (jenkins.ec2.142.txt) 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server

2019-01-17 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-55356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Some workflow jobs fail after restart on Java 11 server   
 

  
 
 
 
 

 
 Yes, there are no changes in any recent Pipeline plugin release I am aware of that would explain or fix this issue. I investigated a few weeks ago but was not able to create a reproduction case. The error message comes from workflow-durable-task-step. It would be interesting to check whether the directory mentioned in the error actually exists on the agent, or if it is missing, or exists but has a different name (perhaps a randomized suffix or `-` instead of `_` or something, which could be related to recent branch-api changes).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-17 Thread tobias.h...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Herrmann Hinz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55654  
 
 
  infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
Change By: 
 Tobias Herrmann Hinz  
 
 
Summary: 
 infinite redirect loop when auth provider is oidc  (after update to 2.160)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41196) Pluggable core component

2019-01-17 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as per Jesse Glick recommendation in https://github.com/jenkinsci/jenkins/pull/2754#issuecomment-453667192. We'll reopen when/if this works gets rebooted. Most of the related PRs now also need anyway to get conflict resolution and didn't receive changes since 1+ year.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41196  
 
 
  Pluggable core component   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-17 Thread eric.blackw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blackwell edited a comment on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 Yes, I am running a job that uses packer.io to build GCE images from a 'recipe' I maintain in a git repo. I eventually want to be able to use my script to build several different flavors of my 'golden image', and tag them all using the os_family.Then I can have This plugin always use the latest build automatically from that family. This way I am not constantly having to adjust which image jenkins uses for the slaves/agents. And I can just run my golden image builds, and know that jenkins will always pull the latest from the family specified if that makes sense? And, no templates is not what I am looking for.  [~zombiemoose]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-17 Thread eric.blackw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blackwell commented on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 Yes, I am running a job that uses packer.io to build GCE images from a 'recipe' I maintain in a git repo.  I eventually want to be able to use my script to build several different flavors of my 'golden image', and tag them all using the os_family. Then I can have This plugin always use the latest build automatically from that family. This way I am not constantly having to adjust which image jenkins uses for the slaves/agents. And I can just run my golden image builds, and know that jenkins will always pull the latest from the family specified if that makes sense?   And, no templates is not what I am looking for.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server

2019-01-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-55356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Some workflow jobs fail after restart on Java 11 server   
 

  
 
 
 
 

 
 It seems that workflow-support 3.0 and 3.1 did not address this. I still see the following report in the Windows agent on my Java 11 server when I safeRestart the Jenkins server during Pipeline execution: 

 
[INFO] ---
[INFO] Running InjectedTest
[INFO] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.181 s - in InjectedTest
[INFO] Running hudson.plugins.git.BranchTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.374 s - in hudson.plugins.git.BranchTest
[INFO] Running hudson.plugins.git.GitAPIBadInitTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.113 s - in hudson.plugins.git.GitAPIBadInitTest
[INFO] Running hudson.plugins.git.GitExceptionTest
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.534 s - in hudson.plugins.git.GitExceptionTest
[INFO] Running hudson.plugins.git.GitLockFailedExceptionTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in hudson.plugins.git.GitLockFailedExceptionTest
[INFO] Running hudson.plugins.git.GitObjectTest
[INFO] Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.297 s - in hudson.plugins.git.GitObjectTest
[INFO] Running hudson.plugins.git.GitToolResolverTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.028 s - in hudson.plugins.git.GitToolResolverTest
[INFO] Running hudson.plugins.git.GitToolTest
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.005 s - in hudson.plugins.git.GitToolTest
[INFO] Running hudson.plugins.git.IndexEntryTest
[INFO] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s - in hudson.plugins.git.IndexEntryTest
[INFO] Running hudson.plugins.git.RevisionTest
[INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in hudson.plugins.git.RevisionTest
[INFO] Running hudson.plugins.git.TagTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s - in hudson.plugins.git.TagTest
[INFO] Running org.jenkinsci.plugins.gitclient.CliGitAPIImplTest
missing workspace C:\J\T\workspace\it-client-pipeline-github_master on mark-pc3-ssh
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-55662) Type 'org/apache/commons/codec/binary/Base64' (current frame, stack[2]) is not assignable to 'org/apache/commons/codec/binary/BaseNCodec' Current Frame:

2019-01-17 Thread ajay.b5...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bob Aj created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55662  
 
 
  Type 'org/apache/commons/codec/binary/Base64' (current frame, stack[2]) is not assignable to 'org/apache/commons/codec/binary/BaseNCodec' Current Frame:   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Victor Martinez  
 
 
Components: 
 jenkinslint-plugin  
 
 
Created: 
 2019-01-17 21:44  
 
 
Environment: 
 Redhat  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Bob Aj  
 

  
 
 
 
 

 
 I am getting below error when compiling a maven job with Jenkins. How ever I am able to compile the same code manually(Not with Jenkins) with out any issues. Could you please suggest which Jenkins dependency plugin is required to fix this issue?       {{[ERROR] FATAL ERROR [INFO]  [INFO] Bad type on operand stack Exception Details: Location: org/apache/commons/codec/binary/Base64OutputStream.(Ljava/io/OutputStream;Z)V @11: invokespecial Reason: Type 'org/apache/commons/codec/binary/Base64' (current frame, stack[2]) is not assignable to 'org/apache/commons/codec/binary/BaseNCodec' Current Frame: bci: @11 flags: { flagThisUninit } locals: { uninitializedThis, 'java/io/OutputStream', integer } stack: { uninitializedThis, 'java/io/OutputStream', 'org/apache/commons/codec/binary/Base64', integer }}}  
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-55640) java.lang.OutOfMemoryError: GC overhead limit exceeded

2019-01-17 Thread issac1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Issac assigned an issue to Daniel Beck  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55640  
 
 
  java.lang.OutOfMemoryError: GC overhead limit exceeded   
 

  
 
 
 
 

 
Change By: 
 Daniel Issac  
 
 
Assignee: 
 Daniel Beck  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55640) java.lang.OutOfMemoryError: GC overhead limit exceeded

2019-01-17 Thread issac1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Issac updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55640  
 
 
  java.lang.OutOfMemoryError: GC overhead limit exceeded   
 

  
 
 
 
 

 
Change By: 
 Daniel Issac  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37632) Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely

2019-01-17 Thread d...@frascone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Frascone commented on  JENKINS-37632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely   
 

  
 
 
 
 

 
 Jeremy P: How did you find the hung thread and get that stack dump? I'm going to test my fix above over time, and I'll need to be able to dump threads when our server starts working strangely. (I'm going to put that PR code up live, as a test, since I have low confidence in the fix)   Thanks in advance!   -Dave  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37632) Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely

2019-01-17 Thread d...@frascone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Frascone commented on  JENKINS-37632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely   
 

  
 
 
 
 

 
 Shot in the dark: https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/pull/183  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37632) Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely

2019-01-17 Thread d...@frascone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Frascone commented on  JENKINS-37632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely   
 

  
 
 
 
 

 
 Relevant - this looks very similar to the plugin's implementation:   https://stackoverflow.com/questions/27968669/socket-timeout-not-working-inputstream-read-blocks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-30319) SSH - Ed25519 keys not supported

2019-01-17 Thread bguer...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benoit Guérout commented on  JENKINS-30319  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSH - Ed25519 keys not supported   
 

  
 
 
 
 

 
 Do you know if https://github.com/jenkinsci/trilead-ssh2/pull/13 is supposed to fix this ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37632) Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely

2019-01-17 Thread d...@frascone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Frascone commented on  JENKINS-37632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely   
 

  
 
 
 
 

 
 So, the timeouts are set to 6ms (60 seconds), in ApiClient.java here: 

 

HttpClientParams params = client.getParams();
params.setConnectionManagerTimeout(DEFAULT_TIMEOUT);
params.setSoTimeout(DEFAULT_TIMEOUT);
 

   I then added debug to the `send(HttpMethodBase req)` function, and the client's parameters contain 6 in params.getSoTimeout()   So, my question is: Is it being set correctly? And, if not in the apache commons Method Params (https://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/HttpMethodParams.html), where should the timeout(s) be set, when using `client.executeMethod()`?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55485) Declarative pipeline, lock() in stage options is executed before when clause

2019-01-17 Thread daniel.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 D Pasto commented on  JENKINS-55485  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Declarative pipeline, lock() in stage options is executed before when clause   
 

  
 
 
 
 

 
 I verified the workaround of adding an additional level of stage - I have a group stage with the when clause containing a group stage with the lock, containing the actual stages.  With this structure I'm able to use the when clause to disable deploy and test stages, and not get stuck waiting for a lock behind a long-running test. The workaround is conceptually easy, but adds a lot of boilerplate and makes the Jenkinsfile that much harder to read.  I'm now up to 10 levels of tabs in my Jenkinsfile and have a check-in with hundreds of lines of changes that is just indenting.  It's getting pretty ugly. This is exactly the mess the "beforeAgent" directive to the "when" clause prevents - we need a similar solution here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55660) Kubernetes Plugin Settings Wiped on Jenkins Restart

2019-01-17 Thread aabl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Blumberg closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closed @ Layer 8  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55660  
 
 
  Kubernetes Plugin Settings Wiped on Jenkins Restart   
 

  
 
 
 
 

 
Change By: 
 Aaron Blumberg  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55660) Kubernetes Plugin Settings Wiped on Jenkins Restart

2019-01-17 Thread aabl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Blumberg commented on  JENKINS-55660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes Plugin Settings Wiped on Jenkins Restart   
 

  
 
 
 
 

 
 Carlos Sanchez - Roger that, thanks Carlos. I do see the config in here. I'll close this ticket, this sounds like an 'us' issue if our jenkins isn't reading this config on startup.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54764) builds fail when using timeout step with the Pipeline Basic Steps Plugin

2019-01-17 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54764  
 
 
  builds fail when using timeout step with the Pipeline Basic Steps Plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52938) Timestamper plugin does not produce timestamps in BlueOcean UI

2019-01-17 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-52938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamper plugin does not produce timestamps in BlueOcean UI   
 

  
 
 
 
 

 
 It can be replicated in this environment Jenkins Core 2.159 BO 1.10.1 Timestamper 1.8.10 If you configure it as an option it would also fail 

 

pipeline {
  agent any
  options{
  timestamps()
  }
  stages {
stage("Stage 1") {
  steps {
sh "echo command"
  }
}
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45712) p4 credentials fail, can't write .p4tickets file

2019-01-17 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran commented on  JENKINS-45712  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: p4 credentials fail, can't write .p4tickets file   
 

  
 
 
 
 

 
 Hi Allen, we just started dockerizing Perforce build with docker host has /var/lib/docker mounted on different volume an a fast SAN storage here is our p4sync 

 

p4sync charset: 'none', credential: 'perforce-x', format: "${clientName}", populate: forceClean(have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource(depot)
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-17 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 jenkins  pipeline-triaged  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55661) Extend test connection functionality to account for server-side permissions

2019-01-17 Thread mark.sym...@weareact.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Symons created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55661  
 
 
  Extend test connection functionality to account for server-side permissions   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Steve Springett  
 
 
Components: 
 dependency-track-plugin  
 
 
Created: 
 2019-01-17 18:20  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mark Symons  
 

  
 
 
 
 

 
 Dependency-Track Plugin connection to Dependency-Track server is managed via "Configure System" and is provided with a Test Connection button. The test connection functionality should be enhanced to account for server-side permissions eg whether or not PROJECT_CREATION_UPLOAD permission exists when "Auto Create Projects" is checked in Jenkins.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
   

[JIRA] (JENKINS-55660) Kubernetes Plugin Settings Wiped on Jenkins Restart

2019-01-17 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez commented on  JENKINS-55660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes Plugin Settings Wiped on Jenkins Restart   
 

  
 
 
 
 

 
 the configuration is stored in config.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54945) Single agent and step(s) for multiple parallel steps

2019-01-17 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-54945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Single agent and step(s) for multiple parallel steps   
 

  
 
 
 
 

 
 Oh, sorry! Yes, that works right now with Declarative 1.3 or later.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55660) Kubernetes Plugin Settings Wiped on Jenkins Restart

2019-01-17 Thread aabl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Blumberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55660  
 
 
  Kubernetes Plugin Settings Wiped on Jenkins Restart   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-01-17 17:56  
 
 
Environment: 
 Docker plugin 1.1.5  Kubernetes plugin 1.14.3  Kubernetes Credentials Plugin 0.4.0  Jenkins 2.148  
 
 
Labels: 
 configuration  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Aaron Blumberg  
 

  
 
 
 
 

 
 The configuration for our Kubernetes plugin is only being contained in memory. A server restart results in a loss of configuration. No xml file can be found containing the configuration options (ex; envinject-plugin-configuration.xml). I am assuming that there is a file like this that must exist for these options to persist over restart. Clicking 'save' after configuring the plugin through Jenkins management does not generate such a file.  
 

  
 
 
 
 

 
 
 

 
 
  

[JIRA] (JENKINS-55307) Update HudsonPrivateSecurityRealm use of SecurityListener

2019-01-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-55307  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55307  
 
 
  Update HudsonPrivateSecurityRealm use of SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55305) Add user creation listener-methods to SecurityListener

2019-01-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-55305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55305  
 
 
  Add user creation listener-methods to SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id

2019-01-17 Thread michael.albergh...@keysight.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Alberghini commented on  JENKINS-55639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ec2-plugin only attempts to retrieve spot instance using old id   
 

  
 
 
 
 

 
 We also faced this problem on Jenkins 2.157 with ec2-plugin 1.42.  Switching our spot instances to regular did not fix the issue, but downgrading the plugin to 1.41 did  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54945) Single agent and step(s) for multiple parallel steps

2019-01-17 Thread brian.murr...@intel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-54945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Single agent and step(s) for multiple parallel steps   
 

  
 
 
 
 

 
 Is that a suggestion on a proposed configuration which would require code changes to support or are you suggesting that the above should actually work currently?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55611) Make EXECUTOR_NUMBER available for yaml definition

2019-01-17 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-55611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make EXECUTOR_NUMBER available for yaml definition   
 

  
 
 
 
 

 
 Carlos Sanchez - correct, we don't have the executor number until we're on the executor, so...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12623) Provide config to hide Jenkins behind Apache

2019-01-17 Thread robert.osowie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robet Osowiecki edited a comment on  JENKINS-12623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide config to hide Jenkins behind Apache   
 

  
 
 
 
 

 
 Adding "nocanon" option to ProxyPass solves problems with some URLs, see: JENKINS-55656 and https://bz.apache.org/bugzilla/show_bug.cgi?id=63084 Please be aware that this option may affect security:https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54764) builds fail when using timeout step with the Pipeline Basic Steps Plugin

2019-01-17 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54764  
 
 
  builds fail when using timeout step with the Pipeline Basic Steps Plugin   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-basic-steps-plugin  
 
 
Component/s: 
 workflow-durable-task-step-plugin  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54835) Pipeline stage view is showing all stages twice

2019-01-17 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54835  
 
 
  Pipeline stage view is showing all stages twice   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 pipeline-stage-view-plugin  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 pipeline-view-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54945) Single agent and step(s) for multiple parallel steps

2019-01-17 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-54945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Probably the right way to do this would be to do something like: 

 

stage('Test') {
  agent {
label 'foo'
  }
  stages {
stage('Prepare Agent') {
  steps {
echo "prepare node for test stages"
  }
   }
   stage('Parallel Tests') {
  parallel {
stage('Test 1') { ... }
stage('Test 2') { ... }
// etc
  }
}
  }
}
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54945  
 
 
  Single agent and step(s) for multiple parallel steps   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You 

[JIRA] (JENKINS-12623) Provide config to hide Jenkins behind Apache

2019-01-17 Thread robert.osowie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robet Osowiecki commented on  JENKINS-12623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide config to hide Jenkins behind Apache   
 

  
 
 
 
 

 
 Adding "nocanon" option to ProxyPass solves problems with some URLs, see: JENKINS-55656 and https://bz.apache.org/bugzilla/show_bug.cgi?id=63084  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55656) URLs to matrixProject subtasks don't work behind Apache ProxyPass

2019-01-17 Thread robert.osowie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robet Osowiecki updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55656  
 
 
  URLs to matrixProject subtasks don't work behind Apache ProxyPass   
 

  
 
 
 
 

 
 There's a solution in Apache: add "nocanon" option to ProxyPass. Changing Priority to "minor", please change to Fixed if you like.  
 

  
 
 
 
 

 
Change By: 
 Robet Osowiecki  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  1   2   3   >