[JIRA] (JENKINS-51415) Implementation of command transport for RMI
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-51415 Implementation of command transport for RMI Issue Type: Task Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-05-18 06:57 Priority: Major Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenki
[JIRA] (JENKINS-51414) Implementation of command transport for command invocation
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-51414 Implementation of command transport for command invocation Issue Type: Task Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-05-18 06:56 Priority: Major Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Googl
[JIRA] (JENKINS-51413) Implementation of producer-consumer basic communication
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-51413 Implementation of producer-consumer basic communication Issue Type: Task Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-05-18 06:55 Priority: Major Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google G
[JIRA] (JENKINS-51413) Implementation of producer-consumer basic communication
Title: Message Title Pham Vu Tuan started work on JENKINS-51413 Change By: Pham Vu Tuan Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51340) Create Jenkinsfile for the repository
Title: Message Title Pham Vu Tuan updated JENKINS-51340 Jenkins / JENKINS-51340 Create Jenkinsfile for the repository Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51340) Create Jenkinsfile for the repository
Title: Message Title Pham Vu Tuan updated JENKINS-51340 Jenkins / JENKINS-51340 Create Jenkinsfile for the repository Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51412) waitforqualitygate directive does not work for multiple sonar analysis in pipeline
Title: Message Title Avijit Pal updated an issue Jenkins / JENKINS-51412 waitforqualitygate directive does not work for multiple sonar analysis in pipeline Change By: Avijit Pal The waitforqualitygate directive does not work with multiple sonar analysis with withSonarQubeEnv directive in Jenkins pipeline . If there are multiple withSonarQubeEnv directive with corresponding waitforqualitygate directive, the taskid used by all waitforqualitygate is only for the first withSonarQubeEnv directive. Hence the second or the following waitforqualitygate directive provides false results which refers to the task id for first withSonarQubeEnv directive not for second or following withSonarQubeEnv directive. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For mor
[JIRA] (JENKINS-51412) waitforqualitygate directive does not work for multiple sonar analysis in pipeline
Title: Message Title Avijit Pal created an issue Jenkins / JENKINS-51412 waitforqualitygate directive does not work for multiple sonar analysis in pipeline Issue Type: Improvement Assignee: Rafael Ramos Components: sonar-quality-gates-plugin Created: 2018-05-18 06:34 Environment: Jenkins 2.122 Pipeline 2.5 Priority: Major Reporter: Avijit Pal The waitforqualitygate directive does not work with multiple sonar analysis with withSonarQubeEnv directive. If there are multiple withSonarQubeEnv directive with corresponding waitforqualitygate directive, the taskid used by all waitforqualitygate is only for the first withSonarQubeEnv directive. Hence the second or the following waitforqualitygate directive provides false results which refers to the task id for first withSonarQubeEnv directive not for second or following withSonarQubeEnv directive. Add Comment
[JIRA] (JENKINS-51151) GSoC: Community Bonding tasks for Remoting over Message Bus plugin
Title: Message Title Pham Vu Tuan updated JENKINS-51151 Jenkins / JENKINS-51151 GSoC: Community Bonding tasks for Remoting over Message Bus plugin Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51151) GSoC: Community Bonding tasks for Remoting over Message Bus plugin
Title: Message Title Pham Vu Tuan updated JENKINS-51151 Jenkins / JENKINS-51151 GSoC: Community Bonding tasks for Remoting over Message Bus plugin Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51152) Start discussion in the mailing list
Title: Message Title Pham Vu Tuan updated JENKINS-51152 Jenkins / JENKINS-51152 Start discussion in the mailing list Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51152) Start discussion in the mailing list
Title: Message Title Pham Vu Tuan updated JENKINS-51152 Jenkins / JENKINS-51152 Start discussion in the mailing list Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51152) Start discussion in the mailing list
Title: Message Title Pham Vu Tuan started work on JENKINS-51152 Change By: Pham Vu Tuan Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51147 Re: Plugin Kubernetes Continuous Deploy Plugin makes input command fail Code changed in jenkins User: Menghua Xiao Path: pom.xml http://jenkins-ci.org/commit/kubernetes-cd-plugin/64b145d0d5403e1ad7ddcfe833569c993ded8672 Log: Merge pull request #37 from ArieShout/jep200 Update azure-commons version to pick up XStream whitelist (JENKINS-51147) Compare: https://github.com/jenkinsci/kubernetes-cd-plugin/compare/29f90c623843...64b145d0d540 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51147 Re: Plugin Kubernetes Continuous Deploy Plugin makes input command fail Code changed in jenkins User: Menghua Xiao Path: pom.xml http://jenkins-ci.org/commit/kubernetes-cd-plugin/8a2eedc8c8a1b3efe2a8f690c3690d32f138e953 Log: Update azure-commons version to pick up XStream whitelist (JENKINS-51147) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51340) Create Jenkinsfile for the repository
Title: Message Title Pham Vu Tuan started work on JENKINS-51340 Change By: Pham Vu Tuan Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51342) Link Google Drive and Timeline from the project page on jenkins.io
Title: Message Title Pham Vu Tuan resolved as Fixed Jenkins / JENKINS-51342 Link Google Drive and Timeline from the project page on jenkins.io Change By: Pham Vu Tuan Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-51395 Re: withDockerRegistry([...]) syntax no longer accepted The patch works. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37072) Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null"
Title: Message Title Kazuhide Takahashi commented on JENKINS-37072 Re: Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null" I submitted a PR #95 to github with a modification that seems to be related to this article. Please someone use snapshots and check the problem is solved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51408) Logon failure when testing config
Title: Message Title Leandro França closed an issue as Not A Defect When the username belongs from a AD domain, it need to be informated. Jenkins / JENKINS-51408 Logon failure when testing config Change By: Leandro França Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit ht
[JIRA] (JENKINS-51408) Logon failure when testing config
Title: Message Title Leandro França started work on JENKINS-51408 Change By: Leandro França Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51408) Logon failure when testing config
Title: Message Title Leandro França commented on JENKINS-51408 Re: Logon failure when testing config Sorry Alex, you are right. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51081) no issues found verdict for any issue
Title: Message Title Tatiana Didik commented on JENKINS-51081 Re: no issues found verdict for any issue Zlatko Mozanic see https://plugins.jenkins.io/sonar-gerrit Project Settings section Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51411) Docker Pipeline Plugin: NPE Regression in 1.16
Title: Message Title
Illya Chekrygin created an issue
Jenkins / JENKINS-51411
Docker Pipeline Plugin: NPE Regression in 1.16
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2018-05-17 23:48
Labels:
jenkins docker
Priority:
Major
Reporter:
Illya Chekrygin
After upgrading to 1.16 Pipeline segment: withDockerRegistry([credentialsId: 'gcr:long-disk-191222', url: 'https://gcr.io']) { {{ sh "docker push $IMAGE_REPO:$IMAGE_TAG"}} } Error: java.lang.NullPointerException at org.jenkinsci.plugins.docker.workflow.RegistryEndpointStep$Execution.newKeyMaterialFactory(RegistryEndpointStep.java:81) at org.jenkinsci.plugins.docker.workflow.AbstractEndpointStepExecution.start(AbstractEndpointStepExecution.java:44) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuk
[JIRA] (JENKINS-33051) Groovy Star-Dot operator not supported in sandbox
Title: Message Title Graham Burgess edited a comment on JENKINS-33051 Re: Groovy Star-Dot operator not supported in sandbox I just hit this bug while building a shared library that really could use the spread (*) operator to spread method params! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33051) Groovy Star-Dot operator not supported in sandbox
Title: Message Title Graham Burgess commented on JENKINS-33051 Re: Groovy Star-Dot operator not supported in sandbox I just hit this bug while building a shared library that really could use the spread operator to spread method params! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-51232
Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Change By:
Cyrille Le Clerc
Context:Trying to move .zip file from Nexus Maven repository using Jenkins' withMaven plugin. However, Jenkins incorrectly references Parent POM file when there isn't a POM file in the repository.Error Message (With redacted URL):{noformat}Failed to execute goal org.apache.maven.plugins:maven-dependency- plugin:3.1.0:get (default-cli) on project standalone-pom: Couldn't download artifact: Failed to read artifact descriptor for com.company.app.apigee:template-api:zip:dev:LATEST: Could not transfer artifact com.company.app.apigee:parent-pom:pom:1.0 from/to maven-snapshots (http://app-apigw-devops-nexus.srv.company:8081/repository/maven- snapshots/): Failed to transfer file: http://app-apigw-devops- nexus.srv.company:8081/repository/maven- snapshots/com/company/app/apigee/parent-pom/1.0/parent-pom-1.0.pom. Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 1.0. -> [Help 1]{noformat}Input to Jenkins' Pipeline configuration:{code:java}node { stage('Deploy from Nexus') { withMaven(maven: 'M3') { sh 'mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:get ' +'-Dartifact=com.company.app.apigee:template-api:LATEST:zip:dev ' +'-DremoteRepositories=maven-snapshots::default::http://app-apigw- devops-nexus.srv.company:8081/repository/maven-snapshots/ ' +'-Dtransitive=false -e -X' } } }{code}Additional Info:Content of Template-api-1.0-20180509.042951-1.pom:{code:xml} 4.0.0 com.company.app.apigee template-api 1.0-SNAPSHOT zip{code}Content of maven-metadata.xml:{code:xml} com.company.app.apigee template-api 1.0-SNAPSHOT20180509050620 {code}
Add Comment
[JIRA] (JENKINS-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title Cyrille Le Clerc commented on JENKINS-51232 Re: Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files. formatting your error message, I found "Repository version policy: SNAPSHOT does not allow version: 1.0" It seems that your maven repository server says that you try to get the released version "1.0" from the "snapshot" repository. Can you try to verify what is the version mapped by the "LATEST" flag. Could someone have created the 1.0 release of your artifact? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-51232
Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Change By:
Cyrille Le Clerc
Context:Trying to move .zip file from Nexus Maven repository using Jenkins' withMaven plugin. However, Jenkins incorrectly references Parent POM file when there isn't a POM file in the repository.Error Message (With redacted URL):{ { noformat} Failed to execute goal org.apache.maven.plugins:maven-dependency- plugin:3.1.0:get (default-cli) on project standalone-pom:Couldn't download artifact: Failed to read artifact descriptor for com.company.app.apigee:template-api:zip:dev:LATEST:Could not transfer artifact com.company.app.apigee:parent-pom:pom:1.0from/to maven-snapshots (http://app-apigw-devops-nexus.srv.company:8081/repository/maven- snapshots/):Failed to transfer file: http://app-apigw-devops- nexus.srv.company:8081/repository/maven- snapshots/com/company/app/apigee/parent-pom/1.0/parent-pom-1.0.pom.Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 1.0. -> [Help 1] {noformat } } Input to Jenkins' Pipeline configuration:{ { code:java} node \ {stage('Deploy from Nexus') \ {withMaven(maven: 'M3') \ {sh 'mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:get ' + '-Dartifact=com.company.app.apigee:template-api:LATEST:zip:dev ' + '-DremoteRepositories=maven-snapshots::default::http://app-apigw- devops-nexus.srv.company:8081/repository/maven-snapshots/ ' + '-Dtransitive=false -e -X'}}} {code } } Additional Info:Content of Template-api-1.0-20180509.042951-1.pom:{ { code:xml} < ?xml version="1.0" encoding="UTF-8"?>< project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> 4.0.0 com.company.app.apigee template-api 1.0-SNAPSHOT zip{code } } Content of maven-metadata.xml:{ { code:xml} < ?xml version="1.0" encoding="UTF-8"?>< metadata> com.company.app.apigee template-api 1.0-SNAPSHOT 20180509050620 {code } }
[JIRA] (JENKINS-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-51232 Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files. Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Carlos Sanchez commented on JENKINS-51353 Re: In declarative pipeline, volumes and imagepullsecrets needed You can do it with the yaml syntax Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51410) Error stopping mongod service inside Docker container
Title: Message Title
Alexander Reifert created an issue
Jenkins / JENKINS-51410
Error stopping mongod service inside Docker container
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker, pipeline
Created:
2018-05-17 21:38
Environment:
Jenkins 2.107.3 Amazon Linux 4.14.33-51.37.amzn1.x86_64 Docker version 17.12.1-ce, build 3dfb8343b139d6342acfd9975d7f1068b5b1c3d3 Java OpenJDK version 1.8.0_171 Jenkins installed via YUM, builds run on slaves connected via SSH
Labels:
docker pipeline Amazon
Priority:
Minor
Reporter:
Alexander Reifert
I have a Docker image with MongoDB installed. My pipeline tries to start the mongod service, run some database commands, and then stop the mongod service. When trying to stop the mongod service, the pipeline hangs for 5 minutes and then returns a failed exit status. I've confirmed that I'm able to run these same commands within a Docker container manually, on the same machine, with no issues, so this seems like a Jenkins issue of some sort. To reproduce: Create an image using the following Dockerfile:
FROM amazonlinux
ENV MONGO_VERSION=3.6
RUN echo -e "[mongodb-org-${MONGO_VERSION}]\nname=MongoDB\nbaseurl=https://repo.mongodb.org/yum/amazon/2013.03/mongodb-org/${MONGO_VERSION}/x86_64/\nenabled=1\ngpgcheck=1\ngpgkey=https://www.mongodb.org/static/pgp/server-${MONGO_VERSION}.asc\n" > /etc/yum.repos.d/mongodb.repo \
&& yum groupinstall -y "Deve
[JIRA] (JENKINS-51408) Logon failure when testing config
Title: Message Title Alex Earl commented on JENKINS-51408 Re: Logon failure when testing config If it's a domain account, can you verify you specified the domain in the username field? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51409) SauceConnect PID Not Being Removed
Title: Message Title Sam Schiavo created an issue Jenkins / JENKINS-51409 SauceConnect PID Not Being Removed Issue Type: Bug Assignee: Yeh Fang Attachments: sc.log Components: sauce-ondemand-plugin Created: 2018-05-17 21:14 Environment: Jenkins version 2.118 Sauce OnDemand plugin version 1.175 Labels: plugin jenkins sauce-connect SauceOnDemand Priority: Minor Reporter: Sam Schiavo When we run a SauceConnect job, it leaves the process running so the PID file is never removed. The next job tries to run and gets the error message "Error creating pidfile /tmp/sc_client.pid: resource temporarily unavailable" I can manually kill the process, remove the sc_client.pid file, then start the job and it runs with no issues. At the end of the job that runs correctly, there is a java error, but I'm not sure if it is related or not. Finished post-build for Sauce Labs plugin Starting Sauce Labs test publisher Finished Sauce Labs test publisher ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.processBuildOutput(SauceOnDemandReportPublisher.java:349) at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:162) at hudson.plugins.sauce_ondemand.SauceOnDemandTestPublisher.addTestDataPublishersToBuildReport(SauceOnDemandTestPublisher.
[JIRA] (JENKINS-51408) Logon failure when testing config
Title: Message Title Leandro França created an issue Jenkins / JENKINS-51408 Logon failure when testing config Issue Type: Bug Assignee: Alex Earl Components: publish-over-cifs-plugin Created: 2018-05-17 20:36 Environment: Jenkins ver. 2.107.3 Publish Over CIFS 0.10 Labels: publish-over-cifs Priority: Critical Reporter: Leandro França After plugin update from 0.9 to 0.10 some connections stop works. To solve the problem I downgrade the plugin version and everything works fine! The problem occurs on windows shared folder. Stacktrace: jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad password. at jcifs.smb.SmbTransportImpl.checkStatus(SmbTransportImpl.java:1330) at jcifs.smb.SmbTransportImpl.checkStatus(SmbTransportImpl.java:1509) at jcifs.smb.SmbTransportImpl.sendrecv(SmbTransportImpl.java:980) at jcifs.smb.SmbTransportImpl.send(SmbTransportImpl.java:1475) at jcifs.smb.SmbTransportImpl.send(SmbTransportImpl.java:1439) at jcifs.smb.SmbSessionImpl.sessionSetupSMB1(SmbSessionImpl.java:878) at jcifs.smb.SmbSessionImpl.sessionSetup(SmbSessionImpl.java:466) at jcifs.smb.SmbSessionImpl.send(SmbSessionImpl.java:358) at jcifs.smb.SmbSessionImpl.send(SmbSessionImpl.java:336) at jcifs.smb.SmbTreeImpl.treeConnect(SmbTreeImpl.java:600) at jcifs.smb.SmbTreeConnection.connectTree(SmbTreeConnec
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title David Taylor commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Why is this marked as Resolved? The original request was to be able to see build history of pipelines under each node's "Build History" section. Its May 2018 and pipelines still do not show up in this section. This ticket should not be marked as Resolved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51283) CASC_JENKINS_CONFIG environment variable is not used anymore
Title: Message Title Baptiste Mathus resolved as Fixed Jenkins / JENKINS-51283 CASC_JENKINS_CONFIG environment variable is not used anymore Change By: Baptiste Mathus Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title Jesse Glick commented on JENKINS-51397 Re: docker login being called without server-related environment variables (The downloads above also include the fix for JENKINS-51395.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42210) Support for Jenkins pipelines
Title: Message Title Josh McFarlane commented on JENKINS-42210 Re: Support for Jenkins pipelines This should be available in 1.19 going forward - https://github.com/jenkinsci/aws-codedeploy-plugin/releases/tag/codedeploy-1.19 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42210) Support for Jenkins pipelines
Title: Message Title Josh McFarlane resolved as Fixed Jenkins / JENKINS-42210 Support for Jenkins pipelines Change By: Josh McFarlane Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist Josh McFarlane Great, thanks a lot! I have reassigned the open issues to you and also made you a default assignee for the new ones Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42210) Support for Jenkins pipelines
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-42210 Support for Jenkins pipelines Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39752) Version file parameter in codedeploy-plugin doesn't seem to work...
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-39752 Version file parameter in codedeploy-plugin doesn't seem to work... Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31650) Issue with variable in "AWS CodeDeploy Deployment Group" field
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-31650 Issue with variable in "AWS CodeDeploy Deployment Group" field Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31971) Using old SDK, deploy is broken because of jdk8u60+ and old joda-time version
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-31971 Using old SDK, deploy is broken because of jdk8u60+ and old joda-time version Change By: Oleg Nenashev Assignee: Adrien Lecharpentier Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31332) CodeDeploy Plugin revision date time pattern
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-31332 CodeDeploy Plugin revision date time pattern Change By: Oleg Nenashev Assignee: Nicolas De Loof Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-50974 AWS CodeDeploy plug-in fails with new JEP-200 whitelist Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38474) Error after updating AWS SDK to 1.11.37
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-38474 Error after updating AWS SDK to 1.11.37 Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31709) Support more then 1 post build code deployment
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-31709 Support more then 1 post build code deployment Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33031) No proxy authentication for AWS codedeploy plugin
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-33031 No proxy authentication for AWS codedeploy plugin Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41003) eu-west2 missing
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-41003 eu-west2 missing Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32750) Server-Side Encryption
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-32750 Server-Side Encryption Change By: Oleg Nenashev Assignee: Andrew Fitz Gibbon Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31331) CodeDeploy Plugin bucket region error
Title: Message Title Oleg Nenashev assigned an issue to Josh McFarlane Reassigned the issue to Josh McFarlane according to his comment in JENKINS-50974 Jenkins / JENKINS-31331 CodeDeploy Plugin bucket region error Change By: Oleg Nenashev Assignee: Nicolas De Loof Josh McFarlane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Josh McFarlane commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist Yup - I'm happy to be first point of contact for these issues and can re-assign within our team as necessary. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist Josh McFarlane IIUC you are the maintainer according to https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-codedeploy.yml , right? I will change the default assignee. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title Jesse Glick commented on JENKINS-51397 Re: docker login being called without server-related environment variables BTW Nico Navarrete the version of the docker plugin is probably irrelevant here. docker-commons and docker-workflow are the plugins involved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title Jesse Glick commented on JENKINS-51397 Re: docker login being called without server-related environment variables Nico Navarrete Scott Williams Hans Schulz et al., anyone care to test a proposed fix? If so, use the Advanced tab to manually update this build of docker-commons and of docker-workflow. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47005 Let user specify p4 workspace root in manual config Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46321) JSONException: null object when 'auths' key is not exist in .docker/config.json file.
Title: Message Title Jesse Glick commented on JENKINS-46321 Re: JSONException: null object when 'auths' key is not exist in .docker/config.json file. See JENKINS-51407. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46321) JSONException: null object when 'auths' key is not exist in .docker/config.json file.
Title: Message Title Jesse Glick resolved as Won't Fix Do not plan to work on that since the new APIs normally call docker login and do not use that code path. Jenkins / JENKINS-46321 JSONException: null object when 'auths' key is not exist in .docker/config.json file. Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick updated JENKINS-38018 Jenkins / JENKINS-38018 withDockerRegistry fails to authenticate with DockerHub Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Filed JENKINS-51406 & JENKINS-51407 for integration into other non-Pipeline plugins, so this issue can be considered strictly about Docker Pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38018 withDockerRegistry fails to authenticate with DockerHub Change By: Jesse Glick Component/s: docker-build-publish-plugin Component/s: docker-custom-build-environment-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Please do not comment further on this issue. Check JENKINS-51395 and JENKINS-51397, or file a fresh bug and link it here if you are sure you have encountered a distinct issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41051) withRegistry is not doing a "docker login"
Title: Message Title Jesse Glick resolved as Duplicate Already done. Jenkins / JENKINS-41051 withRegistry is not doing a "docker login" Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51406) Integrate with new docker login APIs
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51406 Integrate with new docker login APIs Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2018-05-17 19:38 Priority: Major Reporter: Jesse Glick Update the docker-commons dependency and see JENKINS-38018 for background. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51407) Integrate with new docker login APIs
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51407 Integrate with new docker login APIs Issue Type: Improvement Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2018-05-17 19:38 Priority: Major Reporter: Jesse Glick Update the docker-commons dependency and see JENKINS-38018 for background. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-51404 processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Josh McFarlane commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist Oleg Nenashev: Andrew no longer maintains the plugin - Is there a spot we need to update for new maintainers? CodeDeploy Plugin issues can be assigned to me Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title joe ferr commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite perfect, will do. I'll let you know the outcome. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title Jesse Glick updated JENKINS-51397 Jenkins / JENKINS-51397 docker login being called without server-related environment variables Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error joe ferr please download the pull request build and install it in your environment. If it resolves the problem, please note that in the pull request or in this thread. I can't duplicate the problem. I'm relying on users to report their success with the proposed change. Evaluating a pull request by running it in your environment is a great way to be a contributor without compiling anything and with an easy way to "fall back" to the previous version if the pull request build doesn't meet your needs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title joe ferr commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Apologies if this is the wrong place for this. I'm an end user, not a contributor. Seems like the PR has been ready for quite some time. This issue is actually huge for us. We have a Jenkins based kubernetes continuous delivery system (homegrown, I grew it!) that uses the multi-scm plugin and uses around 5 git repos per environment. We deploy to 8 envs for our production deploy so we are getting 40+ repos w. every deploy with up to 30 deploys a dayso this impacts us at least once a day, more often multiple times a day. Any status updates on this? At my company this is getting very high visibility Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50481) Unable to check updates for plugins
Title: Message Title John Tomko commented on JENKINS-50481 Re: Unable to check updates for plugins I'm seeing this on Windows Server Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title Jesse Glick started work on JENKINS-51397 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46248) Deadlock in queue maintenance + node removal
Title: Message Title Alexey Grigorov commented on JENKINS-46248 Re: Deadlock in queue maintenance + node removal I have same problem, deadlocks started to appear daily Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title Jesse Glick updated JENKINS-51395 Fix available for download Jenkins / JENKINS-51395 withDockerRegistry([...]) syntax no longer accepted Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-51395 withDockerRegistry([...]) syntax no longer accepted Change By: Jesse Glick Assignee: Ivan Fernandez Calvo Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51395 withDockerRegistry([...]) syntax no longer accepted Change By: Jesse Glick Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51405) Snippetizer & DSL disagree on behavior of step w/ mandatory struct param + opt param
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51405 Snippetizer & DSL disagree on behavior of step w/ mandatory struct param + opt param Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-05-17 18:27 Priority: Minor Reporter: Jesse Glick See JENKINS-51395 for background. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51395 Re: withDockerRegistry([...]) syntax no longer accepted Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/docker/workflow/RegistryEndpointStep.java src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy src/test/java/org/jenkinsci/plugins/docker/workflow/RegistryEndpointStepTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/8c463ba72f69c0c0e1fca60c11fb5e88e3dbe0e4 Log: JENKINS-51395 Switching recommended syntax to inline arguments, while still supporting the old syntax. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Olivier Lamy >> you are using this plugin as well jira-steps-plugin ? I only configured both and do not use it in Jenkinsfile yet. My goal is to have SCM list of changes for the job + build result in a Jira comment. You think that I should disable Jira Steps Plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51395 Re: withDockerRegistry([...]) syntax no longer accepted Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/docker/workflow/RegistryEndpointStep.java src/main/java/org/jenkinsci/plugins/docker/workflow/ServerEndpointStep.java src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy src/test/java/org/jenkinsci/plugins/docker/workflow/RegistryEndpointStepTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/e8a1815cf41ba67a72ad7ce4384763f36143c4d1 Log: Merge pull request #138 from jglick/withDockerRegistry-syntax-JENKINS-51395 JENKINS-51395 Syntax problems in withDockerRegistry Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/c5a73943a283...e8a1815cf41b *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51395 Re: withDockerRegistry([...]) syntax no longer accepted Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/docker/workflow/RegistryEndpointStepTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/732e1bbf514a65893ebb381850884385e69b9ae1 Log: JENKINS-51395 At least reproduced problem in test. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" I suspect that there is a problem of a xerces jar with an incompatible / outdated version being pulled in Jenkins classpath. Can you please look at the following FAQ entry and verify which jar provides Xerces parsing library https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-WhydoIseemessages%22javax.xml.parsers.FactoryConfigurationError:Providerforclassjavax.xml.parsers.DocumentBuilderFactorycannotbecreated%22 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51374) Create a plugin skeleton
Title: Message Title Abhishek Gautam commented on JENKINS-51374 Re: Create a plugin skeleton What does "stub Pipeline source implementation" means? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51226) debian package must depend on *some* jre
Title: Message Title James Ladan commented on JENKINS-51226 Re: debian package must depend on *some* jre This doesn't feel all that 'minor' (current bug classification) when your package manager decides to uninstall default-jre-headless on update because no packages now depend on it, you miss that happening, and Jenkins fails to start after the server's scheduled 5am reboot, post-update. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50551) Trend Graph: Suppress First, Reference Build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50551 Re: Trend Graph: Suppress First, Reference Build Code changed in jenkins User: Ulli Hafner Path: src/main/java/io/jenkins/plugins/analysis/core/model/AnalysisResult.java http://jenkins-ci.org/commit/analysis-core-plugin/48bfcde2ea562a70149efe576f4ba8292009c22c Log: [FIXED JENKINS-50551] The first build should not produce new issues. *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50551) Trend Graph: Suppress First, Reference Build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50551 Re: Trend Graph: Suppress First, Reference Build Code changed in jenkins User: Ulli Hafner Path: src/test/java/io/jenkins/plugins/analysis/warnings/IssuesRecorderITest.java http://jenkins-ci.org/commit/warnings-plugin/a4cb31a6e67ab189b6b94eb1441f5e0944804bd3 Log: [FIXED JENKINS-50551] The first build should not produce new issues. *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26802) Copying artifacts from many projects
Title: Message Title Aaron Marasco commented on JENKINS-26802 Re: Copying artifacts from many projects I'm assuming that with pipelines, this is pretty much OBE. You can manipulate/loop variables and call the plugin as many times as you want. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51404 processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-05-17 17:00 Environment: Jenkins Core 2.107.x Maven-pipeline 3.5.6 Priority: Minor Reporter: Alex Taylor Issue: When running a maven process inside of a build an error popped up saying java.lang.IllegalAccessError: tried to access method org.apache.xerces.parsers.XML11Configuration.getFeature0(Ljava/lang/String;)Z from class org.apache.xerces.parsers.XIncludeAwareParserConfiguration at org.apache.xerces.parsers.XIncludeAwareParserConfiguration.getFeature(Unknown Source) at org.apache.xerces.parsers.AbstractDOMParser.reset(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:97) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050) It seems to come from the code here: https://github.com/jenkinsci/pipeline-maven-plugin/blob/1729e64250c10213ca428141092540bdeeaba97a/jenkins-plugin/src/main/java/org/jenkinsci/plu
[JIRA] (JENKINS-51163) Issues Tables is not updated after Ajax call
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-51163 Issues Tables is not updated after Ajax call Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Mark Waite commented on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
Zack Snyder sorry, but I don't use the email-ext plugin. I would assume that the block in your example which says
recipientProviders: [[$class: 'DevelopersRecipientProvider'],
[$class: 'CulpritsRecipientProvider'],
[$class: 'UpstreamComitterRecipientProvider']
] ${author_email},
should instead say:
recipientProviders: [[$class: 'DevelopersRecipientProvider'],
[$class: 'CulpritsRecipientProvider'],
[$class: 'UpstreamComitterRecipientProvider']
] author_email,
In this case, author_email is a variable.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You r
[JIRA] (JENKINS-51403) Allow simplified Pipeline surface syntax
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51403 Allow simplified Pipeline surface syntax Issue Type: Improvement Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2018-05-17 16:49 Labels: pipeline Priority: Minor Reporter: Jesse Glick For usability, PublishHTMLStep.DescriptorImpl should effectively inline parameters from HtmlPublisherTarget, so that the square brackets are not needed. Add Comment
[JIRA] (JENKINS-51403) Allow simplified Pipeline surface syntax
Title: Message Title Jesse Glick commented on JENKINS-51403 Re: Allow simplified Pipeline surface syntax The patch for JENKINS-51395 is an example. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51402) Incorrect region when unarchive
Title: Message Title
Ivan Fernandez Calvo created an issue
Jenkins / JENKINS-51402
Incorrect region when unarchive
Issue Type:
Bug
Assignee:
Unassigned
Components:
artifact-manager-s3-plugin
Created:
2018-05-17 16:46
Environment:
Jenkins core 2.122.1 Artifact Manager S3 Plugin https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fartifact-manager-s3-plugin/detail/master/22/artifacts
Priority:
Major
Reporter:
Ivan Fernandez Calvo
testing the big-file example the unarchive fails because the region selected is wrong, my EC2 instance and bucket are in us-west-2, but the request is made for us-east-1
stage('Unarchive') {
unarchive mapping: ["${file}": 'CentOS-7-x86_64-DVD-1505-01-unarchived.iso']
}
hudson.remoting.ProxyException: org.jclouds.aws.AWSResponseException: request GET https://my-bucket.s3.amazonaws.com/?prefix=cmm02/artifacts/big-file/3/artifacts/ HTTP/1.1 failed with code 400, error: AWSError{requestId='489396EF7035020C', requestToken='XXX=', code='AuthorizationHeaderMalformed', message='The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-2'', context='{Region=us-west-2, HostId=XXX=}'}
at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:75)
at org.jclouds.ht
[JIRA] (JENKINS-51336) Simplify configs on Configure System UI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51336 Re: Simplify configs on Configure System UI Code changed in jenkins User: Ulli Hafner Path: src/main/resources/io/jenkins/plugins/analysis/warnings/groovy/GroovyParser/config.jelly src/main/resources/parser/advanced.jelly src/main/resources/parser/advanced.properties src/main/resources/parser/advanced_de.properties src/main/resources/parser/advanced_ja.properties http://jenkins-ci.org/commit/warnings-plugin/910c263c444663a25e8736e9e8515174abaa8159 Log: JENKINS-51336 Integrated PR#122. Hide parser details in system config. See https://github.com/jenkinsci/warnings-plugin/pull/122 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder commented on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
Mark Waite Okay, with some minor changes I can retrive the mail address. However, how can I use it with ext-mail?
def author_email = bat(returnStdout:true, script:'git log -n 1 --pretty=format:%%ae')
echo "author E-mail is ${author_email}"
def currResult = getResultAsString(currentBuild)
def prevResult = getResultAsString(currentBuild.getPreviousBuild())
if (currResult != "SUCCESS" || prevResult != "SUCCESS")
{
echo 'send mail'
emailext body: '''${SCRIPT, template="xion-html.template"}''',
recipientProviders: [[$class: 'DevelopersRecipientProvider'],
[$class: 'CulpritsRecipientProvider'],
[$class: 'UpstreamComitterRecipientProvider']
] ${author_email},
subject: '[Jenkins]: ${JOB_NAME} ${BUILD_DISPLAY_NAME} - ' + currResult,
mimeType: 'text/html'
}
I got following error:
WorkflowScript: 74: expecting '}', found ',' @ line 74, column 66.
] ${author_email},
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51395) withDockerRegistry([...]) syntax no longer accepted
Title: Message Title Jesse Glick updated JENKINS-51395 Jenkins / JENKINS-51395 withDockerRegistry([...]) syntax no longer accepted Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
