[JIRA] (JENKINS-56065) Change handling of symlinks when scanning for files in warnings-ng-plugin

2019-02-15 Thread mike...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Barker commented on  JENKINS-56065  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Change handling of symlinks when scanning for files in warnings-ng-plugin   
 

  
 
 
 
 

 
 I think Job makes the most sense as it is the same place where the fileset is defined.  
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Kumar updated  JENKINS-56165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56165  
 
 
  CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
Change By: 
 Nicketa Kumar  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Kumar commented on  JENKINS-56165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
 My issue got resolved via  https://wiki.jenkins.io/display/JENKINS/Standard+Security+Setup. Thanks for checking.  
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Kumar updated  JENKINS-56165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56165  
 
 
  CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
Change By: 
 Nicketa Kumar  
 
 
Status: 
 Fixed but Unreleased Closed  
 
 
Resolution: 
 Fixed Done  
 

  
 
 
 
 

 
 
 

 
 
 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-48900) Show "Full Name" on Assign Roles page?

2019-02-15 Thread mrinaldut...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mrinal Dutta updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48900  
 
 
  Show "Full Name" on Assign Roles page?   
 

  
 
 
 
 

 
Change By: 
 Mrinal Dutta  
 
 
Comment: 
 how to get started on JIRA? like how should I resolve any issue or add feature ?  
 

  
 
 
 
 

 
 
 

 
 
 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-55955) Remove JAXB dependency from notification plugin

2019-02-15 Thread mrinaldut...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mrinal Dutta commented on  JENKINS-55955  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove JAXB dependency from notification plugin   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/notification-plugin/pull/36  please check the following merge and do as needed Martin d'AnjouOleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-55955) Remove JAXB dependency from notification plugin

2019-02-15 Thread mrinaldut...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mrinal Dutta updated  JENKINS-55955  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55955  
 
 
  Remove JAXB dependency from notification plugin   
 

  
 
 
 
 

 
Change By: 
 Mrinal Dutta  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-53188) New jobs created from Blue Ocean are tied with username that created them

2019-02-15 Thread gmo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-53188  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New jobs created from Blue Ocean are tied with username that created them   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/blueocean-plugin/pull/1915  
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Kumar edited a comment on  JENKINS-56165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
 [Cloned from|http://example.com]This issue clones to  I followed what is listed over https://issues.jenkins-ci.org/browse/JENKINS-19010 . Post to that, I was gone to [http://localhost:8080,|http://localhost:8080,/] this gave me below error:!image-2019-02-16-10-48-07-413.png!When I try to login, it give me following error: !image-2019-02-16-10-49-28-724.png! I'm STRUCK. I don't know what to do now. I googled and nothing is helpful to me. Please help.   
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad edited a comment on  JENKINS-56165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
 [Cloned from|http://example.com] This issue clones to https://issues.jenkins-ci.org/browse/JENKINS-19010  
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56165  
 
 
  CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
 This issue clones to https://issues.jenkins-ci.org/browse/JENKINS-19010  
 

  
 
 
 
 

 
Change By: 
 Nicketa Prasad  
 
 
Environment: 
 Ubuntu 12.04 Windows 7  
 

  
 
 
 
 

 
 
 

 
 
 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-19010) hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad commented on  JENKINS-19010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 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-56165) CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56165  
 
 
  CLONE - hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 current  
 
 
Assignee: 
 deep jain  
 
 
Attachments: 
 image-2019-02-16-09-17-44-896.png, image-2019-02-16-10-39-54-425.png  
 
 
Components: 
 _unsorted, violations-plugin  
 
 
Created: 
 2019-02-16 05:10  
 
 
Due Date: 
2013-08-04 
 
 
Environment: 
 Ubuntu 12.04  
 
 
Fix Versions: 
 current  
 
 
Labels: 
 exception jenkins security  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Nicketa Prasad  
 

  
 
 
 
 

 
 Without assign any permission to anonymous user i clicked on save button now i try to run jenkins i can see only bug like  hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission  Please anyone 

[JIRA] (JENKINS-19010) hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-19010  
 
 
  hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
Change By: 
 Nicketa Prasad  
 
 
Attachment: 
 image-2019-02-16-10-39-54-425.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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection

2019-02-15 Thread subhransubala.rout...@wipro.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Subhransubala Routray commented on  JENKINS-55722  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection   
 

  
 
 
 
 

 
 Alex- We are able to manually connect thru Putty or winscp client. but unable to connect thru Jenkins. Pls advise the next steps to troubleshoot and solve the issue. This is not working across. What debug need to be enabled and how to troubleshoot and solve this issue. Customer really wants progress from us and we r unable to move forward. Pls advise  
 

  
 
 
 
 

 
 
 

 
 
 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-19010) hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-19010  
 
 
  hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
Change By: 
 Nicketa Prasad  
 
 
Attachment: 
 image-2019-02-16-09-17-44-896.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-19010) hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

