[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/plugin-compat-tester/releases/tag/plugins-compat-tester-aggregator-0.1.0  
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 PCT 0.1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Priority: 
 Major 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-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
 Pushed the fix directly to https://github.com/jenkinsci/plugin-compat-tester/pull/140  
 

  
 
 
 
 

 
 
 

 
 
 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-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
 Also, there is a nice log entry there: "Not adding jaxb 2.163 2.3.0 11 as split because jdk specified 11 is newer than running jdk 11".  
 

  
 
 
 
 

 
 
 

 
 
 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-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
 I was able to reproduce the issue, looking at the root cause  
 

  
 
 
 
 

 
 
 

 
 
 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-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-57320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-57320) Fix a possible regression introduced on JENKINS-56312

2019-05-03 Thread bmathus+ossj...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 [~batmat] has worked on adding integration tests to PCT. This is done in this PR: [https://github.com/jenkinsci/plugin-compat-tester/pull/140]With this PR, the Jenkinsfile of PCT runs a test well known to be successful on Java 8 and Java 11.But when testing this PR and a previous one ([https://github.com/jenkinsci/plugin-compat-tester/pull/133]) we found out that PCT fails because it hasn't run any test.In the PR #133 Baptiste reverted the changes on [https://github.com/jenkinsci/plugin-compat-tester/pull/115] and the integration test for PCT ran successfully. So it seems that there is something wrong with this PR (#133).This task is to look into it and fix the problem.  h3. Acceptance criteria:* Create a PR with a fix that makes the Integration Tests introduced on PR #140 run successfully h3. ReproducerCurrently, the following command exits immediately without running any test at all:{noformat}$ curl -sL http://mirrors.jenkins.io/war-stable/2.164.2/jenkins.war --output jenkins.war$ docker run --rm -ti  \  -v maven-repo:/root/.m2 -v $(pwd)/jenkins.war:/pct/jenkins.war:ro \ -v $(pwd)/out:/pct/out -e JDK_VERSION=11 \ -e ARTIFACT_ID=buildtriggerbadge -e VERSION=buildtriggerbadge-2.10 \ jenkins/pct@sha256:caafc379935bae50f77aad8df680b74f79f0f73bec77ae95740e73fa2a22f476+ '[' 0 -eq 1 ']'+ '[' -n buildtriggerbadge ']'+ echo 'Running PCT for plugin buildtriggerbadge'Running PCT for plugin buildtriggerbadge+ CUSTOM_MAVEN_SETTINGS=/pct/m2-settings.xml+ FAIL_ON_ERROR_ARG=+ '[' -n '' ']'+ FAIL_ON_ERROR_ARG=-failOnError+ '[' -f /pct/m2-settings.xml ']'+ MVN_SETTINGS_FILE=/pct/default-m2-settings.xml+ '[' -n '' ']'+ '[' -z buildtriggerbadge ']'+ CHECKOUT_SRC=https://github.com/jenkinsci/buildtriggerbadge-plugin.git+ '[' -f /pct/jenkins.war ']'+ mkdir -p /pct/tmp+ cp /pct/jenkins.war /pct/tmp/jenkins.war+ JENKINS_WAR_PATH=/pct/tmp/jenkins.war+ WAR_PATH_OPT='-war /pct/tmp/jenkins.war '++ groovy /pct/scripts/readJenkinsVersion.groovy /pct/tmp/jenkins.war+ JENKINS_VERSION=2.164.2+ echo 'Using custom Jenkins WAR v. 2.164.2 from /pct/tmp/jenkins.war'Using custom Jenkins WAR v. 2.164.2 from /pct/tmp/jenkins.war+ [[ 2.164.2 =~ .*SNAPSHOT.* ]]+ SHOULD_CHECKOUT=1+ '[' -z buildtriggerbadge-2.10 ']'+ echo 'Will be testing with buildtriggerbadge:buildtriggerbadge-2.10, shouldCheckout=1'Will be testing with buildtriggerbadge:buildtriggerbadge-2.10, shouldCheckout=1+ extra_java_opts=()+ [[ -n '' ]]+ LOCAL_CHECKOUT_ARG=+ '[' 1 -eq 1 ']'+ '[' -z '' ']'+ mkdir -p /pct/tmp/localCheckoutDir+ cd /pct/tmp/localCheckoutDir+ TMP_CHECKOUT_DIR=/pct/tmp/localCheckoutDir/undefined+ '[' -e /pct/plugin-src/pom.xml ']'+ echo 'Checking out from https://github.com/jenkinsci/buildtriggerbadge-plugin.git:buildtriggerbadge-2.10'Checking out from 

[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312

2019-05-03 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 plugin-compat-tester  
 
 
Created: 
 2019-05-03 12:31  
 
 
Labels: 
 java11 java11-devtools-compatibility triaged  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ramon Leon  
 

  
 
 
 
 

 
 Baptiste Mathus has worked on adding integration tests to PCT. This is done in this PR: https://github.com/jenkinsci/plugin-compat-tester/pull/140 With this PR, the Jenkinsfile of PCT runs a test well known to be successful on Java 8 and Java 11. But when testing this PR and a previous one (https://github.com/jenkinsci/plugin-compat-tester/pull/133) we found out that PCT fails because it hasn't run any test. In the PR #133 Baptiste reverted the changes on https://github.com/jenkinsci/plugin-compat-tester/pull/115 and the integration test for PCT ran successfully. So it seems that there is something wrong with this PR (#133). This task is to look into it and fix the problem.   Acceptance criteria: 
 
Create a PR with a fix that makes the Integration Tests introduced on PR #140 run successfully 
  
 

  
 
 
 
 

 
 
 
   

[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57320  
 
 
  Fix a possible regression introduced on JENKINS-56312   
 

  
 
 
 
 

 
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.