[JIRA] (JENKINS-54842) Find and add Java 9+ signatures for Animal Sniffer
Title: Message Title Olivier Lamy commented on JENKINS-54842 Re: Find and add Java 9+ signatures for Animal Sniffer IMHO we do not need anymore animal sniffer but simply use the release compiler flag... Read the motivation section here http://openjdk.java.net/jeps/247 I guess this was inspired by our signatures. This simply insure the code is RELEASE compatible. 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-54831) False-Positive CVE-2017-2604 after update of OWASP Dependency-Check
Title: Message Title Steve Springett closed an issue as Won't Do The Jenkins plugin is simply a wrapper around Dependency-Check core module. Nothing can be done here to fix. False positives need to be reported to https://github.com/jeremylong/DependencyCheck Jenkins / JENKINS-54831 False-Positive CVE-2017-2604 after update of OWASP Dependency-Check Change By: Steve Springett Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48466) Provide JUnit 5 support for JenkinsRule
Title: Message Title
Chris Hunt commented on JENKINS-48466
Re: Provide JUnit 5 support for JenkinsRule
I was able to get something started using a ParameterResolver, like so:
package io.jenkins.plugins.websub;
import org.junit.jupiter.api.extension.AfterEachCallback;
import org.junit.jupiter.api.extension.ExtensionContext;
import org.junit.jupiter.api.extension.ParameterContext;
import org.junit.jupiter.api.extension.ParameterResolutionException;
import org.junit.jupiter.api.extension.ParameterResolver;
import org.jvnet.hudson.test.JenkinsRecipe;
import java.util.Optional;
public class TestUtils {
public static class JenkinsRule extends org.jvnet.hudson.test.JenkinsRule {
private final ParameterContext context;
JenkinsRule(ParameterContext context) {
this.context = context;
}
@Override
public void recipe() throws Exception {
Optional a = context.findAnnotation(JenkinsRecipe.class);
if (!a.isPresent()) return;
final JenkinsRecipe.Runner runner = a.get().value().newInstance();
recipes.add(runner);
tearDowns.add(() -> runner.tearDown(this, a.get()));
}
}
public static class JenkinsParameterResolver implements ParameterResolver, AfterEachCallback {
private static final String key = "jenkins-instance";
private static final ExtensionContext.Namespace ns =
ExtensionContext.Namespace.create(JenkinsParameterResolver.class);
@Override
public boolean supportsParameter(ParameterContext parameterContext, ExtensionContext extensionContext)
throws ParameterResolutionException {
return parameterContext.getParameter().getType().equals(JenkinsRule.class);
}
@Override
public Object resolveParameter(ParameterContext parameterContext, ExtensionContext extensionContext)
throws ParameterResolutionException {
JenkinsRule instance = extensionContext.getStore(ns).getOrComputeIfAbsent(
key, key -> new JenkinsRule(parameterContext), JenkinsRule.class);
try {
instance.before();
return instance;
} catch (Throwable t) {
throw new ParameterResolutionException(t.toString());
}
}
@Override
public void afterEach(ExtensionContext context) throws Exception {
JenkinsRule rule = context.getStore(ns).remove(key, JenkinsRule.class);
if (rule != null)
rule.after();
}
}
}
Used like
package io.jenkins.plugins.websub;
import hudson.model.FreeStyleBuild;
import hudson.model.FreeStyleProject;
import hudson.tasks.Shell;
import org.apache.commons.io.FileUtils;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
@ExtendWith(TestUtils.JenkinsParameterResolver.class)
public class TestWebSubTrigger {
@Test
void testJenkinsParameterResolver(TestUtils.JenkinsRule j) throws Exception {
FreeStyleProject project = j.createFreeStyleProject();
project.getBuildersList().add(new Shell("echo hello"));
[JIRA] (JENKINS-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Carlos Sanchez resolved as Fixed Jenkins / JENKINS-54770 A new client object is created each time the plugin needs to connection to K8s Change By: Carlos Sanchez Status: In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Nicolas Zin commented on JENKINS-53858 Re: Deadlock on EC2 resources Same issue here. Do you know where the official 1.42 will be release? 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-54838) OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-54838 OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities Change By: Steve Springett Assignee: Steve Springett 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-54838) OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Title: Message Title Steve Springett edited a comment on JENKINS-54838 Re: OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities What version of the Dependency-Check Jenkins plugin are you using? What version of analysis-core (Static Code Analysis Plugins) is installed? Do you have the warnings or warnings-ng plugin installed? If so, what version? Did you use the Dependency-Check Maven plugin, CLI, or the Jenkins plugin to produce dependency-check-result.xml? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54838) OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Title: Message Title Steve Springett commented on JENKINS-54838 Re: OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities What version of the Dependency-Check Jenkins plugin are you using? What version of analysis-core (Static Code Analysis Plugins) is installed? Do you have the warnings or warnings-ng plugin installed? If so, what 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-54833) Warnings Parser fails parsing log
Title: Message Title Ulli Hafner commented on JENKINS-54833 Re: Warnings Parser fails parsing log What encoding did you specify for your source files? 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-20679) Define manifest header in the jpi file to capture minimum Java requirement
Title: Message Title Oleg Nenashev commented on JENKINS-20679 Re: Define manifest header in the jpi file to capture minimum Java requirement https://github.com/jenkinsci/plugin-pom/pull/134 is the reference impl 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-54844) Access Modifier Checker 1.16 fails when running with java.level=11
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54844 Access Modifier Checker 1.16 fails when running with java.level=11 Issue Type: Bug Assignee: Unassigned Components: plugin-pom Created: 2018-11-23 17:48 Labels: java11 Priority: Minor Reporter: Oleg Nenashev It seems we need to bump ASM again... [ERROR] Failed to execute goal org.kohsuke:access-modifier-checker:1.16:enforce (default-enforce) on project label-verifier: Execution default-enforce of goal org.kohsuke:access-modifier-checker:1.16:enforce failed.: IllegalArgumentException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.kohsuke:access-modifier-checker:1.16:enforce (default-enforce) on project label-verifier: Execution default-enforce of goal org.kohsuke:access-modifier-checker:1.16:enforce failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute
[JIRA] (JENKINS-54842) Find and add Java 9+ signatures for Animal Sniffer
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54842 Find and add Java 9+ signatures for Animal Sniffer Change By: Oleg Nenashev Labels: java11 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54843 Maven Enforcer Plugin crashes with java.level=11 Change By: Oleg Nenashev Labels: java11 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54843 Maven Enforcer Plugin crashes with java.level=11 Change By: Oleg Nenashev Issue Type: Improvement Bug 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54843 Maven Enforcer Plugin crashes with java.level=11 Issue Type: Improvement Assignee: Unassigned Components: maven-hpi-plugin Created: 2018-11-23 17:28 Priority: Minor Reporter: Oleg Nenashev When I want to enforce Java level 11 in a Jenkins plugin, maven Enforcer crashes on requireBytecodeVersion [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce (display-info) on project label-verifier: Execution display-info of goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce failed: Unknown JDK version given. Should be something like "1.7" -> [Help 1] [ERROR] https://github.com/mojohaus/extra-enforcer-rules/pull/63/files is needed to be upstreamed. CC Baptiste Mathus Add Comment
[JIRA] (JENKINS-54842) Find and add Java 9+ signatures for Animal Sniffer
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54842 Find and add Java 9+ signatures for Animal Sniffer Issue Type: Improvement Assignee: Unassigned Components: plugin-pom Created: 2018-11-23 16:57 Priority: Minor Reporter: Oleg Nenashev Currently there is no Java 9+ signatures for Animal Sniffer, so we cannot really compile code for Java 11 without disable static checks. CC Olivier Lamy who may know workarounds Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54841 Invalid characters in changelist triggers SAXParseException Change By: Karl Wirth Attachment: changelog0.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54841 Invalid characters in changelist triggers SAXParseException Change By: Karl Wirth Attachment: bad_description.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-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54841 Invalid characters in changelist triggers SAXParseException Change By: Karl Wirth Labels: P4_VERIFY 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-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-54841
Invalid characters in changelist triggers SAXParseException
Change By:
Karl Wirth
If a changelist contains a character that is not valid in XML it is written straight to the changelog.xml. When parsed this will cause the following error: {code:java}...cut...com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:50)Caused: org.xml.sax.SAXException: Could not parse perforce changelog: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/Pipeline/builds/28/changelog0.xml; lineNumber: 8; columnNumber: 59; An invalid XML character (Unicode: 0x5) was found in the element content of the document{code}In the above case the character ASCII 5 (ENQ) has been included because it was part of an error message. *Reproduction Steps:*(1) Create a Jenkinsfile that includes 'checkout'. Mine also includes 'changelog' but that value should default to 'true' if not explicitly set: {code:java}node{ stage("Repro") { checkout changelog: true, scm: perforce(credential: 'JenkinsMaster', populate: autoClean(delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', threads: '4' ], pin: '', quiet: false, replace: true, tidy: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: false, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '//streams/main', type: 'WRITABLE', view: ''))) }} {code}(2) Open '//streams/main/test1.c' for edit.(3) Create a changelist with the attached changelist description (bad_description.txt).(4) Create a pipeline job (not multibranch) that runs against //streams/main/Jenkinsfile.(5) Run the job.(6) Full output below:{code:java}tarted by user unknown or anonymousObtained Jenkinsfile from p4-JenkinsMaster-//streams/mainRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/Pipeline[Pipeline] {[Pipeline] stage[Pipeline] { (Repro)[Pipeline] echonull[Pipeline] checkout(p4):cmd:... p4 client -o jenkins-master-Pipeline-0p4 client -o jenkins-master-Pipeline-0(p4):stop:4(p4):cmd:... p4 infop4 info(p4):stop:5(p4):cmd:... p4 infop4 info(p4):stop:6(p4):cmd:... p4 client -ip4 client -iClient jenkins-master-Pipeline-0 saved.(p4):stop:7(p4):cmd:... p4 counter changep4 counter change(p4):stop:8(p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-master-Pipeline-0/...p4 changes -m1 -ssubmitted //jenkins-master-Pipeline-0/...Change 60 on 2018/11/23 by super@ws_stream ' My description... desc.tx'(p4):stop:9(p4):cmd:... p4 repos -Cp4 repos -C(p4):stop:10Building on Node: master(p4):cmd:... p4 client -o
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Karl Wirth commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Have worked with Peter and reproduced the XML parse error he reported. Created new defect: JENKINS-54841 We believe the original problem still exists and is related to multiple nodes running at the same time potentially causing concurrency issues reading and writing the changelog.xml. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-54841
Invalid characters in changelist triggers SAXParseException
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-11-23 16:24
Environment:
Jenkins 2.138.1 P4Plugin 1.9.3
Priority:
Blocker
Reporter:
Karl Wirth
If a changelist contains a character that is not valid in XML it is written straight to the changelog.xml. When parsed this will cause the following error:
...cut...
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:328)
at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:50)
Caused: org.xml.sax.SAXException: Could not parse perforce changelog:
org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/Pipeline/builds/28/changelog0.xml; lineNumber: 8; columnNumber: 59; An invalid XML character (Unicode: 0x5) was found in the element content of the document
In the above case the character ASCII 5 (ENQ) has been included because it was part of an error message. Reproduction Steps: (1) Create a Jenkinsfile that includes 'checkout'. Mine also includes 'changelog' but that value should default to 'true' if not explicitly set:
node{
stage("Repro") {
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title
Marcello Romani edited a comment on JENKINS-54143
Re: Cannot create new users in 2.138.2
I have encountered the same problem.The fix for me was replacing a dot in the username with an underscore.E.g.: {{name.surname}} --> {{name_surname}}That is in line with what [~danielbeck] described above, in particular: {quote} * User name must only contain alphanumeric characters, underscore and dash{quote}
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-54143) Cannot create new users in 2.138.2
Title: Message Title Marcello Romani commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 I have encountered the same problem. The fix for me was replacing a dot in the username with an underscore. E.g.: name.surname --> name_surname That is in line with what Daniel Beck described above, in particular: User name must only contain alphanumeric characters, underscore and dash 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-54143) Cannot create new users in 2.138.2
Title: Message Title
Marcello Romani edited a comment on JENKINS-54143
Re: Cannot create new users in 2.138.2
I have encountered the same problem.The fix for me was replacing a dot in the username with an underscore.E.g.: {{name.surname}} --> {{name_surname}}That is in line with what [~danielbeck] described above, in particular: {quote} * User name must only contain alphanumeric characters, underscore and dash {quote}
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-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Tim Jacomb commented on JENKINS-47882 Re: Unable to connect MongoDB with MONGODB-CR authentication In the meantime i have forked it and am publishing hpi's here: https://github.com/hmcts/build-failure-analyzer-plugin/releases 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-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Tim Jacomb commented on JENKINS-47882 Re: Unable to connect MongoDB with MONGODB-CR authentication PR has been complete for awhile, it is awaiting 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-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Tim Jacomb updated JENKINS-47882 Jenkins / JENKINS-47882 Unable to connect MongoDB with MONGODB-CR authentication Change By: Tim Jacomb 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-54840) UnsupportedOperationException getLogFile
Title: Message Title
Christoph Vogtländer updated an issue
Jenkins / JENKINS-54840
UnsupportedOperationException getLogFile
Change By:
Christoph Vogtländer
Whenever the build failure analyser plug-in runs there will be several warning warnings in the Jenkin slog Jenkins log "Avoid calling getLogFile on ..." because getLogMessage is deprecated:[https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile--] {noformat}Nov 23, 2018 3:20:04 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishTestWorkflow/TestWorkflow #362 completed: FAILURENov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseSingleLineCauses(BuildFailureScanner.java:426) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$000(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$1.run(BuildFailureScanner.java:289) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.model.MultilineBuildLogFailureReader.scan(MultilineBuildLogFailureReader.java:92) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndication(BuildFailureScanner.java:451) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseIndication(BuildFailureScanner.java:393) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$100(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$2.run(BuildFailureScanner.java:306) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.model.MultilineBuildLogFailureReader.scan(MultilineBuildLogFailureReader.java:92) at
[JIRA] (JENKINS-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb commented on JENKINS-54839 Re: Match Text not working on GitHub multibranch pipeline for PRs https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/93 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-54840) UnsupportedOperationException getLogFile
Title: Message Title
Christoph Vogtländer updated an issue
Jenkins / JENKINS-54840
UnsupportedOperationException getLogFile
Change By:
Christoph Vogtländer
Whenever the build failure analyser plug-in runs there will be several warnings in the Jenkins log "Avoid calling getLogFile on ..." because getLogMessage getLogFile is deprecated:[https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile--] {noformat}Nov 23, 2018 3:20:04 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishTestWorkflow/TestWorkflow #362 completed: FAILURENov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseSingleLineCauses(BuildFailureScanner.java:426) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$000(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$1.run(BuildFailureScanner.java:289) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.model.MultilineBuildLogFailureReader.scan(MultilineBuildLogFailureReader.java:92) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndication(BuildFailureScanner.java:451) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseIndication(BuildFailureScanner.java:393) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$100(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$2.run(BuildFailureScanner.java:306) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.model.MultilineBuildLogFailureReader.scan(MultilineBuildLogFailureReader.java:92) at
[JIRA] (JENKINS-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb updated JENKINS-54839 Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Change By: Tim Jacomb 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-54840) UnsupportedOperationException getLogFile
Title: Message Title
Christoph Vogtländer updated an issue
Jenkins / JENKINS-54840
UnsupportedOperationException getLogFile
Change By:
Christoph Vogtländer
Whenever the build failure analyser plug-in runs there will be several warning in the Jenkin slog "Avoid calling getLogFile on ..." because getLogMessage is deprecated: [ https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile-- ] {noformat} Nov 23, 2018 3:20:04 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishTestWorkflow finishTestWorkflow /TestWorkflow #362 completed: FAILURENov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseSingleLineCauses(BuildFailureScanner.java:426) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$000(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$1.run(BuildFailureScanner.java:289) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.model.MultilineBuildLogFailureReader.scan(MultilineBuildLogFailureReader.java:92) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndication(BuildFailureScanner.java:451) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseIndication(BuildFailureScanner.java:393) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$100(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$2.run(BuildFailureScanner.java:306) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at
[JIRA] (JENKINS-54840) UnsupportedOperationException getLogFile
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-54840 UnsupportedOperationException getLogFile Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-11-23 15:04 Environment: Jenkins ver. 2.138.3 Build Failure Analyzer 1.20.0 Priority: Major Reporter: Christoph Vogtländer Whenever the build failure analyser plug-in runs there will be several warning in the Jenkin slog "Avoid calling getLogFile on ..." because getLogMessage is deprecated: https://javadoc.jenkins.io/plugin/workflow-job/org/jenkinsci/plugins/workflow/job/WorkflowRun.html#getLogFile-- Nov 23, 2018 3:20:04 PM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish TestWorkflow/TestWorkflow #362 completed: FAILURE Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile Avoid calling getLogFile on TestWorkflow/TestWorkflow #362 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.parseSingleLineCauses(BuildFailureScanner.java:426) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.access$000(BuildFailureScanner.java:77) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner$1.run(BuildFailureScanner.java:289) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Nov 23, 2018 3:20:04 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile Avoid calling getLogFile on TestWorkflow/TestWorkflow #362
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title
Josh Soref commented on JENKINS-54640
Re: Workspace folders are not unique
So, I think that the plugin is not being careful about whose workspace.txt it's considering... We're using
pipeline {
parallel {
stage {
}
stage {
}
}
}
A quick grep for our project across the various build nodes shows that the hashed directory listed is the one from one build node, but not from the failing build node (which has a different path in the workspaces.txt file).
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-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title
Tim Jacomb updated an issue
Jenkins / JENKINS-54839
Match Text not working on GitHub multibranch pipeline for PRs
Change By:
Tim Jacomb
When verifying my regex against simple pipeline project, all works fine, but when doing same against multibranch pipeline ( Bitbucket Project Type Github ) for a PR it yields null pointer exception. assertionerror I'm using Failure Cause Management / MyError / Advanced... / Match TextI think issue maybe in URL path interpretation: http:// jenkins 127 . company 0 . com 0.1 : 8080 8070 / jenkins/ job/ SimplePipeline spring-boot-template / 1206 job / spring - workshttp: boot-template / /jenkins.company.com:8080/ view/ MultibranchPipeline change-requests /job/ MyTeam PR-69 / job 1 / MyProject/job/master/65/ - yields: {code:java} A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang. NullPointerException AssertionError Folder not found! at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at
[JIRA] (JENKINS-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb started work on JENKINS-54839 Change By: Tim Jacomb 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-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-11-23 14:45 Priority: Major Reporter: Tim Jacomb When verifying my regex against simple pipeline project, all works fine, but when doing same against multibranch pipeline (Bitbucket Project Type) it yields null pointer exception. I'm using Failure Cause Management / MyError / Advanced... / Match Text I think issue maybe in URL path interpretation: http://jenkins.company.com:8080/job/SimplePipeline/1206/ - works http://jenkins.company.com:8080/view/MultibranchPipeline/job/MyTeam/job/MyProject/job/master/65/ - yields: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at
[JIRA] (JENKINS-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Change By: Tim Jacomb Assignee: Tomas Westling Tim Jacomb 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-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Change By: Tim Jacomb Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Josh Soref commented on JENKINS-54640 Re: Workspace folders are not unique So, all I've done is rename workspaces.txt I don't really want to have to go to all 10 of my computers and delete entire trees if i can avoid 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-54640) Workspace folders are not unique
Title: Message Title Josh Soref commented on JENKINS-54640 Re: Workspace folders are not unique ERROR: Unable to launch the agent for somenode java.nio.file.NoSuchFileException: /home/jenkins/workspace/workspaces.txt at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.FilePath$Read.invoke(FilePath.java:1991) at hudson.FilePath$Read.invoke(FilePath.java:1983) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) Caused: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:169) 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.BufferedReader.fill(BufferedReader.java:161) at java.io.BufferedReader.readLine(BufferedReader.java:324) at java.io.BufferedReader.readLine(BufferedReader.java:389) at jenkins.branch.WorkspaceLocatorImpl.load(WorkspaceLocatorImpl.java:221) at jenkins.branch.WorkspaceLocatorImpl.access$500(WorkspaceLocatorImpl.java:80) at jenkins.branch.WorkspaceLocatorImpl$Collector.onOnline(WorkspaceLocatorImpl.java:518) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:693) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:432) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:153) 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) ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused:
[JIRA] (JENKINS-54838) OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Title: Message Title
Marc Peña created an issue
Jenkins / JENKINS-54838
OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Issue Type:
Bug
Assignee:
Unassigned
Components:
dependency-check-jenkins-plugin
Created:
2018-11-23 14:10
Labels:
plugin jenkins dependency-check
Priority:
Minor
Reporter:
Marc Peña
We're using the Jenkins plugin to analyze our software and are experimenting a buggy behavior. Every time we do a scan the plugin says that we got: {{12 new vulnerabilities 12 Fixed vulnerabilities}} And the problem is that all of them are the same vulnerabilities, scan after scan, related to the Bouncy Castle provider: bcprov-jdk15on.jar
Add Comment
[JIRA] (JENKINS-54838) OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Title: Message Title
Marc Peña updated an issue
Jenkins / JENKINS-54838
OWASP Dependency-Check plugin loses trace of bcprov-jdk15on.jar vulnerabilities
Change By:
Marc Peña
We're using the Jenkins plugin to analyze our software and are experimenting a buggy behavior. Every time we do a scan the plugin says that we got: { { code:java} 12 new vulnerabilities12 Fixed vulnerabilities {code } } And the problem is that all of them are the same vulnerabilities, scan after scan, related to the Bouncy Castle provider: *bcprov-jdk15on.jar**!https://user-images.githubusercontent.com/3256953/48907536-0e604600-ee68-11e8-86a3-c95710e01986.png!**!https://user-images.githubusercontent.com/3256953/48907421-a9a4eb80-ee67-11e8-9e90-3ea378a70852.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-53191) Release a new plugin version
Title: Message Title Albert V commented on JENKINS-53191 Re: Release a new plugin version There is any plan for this release? It would be really helpfull 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-54640) Workspace folders are not unique
Title: Message Title Lars-Magnus Skog commented on JENKINS-54640 Re: Workspace folders are not unique kpop Ok. But why would it be intentional? What's the reason for doing 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-54837) Cannot override workspace-volume
Title: Message Title
Andreas Bergmeier created an issue
Jenkins / JENKINS-54837
Cannot override workspace-volume
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-11-23 13:26
Priority:
Major
Reporter:
Andreas Bergmeier
When I add
volumeMounts:
- name: workspace-volume
mountPath: "/home/jenkins"
to the yaml, it complains
Duplicate value: "workspace-volume"
How should one override the workspace-volume then?{{}}
Add Comment
[JIRA] (JENKINS-54836) create a local user in jenkins with admin privilages
Title: Message Title Priyanka Panda created an issue Jenkins / JENKINS-54836 create a local user in jenkins with admin privilages Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-11-23 13:18 Environment: Centos Priority: Minor Reporter: Priyanka Panda We need to create a local user in jenkins alongside having LDAP authentication setup so that when the LDAP server goes down/ or is inaccessible the local user should be able to logon to jenkins and perform basic actions. Does jenkins already support any kind of plugin to do this? Add Comment
[JIRA] (JENKINS-51760) API to get job disable date in jenkins
Title: Message Title Priyanka Panda closed an issue as Fixed Jenkins / JENKINS-51760 API to get job disable date in jenkins Change By: Priyanka Panda Status: Reopened Closed 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-51353) In declarative pipeline, volumes and imagepullsecrets needed
Title: Message Title Andreas Bergmeier commented on JENKINS-51353 Re: In declarative pipeline, volumes and imagepullsecrets needed YAML is not the same as `volumes`, though. The latter automatically applies to all containers. With config in YAML you have to write a whole lot more declarations. 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-54640) Workspace folders are not unique
Title: Message Title kpop commented on JENKINS-54640 Re: Workspace folders are not unique Lars-Magnus Skog, I believe that cutting of the folder names is intentional behavior. I see the same without loss of functionality. The workspaces.txt lists the full project name and project path, as well as the folder that is allocated for it. Josh Soref, check if the workspaces.txt still contains duplicate folder names. I've cleared my entire workspace and also removed that file to get it working. But it might also be sufficient to remove all duplicates in workspaces.txt and the corresponding folders. New collisions are avoided, but I'm unsure if existing collisions are also fixed automatically. 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-54685) data ecomony
Title: Message Title Jakub Bochenski commented on JENKINS-54685 Re: data ecomony Sounds good, though I would prefer to enable keeping the legacy behavior. Both for pure backwards-compatibility and for builds with small amount of metadata/lines it can be convenient to send everything in a single payload. I think we can achieve this by having all three sets configurable: every-message data start event data end event data Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54835) Pipeline stage view is showing all stages twice
Title: Message Title Martin Kadner updated an issue Jenkins / JENKINS-54835 Pipeline stage view is showing all stages twice Change By: Martin Kadner Component/s: pipeline-view-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54835) Pipeline stage view is showing all stages twice
Title: Message Title Martin Kadner updated an issue Jenkins / JENKINS-54835 Pipeline stage view is showing all stages twice Change By: Martin Kadner Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54835) Pipeline stage view is showing all stages twice
Title: Message Title Martin Kadner created an issue Jenkins / JENKINS-54835 Pipeline stage view is showing all stages twice Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-23 12:18 Environment: Jenkins ver. 2.138.2 Pipeline ver. 2.6 Priority: Minor Reporter: Martin Kadner Pipeline stage view is showing all stages twice. The second time the 'Average stage times' are showing NaNy NaNd. This is happening during the job execution. Finished the job the view is again as expected. Add Comment
[JIRA] (JENKINS-52935) Git LFS failing clone
Title: Message Title
Mark Waite edited a comment on JENKINS-52935
Re: Git LFS failing clone
[~swf] I can duplicate the problem you described if I don't enable the "Git LFS pull after checkout" trait on the GitHub Organization folder definition. Once I enable "Git LFS pull after checkout" in the GitHub organization folder definition, the {{git lfs pull}} operation runs successfully.My understanding of the conditions described by [~atsju2] include:* Jenkins server 2.121.2 running on Windows* GitHub Enterprise (not github.com)* Git for Windows installed with LFS support enabled - version unknown* Git LFS version unknownAs far as I can tell from my experiment with a GitHub Organization project, I must provide an https URL and https credentials. I can then add the "checkout over ssh" trait and provide an ssh private key. I provided an ed25519 private key without passphrase and confirmed that my github.com LFS repositories (docker-lfs and docker-private-lfs) are both able to clone successfully, so long as I add the {{Git LFS pull after checkout}} trait.I'm sure there are differences between my environment and yours. Differences that I can identify include:* I'm using github.com rather than GitHub Enterprise* I'm running the master as a Docker image on Linux, not as a Windows master* I'm running Jenkins 2.138.3 with a pre-release version of git plugin 4.0 and a pre-release version of git client plugin 3.0When I was misconfigured (without the {{Git LFS pull before checkout}} trait ) , the stack trace I saw was:{noformat}GitHub has been notified of this commit’s build resulthudson.plugins.git.GitException: Command "git checkout -f 103402b4417738fd6a7dee6386e11710c938950d" returned status code 128:stdout: stderr: Downloading ref/plugins/ace-editor.jpi (4.3 MB)Error downloading object: ref/plugins/ace-editor.jpi (abc9702): Smudge error: Error downloading ref/plugins/ace-editor.jpi (abc97028893c8a71581a5f559ea48e8e1f1a65164faee96dabfed9e95e9abad2): batch request: g...@github.com: Permission denied (publickey).: exit status 255Errors logged to /home/mwaite/mark-pc2.markwaite.net-agent/workspace/e-lfs_cjp-with-plugins-debian9-a/.git/lfs/logs/20181122T211435.33423253.logUse `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failedfatal: ref/plugins/ace-editor.jpi: smudge filter lfs failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2305) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:83) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2614)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to testing-a-mwaite at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor156.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy92.execute(Unknown Source) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1217) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev commented on JENKINS-54834 Re: Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml I like the option 1 BTW. Not sure what needs to be done in Jenkins X dependabot to enable 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-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54834 Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Change By: Oleg Nenashev Currently Jenkins X Serverless does not have automatic update for Custom WAR Packager definitions. There are 2 options we could use: * Option 1: Use pom.xml as plugin list input, it's already supported by Custom War Packager. ** In such case we also get upper bounds dependency checks for plugins OOTB, so that the build fails on conflicting dependencies even before starting the build ** Problem: Dependabot does not seem to scan Jenkins Maven repositories. Could it be tweaked somehow * Option 2: Implement dependabot plugin for BOM.yml (Jenkins JEP-309)CC [~jstrachan] [~jrawlings] [~cosmin_cojocar] 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-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54834 Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Change By: Oleg Nenashev Component/s: custom-war-packager 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-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54834 Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Issue Type: Improvement Assignee: Unassigned Components: other Created: 2018-11-23 11:55 Priority: Minor Reporter: 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-50880) Create a new option for running when condition before stage input
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-50880 Jenkins / JENKINS-50880 Create a new option for running when condition before stage input Change By: Jose Blas Camacho Taboada 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-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-53558 Jenkins / JENKINS-53558 Apply top level failFast option to all parallel stages inside Jenkinsfile. Change By: Jose Blas Camacho Taboada 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-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-53558 Change By: Jose Blas Camacho Taboada 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-54766) Missing target dependency to sue demo-* targets
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-54766 Missing target dependency to sue demo-* targets Change By: Adrien Lecharpentier Comment: https://github.com/jenkinsci/plugin-compat-tester/pull/85 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-54674 PCT: Add Docker packaging for Java 11 Change By: Adrien Lecharpentier Comment: https://github.com/jenkinsci/plugin-compat-tester/pull/86 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-53519) "Caught a IllegalStateException traversing the graph for run" using currentBuild.rawBuild.delete()
Title: Message Title Alexis Gauthiez updated an issue Jenkins / JENKINS-53519 "Caught a IllegalStateException traversing the graph for run" using currentBuild.rawBuild.delete() Change By: Alexis Gauthiez Priority: Minor Major 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-54775) Fix Java 11 build URL
Title: Message Title Baptiste Mathus updated JENKINS-54775 Jenkins / JENKINS-54775 Fix Java 11 build URL Change By: Baptiste Mathus 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54598) Explore JDK11 Upgrade for Evergreen
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54598 Explore JDK11 Upgrade for Evergreen Change By: Baptiste Mathus Assignee: Adrien Lecharpentier Baptiste Mathus 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-54766) Missing target dependency to sue demo-* targets
Title: Message Title Adrien Lecharpentier commented on JENKINS-54766 Re: Missing target dependency to sue demo-* targets https://github.com/jenkinsci/plugin-compat-tester/pull/85 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-54674 Re: PCT: Add Docker packaging for Java 11 https://github.com/jenkinsci/plugin-compat-tester/pull/86 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-54386) preserveStashes does not work with parameter
Title: Message Title JF Ravelo commented on JENKINS-54386 Re: preserveStashes does not work with parameter Btw Andrew Bayer, I think there is a problem of consistency in the docs regarding this point: in Preserving stashes for use with restarted stages it's mentioned as a normal parameter, but in Pipeline syntax it's documented as a named parameter. 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-54386) preserveStashes does not work with parameter
Title: Message Title JF Ravelo edited a comment on JENKINS-54386 Re: preserveStashes does not work with parameter Btw [~abayer], I think there is a problem of consistency in the docs regarding this point: in [Preserving stashes for use with restarted stages|https://jenkins.io/doc/book/pipeline/running-pipelines/#preserving-stashes-for-use-with-restarted-stages] it's mentioned as a normal named parameter, but in [Pipeline syntax|https://jenkins.io/doc/book/pipeline/syntax/#options] it's documented as a named normal parameter. 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-54833) Warnings Parser fails parsing log
Title: Message Title Norbert Lange created an issue Jenkins / JENKINS-54833 Warnings Parser fails parsing log Issue Type: Bug Assignee: Ulli Hafner Attachments: build.tar.xz Components: warnings-ng-plugin Created: 2018-11-23 10:49 Environment: Jenkins ver. 2.138.3 (Docker Hub) Wanings NG 1.0.0-beta5 Priority: Major Reporter: Norbert Lange The log is attached, this is a freestyle job and 2 warnings parsers are configured (Make + GCC and a custom Groovy parser). After the build, the plugin fails with the following output, while also marking the build as failure. Archiving artifacts Skipping issues blame since Git is the only supported SCM up to now. [GNU Make + GNU C Compiler (gcc)] Searching for all files in '/home/build/jenkins/jenkins/workspace/poe-baseline.binaries.tfs' that match the pattern 'build.log' [GNU Make + GNU C Compiler (gcc)] -> found 1 file [GNU Make + GNU C Compiler (gcc)] Successfully parsed file /home/build/jenkins/jenkins/workspace/poe-baseline.binaries.tfs/build.log [GNU Make + GNU C Compiler (gcc)] -> found 3 issues (skipped 2022 duplicates) ERROR: Build step failed with exception java.nio.charset.MalformedInputException: Input length = 1 at java.nio.charset.CoderResult.throwException(CoderResult.java:281) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) at
[JIRA] (JENKINS-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Grigor Lechev commented on JENKINS-54757 Re: High CPU caused by dumping the classloader in CpsFlowExecution I've attached a couple of screenshots from JVM and a thread dump. This is after removing the log line at 1345. The CPU consumption is lower than before, but it's still pretty high. 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-54386) preserveStashes does not work with parameter
Title: Message Title Jan Hoppe commented on JENKINS-54386 Re: preserveStashes does not work with parameter Yes, that works! The example in https://jenkins.io/doc/book/pipeline/syntax/ should be 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-54832) Groovy Parser cannot access console log
Title: Message Title Norbert Lange created an issue Jenkins / JENKINS-54832 Groovy Parser cannot access console log Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-23 10:38 Environment: Jenkins ver. 2.138.3 (Docker Hub) Wanings NG 1.0.0-beta5 Priority: Minor Reporter: Norbert Lange (discussion is split from JENKINS-54759) Issue console parsers currently run on the master and for security reasons, this excludes the customizable Groovy Parser. for an user this is surprising and adding a custom warning parser will need changes in the buildscript to dump output to a log file, ideally adding a parser would not otherwise affect existing jobs . not piping would be the most clear, and similar to the scripts you would run on a local build piping it just to a file will remove all visible status during execution naively splitting it (eg. | tee file.log) will mean the error state of the script doing the build will vanish. see here additionally storing and restoring the errors state of the script adds boilerplate code just to reiterate how invasive this change is, here is my current (POSIX Shell) workaround with variant 4): before: sh buildscript.sh ARGS...
[JIRA] (JENKINS-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Grigor Lechev updated an issue Jenkins / JENKINS-54757 High CPU caused by dumping the classloader in CpsFlowExecution Change By: Grigor Lechev Attachment: memory-sampling.png Attachment: cpu-sampling.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-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Grigor Lechev updated an issue Jenkins / JENKINS-54757 High CPU caused by dumping the classloader in CpsFlowExecution Change By: Grigor Lechev Attachment: tdump-23-11.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-54831) False-Positive CVE-2017-2604 after update of OWASP Dependency-Check
Title: Message Title Robert Paasche updated an issue Jenkins / JENKINS-54831 False-Positive CVE-2017-2604 after update of OWASP Dependency-Check Change By: Robert Paasche Summary: False-Positive CVE-2017-2604after update of OWASP Dependency-Check 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-54386) preserveStashes does not work with parameter
Title: Message Title JF Ravelo commented on JENKINS-54386 Re: preserveStashes does not work with parameter The problem is that preserveStashes() receives a named parameter, so instead of: preserveStashes(5) the value has to be passed this way: preserveStashes(buildCount: 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-54831) False-Positive CVE-2017-2604
Title: Message Title Robert Paasche created an issue Jenkins / JENKINS-54831 False-Positive CVE-2017-2604 Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2018-11-23 10:30 Priority: Blocker Reporter: Robert Paasche Since version 4.0.0 of the plugin "OWASP Dependency-Check" in every project using quartz, we see the following vulnerability: /WEB-INF/lib/quartz-2.3.0.jar , CVE-2017-2604 , Severity: Medium In Jenkins before versions 2.44, 2.32.2 low privilege users were able to act on administrative monitors due to them not being consistently protected by permission checks (SECURITY-371). These projects dose not use jenkins dependencies. Workaround: downgrade plugin to 3.3.4. Add Comment
[JIRA] (JENKINS-54830) Goup mail user are not receiving but shows as recipient list
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-54830 Goup mail user are not receiving but shows as recipient list Change By: Priyanga G For international group mail recipients are not able to recievw mail but it shows in recipient list.[somegr...@groups.int.example.com|mailto:somegr...@groups.int.example.com] Creating joobs jobs in jenkins Jenkins using .yml file for ex:- email-ext: recipients: [priyang...@example.com|mailto:priyang...@example.com] siva-subramania...@example.com thavamani.r...@example.com nithya.gane...@example.com [somegroup|mailto:somegr...@groups.int.example.com]@groups.int.example.com smegr...@example.com gavin.breb...@example.com content-type: html Note: somegr...@example.com==> can able to see the mail[somegr...@groups.int.example.com|mailto:somegr...@groups.int.example.com]==>not able to see 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-39143) Stage view disappears after restarting jenkins
Title: Message Title Omar Malik commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Here is my Stack Trace. Stack trace java.lang.IllegalStateException: Matching start node 3 lost from deserialization at org.jenkinsci.plugins.workflow.graph.BlockEndNode.getStartNode(BlockEndNode.java:65) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.getNodeType(ForkScanner.java:190) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:592) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.next(AbstractFlowScanner.java:212) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:564) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:768) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:633) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:321) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:309) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30) Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at
[JIRA] (JENKINS-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.
Title: Message Title Dawn Minion commented on JENKINS-48879 Re: User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages. Still present in Blue Ocean 1.9.0. Really annoying being unable to see how our parallel stages are doing when one is skipped, have to resort to sifting through the classic console logs. 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-54830) Goup mail user are not receiving but shows as recipient list
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-54830 Goup mail user are not receiving but shows as recipient list Change By: Priyanga G Labels: email-ext 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-54830) Goup mail user are not receiving but shows as recipient list
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-54830 Goup mail user are not receiving but shows as recipient list Change By: Priyanga G For international group mail recipients are not able to recievw mail but it shows in recipient list. [ somegr...@groups.int.example.com |mailto:somegr...@groups.int.example.com] Creating joobs in jenkins using .yml file 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-54830) Goup mail user are not receiving but shows as recipient list
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-54830 Goup mail user are not receiving but shows as recipient list Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-11-23 09:49 Priority: Critical Reporter: Priyanga G For international group mail recipients are not able to recievw mail but it shows in recipient list. somegr...@groups.int.example.com Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54772) computer//systemInfo doesn't report full Environment
Title: Message Title Pavel Janoušek updated JENKINS-54772 Jenkins / JENKINS-54772 computer//systemInfo doesn't report full Environment Change By: Pavel Janoušek 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-54772) computer//systemInfo doesn't report full Environment
Title: Message Title Pavel Janoušek commented on JENKINS-54772 Re: computer//systemInfo doesn't report full Environment PR sent. 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-54829) Nunit Plugin: MAX_PATH is too long for a few windows systems
Title: Message Title Martin Kadner created an issue Jenkins / JENKINS-54829 Nunit Plugin: MAX_PATH is too long for a few windows systems Issue Type: Bug Assignee: Alex Earl Components: nunit-plugin Created: 2018-11-23 09:36 Environment: Windows Server 2012 R2 Jenkins ver. 2.138.2 Nunit ver. 0.23 Priority: Critical Reporter: Martin Kadner The NUnitReportTransformer includes a MAX_PATH of 260. A few windows systems are still able to handle only path length of maximum 256. Add Comment
[JIRA] (JENKINS-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Ben Herfurth edited a comment on JENKINS-54757 Re: High CPU caused by dumping the classloader in CpsFlowExecution Encountering the same issue here. Jenkins 2.138.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-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Ben Herfurth commented on JENKINS-54757 Re: High CPU caused by dumping the classloader in CpsFlowExecution Encountering the same issue here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52935) Git LFS failing clone
Title: Message Title julien staub commented on JENKINS-52935 Re: Git LFS failing clone Hi I had no time to continue investigation. However, thank you for this update. Git LFS pull before checkout seems to have solved the problem. 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-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber closed an issue as Fixed Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54791) VCE for AACD with exam cram that you ought not miss | bootcamp | exam cram 50% OFF Coupon : AACD-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54791 VCE for AACD with exam cram that you ought not miss | bootcamp | exam cram 50% OFF Coupon : AACD-50OFF 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-54804) Try not to miss these 310-013 Questions before test | free test | flashcards 50% OFF Coupon : 310-013-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54804 Try not to miss these 310-013 Questions before test | free test | flashcards 50% OFF Coupon : 310-013-50OFF 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-54800) Pass4sure AHM-540 hot accreditation | test questions | practice questions 50% OFF Coupon : AHM-540-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54800 Pass4sure AHM-540 hot accreditation | test questions | practice questions 50% OFF Coupon : AHM-540-50OFF 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-54798) Lastest CertKillers.net AHM-520 Q for Best exam Prep | mock exam | cheat sheet 50% OFF Coupon : AHM-520-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54798 Lastest CertKillers.net AHM-520 Q for Best exam Prep | mock exam | cheat sheet 50% OFF Coupon : AHM-520-50OFF 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-54794) Get test questions and answers - mock exam and test questions with our A30-327 Practice Test | study guide | test questions 50% OFF Coupon : A30-327-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54794 Get test questions and answers - mock exam and test questions with our A30-327 Practice Test | study guide | test questions 50% OFF Coupon : A30-327-50OFF 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-54806) CertKillers.net genuine questions of API-571 are adequate | exam prep | practice questions 50% OFF Coupon : API-571-50OFF
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-54806 CertKillers.net genuine questions of API-571 are adequate | exam prep | practice questions 50% OFF Coupon : API-571-50OFF 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.