2019-02-15 Thread nicks9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicketa Prasad commented on  JENKINS-19010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission   
 

  
 
 
 
 

 
 Thanks for the resolution. That worked. But what to do after that. It is not letting me login. If I do so, it gives me the error:    PLEASE HELP  
 

  
 
 
 
 

 
 
 

 
 
 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-56104) Jenkins Github SCM building wrong branches

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-56104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Github SCM building wrong branches   
 

  
 
 
 
 

 
 The git plugin output is already quite verbose, in large measure so that diagnosis of failures is a little easier. You could try increasing the logging level of the git plugin and the git client plugin in case something is written to the system log file which might show a difference between the cases where it works and the cases where it fails.  
 

  
 
 
 
 

 
 
 

 
 
 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-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Roger Braunstein  
 

  
 
 
 
 

 
 Every time the uploading to HockeyApp build step runs, it seems to fully upload the app but then terminate from an exception, possibly an unexpected HTTP request or response.{{Uploading to HockeyApp... }}  {{ .apk }}  {{ Proxy Settings: For the URL  [  https://rink.hockeyapp.net/api/2/apps/ ] /app_versions/99.0.0]}}{{ Found proxy configuration [false]}}{{ HockeyApp Upload Speed: 82.27Mbps }}  {{ org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0 }}  {{ at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) }}  {{ at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) }}  {{ at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) }}  {{ at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) }}  {{ at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) }}  {{ at java.io.InputStreamReader.read(InputStreamReader.java:184) }}  {{ at java.io.Reader.read(Reader.java:140) }}  {{ at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537) }}  {{ at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516) }}  {{ at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493) }}  {{ at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441) }}  {{ at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084) }}  {{ at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396) }}  {{ at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281) }}  {{ at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) }}  {{ at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) }}  {{ at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) }}  {{ at hudson.model.Build$BuildExecution.post2(Build.java:186) }}  {{ at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) }}  {{ at hudson.model.Run.execute(Run.java:1841) }}  {{ at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) }}  {{ at hudson.model.ResourceController.execute(ResourceController.java:97) }}  {{ at hudson.model.Executor.run(Executor.java:429) }}  {{ Build step 'Upload to HockeyApp' marked build as failure    }}     I am uploading using an existing app ID and version provided by build parameter. I have tried this with two different API keys although authentication does not seem to be at issue. No proxy. Fails regardless of other settings in the build step.  
 

  
 
 
 
 


[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Roger Braunstein  
 

  
 
 
 
 

 
 Every time the uploading to HockeyApp build step runs, it seems to fully upload the app but then terminate from an exception, possibly an unexpected HTTP request or response. {{ Uploading to HockeyApp... }}  {{  .apk }}  {{  Proxy Settings: For the URL [https://rink.hockeyapp.net/api/2/apps/]/app_versions/99.0.0]  }}{{Found proxy configuration [false]  }}{{HockeyApp Upload Speed: 82.27Mbps }}  {{  org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0 }}  {{  at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) }}  {{  at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) }}  {{  at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) }}  {{  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) }}  {{  at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) }}  {{  at java.io.InputStreamReader.read(InputStreamReader.java:184) }}  {{  at java.io.Reader.read(Reader.java:140) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441) }}  {{  at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084) }}  {{  at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396) }}  {{  at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281) }}  {{  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) }}  {{  at hudson.model.Build$BuildExecution.post2(Build.java:186) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) }}  {{  at hudson.model.Run.execute(Run.java:1841) }}  {{  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) }}  {{  at hudson.model.ResourceController.execute(ResourceController.java:97) }}  {{  at hudson.model.Executor.run(Executor.java:429) }}  {{  Build step 'Upload to HockeyApp' marked build as failure  }} I am uploading using an existing app ID and version provided by build parameter. I have tried this with two different API keys although authentication does not seem to be at issue. No proxy. Fails regardless of other settings in the build step.  
 

  
 
 
 
 
 

[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Roger Braunstein  
 

  
 
 
 
 

 
 Every time the uploading to HockeyApp build step runs, it seems to fully upload the app but then terminate from an exception, possibly an unexpected HTTP request or response.   {{Uploading to HockeyApp... }}  {{  .apk }}  {{  Proxy Settings: For the URL  [ https://rink.hockeyapp.net/api/2/apps/ ] /app_versions/99.0.0]  }}{{Found proxy configuration [false]  }}{{HockeyApp Upload Speed: 82.27Mbps }}  {{  org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0 }}  {{  at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) }}  {{  at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) }}  {{  at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) }}  {{  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) }}  {{  at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) }}  {{  at java.io.InputStreamReader.read(InputStreamReader.java:184) }}  {{  at java.io.Reader.read(Reader.java:140) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441) }}  {{  at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084) }}  {{  at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396) }}  {{  at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281) }}  {{  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) }}  {{  at hudson.model.Build$BuildExecution.post2(Build.java:186) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) }}  {{  at hudson.model.Run.execute(Run.java:1841) }}  {{  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) }}  {{  at hudson.model.ResourceController.execute(ResourceController.java:97) }}  {{  at hudson.model.Executor.run(Executor.java:429) }}  {{  Build step 'Upload to HockeyApp' marked build as failure }}  {{   }}   I am uploading using an existing app ID and version provided by build parameter. I have tried this with two different API keys although authentication does not seem to be at issue. No proxy. Fails regardless of other settings in the build step.  
 

  
 
 
 
 
  

[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Roger Braunstein  
 

  
 
 
 
 

 
 {quote}{{ Every time the  upload  uploading  to  Hockeyapp  HockeyApp build  step runs, it  appears  seems  to  fully  upload the  file successfully  app  but then  raises  terminate from  an exception :}} , possibly an unexpected HTTP request or response.    {{ Uploading to HockeyApp...}}{{ .apk}}{{ Proxy Settings: For the URL [https://rink.hockeyapp.net/api/2/apps/]/app_versions/99.0.0] }}{{ Found proxy configuration [false] }}{{ HockeyApp Upload Speed: 82.27Mbps}}{{ org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0}}{{ at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178)}}{{ at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135)}}{{ at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)}}{{ at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)}}{{ at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)}}{{ at java.io.InputStreamReader.read(InputStreamReader.java:184)}}{{ at java.io.Reader.read(Reader.java:140)}}{{ at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537)}}{{ at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516)}}{{ at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493)}}{{ at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441)}}{{ at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084)}}{{ at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396)}}{{ at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281)}}{{ at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)}}{{ at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)}}{{ at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)}}{{ at hudson.model.Build$BuildExecution.post2(Build.java:186)}}{{ at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)}}{{ at hudson.model.Run.execute(Run.java:1841)}}{{ at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)}}{{ at hudson.model.ResourceController.execute(ResourceController.java:97)}}{{ at hudson.model.Executor.run(Executor.java:429)}}{{ Build step 'Upload to HockeyApp' marked build as failure}}{{  }} {quote}    I am uploading using an existing app ID and version provided by build parameter. I have tried this with two different API keys although authentication does not seem to be at issue. No proxy. Fails regardless of other settings in the build step.  
 

  
 
 
 
 


[JIRA] (JENKINS-38860) Git plugin using local config to update submodules

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38860  
 
 
  Git plugin using local config to update submodules   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Roger Braunstein  
 

  
 
 
 
 

 
 {quote}{{ Every time the upload to Hockeyapp step runs, it appears to upload the file successfully but then raises an exception: }}  {{ Uploading to HockeyApp... }}  {{ .apk }}  {{ Proxy Settings: For the URL  [  https://rink.hockeyapp.net/api/2/apps/ ] /app_versions/99.0.0]}}{{   Found proxy configuration [false]}}{{ HockeyApp Upload Speed: 82.27Mbps }}  {{ org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0 }}  {{  at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) }}  {{  at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) }}  {{  at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) }}  {{  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) }}  {{  at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) }}  {{  at java.io.InputStreamReader.read(InputStreamReader.java:184) }}  {{  at java.io.Reader.read(Reader.java:140) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537) }}  {{  at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493) }}  {{  at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441) }}  {{  at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084) }}  {{  at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396) }}  {{  at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281) }}  {{  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) }}  {{  at hudson.model.Build$BuildExecution.post2(Build.java:186) }}  {{  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) }}  {{  at hudson.model.Run.execute(Run.java:1841) }}  {{  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) }}  {{  at hudson.model.ResourceController.execute(ResourceController.java:97) }}  {{  at hudson.model.Executor.run(Executor.java:429) }}  {{ Build step 'Upload to HockeyApp' marked build as failure }}  {{   }}  {quote} I am uploading using an existing app ID and version provided by build parameter. I have tried this with two different API keys although authentication does not seem to be at issue. No proxy. Fails regardless of other settings in the build step.  
 

  
 
 
 
 


[JIRA] (JENKINS-56104) Jenkins Github SCM building wrong branches

2019-02-15 Thread adam.c...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Chou commented on  JENKINS-56104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Github SCM building wrong branches   
 

  
 
 
 
 

 
 Are there any suggestions on how I can get more debugging enabled to troubleshoot/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-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-15 Thread ro...@eastsidegamestudio.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Braunstein created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mez Pahlan  
 
 
Components: 
 hockeyapp-plugin  
 
 
Created: 
 2019-02-16 02:18  
 
 
Environment: 
 Jenkins 2.164, Java 1.8.0_202, Mac OS 10.13.6, hockeyapp plugin 1.4.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Roger Braunstein  
 

  
 
 
 
 

 
 Every time the upload to Hockeyapp step runs, it appears to upload the file successfully but then raises an exception: Uploading to HockeyApp... .apk Proxy Settings: For the URL https://rink.hockeyapp.net/api/2/apps//app_versions/99.0.0]  Found proxy configuration [false]  HockeyApp Upload Speed: 82.27Mbps org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 1229; received: 0 at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) at java.io.InputStreamReader.read(InputStreamReader.java:184) at java.io.Reader.read(Reader.java:140) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2537) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2516) at org.apache.commons.io.IOUtils.copy(IOUtils.java:2493) at org.apache.commons.io.IOUtils.copy(IOUtils.java:2441) at org.apache.commons.io.IOUtils.toString(IOUtils.java:1084) at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:396) at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:281) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at 

[JIRA] (JENKINS-56104) Jenkins Github SCM building wrong branches

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56104  
 
 
  Jenkins Github SCM building wrong branches   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-56104) Jenkins Github SCM building wrong branches

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-56104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Github SCM building wrong branches   
 

  
 
 
 
 

 
 I don't know how to duplicate the problem. Thanks for the good details in the report. I hope you'll discover additional details as you explore further.  
 

  
 
 
 
 

 
 
 

 
 
 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-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56150  
 
 
  git plugin with repo that has empty .gitmodules file NPE during submodule update   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-56150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git plugin with repo that has empty .gitmodules file NPE during submodule update   
 

  
 
 
 
 

 
 Thanks for the report. I'm unable to duplicate the problem with the simple minded test case I attempted. See https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-56150/Jenkinsfile for my attempt. Any other details on the conditions which cause the NPE or the stack trace from the NPE?  
 

  
 
 
 
 

 
 
 

 
 
 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version

2019-02-15 Thread christopher.fen...@sap.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Fenner commented on  JENKINS-51021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version   
 

  
 
 
 
 

 
 I have the same issue, the plugin doesn't work with my enterprise instance in v1.0.4. However, v1.0.2 is working fine.  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread pe...@psftw.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Salvatore commented on  JENKINS-56004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
 Jesse Glick The log record ordering issue is an artifact of our logging system, nothing to do with Jenkins. The effect is that some records in the attached artifacts.log may not be in exactly the same order as what Jenkins emitted.  
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam commented on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Hi Wadeck Follonier, here is the output from the script console.  Used the same job as all the items captured above for consistency. [true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false]  
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam edited a comment on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Hi [~wfollonier], here is the output from the script console.  Used the same job as all the items captured above for consistency. Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required. [true, C: \ ][true, c:\jenkins][true, c:\jenkins\workspace, false][true, c:\jenkins\workspace\Au, false, false][true, c:\jenkins\workspace\Au, false, false]  
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam edited a comment on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Hi [~wfollonier], here is the output from the script console.  Used the same job as all the items captured above for consistency.Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required.[true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false] For stack traces, I dont' see anything on the console when I attempt to access the project (for it's artifacts), and when I access the workspace the console displays:Feb 15, 2019 12:03:25 PM hudson.model.DirectoryBrowserSupport serveFileWARNING: Trying to access a file outside of the directory, target:Let me know which console and/or debug you're after for more detail.  
 

  
 
 
 
 

 
 
 

 
 
 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-56162) p4 plugin doesn't add '/...' to older p4sync calls.

2019-02-15 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56162  
 
 
  p4 plugin doesn't add '/...' to older p4sync calls.   
 

  
 
 
 
 

 
Change By: 
 Matthew Hall  
 

  
 
 
 
 

 
 Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call:{code:java} p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test',   format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [   enable: false, minbytes: '1024', minfiles: '1',   path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true   ]  ){code}We get in the resultant client:{noformat}View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test{noformat}Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767If we revert plugin to older, and then delete generated client, we see the difference in c.txt output. We also see our view has changed : {noformat}View: //d-alviso/svrtools/mainline/sme-tools/jenkins_test/... //build-repo01-jenkins-test/...{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam edited a comment on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Hi [~wfollonier], here is the output from the script console.  Used the same job as all the items captured above for consistency. I'm currently using version 2.164. Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required.[true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false]For stack traces, I dont' see anything on the console when I attempt to access the project (for it's artifacts), and when I access the workspace the console displays:Feb 15, 2019 12:03:25 PM hudson.model.DirectoryBrowserSupport serveFileWARNING: Trying to access a file outside of the directory, target:Let me know which console and/or debug you're after for more detail.  
 

  
 
 
 
 

 
 
 

 
 
 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-56162) p4 plugin doesn't add '/...' to older p4sync calls.

2019-02-15 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56162  
 
 
  p4 plugin doesn't add '/...' to older p4sync calls.   
 

  
 
 
 
 

 
Change By: 
 Matthew Hall  
 
 
Attachment: 
 c.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-56162) p4 plugin doesn't add '/...' to older p4sync calls.

2019-02-15 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56162  
 
 
  p4 plugin doesn't add '/...' to older p4sync calls.   
 

  
 
 
 
 

 
Change By: 
 Matthew Hall  
 

  
 
 
 
 

 
 Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call:{code:java} p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test',   format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [   enable: false, minbytes: '1024', minfiles: '1',   path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true   ]  ){code}We get in the resultant client:{noformat}View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test{noformat}Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767 If we revert plugin to older, and then delete generated client, we see the difference in c.txt output.  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-56162) p4 plugin doesn't add '/...' to older p4sync calls.

2019-02-15 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56162  
 
 
  p4 plugin doesn't add '/...' to older p4sync calls.   
 

  
 
 
 
 

 
Change By: 
 Matthew Hall  
 

  
 
 
 
 

 
 Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients. For p4sync call: {code:java}  p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test',   format: user + '-${NODE_NAME}-${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [   enable: false, minbytes: '1024', minfiles: '1',   path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true   ]  ) {code}   We get in the resultant client: {noformat} View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test {noformat}   Which then fails to sync/checkout anything. The log output is attached as 'a.txt' Behaviour of this seems changed in :https://swarm.workshop.perforce.com/changes/24767  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-56151) Include more tags in the xml job to job dsl plugin

2019-02-15 Thread alan....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alan Quintiliano commented on  JENKINS-56151  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include more tags in the xml job to job dsl plugin   
 

  
 
 
 
 

 
 Thanks for using the plugin Do you know if Job DSL Plugin (https://wiki.jenkins.io/display/JENKINS/Job+DSL+Plugin) supports these tags? I need it to support these tags before supporting them  
 

  
 
 
 
 

 
 
 

 
 
 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-56162) p4 plugin doesn't add '/...' to older p4sync calls.

2019-02-15 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56162  
 
 
  p4 plugin doesn't add '/...' to older p4sync calls.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 a.txt  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2019-02-15 21:49  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matthew Hall  
 

  
 
 
 
 

 
 Updating our p4 plugin from 1.8.12 to 1.9.6, we find that jobs using the older p4sync, where the trailing '/...' was optional, fails to write out useful/working p4 clients.  For p4sync call:  p4sync(charset: 'none', credential: credential, depotPath: '//depot/svrtools/mainline/sme-tools/jenkins_test', format: user + '${NODE_NAME}${JOB_NAME}', populate: [ $class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4' ], pin: '', quiet: true, replace: true ] ) We get in the resultant client: View: //depot/svrtools/mainline/sme-tools/jenkins_test //build-repo01-jenkins-test/jenkins_test Which then fails to sync/checkout anything.  The log output is attached as 'a.txt'  Behaviour of this seems changed in : https://swarm.workshop.perforce.com/changes/24767  
 

  
 
 
 
 

 
 
 

 
   

[JIRA] (JENKINS-48296) Multibranch pipeline - ignore commits from certain user

2019-02-15 Thread drdam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chirs damour commented on  JENKINS-48296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch pipeline - ignore commits from certain user   
 

  
 
 
 
 

 
 to work around this i created a plugin that supported ANDing and ORing sub strategies.  I submitted a PR for this to https://github.com/jenkinsci/basic-branch-build-strategies-plugin/pull/3  
 

  
 
 
 
 

 
 
 

 
 
 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-55974) "No valid crumb was included in the request" when running behind nginx (since recent update)

2019-02-15 Thread christian.ci...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ciach updated  JENKINS-55974  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55974  
 
 
  "No valid crumb was included in the request" when running behind nginx (since recent update)   
 

  
 
 
 
 

 
Change By: 
 Christian Ciach  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 1.5  
 

  
 
 
 
 

 
 
 

 
 
 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-55974) "No valid crumb was included in the request" when running behind nginx (since recent update)

2019-02-15 Thread christian.ci...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ciach updated  JENKINS-55974  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is a duplicate of JENKINS-55698. The release of kerberos sso 1.5 fixed this issue for us.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55974  
 
 
  "No valid crumb was included in the request" when running behind nginx (since recent update)   
 

  
 
 
 
 

 
Change By: 
 Christian Ciach  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
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-47796) Allow to show full message for skipped test cases.

2019-02-15 Thread zachary.dipasqu...@collins.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary DiPasquale commented on  JENKINS-47796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow to show full message for skipped test cases.   
 

  
 
 
 
 

 
 Any updates on this Issue? According to this https://github.com/junit-team/junit5/blob/master/platform-tests/src/test/resources/jenkins-junit.xsd Junit does not use the message field in the skipped element. It would be helpful for us if Jenkins displayed the text between the skipped tags.   
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam commented on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 For thoroughness, I restarted the instance removing the -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true directive from the startup, and ran the script code above: [true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false]  
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread jeremy....@sjrb.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Kam commented on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Daniel Beck Correct, both the HTTP 403 and the console end with no information after "target:".  
 

  
 
 
 
 

 
 
 

 
 
 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-02-15 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey started work on  JENKINS-55667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Austin Dewey  
 
 
Status: 
 Open In 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-35176) "Tag this build" link repeated in Pipeline job with multiple svn step

2019-02-15 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35176  
 
 
  "Tag this build" link repeated in Pipeline job with multiple svn step   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-scm-step-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-47430) SandboxResolvingClassLoader uses inefficient caching, imposes a classloading bottleneck

2019-02-15 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-47430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SandboxResolvingClassLoader uses inefficient caching, imposes a classloading bottleneck   
 

  
 
 
 
 

 
 PR is stalled and would need to be updated to resolve merge conflicts. Would probably need some additional testing at that point as well to understand the impact.  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-56004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
 Peter Salvatore not sure what that means. Maybe something related to the logging system used in CloudBees Core. If so, please report it through vendor channels, so this issue can be focused on the inappropriate AccessDeniedException2.  
 

  
 
 
 
 

 
 
 

 
 
 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-47430) SandboxResolvingClassLoader uses inefficient caching, imposes a classloading bottleneck

2019-02-15 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum stopped work on  JENKINS-47430  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

2019-02-15 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-56114  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)   
 

  
 
 
 
 

 
 Jeremy Kam To clarify, in the warning getting logged, it ends after the colon? CC Jim Klimov who reported something similar on IRC, also with the message ending at :  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread pe...@psftw.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Salvatore commented on  JENKINS-56004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
 FWIW, I also just noticed that the traceback log output is not guaranteed to be in-order either (for a given timestamp)...  
 

  
 
 
 
 

 
 
 

 
 
 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-56146) Unable to connect to REST service

2019-02-15 Thread luba_pyatigorsk...@globetax.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luba Pyat commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 Thanks! Yes, Jenkins is on Windows. I was able to bring up JIRA page in the browser  from Jenkins Master machine. Worked fine.. Radek Antoniuk  
 

  
 
 
 
 

 
 
 

 
 
 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-55707) FindBugs/SpotBugs messages starting with TEST: Unknown bug pattern

2019-02-15 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55707  
 
 
  FindBugs/SpotBugs messages starting with TEST: Unknown bug pattern   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Summary: 
 Upgrade fb-contrib FindBugs/SpotBugs  messages  to latest version  starting with TEST: Unknown bug pattern  
 

  
 
 
 
 

 
 
 

 
 
 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-55707) FindBugs/SpotBugs messages starting with TEST: Unknown bug pattern

2019-02-15 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-55707  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55707  
 
 
  FindBugs/SpotBugs messages starting with TEST: Unknown bug pattern   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
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 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-56154) PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-56154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;   
 

  
 
 
 
 

 
 This is a valid JEP-200 rejection, logger class instances should not be serialized to the disk. The plugin needs to be updated.  
 

  
 
 
 
 

 
 
 

 
 
 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-56154) PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to PTC ALM  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56154  
 
 
  PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev PTC ALM  
 

  
 
 
 
 

 
 
 

 
 
 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-56158) package v. 2.150.3 is absent

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-56158  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: package v. 2.150.3 is absent   
 

  
 
 
 
 

 
 AFAIK Olivier Vernin is working on the Jenkins Infrastructure fix for 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-56158) package v. 2.150.3 is absent

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-56156) It's not possible to trigger a build via webhook push when there is no new commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56156  
 
 
  It's not possible to trigger a build via webhook push when there is no new commit   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 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-56156) It's not possible to trigger a build via webhook push when there is no new commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-56156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: It's not possible to trigger a build via webhook push when there is no new commit   
 

  
 
 
 
 

 
 The plugin assumes that once a SHA1 is built there is not significant benefit to build it again.  
 

  
 
 
 
 

 
 
 

 
 
 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-56156) It's not possible to trigger a build via webhook push when there is no new commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56156  
 
 
  It's not possible to trigger a build via webhook push when there is no new commit   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-56004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
 The critical part of the stack is what was snipped out: the fact CredentialsAwsGlobalConfiguration.getCredentials is checking ADMINISTER.  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56004  
 
 
  Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 aws-global-configuration-plugin  
 
 
