[JIRA] [docker-workflow-plugin] (JENKINS-33608) Jenkins Pipeline Plugin Docker Integration Failure
Title: Message Title
Lou Sacco closed an issue as Fixed
I was able to get around this by installing docker-io on my slave from this Docker image and using a separate Docker host that could service the calls I needed to make to build, run and push my docker image to my registry.
I ended up using the following script to resolve this:
docker.withServer(DOCKER_MACHINE_HOSTNAME) { def image = docker.build(DOCKER_TAG, '.')
// Test container then stop and remove it def container = image.run('--name ' + DOCKER_CONTAINER_NAME) container.stop()
docker.withRegistry(DOCKER_REGISTRY, QUAY_CREDENTIALS_ID ) { image.push(DOCKER_APPLICATION_TAG) }
}
Jenkins / JENKINS-33608
Jenkins Pipeline Plugin Docker Integration Failure
Change By:
Lou Sacco
Status:
Open Closed
Assignee:
Lou Sacco
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [xunit-plugin] (JENKINS-33248) xUnit only calculates success for and reports results for single file when multiple are specified.
Title: Message Title Sebastian Troy assigned an issue to Gregory Boissinot Jenkins / JENKINS-33248 xUnit only calculates success for and reports results for single file when multiple are specified. Change By: Sebastian Troy Assignee: Gregory Boissinot Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Title: Message Title Kevin Bube commented on JENKINS-22853 Re: SEVERE: Trying to unexport an object that's already unexported Sorry, forgot to mention our Java version: java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) The standard on Debian Wheezy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33384) PluginServletFilters should be let clean up before the Jenkins singleton is cleared
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33384 PluginServletFilters should be let clean up before the Jenkins singleton is cleared Change By: Oliver Gondža Labels: 1.651-fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33681) Jenkins fails to restart with an exception
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33681 Jenkins fails to restart with an exception Change By: Oliver Gondža Labels: lts 1.651 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33891) Unexpected scrolling on job configuration page
Title: Message Title Daniel Beck commented on JENKINS-33891 Re: Unexpected scrolling on job configuration page gus reiber It's not useful to link to private Jenkins instances. Not even I know how to access that one (and for the purposes of this issue tracker, I don't want to know). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-samples-plugin] (JENKINS-33894) Overlapping of text while installing plugins
Title: Message Title Jothi Vignesh C created an issue Jenkins / JENKINS-33894 Overlapping of text while installing plugins Issue Type: Bug Assignee: Unassigned Attachments: Jenkins 2.0.png Components: ui-samples-plugin Created: 2016/Mar/30 8:22 AM Priority: Minor Reporter: Jothi Vignesh C Steps to reproduce: Install Jenkins Configure Proxy Choose required plugins and proceed The download log is overlapping with the progress bar and the text is unreadable. After that Jenkins home page is not loading in full screen, it is showing as popup only. Browser: Chrome 49.0.2623.108. OS: Windows 7.
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-33809 Find out what's wrong with the tests on the 2.0 branch requiring so much RAM Change By: Antonio Muñiz Attachment: java7-forked-booter-1.png Attachment: java7-forked-booter-2.png Attachment: java7-maven-launcher.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-33809
Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Change By:
Antonio Muñiz
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x.h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})h4. Jenkins 1.x1. Maven launcher process:!jenkins1-maven-launcher.png|width=400,height=300!2. Surefire booter:!jenkins1-surefire-booter.png|width=400,height=300!h4. Jenkins 2.01. Maven launcher process!jenkins2-maven-launcher.png|width=400,height=300!2. Surefire booter!jenkins2-surefire-booter.png|width=400,height=300!h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):Surefire forked booter 1:!forked-booter-1.png|width=550,height=300!Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle): !forked-booter-2.png|width=550,height=300!Maven launcher process:!maven-laucher.png|width=550,height=300! h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-forked-booter-1.png|width=750,height=250!Surefire forked booter 2: !java7-forked-booter-2.png|width=750,height=250!Maven launcher process:!java7-maven-launcher.png|width=750,height=250!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and st
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title Antonio Muñiz commented on JENKINS-33809 Re: Find out what's wrong with the tests on the 2.0 branch requiring so much RAM Description updated with reports of a full run on JDK 7. Memory usage does not show anything abnormal. Forked surefire booters use 400-600 MB as much and Maven launcher process doesn't go up to 300MB. I still think -Xmx1g is not really required. Maybe we could activate -XX:+HeapDumpOnOutOfMemoryError on both agents and master JVMs in https://ci.jenkins-ci.org so we get some hint next time it happens. I don't see anything else we can do here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32831 "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Change By: Oliver Gondža Labels: lts 1.651 - candidate fixed plugin plugin-manager regression updateCenter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33693) maven builder fails if latest maven on path on windows
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33693 maven builder fails if latest maven on path on windows Change By: Oliver Gondža Labels: 1. 565.1 651 -rejected lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B&R Corporate updated an issue Jenkins / JENKINS-33612 Provision error (Tried proxying due circular dependency) reported at startup Minimal configuration-file (Extended Email Templates), causing this issue on startup/restart. Change By: GMC Software Development B&R Corporate Attachment: org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B&R Corporate commented on JENKINS-33612 Re: Provision error (Tried proxying due circular dependency) reported at startup Hi, to reproduce this issue, I've setup a "fresh" installation of Jenkins 1.655 on a test-workstation with Windows 7 (x64) - to check, whether "it" also occurs on another machine with a minimal count of installed plugins. After updating the plugins (as currently released) and installing the Email-ext Template Plugin (+ Email-ext plugin) following (enabled) plugins are used: Plugin version ant 1.2 antisamy-markup-formatter 1.3 cloudbees-folder 5.6 credentials 1.26 cvs 2.12 email-ext
[JIRA] [git-plugin] (JENKINS-33878) "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled
Title: Message Title Kim Neunert commented on JENKINS-33878 Re: "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled I should have been more specific. The issue occurs, if you do a post-request. Something like this: $ curl -X POST http://somejenkins.somewhere/git/notifyCommit\?url\=ssh://g...@some.stash.repo:7999/dist/somerepo.git "Content-Type" content="text/html; charset=ISO-8859-1"/> Error 403 No valid crumb was included in the request HTTP ERROR 403 Problem accessing /git/notifyCommit. Reason: No valid crumb was included in the requestPowered by Jetty:// $ Seems to make a difference of the http-method for some reason: https://github.com/jenkinsci/jenkins/blob/4107d86328e907a34e23b09f21cd86340ae137ea/core/src/main/java/hudson/security/csrf/CrumbFilter.java#L56 And unfortunately, Atlassian stash's implementation of webhooks is using POST, not GET. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-33878) "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled
Title: Message Title Kim Neunert commented on JENKINS-33878 Re: "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled I just tested the Bitbucket Webhook to Jenkins which probably is doing a "proper" GET-request. https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkins/server/overview This fixes it for me. So eventually, this is caused by a misuse of the POST-request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32597 Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace Change By: Oliver Gondža Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33878) "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled
Title: Message Title Kim Neunert edited a comment on JENKINS-33878 Re: "Push notification from repository" does not work unless "Prevent Cross Site Request Forgery exploits" is disabled I just tested the Bitbucket Webhook to Jenkins which probably is doing a "proper" GET-request.https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkins/server/overviewThis fixes it for me. So eventually, this is caused by a misuse of the POST-request. Not sure what a proper resolution of this script is, feel free to close. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Change By: Oliver Gondža Labels: lts 1.651 - candidate rejected performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Change By: Oliver Gondža Labels: 1.651-rejected lts-candidate performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Oliver Gondža commented on JENKINS-33467 Re: CauseAction.causes can become huge I prefer not to backport this into 1.651.1 since fix in one of the affected plugins is not released yet. Plus, This is more of an improvement than a bug fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3 Change By: Oliver Gondža Labels: 1.651 jenkins sonar sonar-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3 Change By: Oliver Gondža Labels: 1.651 jenkins lts-candidate sonar sonar-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33681) Jenkins fails to restart with an exception
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33681 Jenkins fails to restart with an exception Change By: Oliver Gondža Labels: 1.651 .1 -fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33693) maven builder fails if latest maven on path on windows
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33693 maven builder fails if latest maven on path on windows Change By: Oliver Gondža Labels: 1.651 .1 -rejected lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28790 Sonar database credentials in build console output not masked since LTS version 1.596.3 Change By: Oliver Gondža Labels: 1.651.1-fixed jenkins sonar sonar-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32831 "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Change By: Oliver Gondža Labels: 1.651 .1 -fixed plugin plugin-manager regression updateCenter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33384) PluginServletFilters should be let clean up before the Jenkins singleton is cleared
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33384 PluginServletFilters should be let clean up before the Jenkins singleton is cleared Change By: Oliver Gondža Labels: 1.651 .1 -fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Change By: Oliver Gondža Labels: 1.651 .1 -rejected lts-candidate performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33895) build-pipeline-plugin does not support the pipeline (workflow) jobs
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-33895 build-pipeline-plugin does not support the pipeline (workflow) jobs Change By: Sorin Sbarnea Labels: Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33895) build-pipeline-plugin does not support the pipeline (workflow) jobs
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-33895 build-pipeline-plugin does not support the pipeline (workflow) jobs Issue Type: Bug Assignee: Matthew DeTullio Components: build-pipeline-plugin, multi-branch-project-plugin, workflow-plugin Created: 2016/Mar/30 10:13 AM Priority: Critical Reporter: Sorin Sbarnea It seems that the build-pipeline-plugin does not support any of the new-style jenkins projects (jenkinsfile ones). As they are quite usable now and with them being default in Jenkins 2.0, this seems to make this plugin not only useless but also confusing because of its name, people would assume that they can use it with the new jobs but that's not true. Add Comment
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: Oliver Gondža Labels: 1.651.1-fixed jnlp remoting security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28289 JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Change By: Oliver Gondža Labels: 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected lts 1.651.1 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19565) dropdownDescriptorSelector is loosing the context of `it`
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-19565 dropdownDescriptorSelector is loosing the context of `it` Change By: Oliver Gondža Labels: credentials lts-candidate stapler Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-30195) Option for appending an unique descriptions only
Title: Message Title Leandro Lucarella commented on JENKINS-30195 Re: Option for appending an unique descriptions only BTW, the current state is not even what the help message states for matrix jobs: "Also set the description on a multi-configuration build. The first description found for any of the invididual builds will be used as description for the multi-configuration build. " Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25440) Failed to create Guice container from all the plugins
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-25440 Failed to create Guice container from all the plugins Change By: Oliver Gondža Labels: classloader lts 1.651.1 - candidate fixed classloader robustness startup Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33377) Functions.isExtensionsAvailable() should return false during termination
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33377 Functions.isExtensionsAvailable() should return false during termination Change By: Oliver Gondža Labels: lts 1.651.1 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33681) Jenkins fails to restart with an exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33681 Re: Jenkins fails to restart with an exception Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/util/PluginServletFilter.java http://jenkins-ci.org/commit/jenkins/c57af86955c2c799930a93cd955ed7f98c7dc504 Log: [FIXED JENKINS-33681] Plugin filters were failing to be removed and blocking restart (cherry picked from commit a5febd7666fd78542d45428505cc62c067315c43) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33384) PluginServletFilters should be let clean up before the Jenkins singleton is cleared
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33384 Re: PluginServletFilters should be let clean up before the Jenkins singleton is cleared Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/util/PluginServletFilter.java core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/d72076c47e09c7e7b4f813ac603bb07bdb476283 Log: [FIXED JENKINS-33384] clean up the PluginServletFilter instances on Jenkins.cleanUp() (cherry picked from commit abf9fd36582ce6277dec929e89f078678e587209) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32831 Re: "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Code changed in jenkins User: Valentina Armenise Path: core/src/main/java/hudson/model/DownloadService.java http://jenkins-ci.org/commit/jenkins/951729c585fa63a85f43849b45ad2c6b3bce505c Log: JENKINS-32831 if metadata for tool installer does not exist should not fail (cherry picked from commit d2b1f15fc56f382f1d578c9317fca917ddabac92) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28790 Re: Sonar database credentials in build console output not masked since LTS version 1.596.3 Code changed in jenkins User: Emilio Escobar Path: core/src/test/java/hudson/util/ArgumentListBuilderTest.java http://jenkins-ci.org/commit/jenkins/f6db6670a8f9107f189fedc4fed07b1bbc6a7dc3 Log: JENKINS-28790 Baptiste comments fixed (cherry picked from commit 7fb1ac9d9f1bc006ca9d90ccaef402eaba4404a2) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UsageStatistics.java http://jenkins-ci.org/commit/jenkins/ce866ddb3cac225c3bf224d6b4eb89eef36f79c8 Log: Revert " JENKINS-32190 Make UsageStatistics#isDue check Jenkins init level before generating stats." This reverts commit d8a13ac07c4357eb74ab45a03955c0db430e3aa9. I noticed a strange drop in usage statistics from the mid Jan 2016, which corresponds to the time this change was released in the wild, and further drop when LTS 1.642.2 is released with this change at the end of Feb. I spent some time trying to determine how this might cause instances to stop sending data, but I couldn't come up with any. I left those notes in JENKINS-32190 . There was some strange behaviours, but none explains what this is. So I'd like to back out this change and see if that makes any impact on the stats collection. If it backs up, then we know empirically this change is to blame, so that would justify spending further effort or come up with a fix from a different angle. (cherry picked from commit b2013edbf7a4d40df2bc05a1e219d8599e642961) Compare: https://github.com/jenkinsci/jenkins/compare/003f1e5b0c5e...ce866ddb3cac Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java pom.xml http://jenkins-ci.org/commit/jenkins/af1a53d91c4863f27e4fad295911f131beb64b9a Log: Merge pull request #2010 from jenkinsci/jnlp3 [FIXED JENKINS-26580][FIXED JENKINS-28289] Activate JNLP3 support (cherry picked from commit 6d3e05439643097d2f172761ea82a32a857d058a) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25440) Failed to create Guice container from all the plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25440 Re: Failed to create Guice container from all the plugins Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/ExtensionFinder.java http://jenkins-ci.org/commit/jenkins/9ea9761adc9abc52c4d979f7383ccb595b5ca32c Log: [FIXED JENKINS-25440] Recursively resolve @Inject’ed extensions, too, looking for LinkageError’s. (cherry picked from commit 1a2d82275c078ca3f651d9924a53acd2b6210a93) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28790 Re: Sonar database credentials in build console output not masked since LTS version 1.596.3 Code changed in jenkins User: Emilio Escobar Path: core/src/main/java/hudson/util/ArgumentListBuilder.java http://jenkins-ci.org/commit/jenkins/f24c536676fe9df50fd499b51c4b4ff2e6edc40c Log: JENKINS-28790 added valentina condition when the first argument is quoted. (cherry picked from commit 344e917cc4a1096bb1805b14f0f2e45978b62757) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32190 Re: UsageStatistics Page Decorator may get called during initialization. Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UsageStatistics.java http://jenkins-ci.org/commit/jenkins/3a44687df5f979ea57a3206b83817c5be7299eb3 Log: Revert " JENKINS-32190 Make UsageStatistics#isDue check Jenkins init level before generating stats." This reverts commit d8a13ac07c4357eb74ab45a03955c0db430e3aa9. I noticed a strange drop in usage statistics from the mid Jan 2016, which corresponds to the time this change was released in the wild, and further drop when LTS 1.642.2 is released with this change at the end of Feb. I spent some time trying to determine how this might cause instances to stop sending data, but I couldn't come up with any. I left those notes in JENKINS-32190 . There was some strange behaviours, but none explains what this is. So I'd like to back out this change and see if that makes any impact on the stats collection. If it backs up, then we know empirically this change is to blame, so that would justify spending further effort or come up with a fix from a different angle. (cherry picked from commit b2013edbf7a4d40df2bc05a1e219d8599e642961) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java pom.xml http://jenkins-ci.org/commit/jenkins/af1a53d91c4863f27e4fad295911f131beb64b9a Log: Merge pull request #2010 from jenkinsci/jnlp3 [FIXED JENKINS-26580][FIXED JENKINS-28289] Activate JNLP3 support (cherry picked from commit 6d3e05439643097d2f172761ea82a32a857d058a) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28790 Re: Sonar database credentials in build console output not masked since LTS version 1.596.3 Code changed in jenkins User: Emilio Escobar Path: core/src/main/java/hudson/util/ArgumentListBuilder.java http://jenkins-ci.org/commit/jenkins/717c5f56bcaa8fcfae109dd87a7c6e4069a3baed Log: JENKINS-28790 NIT: tabulation issue (cherry picked from commit 5423f695ab83ec7d49daae538d25177872b0aada) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33377) Functions.isExtensionsAvailable() should return false during termination
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33377 Re: Functions.isExtensionsAvailable() should return false during termination Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/Functions.java http://jenkins-ci.org/commit/jenkins/5ca718ac016b970e3588bd133bd048e8a224989b Log: [FIXED JENKINS-33377] Add a check for termination to Functions.isExtensionsAvailable() (cherry picked from commit 1ed395aa06b64eea29504a39556995491db3ce57) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28790 Re: Sonar database credentials in build console output not masked since LTS version 1.596.3 Code changed in jenkins User: Emilio Escobar Path: core/src/main/java/hudson/util/ArgumentListBuilder.java core/src/test/java/hudson/util/ArgumentListBuilderTest.java http://jenkins-ci.org/commit/jenkins/0782aa567b4d2cf52aec5f5f5e0e8440c01edae4 Log: JENKINS-28790 solved the issue masked parameters not masked in windows system. toWindowsCommand joins all args in one, missing masked. (cherry picked from commit b9a72bcd967fd8b0d422ccf81daf1de576702fd1) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33730) ATH needs to be made to work with 2.0
Title: Message Title Oliver Gondža commented on JENKINS-33730 Re: ATH needs to be made to work with 2.0 Tom FENNELLY, thanks for looking at it. Can you push what you have so we can collaborate? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33896) Possible Memory Leak with highly frequent Pipeline runs
Title: Message Title Tony Finn created an issue Jenkins / JENKINS-33896 Possible Memory Leak with highly frequent Pipeline runs Issue Type: Bug Assignee: Jesse Glick Attachments: Screen Shot 2016-03-30 at 11.42.51 AM.png, Screen Shot 2016-03-30 at 11.43.33 AM.png, Screen Shot 2016-03-30 at 11.43.49 AM.png Components: workflow-plugin Created: 2016/Mar/30 10:56 AM Environment: Jenkins 1.644 Pipeline Plugin 1.9 & 1.15 CentOS 6.6 Oracle Java 1.7 Priority: Major Reporter: Tony Finn We recently added a new, very frequently run Pipeline job (from 20-30 pipeline builds a day to this new job which ran every minute and now runs every 10) and found that our Jenkins instance began running out of memory in 2-3 days. We have since refactored this job to run less frequently, but our memory usage is still steadily increasing over time. After downloading a heap dump and opening it in VisualVM, the two largest contributors are ListHashMap instances from Groovy, and Object[] held by those ListHashMap instances. I'm not the most e
[JIRA] [workflow-plugin] (JENKINS-33896) Possible Memory Leak with highly frequent Pipeline runs
Title: Message Title Tony Finn updated an issue Jenkins / JENKINS-33896 Possible Memory Leak with highly frequent Pipeline runs Change By: Tony Finn We recently added a new, very frequently run Pipeline job (from 20-30 pipeline builds a day to this new job which ran every minute and now runs every 10) and found that our Jenkins instance began running out of memory in 2-3 days. We have since refactored this job to run less frequently, but our memory usage is still steadily increasing over time. We were initially on version 1.9 of the Workflow/Pipeline plugin, but we tried upgrading to 1.15 in case it fixed this issue, but it appeared not to resolve the issue. After downloading a heap dump and opening it in VisualVM, the two largest contributors are ListHashMap instances from Groovy, and Object[] held by those ListHashMap instances. I'm not the most experience with JVisualVM, but following the chain of Show instance on references to these ListHashMap instances, it appears that they are belonging to parts of a Groovy AST held by instances of com.cloudbees.groovy.cps.CpsTransformer (1x per build that has run since Jenkins restarted) in a list called compilationCustomizers belonging to org.codehaus.groovy.control.CompilerConfiguration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://group
[JIRA] [remoting] (JENKINS-33886) Can only connect one JNLP3 slave per IP address
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33886 Can only connect one JNLP3 slave per IP address Change By: Daniel Beck Labels: encryption regression remoting security slave Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-33897) The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-33897 The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin Issue Type: Bug Assignee: Félix Belzunce Arcos Components: authorize-project-plugin Created: 2016/Mar/30 11:02 AM Priority: Minor Reporter: Félix Belzunce Arcos The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin. The stacktrace comes from: https://github.com/stapler/stapler/blob/master/jelly/src/main/java/org/kohsuke/stapler/framework/adjunct/AdjunctsInPage.java#L166 In the plugin the adjunct is referenced here: https://github.com/jenkinsci/authorize-project-plugin/blob/c2aaa513780dd7e695f8234bf86ef06cba2485f4/src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly#L52 But the adjunct is with capital T: https://github.com/jenkinsci/authorize-project-plugin/blob/c2aaa513780dd7e695f8234bf86ef06cba2485f4/src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/passwordApiTokenSwitch.js "org.jenkinsci.plugins.authorizeproject.strategy.SpecificUsersAuthorizationStrategy.passwordApitokenSwitch" /> lowercase src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/passwordApiTokenSwitch.js <<< uppercase
[JIRA] [authorize-project-plugin] (JENKINS-33897) The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin
Title: Message Title Félix Belzunce Arcos started work on JENKINS-33897 Change By: Félix Belzunce Arcos Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-33897) The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33897 The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/authorize-project-plugin/pull/23 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33847) Support for implicit variable WORKSPACE in Pipeline stages
Title: Message Title Daniel Beck commented on JENKINS-33847 Re: Support for implicit variable WORKSPACE in Pipeline stages $PWD? Of course only works until you change directory, but add a WORKSPACE=$PWD on top as needed and done. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [suppress-stack-trace-plugin] (JENKINS-33685) filter stacktrace in all cases
Title: Message Title Jesse Glick updated JENKINS-33685 Jenkins / JENKINS-33685 filter stacktrace in all cases Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [suppress-stack-trace-plugin] (JENKINS-33685) filter stacktrace in all cases
Title: Message Title Jesse Glick started work on JENKINS-33685 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [suppress-stack-trace-plugin] (JENKINS-33685) filter stacktrace in all cases
Title: Message Title Jesse Glick reopened an issue Filing a PR does not count as “fixed”—has to be merged to trunk. Jenkins / JENKINS-33685 filter stacktrace in all cases Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-33797) Github Organization folder creation causes exception with space in job name
Title: Message Title Antonio Muñiz commented on JENKINS-33797 Re: Github Organization folder creation causes exception with space in job name The quoted exception is certainly ugly enough, but it is being caught, so is probably not what is preventing the folder from being created Jesse Glick the folder is created (even throwing that exception). This plugin tries to pre-configure some details (icon, links, etc) supposing that the GH organization exists. So this is more a matter of what to log and at which level. A possible fix would be to add a special catch for FileNotFoundException (yes, github-api throws that...) and just logging it at FINE instead of WARNING. Working on it... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma created an issue Jenkins / JENKINS-33898 Add support for auto updating ( resolving ) JIRA issue created by this plugin Issue Type: New Feature Assignee: Neeraj Sharma Components: jiratestresultreporter-plugin Created: 2016/Mar/30 11:56 AM Priority: Major Reporter: Neeraj Sharma The requirement is to resolve the issue in JIRA once the code has been fixed and tests are back to normal in subsequent execution of Jenkins jobs. This would minimise the further manual work and add more step towards Continuous Integration and Deployment. The assumption is that developer would not change the summary but may change the description or add comments. At each execution the plugin would get all the Open issues for given project and try to match the summary of all successful tests in the build. In case of a match, it would update the status of the issue in JIRA as resolved. Add Comment
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33467 Re: CauseAction.causes can become huge Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/03d057f88f08e4b3ca9e14eebd48df043e27067f Log: Don't crash because JENKINS-33467 has changed expected behaviour Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma closed an issue as Duplicate Jenkins / JENKINS-33898 Add support for auto updating ( resolving ) JIRA issue created by this plugin Change By: Neeraj Sharma Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Neeraj Sharma started work on JENKINS-32738 Change By: Neeraj Sharma Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Neeraj Sharma assigned an issue to Neeraj Sharma Jenkins / JENKINS-32738 on success, the plugin should resolve the issue Change By: Neeraj Sharma Assignee: Alexander Leibzon Neeraj Sharma Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma reopened an issue Jenkins / JENKINS-33898 Add support for auto updating ( resolving ) JIRA issue created by this plugin Change By: Neeraj Sharma Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Neeraj Sharma stopped work on JENKINS-32738 Change By: Neeraj Sharma Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-33776) Cannot start from preview rpm
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33776 Re: Cannot start from preview rpm Code changed in jenkins User: Sam Van Oort Path: deb/build/debian/jenkins.default osx/Library/Application Support/Jenkins/jenkins-runner.sh osx/Library/Documentation/Jenkins/command-line-preferences.html rpm/build/SOURCES/jenkins.init.in rpm/build/SOURCES/jenkins.sysconfig.in suse/build/SOURCES/jenkins.init.in suse/build/SOURCES/jenkins.sysconfig.in http://jenkins-ci.org/commit/packaging/fd3abc6bae3575829a2c42609f3257b90408e471 Log: Merge pull request #51 from jenkinsci/remove-ajp Remove AJP per JENKINS-33776 because Jetty 9 dropped support Compare: https://github.com/jenkinsci/packaging/compare/b3ce03afe1af...fd3abc6bae35 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alexander Leibzon commented on JENKINS-32738 Re: on success, the plugin should resolve the issue Implemented here https://github.com/alexanderlz/jenkins-pagerduty-plugin will push to jenkins repo in the following day Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alexander Leibzon stopped work on JENKINS-32738 Change By: Alexander Leibzon Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alexander Leibzon started work on JENKINS-32738 Change By: Alexander Leibzon Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alexander Leibzon started work on JENKINS-32738 Change By: Alexander Leibzon Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alexander Leibzon assigned an issue to Alexander Leibzon Jenkins / JENKINS-32738 on success, the plugin should resolve the issue Change By: Alexander Leibzon Assignee: Neeraj Sharma Alexander Leibzon Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-33672) File Setting Failure in Extended Choice Parameter Plugin on Slave
Title: Message Title vimil commented on JENKINS-33672 Re: File Setting Failure in Extended Choice Parameter Plugin on Slave Ed, You could also specify an http url path to the file in source control repository, without having to create a job to download the file into the workspace Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-33672) File Setting Failure in Extended Choice Parameter Plugin on Slave
Title: Message Title vimil edited a comment on JENKINS-33672 Re: File Setting Failure in Extended Choice Parameter Plugin on Slave Ed,You could also specify an http url path to the file in source control repository, without having to create a job to download the file into the workspace The issue with using a workspace relative path is that ECP plugin is invoked before the job is started. Jenkins decides which slave to use only when the job starts, so ECP cannot predict behore-hand which slave's workspace the configuration should be read from. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma started work on JENKINS-33898 Change By: Neeraj Sharma Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma updated JENKINS-33898 Jenkins / JENKINS-33898 Add support for auto updating ( resolving ) JIRA issue created by this plugin Change By: Neeraj Sharma Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter-plugin] (JENKINS-33898) Add support for auto updating ( resolving ) JIRA issue created by this plugin
Title: Message Title Neeraj Sharma commented on JENKINS-33898 Re: Add support for auto updating ( resolving ) JIRA issue created by this plugin Code is under review at https://github.com/jenkinsci/JiraTestResultReporter-plugin/pull/9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-33899) Text-file-operations-plugin failing on versions above 1.2.1
Title: Message Title Nicky Goethals created an issue Jenkins / JENKINS-33899 Text-file-operations-plugin failing on versions above 1.2.1 Issue Type: Bug Assignee: Sanketh PB Attachments: Screen Shot 2016-03-30 at 14.47.34.png Components: text-file-operations-plugin Created: 2016/Mar/30 12:50 PM Environment: Linux, Jenkins 1.654 Priority: Minor Reporter: Nicky Goethals After updating to 1.3.0 or 1.3.1 the plugin is giving errors in the output (tried adjusting all settings, and using the new workspace toggle). See attached screenshot for example value. Failed to create/update file. null Build step 'Create/Update Text File' marked build as failure Finished: FAILURE
[JIRA] [multi-branch-project-plugin] (JENKINS-33900) save/apply button is missing when editing mutibranch jobs created inside a github organization folder
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-33900 save/apply button is missing when editing mutibranch jobs created inside a github organization folder Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin, workflow-plugin Created: 2016/Mar/30 1:19 PM Priority: Major Reporter: Sorin Sbarnea It seems that even if there is a menu item named "Edit Configuration" for the jobs created by the multibranch plugin, the configuration pages are missing any save/apply buttons, very confusing and annoying. Add Comment
[JIRA] [git-plugin] (JENKINS-29714) infinite polling with variable in branchspec
Title: Message Title Leandro Lucarella commented on JENKINS-29714 Re: infinite polling with variable in branchspec More info, this is how my polling looks when using a parameter for the branch specification: Started on Mar 30, 2016 1:19:00 PM Using strategy: Default [poll] Last Built Revision: Revision ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x) using GIT_SSH to set credentials cred SSH key > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:some/repo.git # timeout=10 Found 32 remote heads on g...@github.com:some/repo.git [poll] Latest remote head revision on refs/heads/v1.7.x is: 138b74fc9ce8885aefdeabfdf8bc3ecca572d264 - already built by 333 [poll] Latest remote head revision on refs/heads/v1.4.x is: 57d03eb35379098071726699783055535a8bd425 - already built by 338 [poll] Latest remote head revision on refs/heads/v1.17.x is: 22d0d8742bacf4c89602fc98f20017c323cdf7bc - already built by 18 [poll] Latest remote head revision on refs/heads/v1.2.x is: b919d378aac4e503c21b58d940197553f4983344 - already built by 340 [poll] Latest remote head revision on refs/heads/v1.27.x is: fe1052f3b95a5b75be18b45ce41743da900712f9 - already built by 343 [poll] Latest remote head revision on refs/heads/v1.5.x is: 0ae940fecddcd4a5a785e5871e12b200ddfb7bee - already built by 345 [poll] Latest remote head revision on refs/heads/v1.24.x is: 71c050ef5b8fc3430f80cafb27109d34aa103876 - already built by 347 [poll] Latest remote head revision on refs/heads/v1.19.x is: d09a06c871bdc8f518f694877110189258792392 - already built by 349 [poll] Latest remote head revision on refs/heads/v1.26.x is: 1d053f81485174957c38cee420eac1292ceb82ef - already built by 351 [poll] Latest remote head revision on refs/heads/master is: 3a9bf5071b66bd78b2e90984b88dba22ffea489e - already built by 336 [poll] Latest remote head revision on refs/heads/v1.25.x is: 912e94dbb7f9bdc4ceec75a9c7e56cb1dbbbce75 - already built by 352 [poll] Latest remote head revision on refs/heads/v1.23.x is: b7919967ce1e152ef4656b7b4866ba14b8ec - already built by 357 [poll] Latest remote head revision on refs/heads/v1.6.x is: fababe9cd990e1867e28f501b0e91faf1e920a5a - already built by 359 [poll] Latest remote head revision on refs/heads/v1.18.x is: 987f8c23304b99a6377cae63c7a9a7b5051f4e62 - already built by 361 [poll] Latest remote head revision on refs/heads/v1.1.x is: 4008675d54b10bafd675a25ba093190697af867f - already built by 365 [poll] Latest remote head revision on refs/heads/v1.22.x is: 2e47914dfa42cb595731b264cbecc277620aced0 - already built by 19 [poll] Latest remote head revision on refs/heads/v1.13.x is: cf834f5d3968d8b3996025fc1eb570d17b6a3083 Done. Took 2.4 sec Changes found refs/heads/v1.13.x is not detected as being already built, but instead of building that reference, the last reference is built (ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x)), so on the next polling the same happens, refs/heads/v1.13.x is detected as not being built and again the last version built gets rebuilt, getting into an infinite rebuilding loop. And this is how it looks when just leaving the branch specification empty: Started on Mar 30, 2016 12:59:00 PM Polling SCM changes on master Using strategy: Default [poll] Last Built Revision: Revision ace29d00302d20dddb3763057f31ab40b1fe8b4b (origin/v2.x.x) > git rev-parse --is-inside-work-tr
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title Jean-Paul Delimat created an issue Jenkins / JENKINS-33901 Bitbucket notifier plugin does not support SSH on port 443 Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2016/Mar/30 1:36 PM Environment: Plugin org.jenkins-ci.plugins:bitbucket-build-status-notifier:1.1.0 Priority: Minor Reporter: Jean-Paul Delimat On some servers the outgoing traffic on port 22 is blocked and BitBucket supports that by providing an alternative URL scheme. See section "SSH on Port 443" at the bottom of this page. So the URL looks like this: ssh://g...@altssh.bitbucket.org:443/accountname/reponame/ The plugin throws an error like this: itbucket notify on start failed: Bitbucket build notifier support only repositories hosted in bitbucket.org java.lang.Exception: Bitbucket build notifier support only repositories hosted in bitbucket.org at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:183) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.notifyBuildStatus(BitbucketBuildStatusNotifier.java:215) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:85)
[JIRA] [credentials-plugin] (JENKINS-33902) Migrate to JTH 2.x and improve test coverage
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-33902 Migrate to JTH 2.x and improve test coverage Issue Type: Task Assignee: Armando Fernandez Components: credentials-plugin Created: 2016/Mar/30 1:47 PM Priority: Minor Reporter: Armando Fernandez In order to keep the plugin up to date and with a better test coverage, it'd be good to: Migrate tests to JTH 2.x. Improve test coverage. Add Comment
[JIRA] [credentials-plugin] (JENKINS-33902) Migrate to JTH 2.x and improve test coverage
Title: Message Title Armando Fernandez started work on JENKINS-33902 Change By: Armando Fernandez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-33903) github-organization fails to detect new repositories, probably due to pagination
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-33903 github-organization fails to detect new repositories, probably due to pagination Change By: Sorin Sbarnea github-organization fails to detect new repositories, probably due to pagination as we have about 20 repositories and it failed to detect a new one, being consistent in its behaviour, even if this repository is configured with a Jenkinfile inside and with the same access as the other ones.I checked the logs and it doesn't even spot it, which tells me that probably the GitHub API call is paginated and returns only a limited number of repositories. I marked this as critical because there is no workaround for this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-33903) github-organization fails to detect new repositories, probably due to pagination
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-33903 github-organization fails to detect new repositories, probably due to pagination Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Mar/30 1:51 PM Priority: Critical Reporter: Sorin Sbarnea github-organization fails to detect new repositories, probably due to pagination as we have about 20 repositories and it failed to detect a new one, being consistent in its behaviour, even if this repository is configured with a Jenkinfile inside and with the same access as the other ones. I checked the logs and it doesn't even spot it, which tells me that probably the GitHub API call is paginated and returns only a limited number of repositories. Add Comment
[JIRA] [core] (JENKINS-6056) Install Windows service with Log on As
Title: Message Title Rick Patterson commented on JENKINS-6056 Re: Install Windows service with Log on As We are at Jenkins 1.592 - when the slave connection service created on the Windows slave, it does have the user credentials in the Logon Tab of the service as is specified on the jenkins slave configuration page, so this problem appears to have been fixed at some time or other. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33904) Jenkinsfile batch steps randomly hang when complete
Title: Message Title
obearn created an issue
Jenkins / JENKINS-33904
Jenkinsfile batch steps randomly hang when complete
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-plugin
Created:
2016/Mar/30 2:06 PM
Priority:
Major
Reporter:
obearn
When executing simple JenkinsFile a simple maven build hangs when completed. It works well with some, but always fail with others.
#!groovy node { checkout scm bat "$ {tool 'maven 3.0.5'}
/bin/mvn -DskipTests=true clean install" }
Add Comment
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-33809 Find out what's wrong with the tests on the 2.0 branch requiring so much RAM Change By: Antonio Muñiz Attachment: java7-1.x-surefire-booter1.png Attachment: java7-1.x-surefire-booter2.png Attachment: java7-1.x-maven-launcher.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file Code changed in jenkins User: Kohsuke Kawaguchi Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy http://jenkins-ci.org/commit/workflow-plugin/ff210c3819a66e6fec7772a3242ff105c3646513 Log: JENKINS-32925 Handle recursion Use stack to keep track of traversal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file Code changed in jenkins User: Jesse Glick Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy http://jenkins-ci.org/commit/workflow-plugin/9bf98f696517d3b8d71a83d6b1114eae03096cd8 Log: Merge pull request #371 from kohsuke/ JENKINS-32925 JENKINS-32925 Handle recursion Compare: https://github.com/jenkinsci/workflow-plugin/compare/041c313d2b89...9bf98f696517 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31094) Proposal: Jenkins Configuration DSL
Title: Message Title Sean Abbott commented on JENKINS-31094 Re: Proposal: Jenkins Configuration DSL +1 for basically everything above, especially the plugin configuration requirements. Also, failing some of that, some sort of config validation that is plugin aware (i.e., you can pass it in xml for something you're trying to configure and it comes back with anything that gets ignored or fails) would also be super helpful, mostly for things like jobs and agents. But good config options as outline above might eliminate the need for that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-33809
Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Change By:
Antonio Muñiz
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x.h3. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})h4. Jenkins 1.x1. Maven launcher process:!jenkins1-maven-launcher.png|width=400,height=300!2. Surefire booter:!jenkins1-surefire-booter.png|width=400,height=300!h4. Jenkins 2.01. Maven launcher process!jenkins2-maven-launcher.png|width=400,height=300!2. Surefire booter!jenkins2-surefire-booter.png|width=400,height=300!h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):Surefire forked booter 1:!forked-booter-1.png|width=550,height=300!Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle): !forked-booter-2.png|width=550,height=300!Maven launcher process:!maven-laucher.png|width=550,height=300!h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-forked-booter-1.png|width=750,height=250!Surefire forked booter 2: !java7-forked-booter-2.png|width=750,height=250!Maven launcher process:!java7-maven-launcher.png|width=750,height=250! h3. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-1.x-surefire-booter1.png|width=750,height=200!Surefire forked booter 2: !java7-1.x-surefire-booter2.png|width=750,height=200!Maven launcher process:!java7-1.x-maven-launcher.png|width=750,height=200!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-33809
Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Change By:
Antonio Muñiz
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x. h3 h2 . Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}}) h4 h3 . Jenkins 1.x1. Maven launcher process:!jenkins1-maven-launcher.png|width=400,height=300!2. Surefire booter:!jenkins1-surefire-booter.png|width=400,height=300! h4 h3 . Jenkins 2.01. Maven launcher process!jenkins2-maven-launcher.png|width=400,height=300!2. Surefire booter!jenkins2-surefire-booter.png|width=400,height=300! h3 h2 . Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):Surefire forked booter 1:!forked-booter-1.png|width=550,height=300!Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle): !forked-booter-2.png|width=550,height=300!Maven launcher process:!maven-laucher.png|width=550,height=300!h3. Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-forked-booter-1.png|width=750,height=250!Surefire forked booter 2: !java7-forked-booter-2.png|width=750,height=250!Maven launcher process:!java7-maven-launcher.png|width=750,height=250! h3 h2 . Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-1.x-surefire-booter1.png|width=750,height=200!Surefire forked booter 2: !java7-1.x-surefire-booter2.png|width=750,height=200!Maven launcher process:!java7-1.x-maven-launcher.png|width=750,height=200!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title
Antonio Muñiz updated an issue
Jenkins / JENKINS-33809
Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Change By:
Antonio Muñiz
Tests on the 2.0 branch require crazy amounts of RAM or that the VM be killed after every test. This appears to be a regression from 1.x.h2. Jenkins 1.x vs. 2.0 comparison running a single test ({{JDKInstallerTest}})h3. Jenkins 1.x1. Maven launcher process:!jenkins1-maven-launcher.png|width=400,height=300!2. Surefire booter:!jenkins1-surefire-booter.png|width=400,height=300!h3. Jenkins 2.01. Maven launcher process!jenkins2-maven-launcher.png|width=400,height=300!2. Surefire booter!jenkins2-surefire-booter.png|width=400,height=300!h2. Running the full test suite (on 2.0, Maven 3.3.3 and Java 8):Surefire forked booter 1:!forked-booter-1.png|width=550,height=300!Surefire forked booter 2 (there is a little jconsole disconnection of ~4 minutes in my local env, but nothing remarkable happened in the middle): !forked-booter-2.png|width=550,height=300!Maven launcher process:!maven-laucher.png|width=550,height=300! h3 h2 . Running the full test suite (on 2.0, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-forked-booter-1.png|width=750,height=250!Surefire forked booter 2: !java7-forked-booter-2.png|width=750,height=250!Maven launcher process:!java7-maven-launcher.png|width=750,height=250!h2. Running the full test suite (on 1.x, Maven 3.3.3 and Java 7):Surefire forked booter 1:!java7-1.x-surefire-booter1.png|width=750,height=200!Surefire forked booter 2: !java7-1.x-surefire-booter2.png|width=750,height=200!Maven launcher process:!java7-1.x-maven-launcher.png|width=750,height=200!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [packaging] (JENKINS-33776) Cannot start from preview rpm
Title: Message Title Sam Van Oort closed an issue as Fixed Jenkins / JENKINS-33776 Cannot start from preview rpm Change By: Sam Van Oort Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33905) Advice about how to recover input step parameters
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-33905 Advice about how to recover input step parameters Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/30 2:54 PM Priority: Minor Reporter: Emilio Escobar Snippet generator is a great tool that helps developers to create new Pipelines. As when a parameterized input step is generated at snippet generator without mention of how to recover them, it'd be great if snippet it self can provide the example. If it not possible, at least the help should provide an example, not only _ If multiple parameters are listed, the return value will be a map keyed by the parameter names._ as currently. https://github.com/jenkinsci/workflow-plugin/blob/118b89e1b1828a39f50fb955942ffcbbe69e653e/support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/InputStep/help.html https://github.com/jenkinsci/workflow-plugin/blob/118b89e1b1828a39f50fb955942ffcbbe69e653e/support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/InputStep/help-parameters.html For example: def inputParameter = input message: 'One Parameter', parameters: [[$class: 'StringParameterDefinition', defaultValue: '', description: '', name: 'inputParameter']] def inputParameterMap = input message: 'Two Parameters', parameters: [[$class: 'StringPa
[JIRA] [multi-branch-project-plugin] (JENKINS-33906) Icon based on status of single branch
Title: Message Title Jesse Bowes created an issue Jenkins / JENKINS-33906 Icon based on status of single branch Issue Type: Improvement Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Mar/30 2:55 PM Priority: Minor Reporter: Jesse Bowes Currently, we are able to configure a ball status icon for the Jenkins Project containing all the branches, but if a branch has a failure, this icon is red. It would be nice to be able to configure this to use the status of a specific branch (like default or release). Add Comment
