[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should

2019-04-13 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this one requires a rewrite of a chunk of pipeline engine - Andrew Bayer is it fair to say that this is part of new generation ?   I don't see this changing for declarative (given all things use "currentBuild." which can't work with this by design) - so I am not sure if this will be done in this form.   
 

  
 
 
 
 

 
 
 

 
 
 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view

2019-04-13 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-47286  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view   
 

  
 
 
 
 

 
 (can't leave this unassigned for some reason).   
 

  
 
 
 
 

 
 
 

 
 
 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view

2019-04-13 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Paul Horvath  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47286  
 
 
  Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 James Dumay Paul Horvath  
 

  
 
 
 
 

 
 
 

 
 
 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-44869) Activity tabs Run id column should expand to fit value

2019-04-13 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-44869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Activity tabs Run id column should expand to fit value   
 

  
 
 
 
 

 
 Reinhold Füreder having trouble following - any chance you can mock it up what it may look like in your 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view

2019-04-13 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Reinhold Füreder  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47286  
 
 
  Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 Paul Horvath Reinhold Füreder  
 

  
 
 
 
 

 
 
 

 
 
 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-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible

2019-04-13 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56984  
 
 
  Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible   
 

  
 
 
 
 

 
Change By: 
 dan tran  
 

  
 
 
 
 

 
 first mentioned in JENKINS- 38522 38552 I was asked to assign to [~fbelzunc] by [~stephenconnolly]after upgrading to 1.3 i started getting this in my logs{code:java}SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.MultiBranchProject$SCMEventListenerImpl@1cf8cddc propagated an exceptionjava.lang.AbstractMethodError: jenkins.branch.BranchBuildStrategy.isAutomaticBuild(Ljenkins/scm/api/SCMSource;Ljenkins/scm/api/SCMHead;Ljenkins/scm/api/SCMRevision;Ljenkins/scm/api/SCMRevision;Lhudson/model/TaskListener;)Z at jenkins.branch.buildstrategies.basic.AllBranchBuildStrategyImpl.isAutomaticBuild(AllBranchBuildStrategyImpl.java:77) at jenkins.branch.BranchBuildStrategy.automaticBuild(BranchBuildStrategy.java:190) at jenkins.branch.MultiBranchProject.isAutomaticBuild(MultiBranchProject.java:2231) at jenkins.branch.MultiBranchProject.access$1200(MultiBranchProject.java:125) at jenkins.branch.MultiBranchProject$SCMHeadObserverImpl.observe(MultiBranchProject.java:2076) at jenkins.scm.api.SCMHeadObserver$Wrapped.observe(SCMHeadObserver.java:638) at jenkins.scm.api.SCMHeadEvent$Validated.observe(SCMHeadEvent.java:295) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:357) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:249) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:917) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:327) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.processHeadUpdate(MultiBranchProject.java:1576) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.onSCMHeadEvent(MultiBranchProject.java:1177) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:246) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:229) at jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:479) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} the issue is the all/none/any wrapper strategies now assume any wrapped strategy implements the new interface method...however older plugin will NOT implement such a method.Could add another interface inbetween, or use reflection, or try catch to make this all work.but 

[JIRA] (JENKINS-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

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


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-55655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does   
 

  
 
 
 
 

 
 [~bulb] I've created tests and an implementation to pass the tests in [PR 421|https://github.com/jenkinsci/git-client-plugin/pull/421].  I would love to have a code review of that PR and any interactive testing of the PR that you are able to provide. The automated tests are failing and I don't have a reasonable explanation why they are failing.  I don't have time to spend on deeper investigation, so I'll close the pull request until I can take more time to investigate.  
 

  
 
 
 
 

 
 
 

 
 
 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-56604) Not able to install necessary plugins like ssh slave, ssh, cvs.

2019-04-13 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams commented on  JENKINS-56604  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to install necessary plugins like ssh slave, ssh, cvs.   
 

  
 
 
 
 

 
 Needs more detail if it's going to get any attention  
 

  
 
 
 
 

 
 
 

 
 
 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-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-55655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does   
 

  
 
 
 
 

 
 Jan Hudec I've created tests and an implementation to pass the tests in PR 421. I would love to have a code review of that PR and any interactive testing of the PR that you are able to provide.  
 

  
 
 
 
 

 
 
 

 
 
 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-55018) Configuration slicing change log is not up to date

2019-04-13 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55018  
 
 
  Configuration slicing change log is not up to date   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 
 
Summary: 
 Change Configuration slicing change  log is not up to date  
 

  
 
 
 
 

 
 
 

 
 
 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-56998) Extended Choice plugin Wiki page incorrect

2019-04-13 Thread ian.willia...@telus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56998  
 
 
  Extended Choice plugin Wiki page incorrect   
 

  
 
 
 
 

 
Change By: 
 Ian Williams  
 
 