Component/s: 
 artifact-manager-s3-plugin  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-56004) Overall/Administrator required to view s3 artifacts?

2019-02-15 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56004  
 
 
  Overall/Administrator required to view s3 artifacts?   
 

  
 
 
 
 

 
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-35176) "Tag this build" link repeated in Pipeline job with multiple svn step

2019-02-15 Thread michael.kostu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Kostukov edited a comment on  JENKINS-35176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Tag this build" link repeated in Pipeline job with multiple svn step   
 

  
 
 
 
 

 
 The issue is still present in Jenkins  2.150.3. When using scripted pipeline, each "checkout(changelog: false, scm: [$class: 'SubversionSCM'..." results in duplicated "Tag this build" links under the build: !image-2019-02-15-12-42-31-236.png!  P.S. *This is a separate issue from* "Tag this build" appearing twice (which is also an unresolved bug). In addition to that, each svn checkout duplicates the duplicated links :) In the image above, I have 4 checkouts - which result in 8 links (while there should be just 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-35176) "Tag this build" link repeated in Pipeline job with multiple svn step

2019-02-15 Thread michael.kostu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Kostukov edited a comment on  JENKINS-35176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Tag this build" link repeated in Pipeline job with multiple svn step   
 

  
 
 
 
 

 
 The issue is still present in Jenkins  2.150.3. When using scripted pipeline, each "checkout(changelog: false, scm: [$class: 'SubversionSCM'..." results in duplicated "Tag this build" links under the build: !image-2019-02-15-12- 41 42 - 23 31 - 114 236 .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-56146) Unable to connect to REST service

