[JIRA] [xfpanel-plugin] (JENKINS-28914) Group jobs into projects
Title: Message Title Bart Kummel created an issue Jenkins / JENKINS-28914 Group jobs into projects Issue Type: Improvement Assignee: Julien RENAUT Components: xfpanel-plugin Created: 16/Jun/15 7:25 AM Priority: Minor Reporter: Bart Kummel Currently, we use the radiator plugin, that has the ability to group jobs into projects. A single box is displayed for the project, which is green as long as all jobs in the project are green. We do like the better display options of the xfpanel plugin. However, we're unable to use it, as long as there's no possibility to group jobs into projects. Can you please add this option? Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-28848) Erratic PIPELINE_VERSION behavior with other Parameters
Title: Message Title Patrik Boström commented on JENKINS-28848 Re: Erratic PIPELINE_VERSION behavior with other Parameters Have created a PR (https://github.com/Diabol/delivery-pipeline-plugin/pull/120) with your testcase and a fix for it. Is it possible for you to do a test of the 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-28915) Thread Death and build number is already in use
Title: Message Title Michael Damberger created an issue Jenkins / JENKINS-28915 Thread Death and build number is already in use Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Jun/15 8:17 AM Environment: Windows Server 2008 R2 Standard java version "1.8.0_45" Java(TM) SE Runtime Environment (build 1.8.0_45-b15) Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) jenkins 1.614 in apache-tomcat-7.0.62 Priority: Major Reporter: Michael Damberger Jun 16, 2015 5:29:37 AM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: cannot create a build with number 6 since that (or higher) is already in use among [967] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:192) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1011) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor$1.call(Executor.java:328) at hudson.model.Executor$1.call(Executor.java:310) at hudson.model.Queue._withLock(Queue.java:1251) at hudson.model.Queue.withLock(Queue.java:1189) at hudson.model.Executor.run(Executor.java:310
[JIRA] [core] (JENKINS-28915) Thread Death and build number is already in use
Title: Message Title Daniel Beck commented on JENKINS-28915 Re: Thread Death and build number is already in use How did that happen? Please provide more information. 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-26277) Memory leak
Title: Message Title Daniel Beck commented on JENKINS-26277 Re: Memory leak I'm sorry I didn't respond earlier. Is this still a problem you're struggling with? 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] [ghprb-plugin] (JENKINS-28916) ghbrp PKIX path validation failed
Title: Message Title Adam Gavish created an issue Jenkins / JENKINS-28916 ghbrp PKIX path validation failed Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 16/Jun/15 8:36 AM Environment: Jenkins ver. 1.613 Ghbrp ver. 1.23.2 Priority: Major Reporter: Adam Gavish When trying to work with Github enterprise and jenkins ghprb plugin, the webhook looks ok on github enterprise but in jenkins.log I see that there are exceptions that make the pull request trigger to fail. Also, my github enterprise server is based on an ssl certificate, maybe that's the problem? Jun 16, 2015 11:35:00 AM org.jenkinsci.plugins.ghprb.GhprbGitHubAuth getConnection SEVERE: Unable to connect using credentials: fab49720-e9f1-4fac-aad0-f4de321a6b42 javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.pro
[JIRA] [core] (JENKINS-11851) More options for default parameters
Title: Message Title Hannes Kogler commented on JENKINS-11851 Re: More options for default parameters as I see it the the implementation described here: https://wiki.jenkins-ci.org/display/JENKINS/Parameter+Defaults+Options?focusedCommentId=80183932&#comment-80183932 would be much easier regarding usability. I really don't know why you won't let the users decide what and which plugin he prefers to cover this use case? 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-11851) More options for default parameters
Title: Message Title Hannes Kogler edited a comment on JENKINS-11851 Re: More options for default parameters as I see it the the implementation described here: https://wiki.jenkins-ci.org/display/JENKINS/Parameter+Defaults+Options?focusedCommentId=80183932&#comment-80183932would be much easier regarding usability than the workaround with the EnvInject Plugin, that has other intentions than just "hide" properties being setup individually for single jobs from the gui . So I really don't know why you won't let the users decide what and which plugin he prefers to cover this use case? 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-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title Nikolay Diakov commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses We have moved the Jenkins under IT management since the original issue. I will see when I can test again locally. 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-28915) Thread Death and build number is already in use
Title: Message Title Michael Damberger commented on JENKINS-28915 Re: Thread Death and build number is already in use jenkins runs jobs over night with 4 build processors and one of them dies almost nightly since 1.614 was installed at the time of death all processors were busy. another job hat a failure at this time. is it possible to determine what build it was that was trying to run, causing the IllegalStateException? because this problem is occurring almost every night, so I could easily provide more information, if some log level can be modified somewhere 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-28915) Thread Death and build number is already in use
Title: Message Title Michael Damberger edited a comment on JENKINS-28915 Re: Thread Death and build number is already in use jenkins runs jobs over night with 4 build processors and one of them dies almost nightly since 1.614 was installedat the time of death all processors were busy. another job hat had a failure at this time.is it possible to determine what build it was that was trying to run, causing the IllegalStateException?because this problem is occurring almost every night, so I could easily provide more information, if some log level can be modified somewhere (?) 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] [swarm-plugin] (JENKINS-28917) Swarm CLI with latest Jenkins Slave Jar
Title: Message Title Karthi Venkataraman created an issue Jenkins / JENKINS-28917 Swarm CLI with latest Jenkins Slave Jar Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 16/Jun/15 8:59 AM Priority: Minor Reporter: Karthi Venkataraman The more recent Swarm CLI available, does not seem to contain the Slave jar for the Jenkins LTS Version.. So when we try to connect a slave to the LTS version master, we get a warning that the slave.jar is old and the slave remains offline and had to be brought online manually. Will this be updated any sooner ? Add Comment
[JIRA] [vsphere-cloud-plugin] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title Ichai Luzon assigned an issue to Ichai Luzon Jenkins / JENKINS-28870 allow specifying target host when cloning a VM Change By: Ichai Luzon Assignee: Ichai Luzon 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] [vsphere-cloud-plugin] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title Ichai Luzon started work on JENKINS-28870 Change By: Ichai Luzon 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] [swarm-plugin] (JENKINS-28917) Swarm CLI with latest Jenkins Slave Jar
Title: Message Title Karthi Venkataraman updated an issue Jenkins / JENKINS-28917 Swarm CLI with latest Jenkins Slave Jar Change By: Karthi Venkataraman Environment: Jenkins LTS - 1.580.1Slave.jar version - 2.47Swarm Plugin - .1.24Swarm CLI - 1.24 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-11851) More options for default parameters
Title: Message Title Daniel Beck commented on JENKINS-11851 Re: More options for default parameters So I really don't know why you won't let the users decide what and which plugin he prefers to cover this use case? This is a change requested for Jenkins core, not about a new plugin. The trend has long been to move functionality out of core into independently updatable plugins, so rejecting new feature requests that are very similar to established plugins' features is consistent with that. Of course I'm not the final arbiter on what goes in and what does not, so feel free to reopen this issue. But based on my experience, this will not make it in, as it is not actually a necessary feature (since it has adequate alternatives), and brings significant additional complexity with 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] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Title: Message Title Olaf Lenz commented on JENKINS-10629 Re: Tar implimentation can't handle > 8GB and doesn't error out. What is the current state of this issue? As far as I understood, the integration into the main branch has been reverted, as it caused some problems. Does anybody work on this? What needs to be 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] [delivery-pipeline-plugin] (JENKINS-28918) Ability to browse previous pipeline with paging
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-28918 Ability to browse previous pipeline with paging Issue Type: New Feature Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 16/Jun/15 9:39 AM Priority: Minor Reporter: Marcin Zajączkowski It would sometimes useful to be able to browse old pipelines. Displaying 50 pipelines brings some load time issues and it would be good to have an ability to use paging (e.g. 5 pipelines on a page and paging to see more). Add Comment
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Title: Message Title Oleg Nenashev commented on JENKINS-10629 Re: Tar implimentation can't handle > 8GB and doesn't error out. We need to develop more extensive tests. It's my action item, but I have not implemented them yet. ETA - July 2015th 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-blocker-plugin] (JENKINS-28919) Build-Blocker-Plugin NullPointerException
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-28919 Build-Blocker-Plugin NullPointerException Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 16/Jun/15 9:52 AM Environment: Windows Server 2013 Jenkins 1.609.1 LTS Build Blocker Plugin 1.6 Priority: Critical Reporter: Christoph Vogtländer Sometimes the build blocker plugin fails with a null pointer exception. Jobs are queued first, then vanish from the queue without being built. Jenkins log: java.lang.NullPointerException at hudson.plugins.buildblocker.BlockingJobsMonitor.getBlockingJob(BlockingJobsMonitor.java:85) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canRun(BuildBlockerQueueTaskDispatcher.java:80) at hudson.model.Queue.isBuildBlocked(Queue.java:1110) at hudson.model.Queue.maintain(Queue.java:1320) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2450) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.Schedul
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Rene Affourtit commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. A scenario to reproduce: SVN repository hosted via https (assume https://localhost/svn/) SVN authentification via username/password. (other combinations have not been tested) In the Repository are two projects: projecta/trunk and projectb/trunk. projecta/trunk has an svn:externals property projb=^/projectb/trunk. Jenkins project points to https://localhost/svn/projecta/trunk. To exclude faults additional credentials have been added for https://localhost/svn/projectb/trunk. When a user commits only to projecta all is well. When a user commits to projectb, retrieving of the changelog fails. when polling is used to trigger, no build is started. When a timed build is used, the build fails because the change log can not be made. logging shows that in CredentialsSVNAuthenticationProviderImpl.requestClientAuthentication the 'List authentications' remains empty. 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] [performance-plugin] (JENKINS-27373) Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero)
Title: Message Title Raoul Adler commented on JENKINS-27373 Re: Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero) When can we expect a new release of the Performance 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] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title stephenconnolly commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Rene Affourtit thank you for that test case. I will see if I can reproduce the issue from your description 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] [docker-build-step-plugin] (JENKINS-28920) Support multiple Docker servers
Title: Message Title vjuranek created an issue Jenkins / JENKINS-28920 Support multiple Docker servers Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 16/Jun/15 11:04 AM Priority: Major Reporter: vjuranek Allow to define multiple docker servers where containers can run and allow to select docker server in job configuration Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-11851) More options for default parameters
Title: Message Title Hannes Kogler reopened an issue I have tried out the workaround with the EnvInjectPlugin and generally it works. (by just declaring the key/value paris in the "Properties Content" section, like shown here: ) https://wiki.jenkins-ci.org/download/attachments/57999800/EnvInject_Path.png?version=1&modificationDate=1342694716000 But I still have a big disadvantage using this workaround. Finally I am also using the Promoted Builds Plugin and unfortunately the build parameters, predefined with the EnvInjectPlugin, won't be read by the Job Promotion being executed. Sure I have the possibility to configure the EnvInjectPlugin with my needed properties also for every single promotion step, but after all I need to duplicate the property definitions here again and again... and thats exactly what I wanted to prevent by using the EnvInjectPlugin! Whereas the properties, defined with the Jenkins Core functionality, are indeed readable by the configured promotion executions out-of-the-box. Or do you know any workaround for this use case as well? Jenkins / JENKINS-11851 More options for default parameters Change By: Hannes Kogler Resolution: Won't Fix Status: Resolved Reopened Assignee: Jacob Robertson Add Comment
[JIRA] [core] (JENKINS-11851) More options for default parameters
Title: Message Title Hannes Kogler assigned an issue to Daniel Beck Jenkins / JENKINS-11851 More options for default parameters Change By: Hannes Kogler Assignee: Jacob Robertson Daniel Beck 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-11851) More options for default parameters
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-11851 More options for default parameters Change By: Daniel Beck Assignee: Daniel Beck 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-11851) More options for default parameters
Title: Message Title Daniel Beck commented on JENKINS-11851 Re: More options for default parameters Or do you know any workaround for this use case as well? No. IMO, Promoted Builds is beyond broken, so I haven't used it in years. Also IMO, not a reason to reject env-inject for the original use case. Because I'm fairly sure it makes no difference in most use cases. This could easily be changed to an enhancement request for Promoted Builds without needing to change completely how parameters work. 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-28915) Thread Death and build number is already in use
Title: Message Title Daniel Beck commented on JENKINS-28915 Re: Thread Death and build number is already in use It's a project with a single build with the build number 967. Does that help? 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] [cli] (JENKINS-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
Title: Message Title Daniel Beck commented on JENKINS-22346 Re: CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean Is anyone experiencing this issue despite setting the hudson.model.User.allowNonExistentUserToLogin system property? 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-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title Sandra Greenhalgh created an issue Jenkins / JENKINS-28921 Can't access Jenkins Global Properties from groovy script Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 16/Jun/15 12:38 PM Environment: workflow-plugin: v1.8 jenkins: v1.616 Priority: Minor Reporter: Sandra Greenhalgh When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below) To replicate issue: Browse to Manage Jenkins > Configure System under the "Global Properties" make sure "Environment variables" is checked under the "Global Properties" > "Environment variables" add a new variable name = TEST_VAR
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- select "Workflow" job type- under the "Workflow" heading - - Definition: "Groovy CPS DSL" - - Script:echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"- Build workflow job and go to Console output- echo "JOB_NAME from env: ${env.JOB_NAME}" - - WORKS: it prints the name of the workflow job- echo "global property from env: ${env.TEST_VAR}" - - DOES NOT WORK: ${env.TEST_VAR} evaluates to null- echo "global property: ${TEST_VAR}" - - ERRORS: groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script: {code:java} echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}" {code} - Build workflow job and go to Console output- echo "JOB_NAME from env: ${env.JOB_NAME}" -- WORKS: it prints the name of the workflow job- echo "global property from env: ${env.TEST_VAR}" -- DOES NOT WORK: ${env.TEST_VAR} evaluates to null- echo "global property: ${TEST_VAR}" -- ERRORS: {code:java} groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25) {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"{code}- Build workflow job and go to Console output- echo "JOB_NAME from env: ${env.JOB_NAME}" -- WORKS: it prints the name of the workflow job- {noformat} echo "global property from env: ${env.TEST_VAR}" {noformat} -- DOES NOT WORK: ${env.TEST_VAR} evaluates to null- echo "global property: ${TEST_VAR}" -- ERRORS: {code:java}groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"{code}- Build workflow job and go to Console output- echo "JOB_NAME from env: ${env.JOB_NAME}" -- WORKS: it prints the name of the workflow job- {noformat} echo "global property from env: ${env.TEST_VAR}" {noformat} -- DOES NOT WORK: ${env.TEST_VAR} evaluates to null- echo "global property: ${TEST_VAR}" -- ERRORS: {code:java}groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- my job was named "workflow-test"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script: {code:java}echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"{code}- Build workflow job and go to Console output- from the output can see that the above script evaluates to:{code:java} echo "JOB_NAME from env: ${env.JOB_NAME}" - - WORKS > "JOB_NAME from env : it prints the name of the workflow job - {noformat} test" (worked) echo "global property from env: ${env.TEST_VAR}" {noformat} - - DOES NOT WORK: ${ > "global property from env .TEST_VAR} evaluates to : null " (not worked, but didn't error) - echo "global property: ${TEST_VAR}" - - ERRORS: > ERROR {code:java} groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- my job was named "workflow-test"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"{code}Build workflow job and go to Console outputfrom the output can see that the above script evaluates to:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}" -> "JOB_NAME from env: workflow-test" (worked)echo "global property from env: ${env.TEST_VAR}" -> "global property from env: null" ( not worked didn't work , but didn't error)echo "global property: ${TEST_VAR}" -> ERROR groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Sandra Greenhalgh updated an issue
Jenkins / JENKINS-28921
Can't access Jenkins Global Properties from groovy script
Change By:
Sandra Greenhalgh
When I try to access the Global Properties environment variables (Manage Jenkins > Configure System > Global Properties) I either get null or an error (details below)To replicate issue:- Browse to Manage Jenkins > Configure System- under the "Global Properties" make sure "Environment variables" is checked- under the "Global Properties" > "Environment variables" add a new variable - name = TEST_VAR - value = some value- In left navigation add "New Item"- my job was named "workflow-test"- select "Workflow" job type- under the "Workflow" heading -- Definition: "Groovy CPS DSL" -- Script:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}"echo "global property from env: ${env.TEST_VAR}"echo "global property: ${TEST_VAR}"{code} - Build workflow job and go to Console output - from the output can see that the above script evaluates to:{code:java}echo "JOB_NAME from env: ${env.JOB_NAME}" -> "JOB_NAME from env: workflow-test" (worked)echo "global property from env: ${env.TEST_VAR}" -> "global property from env: null" (not worked, but didn't error)echo "global property: ${TEST_VAR}" -> ERROR groovy.lang.MissingPropertyException: No such property: TEST_VAR for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:25) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17) at WorkflowScript.run(WorkflowScript:25){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-28906) Provide information about build requirements
Title: Message Title Gustave Laville resolved as Cannot Reproduce Jenkins / JENKINS-28906 Provide information about build requirements Change By: Gustave Laville Status: Open Resolved Resolution: Cannot Reproduce 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-28906) Provide information about build requirements
Title: Message Title Gustave Laville commented on JENKINS-28906 Re: Provide information about build requirements Sorry, I cannot reproduce it today - probably my fault. So I'll close this issue. Good to know that there are no specifc requirements, anyway - thanks! 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/remoting/GetRelatedStreams.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/Polling.java src/main/java/net/praqma/hudson/scm/pollingmode/BaselineCreationEnabled.java src/main/java/net/praqma/hudson/scm/pollingmode/PollChildMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSelfMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSiblingMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingModeDescriptor.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/global.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/help-hLinkFeedFrom.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/help-createBaseline.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollSelfMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/help-createBaseline.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/help-useHyperLinkForPolling.html src/main/webapp/scm/help-createBaseline.html src/test/java/net/praqma/hudson/test/CCUCMRule.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/12b03a047cf797ca8445f54d36caea0d2486e2ad Log: First commit for JENKINS-26484 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-is
[JIRA] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/Config.java src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/pollingmode/PollChildMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSelfMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSiblingMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingMode.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSelfMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollingMode/config.jelly src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/integration/child/ActivityTest.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFoundFailed.java src/test/java/net/praqma/hudson/test/integration/child/GetBaselinesTest.java src/test/java/net/praqma/hudson/test/integration/self/Any.java src/test/java/net/praqma/hudson/test/integration/self/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/self/BaselinesFoundFails.java src/test/java/net/praqma/hudson/test/integration/self/NoNewBaselinesFound.java src/test/java/net/praqma/hudson/test/integration/self/Polling.java src/test/java/net/praqma/hudson/test/integration/sibling/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS13944.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14436.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14702.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14806.java src/test/java/net/praqma/hudson/test/integration/userstories/Story01.java src/test/java/net/praqma/hudson/test/integration/userstories/Story02.java src/test/java/net/praqma/hudson/test/integration/userstories/Story03.java src/test/java/net/praqma/hudson/test/integration/userstories/Story04.java src/test/java/net/praqma/hudson/test/integration/userstories/Story05.java src/test/java/net/praqma/hudson/test/integration/userstories/Story07.java src/test/java/net/praqma/hudson/test/integration/userstories/Story08.java src/test/java/net/praqma/hudson/test/integration/userstories/Story09.java src/test/java/net/praqma/hudson/test/integration/userstories/Story10.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/2ff769e7de16f66f5ec400113a29e338c5d821b6 Log: Fixed test, for JENKINS-26484 Add Comment
[JIRA] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: src/test/java/net/praqma/hudson/test/integration/sibling/BaselinesFound.java src/test/resources/setup-interproject.xml src/test/resources/setup.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/d6f069693ff342d23d3a7dba4033b41d75d31f84 Log: Added new test for JENKINS-26484 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] [clearcase-ucm-plugin] (JENKINS-26529) Changeset should be generated on executing node (case 12604)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26529 Re: Changeset should be generated on executing node (case 12604) Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/hudson/Util.java src/main/java/net/praqma/hudson/remoting/CreateChangeSetRemote.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/a0082986246f2b6025a855f990d65b3f45ae7b21 Log: Fixed JENKINS-26529 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/remoting/GetRelatedStreams.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSiblingMode.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/global.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/help-useHyperLinkForPolling.html src/test/java/net/praqma/hudson/test/integration/child/BaselinesFound.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/f5c510f2ca963a78dd04ce6009304c6a2bbcd16c Log: Changed name of the hyperlink, fixed global config error for JENKINS-26484 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] [clearcase-ucm-plugin] (JENKINS-26593) Performance issues with large changesets (case 12606)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26593 Re: Performance issues with large changesets (case 12606) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/remoting/CreateChangeSetRemote.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/e8e241b1550ddc9b04dcc6cb8a235e34f514 Log: Performance JENKINS-26593 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/Config.java src/main/java/net/praqma/hudson/Util.java src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/remoting/CreateChangeSetRemote.java src/main/java/net/praqma/hudson/remoting/GetRelatedStreams.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/Polling.java src/main/java/net/praqma/hudson/scm/pollingmode/BaselineCreationEnabled.java src/main/java/net/praqma/hudson/scm/pollingmode/PollChildMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSelfMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollSiblingMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingModeDescriptor.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/global.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/help-hLinkFeedFrom.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/help-createBaseline.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollSelfMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/help-createBaseline.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/help-useHyperLinkForPolling.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollingMode/config.jelly src/main/webapp/scm/help-createBaseline.html src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/SystemValidator.java src/test/java/net/praqma/hudson/test/integration/child/ActivityTest.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFoundFailed.java src/test/java/net/praqma/hudson/test/integration/child/GetBaselinesTest.java src/test/java/net/praqma/hudson/test/integration/self/Any.java src/test/java/net/praqma/hudson/test/integration/self/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/self/BaselinesFoundFails.java src/test/java/net/praqma/hudson/test/integration/self/NoNewBaselinesFound.java src/test/java/net/praqma/hudson/test/integration/self/Polling.java src/test/java/net/praqma/hudson/test/integration/sibling/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS13944.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14436.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14702.java src/test/java/net/praqma/hudson/test/integration/userstories/JENKINS14806.java src/test/java/net/praqma/hudson/test/integration/userstories/Story01.java src/test/java/net/praqma/hudson/test/integration/userstories/Story02.java src/test/java/net/praqma/hudson/test/integration/userstories/Story03.java src/test/java/net/praqma/hudson/test/integration/userstories/Story04.java src/test/java/net/praqma/hudson/test/integration/userstories/Story05.java src/test/java/net/praqma/hudson/test/integration/userstories/Story07.java src/test/java/net/praqma/hudson/test/integration/userstories/Story08.java src/test/java/net/praqma/hudson/test/integration/userstories/Story09.java src/test/java/net/praqma/hudson/test/integration/userstories/Story10.java src/test/java/net/praqma/hudson/test/integration/userstories/Story11.java src/test/resources/setup-interproject.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/6a093cc2da
[JIRA] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26985 Re: Poll rebase functionality (case 12578) Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/config.jelly http://jenkins-ci.org/commit/clearcase-ucm-plugin/7c90c3e5f6ddb878c1868eb5e4d371e22adf5d53 Log: Fixed a couple of issues related to JENKINS-26985 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] [clearcase-ucm-plugin] (JENKINS-28835) Reintroduce component for poll rebase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28835 Re: Reintroduce component for poll rebase Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/remoting/CreateRemoteBaseline.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingModeDescriptor.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/help-stream.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/help-component.html src/main/webapp/scm/help-stream.html src/test/java/net/praqma/hudson/test/BaseTestClass.java src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/LoggerRule.java src/test/java/net/praqma/hudson/test/enslaved/Story06WithSlaves.java src/test/java/net/praqma/hudson/test/integration/child/GetBaselinesTest.java src/test/java/net/praqma/hudson/test/integration/rebase/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06Base.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06WithSlaves.java src/test/resources/2bootStrapVob.bat src/test/resources/bootStrapVob.bat http://jenkins-ci.org/commit/clearcase-ucm-plugin/7ec2a7cc30d822b423d30717ca18f9d825db374b Log: Merge pull request #22 from MadsNielsen/ JENKINS-28835 Jenkins 28835 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,
[JIRA] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/a99d2650b2727b113dac348622fa0e18cb43281f Log: Use cool 0.6.38, for JENKINS-26484 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: src/test/resources/setup.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/59bc394997e70ae94ee57b11d248cbe5b33f88ed Log: Fixed and include error for JENKINS-26484 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] [clearcase-ucm-plugin] (JENKINS-28835) Reintroduce component for poll rebase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28835 Re: Reintroduce component for poll rebase Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/remoting/CreateRemoteBaseline.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingModeDescriptor.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/CCUCMScm/help-stream.html src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/help-component.html src/main/webapp/scm/help-stream.html src/test/java/net/praqma/hudson/test/BaseTestClass.java src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/LoggerRule.java src/test/java/net/praqma/hudson/test/enslaved/Story06WithSlaves.java src/test/java/net/praqma/hudson/test/integration/child/GetBaselinesTest.java src/test/java/net/praqma/hudson/test/integration/rebase/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06Base.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06WithSlaves.java src/test/resources/2bootStrapVob.bat src/test/resources/bootStrapVob.bat http://jenkins-ci.org/commit/clearcase-ucm-plugin/665812a54e744498e638728b9e477729fba10f8d Log: Fixed JENKINS-28835 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] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26985 Re: Poll rebase functionality (case 12578) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/CCUCMBuildAction.java src/main/java/net/praqma/hudson/nametemplates/FileFoundable.java src/main/java/net/praqma/hudson/nametemplates/FileTemplate.java src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/notifier/RemotePostBuild.java src/main/java/net/praqma/hudson/remoting/CreateRemoteBaseline.java src/main/java/net/praqma/hudson/remoting/GetRebaseBaselines.java src/main/java/net/praqma/hudson/remoting/RebaseCancelTask.java src/main/java/net/praqma/hudson/remoting/RebaseCompleteTask.java src/main/java/net/praqma/hudson/remoting/RebaseTask.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/Polling.java src/main/java/net/praqma/hudson/scm/pollingmode/PollChildMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollRebaseMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingMode.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSelfMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/SystemValidator.java src/test/java/net/praqma/hudson/test/integration/rebase/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06Base.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/1a4fafdd5734cc4c066d810faeaf2d80023382b5 Log: Merge pull request #21 from MadsNielsen/ JENKINS-26985 JENKINS-26985 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [clearcase-ucm-plugin] (JENKINS-28835) Reintroduce component for poll rebase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28835 Re: Reintroduce component for poll rebase Code changed in jenkins User: Mads Nielsen Path: src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06WithSlaves.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/19f679f87df8d35507daa7bb80e826ad4f08f5eb Log: Disabled a couple of tests for JENKINS-28835 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] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26985 Re: Poll rebase functionality (case 12578) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/hudson/CCUCMBuildAction.java src/main/java/net/praqma/hudson/nametemplates/FileFoundable.java src/main/java/net/praqma/hudson/nametemplates/FileTemplate.java src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java src/main/java/net/praqma/hudson/notifier/RemotePostBuild.java src/main/java/net/praqma/hudson/remoting/CreateRemoteBaseline.java src/main/java/net/praqma/hudson/remoting/GetRebaseBaselines.java src/main/java/net/praqma/hudson/remoting/RebaseCancelTask.java src/main/java/net/praqma/hudson/remoting/RebaseCompleteTask.java src/main/java/net/praqma/hudson/remoting/RebaseTask.java src/main/java/net/praqma/hudson/remoting/RemoteUtil.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/main/java/net/praqma/hudson/scm/Polling.java src/main/java/net/praqma/hudson/scm/pollingmode/PollChildMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollRebaseMode.java src/main/java/net/praqma/hudson/scm/pollingmode/PollingMode.java src/main/resources/net/praqma/hudson/scm/CCUCMScm/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollChildMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollRebaseMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSelfMode/config.jelly src/main/resources/net/praqma/hudson/scm/pollingmode/PollSiblingMode/config.jelly src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/SystemValidator.java src/test/java/net/praqma/hudson/test/integration/rebase/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06Base.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/80079047009b7df550af2e050958fe62a2785312 Log: First iteration on JENKINS-26985 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26985 Re: Poll rebase functionality (case 12578) Code changed in jenkins User: Mads Nielsen Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/d3ab52a1a29ea182225a09719bc560278efb3bd6 Log: Update to the released version of cool, JENKINS-26985 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] [clearcase-ucm-plugin] (JENKINS-28835) Reintroduce component for poll rebase
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28835 Re: Reintroduce component for poll rebase Code changed in jenkins User: Mads Nielsen Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/17b35c4a0d0c8cc1c831ab45769ea0c28e445951 Log: Set for count for JENKINS-28835 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26484 Re: Poll sibling from named stream (case 12577) Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/SystemValidator.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/sibling/BaselinesFound.java src/test/java/net/praqma/hudson/test/integration/userstories/Story11.java src/test/resources/setup-interproject.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/93dd012466c4b771b79b2c7f1ccbe0ace0b183ee Log: Implemented tests for JENKINS-26484 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-27616) Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave
Title: Message Title youri bonnaffe commented on JENKINS-27616 Re: Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave I observed this with 1.614 and 1.617. 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] [zaproxy-plugin] (JENKINS-28922) Support authentication
Title: Message Title Simon Bennetts created an issue Jenkins / JENKINS-28922 Support authentication Issue Type: New Feature Assignee: Ludovic Roucoux Components: zaproxy-plugin Created: 16/Jun/15 1:12 PM Priority: Minor Reporter: Simon Bennetts Apparently the zaproxy plugin doesnt handle authentication: https://groups.google.com/d/msg/zaproxy-users/cZOgjhS8SkI/5pGGD0lw7KsJ As mentioned on that thread a relatively easy way to support this could be to allow the user to specify a ZAP Context that has previously been created using the ZAP GUI. Add Comment
[JIRA] [core] (JENKINS-28685) NullPointerException when saving Jenkins project
Title: Message Title Daniel Beck resolved as Incomplete No response to comment asking for additional information in two weeks, so resolving as incomplete. Any further investigation will need more information than what was provided in this report. Jenkins / JENKINS-28685 NullPointerException when saving Jenkins project Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title Jesse Glick resolved as Fixed IMO the original fix to getResource can be merged into stable-1.609 without considering the soak period for the getResources addition. Jenkins / JENKINS-27289 Masking classLoader doesn`t work on remote Slave Change By: Jesse Glick Status: In Progress Resolved 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] [core] (JENKINS-25164) Provide a short $JOB_NAME inside a folder
Title: Message Title
Walter Kacynski commented on JENKINS-25164
Re: Provide a short $JOB_NAME inside a folder
Groovy Script that can be used. This will pull only the last portion of the job name and create a new environment variable.
JOBNAME = build.getEnvironment(null)["JOB_NAME"]
def match = JOBNAME =~ /.*\/(.*)/
if (match) {
e = new hudson.EnvVars()
e.put('SHORT_JOB_NAME', match[0][1])
build.environments.add(hudson.model.Environment.create(e))
}
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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: core/src/main/java/hudson/util/MaskingClassLoader.java http://jenkins-ci.org/commit/jenkins/40e75129f40675f8a71b489b38c5911b37cb8559 Log: Contine the JENKINS-27289 ticket: update the getResources as well 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: changelog.html war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/dc23c1120d7758a9288c418b49ab887309fa5e62 Log: Merge branch 'master' into JENKINS-27289 -update 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/MaskingClassLoader.java http://jenkins-ci.org/commit/jenkins/f3f8abd36bdd60d2d85c9cd5a9f2555640dd53a1 Log: Merge pull request #1725 from liorhson/ JENKINS-27289 -update Contine the JENKINS-27289 ticket: update the getResources as well Compare: https://github.com/jenkinsci/jenkins/compare/a013c033685d...f3f8abd36bdd 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] [violations-plugin] (JENKINS-28880) Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED"
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-28880 Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED" Change By: Tomas Bjerre Assignee: peterkittreilly Tomas Bjerre 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] [gearman-plugin] (JENKINS-25867) Gearman won't schedule new jobs even though there are slots available on master
Title: Message Title Christian Bremer commented on JENKINS-25867 Re: Gearman won't schedule new jobs even though there are slots available on master No we are not using "OFFLINE_NODE_WHEN_COMPLETE=true" in our instances. You are correct in your assumption that we use multiple executors slots on almost all nodes, although I have seen this on nodes with 1 slot as well. 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] [violations-plugin] (JENKINS-28880) Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED"
Title: Message Title Tomas Bjerre started work on JENKINS-28880 Change By: Tomas Bjerre 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] [nested-view-plugin] (JENKINS-28923) Nested View causes StackOverflowError
Title: Message Title Tim-Christian Bloss updated an issue Jenkins / JENKINS-28923 Nested View causes StackOverflowError Change By: Tim-Christian Bloss Attachment: jenkins_stacktrace.txt Attachment: 2015-06-16 16_22_22-01.Entwicklung [Jenkins].png Attachment: 2015-06-16 16_21_43-01.Entwicklung [Jenkins].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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18537 Re: ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Code changed in jenkins User: MerkushevKirill Path: pom.xml http://jenkins-ci.org/commit/github-plugin/5287c6c8e76d2bc18e86372f5d40179964a80d2f Log: fix for build and run with jdk8 ( JENKINS-18537 ) 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18537 Re: ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Code changed in jenkins User: Kanstantsin Shautsou Path: pom.xml http://jenkins-ci.org/commit/github-plugin/518aeccb26a2ca1a91d284aa648c80c974e785e6 Log: Merge pull request #55 from lanwen/webhooks fix for build and run with jdk8 ( JENKINS-18537 ) Compare: https://github.com/jenkinsci/github-plugin/compare/e5e5674f03de...518aeccb26a2 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Christophe Lallement commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions Can you upgrade to at least 3.2.5 ? Or add an option to fully skip pom validation Thx Christophe 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Christophe Lallement edited a comment on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions Can you upgrade to at least 3.2.5 ?Or add an option to fully skip pom validationThx Christophe 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] [cli] (JENKINS-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
Title: Message Title Jonathon Golden commented on JENKINS-22346 Re: CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean Daniel Beck, Starting Jenkins with that property I can pass the private key successfully if security is turned off but the user with the corresponding public key still exists at /var/lib/jenkins/users. With security is turned off, if I pass the key and that user does not exist I just get an auth failure. I'm assuming this is the expected behavior but it would be helpful if there was a way to pass the key every time and just proceed anonymously if there is no need for the key yet. The use case I'm interested in this for is when managing the Jenkins instances with Puppet. This behavior creates a major chicken and egg dilemma. There is a workaround described here: https://forge.puppetlabs.com/rtyler/jenkins but is is not very desirable. Given that I can at least seed the user with a config file managed with puppet and using the java arg you suggested I have a better workaround now. It would be nice, however, if instead it behaved the way I described above. 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] [parallel-test-executor-plugin] (JENKINS-28924) Make the plugin generic and language neutral
Title: Message Title Timmy Brolin created an issue Jenkins / JENKINS-28924 Make the plugin generic and language neutral Issue Type: New Feature Assignee: Unassigned Components: parallel-test-executor-plugin Created: 16/Jun/15 4:46 PM Priority: Minor Reporter: Timmy Brolin We would like to use this plugin for VHDL testing. Unfortunately, several aspects of the plugin makes it java-specific. I suggest the plugin is modified so that it becomes more generic and useful for all kinds of tests regardless of language. These changes must be made: 1: The plugin currently paralellises on the "testclass" granularity. In systems other than java there is no "testclass" concept. Just a bunch of "testcases". The plugin assumes all testcases belong to the same class, and is unable to paralellise any tests. The plugin should be changed to parallelize on the "testcase" granularity. For backwards compatibility, the plugin could autodetect if any testclasses exists. 2: The plugin appends ".java" and ".class" to each testname in the exclusionfile. The testnames should be unmodified. 3: The plugin replaces all "." with "/" in the testnames. The testnames should be unmodified.
[JIRA] [parallel-test-executor-plugin] (JENKINS-28924) Make the plugin generic and language neutral
Title: Message Title Timmy Brolin updated an issue Jenkins / JENKINS-28924 Make the plugin generic and language neutral Change By: Timmy Brolin We would like to use this plugin for VHDL testing.Unfortunately, several aspects of the plugin makes it java-specific.I suggest the plugin is modified so that it becomes more generic and useful for all kinds of tests regardless of language.These changes must be made:1: The plugin currently paralellises parallelises on the "testclass" granularity. In systems other than java there is no "testclass" concept. Just a bunch of "testcases". The plugin assumes all testcases belong to the same class, and is unable to paralellise parallelise any tests. The plugin should be changed to parallelize parallelise on the "testcase" granularity.For backwards compatibility, the plugin could autodetect if any testclasses exists.2: The plugin appends ".java" and ".class" to each testname in the exclusionfile. The testnames should be unmodified.3: The plugin replaces all "." with "/" in the testnames. The testnames should be unmodified. 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] [windows-slaves-plugin] (JENKINS-25785) Windows slaves controlled as Windows Service do not use credentials manager
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25785 Re: Windows slaves controlled as Windows Service do not use credentials manager Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/ClassicPluginStrategy.java http://jenkins-ci.org/commit/jenkins/78f631805dacc6682e67123bd5e9c16e251259ef Log: Merge pull request #1735 from Vlatombe/JENKINS-25785_prerequisite Prerequisite for JENKINS-25785 Compare: https://github.com/jenkinsci/jenkins/compare/f3f8abd36bdd...78f631805dac 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] [windows-slaves-plugin] (JENKINS-25785) Windows slaves controlled as Windows Service do not use credentials manager
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25785 Re: Windows slaves controlled as Windows Service do not use credentials manager Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/hudson/ClassicPluginStrategy.java http://jenkins-ci.org/commit/jenkins/a65d007533cc882d85715677ec75f06e001e1e8a Log: Prerequisite for JENKINS-25785 in order to break dependency cycle when windows-slaves will depend on credentials 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-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title Jesse Glick resolved as Not A Defect Per-node environment variables are not expected to be defined unless you are inside a node block which winds up running on the node in question. Jenkins / JENKINS-28921 Can't access Jenkins Global Properties from groovy script Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1
Title: Message Title Jesse Glick resolved as Duplicate Closing as covered by the core fix unless I hear information to the contrary. Jenkins / JENKINS-27476 Plugin casue deadlock on Jenkins LTS 1.596.1 Change By: Jesse Glick Status: Open Resolved 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] [workflow-plugin] (JENKINS-28892) Parts of workflow not cancelable after crash
Title: Message Title Jesse Glick resolved as Incomplete Certainly a bug, but cannot diagnose without a way to reproduce, or detailed analysis of logs and build records. Jenkins / JENKINS-28892 Parts of workflow not cancelable after crash Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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] [parameterized-trigger-plugin] (JENKINS-28925) Job triggered on failure (when it shouldn't)
Title: Message Title Edgar Merino created an issue Jenkins / JENKINS-28925 Job triggered on failure (when it shouldn't) Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 16/Jun/15 5:05 PM Environment: Jenkins 1.617 Parameterized Trigger Plugin 2.26 CentOS 5 Priority: Minor Reporter: Edgar Merino When using the plugin as a build step (post build task, Trigger/call builds on other projects), the build will be triggered when the current job fails, even when "Execute only in case of success". I'd expect the job to be triggered only when the job was successful, but it'll run everytime (even if it fails). Add Comment
[JIRA] [core] (JENKINS-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Eloy Lafuente created an issue Jenkins / JENKINS-28926 Jenkins queue self-locking without apparent reason? Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Jun/15 5:07 PM Priority: Minor Reporter: Eloy Lafuente Since some weeks ago we are experimenting some problems with the jenkins queue. While looking for dupes before creating this... I've found a bunch of issues, similar, but I'm not sure if any of them are the very same issue than this, because they often comment about various plugins we are not using at all). Here it's a brief list of those "similar" issues, just in case, at the end, all them are the same problem: JENKINS-28532, JENKINS-28887, JENKINS-28136, JENKINS-28376, JENKINS-28690 ... One thing in common for all them is that they are really recent and it seems to be common that, whatever the problem is, it started around 1.611. While I don't have the exact version for our case (coz we update continuously) I'd say it started happening also recently here. Description: We have 2 jenkins server, a public one (linux) and a private/testing (mac) one. And we are experimenting the same problem in both. This is the URL of the public one: http://integration.moodle.org There we have some "chains" of free-form jobs, with all the
[JIRA] [core] (JENKINS-28899) Break dependency cycles between credentials and windows-slaves plugins
Title: Message Title Vincent Latombe closed an issue as Fixed Jenkins / JENKINS-28899 Break dependency cycles between credentials and windows-slaves plugins Change By: Vincent Latombe 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] [core] (JENKINS-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Eloy Lafuente updated an issue Jenkins / JENKINS-28926 Jenkins queue self-locking without apparent reason? Change By: Eloy Lafuente Since some weeks ago we are experimenting some problems with the jenkins queue.While looking for dupes before creating this... I've found a bunch of issues, similar, but I'm not sure if any of them are the very same issue than this, because they often comment about various plugins we are not using at all). Here it's a brief list of those "similar" issues, just in case, at the end, all them are the same problem: JENKINS-28532, JENKINS-28887, JENKINS-28136, JENKINS-28376, JENKINS-28690...One thing in common for all them is that they are really recent and it seems to be common that, whatever the problem is, it started around 1.611. While I don't have the exact version for our case (coz we update continuously) I'd say it started happening also recently here.Description:We have 2 jenkins server, a public one (linux) and a private/testing (mac) one. And we are experimenting the same problem in both. This is the URL of the public one:http://integration.moodle.orgThere we have some "chains" of free-form jobs, with all the jobs having both the "Block build when upstream project is building" and "Block build when downstream project is building" settings ticked.The first job is always a git-pull-changes one and it starts the "chain" whenever changes are detected in the target branch. We have one chain for every supported branch.And this has been working since ages ago (years). If for any reason a job was manually launched or the scheduled (every 5 minutes) git job detected new changes... it never has been a problem. Those new jobs were there, in the queue, waiting for the current "chain" to finish. And, once finished, the queue handling was clever enough to detect the 1st job to execute from it, also deleting dupes or whatever was needed.Basically, the summary is that it never become stuck, no matter how new jobs were in the queue or how they had landed to it (manually or automatically). So far, perfect.But, since some versions ago.. that has changed drastically. Now, if we add manually jobs to the queue, of if multiple changes are detected in a short period of time... those jobs in the queue correctly wait for the current "chain" to end (like they used to do, can be viewed hovering over elements). But once the chain has ended, the queue is not able to decide any job to start with, and it became "locked" forever.Right now, if you go to the server above... you'll see that there are 4 jobs, all them belonging to the "master" view/branch/chain, awaiting in the queue... never launched and, worse, preventing new runs in that branch to happen. And the hover information does not show any waiting cause (screenshots added, showing both manually added jobs when the chain was running and automatic jobs, any of them with a reason for the locking, as far as all the executors are idle).And those self-locks are really having an impact here, because it's transforming our "continuous automatic integration" experience into a "wow, we have not run tests for master since 2 days ago, wtf, let's kill the queue manually and process all changes together, grrr" thing. Sure you get it, lol.Those servers and chains have been working perf
[JIRA] [core] (JENKINS-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Eloy Lafuente updated an issue Jenkins / JENKINS-28926 Jenkins queue self-locking without apparent reason? Change By: Eloy Lafuente Attachment: self_locked_automatic.png Attachment: self_locked_manual.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] [cloudbees-folder-plugin] (JENKINS-28806) Windows C / C++ project doesn't compile after using cloudbee folder
Title: Message Title Jesse Glick resolved as Incomplete Almost certainly a user error of some kind, but it is too hard to diagnose without a minimal test case. Jenkins / JENKINS-28806 Windows C / C++ project doesn't compile after using cloudbee folder Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete Did you check with Workflow 1.8? 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-28797) NPE in CpsFlowExecution sometimes results in unkillable build
Title: Message Title Jesse Glick resolved as Incomplete Unless there is a way to reproduce, probably not enough info here. Would require analyzing build record files in detail. Jenkins / JENKINS-28797 NPE in CpsFlowExecution sometimes results in unkillable build Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title Daniel Beck commented on JENKINS-28921 Re: Can't access Jenkins Global Properties from groovy script Jesse Glick These aren't the master-specific env vars and expected to really be global AFAICT. 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-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Eloy Lafuente updated an issue Jenkins / JENKINS-28926 Jenkins queue self-locking without apparent reason? Change By: Eloy Lafuente Since some weeks ago we are experimenting some problems with the jenkins queue.While looking for dupes before creating this... I've found a bunch of issues, similar, but I'm not sure if any of them are the very same issue than this, because they often comment about various plugins we are not using at all). Here it's a brief list of those "similar" issues, just in case, at the end, all them are the same problem: JENKINS-28532, JENKINS-28887, JENKINS-28136, JENKINS-28376, JENKINS-28690...One thing in common for all them is that they are really recent and it seems to be common that, whatever the problem is, it started around 1.611. While I don't have the exact version for our case (coz we update continuously) I'd say it started happening also recently here.Description:We have 2 jenkins server, a public one (linux) and a private/testing (mac) one. And we are experimenting the same problem in both. This is the URL of the public one:http://integration.moodle.orgThere we have some "chains" of free-form jobs, with all the jobs having both the "Block build when upstream project is building" and "Block build when downstream project is building" settings ticked.The first job is always a git-pull-changes one and it starts the "chain" whenever changes are detected in the target branch. We have one chain for every supported branch.And this has been working since ages ago (years). If for any reason a job was manually launched or the scheduled (every 5 minutes) git job detected new changes... it never has been a problem. Those new jobs were there, in the queue, waiting for the current "chain" to finish. And, once finished, the queue handling was clever enough to detect the 1st job to execute from it, also deleting dupes or whatever was needed.Basically, the summary is that it never become became stuck, no matter how new jobs were in the queue or how they had landed to it (manually or automatically). So far, perfect.But, since some versions ago.. that has changed drastically. Now, if we add manually jobs to the queue, of if multiple changes are detected in a short period of time... those jobs in the queue correctly wait for the current "chain" to end (like they used to do, can be viewed hovering over elements). But once the chain has ended, the queue is not able to decide any job to start with, and it became "locked" forever.Right now, if you go to the server above... you'll see that there are 4 jobs, all them belonging to the "master" view/branch/chain, awaiting in the queue... never launched and, worse, preventing new runs in that branch to happen. And the hover information does not show any waiting cause (screenshots added, showing both manually added jobs when the chain was running and automatic jobs, any of them with a reason for the locking, as far as all the executors are idle).And those self-locks are really having an impact here, because it's transforming our "continuous automatic integration" experience into a "wow, we have not run tests for master since 2 days ago, wtf, let's kill the queue manually and process all changes together, grrr" thing. Sure you get it, lol.Those servers and chains have been wo
[JIRA] [core] (JENKINS-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Daniel Beck commented on JENKINS-28926 Re: Jenkins queue self-locking without apparent reason? There we have some "chains" of free-form jobs, with all the jobs having both the "Block build when upstream project is building" and "Block build when downstream project is building" settings ticked. The jobs in the queue block each 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-28921) Can't access Jenkins Global Properties from groovy script
Title: Message Title
Jesse Glick commented on JENKINS-28921
Re: Can't access Jenkins Global Properties from groovy script
Well I guess these are distinct from the master vars listed at /computer/(master)/configure. Anyway node-based env vars are available only inside node steps. You can see them all for example with
node {sh 'env'}
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-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Eloy Lafuente commented on JENKINS-28926 Re: Jenkins queue self-locking without apparent reason? The jobs in the queue block each other. 1) There is not information in the "hover" information about those blockings at all (see screenshots). 2) Until recently, that did not happen ever. The queue was clever enough to pick the first (in the chain) job and start executing it. That's the point. It has become "silly", lol. Ciao 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-22028) HTML in job description does not get rendered (all html tags escaped)
Title: Message Title Jesse Glick commented on JENKINS-22028 Re: HTML in job description does not get rendered (all html tags escaped) Radek Antoniuk file a PR to change the UI labels to refer to “plain text”. 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-28769) enable codemirror on workflow DSL
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28769 enable codemirror on workflow DSL Change By: Jesse Glick Priority: Minor Critical 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-28769) enable codemirror on workflow DSL
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28769 enable codemirror on workflow DSL Change By: Jesse Glick Labels: codemirror 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-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Daniel Beck commented on JENKINS-28926 Re: Jenkins queue self-locking without apparent reason? Uh… yeah that wasn't supposed to be the only text in the comment. Sorry about that. So yes, it's a problem. The feature was (IMO) pretty bad to begin with, now it's a joke. Will probably need to exclude queued items from being considered, so something will be able to escape the deadlock. 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-28926) Jenkins queue self-locking without apparent reason?
Title: Message Title Daniel Beck assigned an issue to stephenconnolly Assigning stephenconnolly, asking for feedback. WDYT? Looks like this was introduced by the queue fixes. Jenkins / JENKINS-28926 Jenkins queue self-locking without apparent reason? Change By: Daniel Beck Assignee: stephenconnolly 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.