Summary: 
 extended Extended  Choice  plugin  Wiki page incorrect  
 

  
 
 
 
 

 
 
 

 
 
 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-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55655  
 
 
  BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 I have built a docker container, based on {{jenkins/jenkins: lte lts }}, where I configured appropriate {{ProxyCommand}} for our convoluted intranet setup in {{/etc/ssh/ssh_config}}, and preinstalled the {{blueocean}} plugin using the {{/usr/local/bin/install-plugins.sh}} script.With this setup, I can create a project referring to our internal git repository as the Git client plugin uses the git binary (as is by default), which uses ssh, which reads the configuration and correctly tunnels through the proxy. However when I switch to BlueOcean, and try to create the pipeline from there, it fails to connect. The log says:{noformat}SEVERE: Error running git remote-ls: org.eclipse.jgit.api.errors.TransportException: ssh://g...@internal.git.server.com:4567/dep/Project.git: Failed to connecthudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: ssh://g...@internal.git.server.com:4567/dep/Project.git: Failed to connectCaused by: org.eclipse.jgit.api.errors.TransportException: ssh://g...@internal.git.server.com:4567/dep/Project.git: Failed to connectCaused by: org.eclipse.jgit.errors.TransportException: ssh://g...@internal.git.server.com:4567/dep/Project.git: Failed to connectCaused by: java.io.IOException: There was a problem while connecting to internal.git.server.com:4567Caused by: java.net.UnknownHostException: internal.git.server.com: Name or service not known{noformat}(anonymised the server and project name, otherwise exact log except the backtraces; full log including the backtraces attached)The server name is not known, because only the proxy server can resolve it. The configuration in {{/etc/ssh/ssh_config}} is like:{noformat}Host internal.git.server.comProxyCommand socat - proxy:10.20.30.40:%h:%p,proxyport=8080,proxyauth=user:password {noformat}The {{%h}}, which gets expanded to {{internal.git.server.com}}, is resolved by the proxy, so it does not matter than the Jenkins host does not have the DNS for the land behind the proxy. However, the blueocean connection manages to do a request that goes through the JGit and the Java ssh2 library (com.trilead.ssh2), even when they are not configured in the git-client-plugin options, and this does not honor that configuration and fails.h4. WorkaroundI haven't tested it yet, but I realised a workaround would be to: # Add internal.git.server.com to /etc/hosts, pointing to localhost and # Get socat tcp-listen:4567,reuseaddr,fork proxy:1020.30.40:internal.git.server.com:4567,proxyport=8080,proxyauth=user:password running in the background—that is, create kind of transparent proxy of it.Then no ssh configuration is needed.I still believe that either the access should consistently honour the settings.  
 

 

[JIRA] (JENKINS-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55655  
 
 
  BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Environment: 
 Docker image jenkins/jenkins: lte lts , Linux-amd64, Jenkins ver. 2.150.1, BlueOcean 1.10.1, Git plugin 3.9.1, Git client plugin 2.7.6.  
 

  
 
 
 
 

 
 
 

 
 
 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-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

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


 
 
 
 

 
 
 

 
   
 Mark Waite started work on  JENKINS-55655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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-56672) Artifacts tab in blue ocean does not have link to view an artifact

2019-04-13 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-56672  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts tab in blue ocean does not have link to view an artifact   
 

  
 
 
 
 

 
 Patch submitted: https://github.com/jenkinsci/blueocean-plugin/pull/1951  
 

  
 
 
 
 

 
 
 

 
 
 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-56672) Artifacts tab in blue ocean does not have link to view an artifact

2019-04-13 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues assigned an issue to Craig Rodrigues  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56672  
 
 
  Artifacts tab in blue ocean does not have link to view an artifact   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Assignee: 
 Craig Rodrigues  
 

  
 
 
 
 

 
 
 

 
 
 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-56672) Artifacts tab in blue ocean does not have link to view an artifact

2019-04-13 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues started work on  JENKINS-56672  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
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-37862) Extract build symlink handling to a plugin

2019-04-13 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-37862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37862  
 
 
  Extract build symlink handling to a plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible

2019-04-13 Thread drdam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chirs damour commented on  JENKINS-56984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible   
 

  
 
 
 
 

 
 others reporting same issue https://issues.jenkins-ci.org/browse/JENKINS-48296?focusedCommentId=364779=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-364779  
 

  
 
 
 
 

 
 
 

 
 
 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-48296) Multibranch pipeline - ignore commits from certain user

2019-04-13 Thread drdam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chirs damour commented on  JENKINS-48296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch pipeline - ignore commits from certain user   
 

  
 
 
 
 

 
 yup they broke it with JENKINS-38552 i filed JENKINS-56984  
 

  
 
 
 
 

 
 
 

 
 
 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] (TEST-168) RCB results

2019-04-13 Thread tejaswibollepa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 tejaswi rachavelpula created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 test /  TEST-168  
 
 
  RCB results   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 foo10  
 
 
Created: 
 2019-04-13 10:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 tejaswi rachavelpula  
 

  
 
 
 
 

 
 
 

 
 
 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-56450) MSBuild parser fails when compiling with /MP

2019-04-13 Thread lor...@xca.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenz Aebi updated  JENKINS-56450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56450  
 
 
  MSBuild parser fails when compiling with /MP   
 

  
 
 
 
 

 
Change By: 
 Lorenz Aebi  
 
 
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-56450) MSBuild parser fails when compiling with /MP

2019-04-13 Thread lor...@xca.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenz Aebi started work on  JENKINS-56450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Lorenz Aebi  
 
 
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-31660) StackOverflowError when maximum number of builds archived

2019-04-13 Thread zby...@geogebra.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zbynek Konecny commented on  JENKINS-31660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverflowError when maximum number of builds archived   
 

  
 
 
 
 

 
 This happens often when there are skipped tests because of a bug in the Junit plugin, see https://github.com/jenkinsci/junit-plugin/pull/117 It's independent on Build Stability 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.