2019-02-15 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radek Antoniuk commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 Are you running your Jenkins Master on Windows? If yes, check if you can load JIRA page in the browser from that machine that is running Jenkins Master.  
 

  
 
 
 
 

 
 
 

 
 
 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-35176) "Tag this build" link repeated in Pipeline job with multiple svn step

2019-02-15 Thread michael.kostu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Kostukov reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The issue is still present in Jenkins  2.150.3.   When using scripted pipeline, each "checkout(changelog: false, scm: [$class: 'SubversionSCM'..." results in duplicated "Tag this build" links under the build:     
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35176  
 
 
  "Tag this build" link repeated in Pipeline job with multiple svn step   
 

  
 
 
 
 

 
Change By: 
 Michael Kostukov  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread ivan.nieto.so...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Nieto commented on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
     Thanks a lot Evgeny Shepelyuk  
 

  
 
 
 
 

 
 
 

 
 
 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread eshepel...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evgeny Shepelyuk edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 [~ivannieto] this is not an issue but rather lack of documentation.  You can later configure SSH for fetching your code but not from this screen . Since , because  this  credentilas  credentials  are used to scan Bitbucket via REST API, so  on e  one  is  forecd  forced  to use login / password  in this case  authentication . Go to configuration of multibranch pipeline and setup checkout policy via SSH. !image-2019-02-15-18-41-45-586.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-55096) can not override jnlp container

2019-02-15 Thread syaramad...@scrippsnetworks.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada edited a comment on  JENKINS-55096  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: can not override jnlp container   
 

  
 
 
 
 

 
 I tried with custom image didn't work so given jenkins-jnlp official image even didn't work  using this on scripted pipelinenode('eks-cluster') { stage('Check jnlp') { sh 'rm -rf *'  
 

  
 
 
 
 

 
 
 

 
 
 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-55096) can not override jnlp container

2019-02-15 Thread syaramad...@scrippsnetworks.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada commented on  JENKINS-55096  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: can not override jnlp container   
 

  
 
 
 
 

 
 I tried with custom image didn't work so given jenkins-jnlp official image even didn't work  
 

  
 
 
 
 

 
 
 

 
 
 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread eshepel...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evgeny Shepelyuk edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 [~ivannieto] this is not an issue but rather lack of documentation. You can later configure SSH for fetching your code but not from this screen. Since this credentilas are used to scan Bitbucket via REST API, so on e is forecd to use login / password in this case. !image-2019-02-15-18-41-45-586.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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread eshepel...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evgeny Shepelyuk commented on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 Ivan Nieto this is not an issue but rather lack of documentation.  You can later configure SSH for fetching your code but not from this screen. Since this credentilas are used to scan Bitbucket via REST API, so on e is forecd to use login / password in this 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-55096) can not override jnlp container

2019-02-15 Thread syaramad...@scrippsnetworks.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada commented on  JENKINS-55096  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: can not override jnlp container   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 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-55096) can not override jnlp container

2019-02-15 Thread syaramad...@scrippsnetworks.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55096  
 
 
  can not override jnlp container   
 

  
 
 
 
 

 
Change By: 
 suryatej yaramada  
 
 
Attachment: 
 Screenshot from 2019-02-15 11-39-39.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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread ivan.nieto.so...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Nieto edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 This is essential, any updates?  I can replicate the issue as well.  :|  
 

  
 
 
 
 

 
 
 

 
 
 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-55096) can not override jnlp container

2019-02-15 Thread syaramad...@scrippsnetworks.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada commented on  JENKINS-55096  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: can not override jnlp container   
 

  
 
 
 
 

 
 I am facing the same issue  here are logs  Error in provisioning; agent=KubernetesSlave name: eks-cluster-zjkg8, template=PodTemplate{inheritFrom='', name='eks-cluster', namespace='default', slaveConnectTimeout=30, label='eks-cluster', nodeSelector='', nodeUsageMode=NORMAL, workspaceVolume=EmptyDirWorkspaceVolume [memory=false], volumes=[HostPathVolume [mountPath=/var/run/docker.sock, hostPath=/var/run/docker.sock]], containers=[ContainerTemplate {name='jnlp', image='jenkins/jnlp-slave:alpine', alwaysPullImage=true, workingDir='/home/jenkins', command='/bin/sh -c', args='cat', ttyEnabled=true, resourceRequestCpu='', resourceRequestMemory='', resourceLimitCpu='', resourceLimitMemory='', livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@1c48445b} ], yaml=} java.lang.IllegalStateException: Agent is not connected after 30 seconds, status: Running at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:224) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)  
 

  
 
 
 
 

 
 
 

 
 
 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-02-15 Thread ivan.nieto.so...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Nieto commented on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 This is essential, any updates? :|  
 

  
 
 
 
 

 
 
 

 
 
 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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56161  
 
 
  EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 Deserialisation errors seen with class {{hudson.EnvVars}}:{noformat} java.io.InvalidClassException: hudson.EnvVars; local class incompatible: stream classdesc serialVersionUID = -234198271843838088, local class serialVersionUID = 4320331661987259022{noformat}   {{hudson.EnvVars}} is serialisable, but doesn't have a {{serialVersionUID.}} The generated one has changed between v2.138 (-234198271843838088) & v2.150 (4320331661987259022) causing these deserialisation errors  when CJOC runs remote operations on .This is to ensure the compatibility with  a  master at  derived tool and as it's good practise to have  a  different version  static {{serialVersionUID}}, we should add 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-56146) Unable to connect to REST service

2019-02-15 Thread luba_pyatigorsk...@globetax.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luba Pyat commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 Unfortunately I am new to Jenkins. I  tried to find the ways to connect via curl to the JIRA URL API endpoint from Jenkins Master SSH console unsuccessfully. I could not even find Jenkins Master SSH console! The pointers that I found not really helpful. Can you please give me more info? Any help is much appreciated! THANKS! Radek Antoniuk  
 

  
 
 
 
 

 
 
 

 
 
 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-56158) package v. 2.150.3 is absent

2019-02-15 Thread uwe.hani...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uwe Hanisch commented on  JENKINS-56158  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: package v. 2.150.3 is absent   
 

  
 
 
 
 

 
 2.150.3 LTS version is neither available for  
 
openSUSE 
 
https://pkg.jenkins.io/opensuse-stable/ 
  
RedHat/CentOS 
 
https://pkg.jenkins.io/redhat-stable/ 
  
  
 

  
 
 
 
 

 
 
 

 
 
 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-56158) package v. 2.150.3 is absent

2019-02-15 Thread uwe.hani...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uwe Hanisch updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Uwe Hanisch  
 
 
Environment: 
 Ubuntu 16.04 CentOS7  OpenSuse  openSUSE  
 

  
 
 
 
 

 
 
 

 
 
 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-56158) package v. 2.150.3 is absent

2019-02-15 Thread uwe.hani...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uwe Hanisch updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Uwe Hanisch  
 
 
Environment: 
 Ubuntu 16.04 CentOS7  OpenSuse  
 

  
 
 
 
 

 
 
 

 
 
 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-56158) package v. 2.150.3 is absent

2019-02-15 Thread uwe.hani...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uwe Hanisch updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Uwe Hanisch  
 
 
Priority: 
 Minor 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-56158) package v. 2.150.3 is absent

2019-02-15 Thread uwe.hani...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Uwe Hanisch updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Uwe Hanisch  
 
 
Environment: 
 Ubuntu 16.04  CentOS7  
 

  
 
 
 
 

 
 
 

 
 
 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-56146) Unable to connect to REST service

2019-02-15 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radek Antoniuk commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 What I meant by "open" is that if you can connect via curl to the JIRA URL API endpoint from Jenkins Master SSH console.  
 

  
 
 
 
 

 
 
 

 
 
 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-56146) Unable to connect to REST service

2019-02-15 Thread luba_pyatigorsk...@globetax.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luba Pyat commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 Firewall is not open.. does it have to be open to use Jira plugins? Nothing really in the debug.. Radek Antoniuk  
 

  
 
 
 
 

 
 
 

 
 
 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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier started work on  JENKINS-56161  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Status: 
 Open In 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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-56161  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
 Link to the PR. Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 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-56146) Unable to connect to REST service

2019-02-15 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radek Antoniuk updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56146  
 
 
  Unable to connect to REST service   
 

  
 
 
 
 

 
Change By: 
 Radek Antoniuk  
 
 
Component/s: 
 jira-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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread mwynnmacken...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Wynn-Mackenzie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56161  
 
 
  EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mark Wynn-Mackenzie  
 
 
Components: 
 core  
 
 
Created: 
 2019-02-15 14:18  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Wynn-Mackenzie  
 

  
 
 
 
 

 
 Deserialisation errors seen with class `hudson.EnvVars`: `java.io.InvalidClassException: hudson.EnvVars; local class incompatible: stream classdesc serialVersionUID = -234198271843838088, local class serialVersionUID = 4320331661987259022`   `hudson.EnvVars` is serialisable, but doesn't have a `serialVersionUID`. The generated one has changed between v2.138 (-234198271843838088) & v2.150 (4320331661987259022) causing these deserialisation errors when CJOC runs remote operations on a master at a different version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
  

[JIRA] (JENKINS-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56161  
 
 
  EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Comment: 
 I see you are speaking about CJOC, so I guess you have support for this. Is this something you spoke about with CloudBees support?  
 

  
 
 
 
 

 
 
 

 
 
 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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-56161  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
 I see you are speaking about CJOC, so I guess you have support for this. Is this something you spoke about with CloudBees support?  
 

  
 
 
 
 

 
 
 

 
 
 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-56161) EnvVars deserialisation failure due to changed serialVersionUID

2019-02-15 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56161  
 
 
  EnvVars deserialisation failure due to changed serialVersionUID   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 Deserialisation errors seen with class  `  {{ hudson.EnvVars ` }} : {noformat}  ` java.io.InvalidClassException: hudson.EnvVars; local class incompatible: stream classdesc serialVersionUID = -234198271843838088, local class serialVersionUID = 4320331661987259022 ` {noformat}     ` {{ hudson.EnvVars ` }}  is serialisable, but doesn't have a  `  {{ serialVersionUID ` . }}   The generated one has changed between v2.138 (-234198271843838088) & v2.150 (4320331661987259022) causing these deserialisation errors when CJOC runs remote operations on a master at a different version.  
 

  
 
 
 
 

 
 
 

 
 
 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-56146) Unable to connect to REST service

2019-02-15 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radek Antoniuk commented on  JENKINS-56146  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to REST service   
 

  
 
 
 
 

 
 Do you have firewall open and connectivity works fine from the console?  Do you see anything meaningful in the logs in debug mode?  
 

  
 
 
 
 

 
 
 

 
 
 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   >