[JIRA] [wildfly-deployer-plugin] (JENKINS-33504) FATAL: missing dependencies
Title: Message Title John Redwood commented on JENKINS-33504 Re: FATAL: missing dependencies I'm getting the same issue: Jenkins : 1.651.2 WildFly Deployer Plugin: 1.0.2 OpenJDK Runtime Environment1.8.0_91-8u91-b14-0ubuntu4~15.10.1-b14 I didn't go through your effort, i just ignored the plugin all together and added a post step of maven to run command wildfly:deploy with the appropriate login details for deploy access. and that works a treat. 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-18643) Make tests run on Windows
Title: Message Title ikedam resolved as Incomplete Sorry, but I give up this issue as I don't enough time to work on. Jenkins / JENKINS-18643 Make tests run on Windows Change By: ikedam 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] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory
Title: Message Title ikedam assigned an issue to larsskj Fixed in 1.2.2. It will be available in the update center in a day. Please try that. But as I described before, that fix results builds running as anonymous user for users Active Directory failed to access user information. You have to configure Active Directory plugin to allow to access user information even without user credentials. Jenkins / JENKINS-34279 Fails with Active Directory Change By: ikedam Assignee: ikedam larsskj Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34279 Re: Fails with Active Directory Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategyTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/testutil/SecurityRealmWithUserFilter.java http://jenkins-ci.org/commit/authorize-project-plugin/e4ff3a19bc775b46361f4bfdac7d0a4b0f114b06 Log: [FIXED JENKINS-34279] Handle UsernameNotFoundException. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34279 Re: Fails with Active Directory Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategyTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/testutil/SecurityRealmWithUserFilter.java http://jenkins-ci.org/commit/authorize-project-plugin/cf96cbb0120200b1353e10bf60b048130c5b980e Log: Merge pull request #24 from ikedam/feature/ JENKINS-34279 _UsernameNotFound [FIXED JENKINS-34279] Handle UsernameNotFoundException. Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/5a3088e771fa...cf96cbb01202 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34279 Fails with Active Directory Change By: SCM/JIRA link daemon 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] [build-timeout-plugin] (JENKINS-34846) Upgrade build-timeout-plugin to new parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34846 Re: Upgrade build-timeout-plugin to new parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml http://jenkins-ci.org/commit/build-timeout-plugin/1c0bc91f64ab6085ca02c14255f0bbeeded7354c Log: JENKINS-34846 Keep 1.466 baseline. Use 1.466 test harness. 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-timeout-plugin] (JENKINS-34846) Upgrade build-timeout-plugin to new parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34846 Re: Upgrade build-timeout-plugin to new parent pom Code changed in jenkins User: Armando Fernandez Path: pom.xml src/main/java/hudson/plugins/build_timeout/BuildTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/DeadlineTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/LikelyStuckTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/NoActivityTimeOutStrategy.java src/main/resources/index.jelly http://jenkins-ci.org/commit/build-timeout-plugin/be43f3966617acd56f8d7f69f03df3b8162da83f Log: JENKINS-34846 Migrate to 2.9 parent pom. Bump baseline Fix javadoc issues. 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-timeout-plugin] (JENKINS-34846) Upgrade build-timeout-plugin to new parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34846 Re: Upgrade build-timeout-plugin to new parent pom Code changed in jenkins User: ikedam Path: pom.xml src/main/java/hudson/plugins/build_timeout/BuildTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/DeadlineTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/LikelyStuckTimeOutStrategy.java src/main/java/hudson/plugins/build_timeout/impl/NoActivityTimeOutStrategy.java src/main/resources/index.jelly http://jenkins-ci.org/commit/build-timeout-plugin/116563d0ebbea77d3011e8668c99a2281431e776 Log: Merge pull request #53 from armfergom/JENKINS-34846 JENKINS-34846 Migrate to 2.9 plugin pom Compare: https://github.com/jenkinsci/build-timeout-plugin/compare/fe9dcd5359b3...116563d0ebbe 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] [ec2-plugin] (JENKINS-35196) EC2-plugin not spooling up stopped nodes - job is in queue, node is offline
Title: Message Title Gleb Zverinskiy updated an issue Jenkins / JENKINS-35196 EC2-plugin not spooling up stopped nodes - job is in queue, node is offline Change By: Gleb Zverinskiy Attachment: Untitled3.png Job is in queue waiting to go, slave is in "stopped" state and is not started by Jenkins. If a user presses "Launch Agent" then the node will be started.!Untitled.png|thumbnail!!Untitled1.png|thumbnail!!Untitled2.png|thumbnail! !Untitled3.png|thumbnail! 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] [ec2-plugin] (JENKINS-35196) EC2-plugin not spooling up stopped nodes - job is in queue, node is offline
Title: Message Title Gleb Zverinskiy updated an issue Jenkins / JENKINS-35196 EC2-plugin not spooling up stopped nodes - job is in queue, node is offline Jenkins log May 27, 2016 6:07:53 PM hudson.model.Run execute INFO: AWS_slave_cds_test #17 main build action completed: SUCCESS May 27, 2016 6:07:53 PM jenkins.plugins.model.JobFailedTimeInfo recordFailedTimeInfo INFO: last7days buildCount : 2 May 27, 2016 6:08:46 PM hudson.model.Run execute INFO: AWS_slave_cds_test #18 main build action completed: SUCCESS May 27, 2016 6:08:46 PM jenkins.plugins.model.JobFailedTimeInfo recordFailedTimeInfo INFO: last7days buildCount : 2 May 27, 2016 6:13:37 PM hudson.plugins.ec2.EC2RetentionStrategy internalCheck INFO: Idle timeout of slave (**) after 4 idle minutes, with 0 minutes remaining in billing period May 27, 2016 6:13:37 PM hudson.plugins.ec2.EC2AbstractSlave idleTimeout INFO: EC2 instance idle time expired: *** May 27, 2016 6:13:38 PM hudson.plugins.ec2.EC2AbstractSlave stop INFO: EC2 instance stop request sent for *** May 27, 2016 6:14:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 6:14:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 511 ms May 27, 2016 6:15:37 PM hudson.plugins.ec2.EC2RetentionStrategy internalCheck INFO: Idle timeout of slave (**) after 6 idle minutes, with 0 minutes remaining in billing period May 27, 2016 6:15:37 PM hudson.plugins.ec2.EC2AbstractSlave idleTimeout INFO: EC2 instance idle time expired: *** May 27, 2016 6:15:40 PM hudson.plugins.ec2.EC2AbstractSlave stop INFO: EC2 instance stop request sent for *** May 27, 2016 6:24:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 6:24:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 572 ms May 27, 2016 6:34:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 6:34:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 628 ms May 27, 2016 6:44:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 6:44:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 605 ms May 27, 2016 6:54:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 6:54:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 629 ms May 27, 2016 7:04:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 7:04:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 570 ms May 27, 2016 7:13:37 PM hudson.plugins.ec2.EC2RetentionStrategy internalCheck INFO: Idle timeout of slave (**) after 64 idle minutes, with 0 minutes remaining in billing period May 27, 2016 7:13:37 PM hudson.plugins.ec2.EC2AbstractSlave idleTimeout INFO: EC2 instance idle time expired: *** May 27, 2016 7:13:38 PM hudson.plugins.ec2.EC2AbstractSlave stop INFO: EC2 instance stop request sent for *** May 27, 2016 7:14:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor May 27, 2016 7:14:25 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 462 ms May 27, 2016 7:15:37 PM hudson.plugins.ec2.EC2RetentionStrategy internalCheck INFO: Idle timeout of slave
[JIRA] [ec2-plugin] (JENKINS-35196) EC2-plugin not spooling up stopped nodes - job is in queue, node is offline
Title: Message Title Gleb Zverinskiy created an issue Jenkins / JENKINS-35196 EC2-plugin not spooling up stopped nodes - job is in queue, node is offline Issue Type: Bug Assignee: Francis Upton Attachments: Untitled.png, Untitled1.png, Untitled2.png Components: ec2-plugin Created: 2016/May/28 1:51 AM Environment: Jenkins 2.6(docker) EC2 plugin 1.33 Priority: Major Reporter: Gleb Zverinskiy Job is in queue waiting to go, slave is in "stopped" state and is not started by Jenkins. If a user presses "Launch Agent" then the node will be started.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view
Title: Message Title Ken Lamb commented on JENKINS-33498 Re: Improve full screen view of pipeline stage view FWIW: I would like this ability as well. Currently, I have long stage names that stretch the stages to the right where they get cut off and I have to scroll. Meanwhile, if the page is being displayed in full screen mode, half of the screen is blank next to the stage view. Rather than scrolling right, it would be nice if the screen view would just use all of that real estate. 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat I believe I installed all the dependent plugins. (until i did so, they would not load at all – and printed errors in catalina.out.) - jenkins/blue does not work 17:00:49 root@jenkins /var/lib/jenkins/plugins $ ls *.hpi *.jpi ace-editor.jpi git.jpi promoted-builds.jpi active-directory.jpi git-server.jpi publish-over-cifs.jpi ansicolor.jpi groovy.jpi rebuild.jpi antisamy-markup-formatter.jpi groovy-postbuild.jpi run-condition.jpi ant.jpi handlebars.jpi rundeck.jpi blueocean-commons.hpi icon-shim.jpi scm-api.jpi blueocean-dashboard.hpi jackson2-api.jpi scriptler.jpi blueocean-rest.hpi javadoc.jpi script-security.jpi blueocean-web.hpi jenkinswalldisplay.jpi setenv.jpi bootstrap.hpi jquery-detached.jpi shelve-project-plugin.jpi branch-api.jpi jquery.jpi sse-gateway.jpi build-flow-plugin.jpi junit.jpi ssh-credentials.jpi buildgraph-view.jpi ldap.jpi ssh-slaves.jpi build-history-metrics-plugin.jpi mailer.jpi storable-configs-plugin.jpi build-timeout.jpi mapdb-api.jpi structs.jpi cloudbees-folder.jpi matrix-auth.jpi subversion.jpi conditional-buildstep.jpi matrix-project.jpi timestamper.jpi console-column-plugin.jpi maven-plugin.jpi token-macro.jpi cors-filter.jpi metrics.jpi translation.jpi credentials.jpi momentjs.jpi uno-choice.jpi cvs.jpi msbuild.jpi validating-string-parameter.jpi dropdown-viewstabbar-plugin.jpi nodelabelparameter.jpi variant.jpi durable-task.jpi pam-auth.jpi versionnumber.jpi dynamicparameter.jpi parameterized-trigger.jpi windows-slaves.jpi email-ext.jpi perforce.jpi workflow-aggregator.jpi envinject.jpi pipeline-build-step.jpi workflow-api.jpi extended-choice-parameter.jpi pipeline-input-step.jpi workflow-basic-steps.jpi extensible-choice-parameter.jpi pipeline-rest-api.jpi workflow-cps-global-lib.jpi external-monitor-job.jpi pipeline-stage-step.jpi workflow-cps.jpi favorite.hpi pipeline-stage-view.jpi workflow-durable-task-step.jpi filesystem-list-parameter-plugin.jpi plain-credentials.jpi workflow-job.jpi git-client.jpi plot.jpi workflow-multibranch.jpi github-api.jpi postbuildscript.jpi workflow-scm-step.jpi github-branch-source.jpi postbuild-task.jpi workflow-step-api.jpi github.jpi powershell.jpi workflow-support.jpi github-organization-folder.jpi PrioritySorter.jpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Vivek Pandey commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat This is strange, for some reason Jenkins is not installing dependent plugins. I tried on Tomcat 7 and it somehow complains not able to find these plugins as some of the dependencies are not resolved. I had to install blueocean-web and see-gateway plugin from Jenkins Manage Plugins console (ManageJenkins->Manage Plugins->Advanced) and then I could load /jenkins/blue page. While we investigate whats going on, you can try this workaround. 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Interesting, have run this with jetty/embedded (not just hpi:run) so I expect this may be easy to solve. 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Curtis Salisbury updated an issue Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Curtis Salisbury Attachment: Test Statistics Grid.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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Curtis Salisbury commented on JENKINS-33952 Re: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed I am having the same problem with the Test Statistics Grid. The numbers for one job have never populated and the others seem to not 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines created an issue Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Issue Type: Bug Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2016/May/27 9:54 PM Priority: Major Reporter: Ben Hines I built the 4 blueocean plugins and copied them to my jenkins (2.6) plugin dir, and i see them in the plugin manager, but i am unable to hit the /jenkins/blue endpoint. It just returns 404. They work fine when run via the hpi:run method. I'm using Jenkins running within Tomcat 7.0.54. There are no errors in catalina.out. Is there anything I need to do to set this up properly? Add Comment
[JIRA] [nodejs-plugin] (JENKINS-19227) NodeJS plugin not showing in configuration
Title: Message Title Bill Warner commented on JENKINS-19227 Re: NodeJS plugin not showing in configuration it seems this is no longer under Jenkins->Configure System, it was moved to Jenkins->Global Tool Configuration. 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-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-34350 CSRF breaks generic polling skipper /git/notifyCommit?url=""> Change By: Mark Waite Comment: [~ydubreuil] that is the first I've seen anyone use a POST with the notifyCommit URL. That URL seems (at least to me) like a clear use of GET. Is there a specific reason you used -X POST instead of using the curl defaults?You're correct that there is no CrumbExclusion in the git plugin. I didn't find one when I looked, and didn't add one. I wanted to confirm that it would be useful and have the desired affect before I added one. I couldn't find any case where the notifyCommit URL was rejected for lack of a crumb. It uses GET in the original blog posting, and in all the examples I've seen except yours. 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] [ec2-plugin] (JENKINS-35194) cannot run job using EC2 plugin
Title: Message Title Gleb Zverinskiy closed an issue as Not A Defect user error, I had EC2 Environment as a build step because I thought it was needed. Jenkins / JENKINS-35194 cannot run job using EC2 plugin Change By: Gleb Zverinskiy Status: Open Closed 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] [script-security-plugin] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-25804 Whitelisted signature presets for Java standard APIs and Jenkins core APIs Change By: Patrick Wolf Summary: Whitelisted signature presets for Java standard APIs and Jenkuns Jenkins core APIs 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] [script-security-plugin] (JENKINS-34658) Whitelist more Functions for trivial operations on builtin types
Title: Message Title Patrick Wolf commented on JENKINS-34658 Re: Whitelist more Functions for trivial operations on builtin types This looks like a duplicate of JENKINS-25804. Can we close this one and link 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] [script-security-plugin] (JENKINS-24982) Bottom-up white/blacklisting vs top-down
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-24982 Bottom-up white/blacklisting vs top-down Change By: Patrick Wolf Labels: api followup 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] [nodejs-plugin] (JENKINS-19227) NodeJS plugin not showing in configuration
Title: Message Title Fred R commented on JENKINS-19227 Re: NodeJS plugin not showing in configuration Running 2.6, same issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Mark Waite commented on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> Yoann Dubreuil that is the first I've seen anyone use a POST with the notifyCommit URL. That URL seems (at least to me) like a clear use of GET. Is there a specific reason you used -X POST instead of using the curl defaults? You're correct that there is no CrumbExclusion in the git plugin. I didn't find one when I looked, and didn't add one. I wanted to confirm that it would be useful and have the desired affect before I added one. I couldn't find any case where the notifyCommit URL was rejected for lack of a crumb. It uses GET in the original blog posting, and in all the examples I've seen except yours. 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-34641) Update CCtray (cc.xml) to support Jenkins2 folders
Title: Message Title Christian Höltje commented on JENKINS-34641 Re: Update CCtray (cc.xml) to support Jenkins2 folders It may be obsolete-ish, but it is really to easy to use and things like the GitHub Authorization plugin expose it without requiring username and password if you want. 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] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title
Sam Van Oort commented on JENKINS-34791
Re: Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits
Ilja Gaitsenja The problem you're experiencing is probably that the job is blocked waiting for an executor slot (which the node block is acquiring), and the stage isn't created until the executor is available (when the node block starts executing its contents).
This should avoid the issue you see:
stage 'testing'
node {
echo 'before input'
sh "echo 'I am doing something that requires a node here' "
sh 'mvn clean install' // Example, something like that
}
// Best practice: don't hold the node longer than you need to, and echo/stage/sleep steps don't need a node to run, of course
stage 'testing 2'
sleep 60
user-settable property to configure the hardcoded limits
That was a small, related request-for-enhancement I wanted to tie together with similar code changes here.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-35194) cannot run job using EC2 plugin
Title: Message Title Gleb Zverinskiy created an issue Jenkins / JENKINS-35194 cannot run job using EC2 plugin Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/May/27 8:05 PM Environment: Jenkins 2.6 using docker EC2 plugin version: 1.33 Priority: Major Reporter: Gleb Zverinskiy I have a AMI in Amazon, I can launch an instance from the nodes screen and the instance comes up and shows that it is connected. When I run my job itself I get the following error message in the job log us-east-1 Tagging ENVIRONMENT [undefined] with VERSION [undefined] 15:33:24 ERROR: Could not tag ENVIRONMENT [undefined] with VERSION [undefined] jenkins logs: May 27, 2016 4:05:17 PM de.codecentric.jenkins.dashboard.impl.environments.ec2.EC2Connector tagEnvironmentWithVersion INFO: tagEnvironmentWithVersion us-east-1 Tag undefined version undefined May 27, 2016 4:05:19 PM hudson.model.Run execute INFO: AWS_slave_cds_test #8 main build action completed: FAILURE May 27, 2016 4:05:19 PM jenkins.plugins.model.JobFailedTimeInfo recordFailedTimeInfo INFO: last7days buildCount : 0
[JIRA] [_unsorted] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Sergii Snig created an issue Jenkins / JENKINS-35193 Cannot check connection status of the update site with ID='default' Issue Type: Bug Assignee: Oleg Nenashev Attachments: error.png Components: _unsorted Created: 2016/May/27 7:47 PM Environment: Name : jenkins Arch : noarch Version : 2.6 Release : 1.1 Priority: Critical Reporter: Sergii Snig Fresh installation of Jenkins 2.6 on Fedore 21 By attempting to connect http://localhost:8080 after admin password confirmation appeared — An error occurred Default update site connectivity check failed with fatal error: Cannot check connection status of the update site with ID='default'. This update center cannot be resolved. If you see this issue for the custom Jenkins WAR bundle, consider setting the correct value of the hudson.model.UpdateCenter.defaultUpdateSiteId system property (requires Jenkins restart). Otherwise please create a bug in Jenkins JIRA. — Tried https://issues.jenkins-ci.org/browse/JENKINS-24259 but no luck The package is not
[JIRA] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title Ulli Hafner commented on JENKINS-34157 Re: Warnings plugin doesn't allow environment variables in file names I see. Maybe expansion does not work in the same way on Windows. I'm not sure if I can setup a test fixture that uses a Windows slave. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35191) Add Map.keySet() and Map.values() to whitelist
Title: Message Title Andrew Bayer commented on JENKINS-35191 Re: Add Map.keySet() and Map.values() to whitelist Not true! Java 5-style for loops do work in CPS with Set. It was an interesting discovery. 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] [script-security-plugin] (JENKINS-28170) Named parameters are not supported in the sandbox
Title: Message Title Andrew Bayer commented on JENKINS-28170 Re: Named parameters are not supported in the sandbox Possibly related to JENKINS-34741? 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] [script-security-plugin] (JENKINS-32688) workflow scripts can't use String.replaceFirst( string, string )
Title: Message Title Andrew Bayer resolved as Fixed This was added in script-security 1.19. Jenkins / JENKINS-32688 workflow scripts can't use String.replaceFirst( string, string ) Change By: Andrew Bayer Status: Open 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] [script-security-plugin] (JENKINS-33024) XmlSlurper.parseText() not whitelisted
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-33024 XmlSlurper.parseText() not whitelisted Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [script-security-plugin] (JENKINS-33024) XmlSlurper.parseText() not whitelisted
Title: Message Title Andrew Bayer commented on JENKINS-33024 Re: XmlSlurper.parseText() not whitelisted Jesse Glick - not sure if this should be whitelisted - your thoughts? 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] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step
Title: Message Title Alexandru Somai started work on JENKINS-35192 Change By: Alexandru Somai 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] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step
Title: Message Title Alexandru Somai created an issue Jenkins / JENKINS-35192 [EWM] Implement the exwsAllocate step Issue Type: New Feature Assignee: Alexandru Somai Components: external-workspace-manager-plugin Created: 2016/May/27 7:30 PM Priority: Major Reporter: Alexandru Somai Implement the exwsAllocate step for the upstream job (when upstream param is null) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [script-security-plugin] (JENKINS-34466) Fix PCT against 2.0
Title: Message Title Andrew Bayer commented on JENKINS-34466 Re: Fix PCT against 2.0 Should this be marked resolved? 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] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-35140 JsonSlurper does not work after updating to Jenkins 2.x Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Andrew Bayer commented on JENKINS-35140 Re: JsonSlurper does not work after updating to Jenkins 2.x PR up at https://github.com/jenkinsci/script-security-plugin/pull/77 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] [script-security-plugin] (JENKINS-27390) Number.valueOf(...) should be whitelisted
Title: Message Title Andrew Bayer commented on JENKINS-27390 Re: Number.valueOf(...) should be whitelisted PR up at https://github.com/jenkinsci/script-security-plugin/pull/76 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] [script-security-plugin] (JENKINS-27390) Number.valueOf(...) should be whitelisted
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-27390 Number.valueOf(...) should be whitelisted Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [script-security-plugin] (JENKINS-27390) Number.valueOf(...) should be whitelisted
Title: Message Title Andrew Bayer commented on JENKINS-27390 Re: Number.valueOf(...) should be whitelisted I'm assuming you mean Number.intValue() and friends. And ScriptBytecodeAdapter.compareEqual() got added since this was created. 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-35178) "Delete build step" button has bad layout in Safari
Title: Message Title Manuel Recena Soto started work on JENKINS-35178 Change By: Manuel Recena Soto 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] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-32661 workflow scripts can't use String.substring(int) Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Brendan Stewart commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed Here is more: ERROR: Connection terminated java.io.IOException: Pipe closed at java.io.PipedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Failed to install restarter Ouch: Connection terminated hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) at ..remote call to Jenkins Slave (i-0f31fdf7)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at org.jenkinsci.modules.systemd_slave_installer.SlaveInstallerFactoryImpl.createIfApplicable(SlaveInstallerFactoryImpl.java:33) at org.jenkinsci.modules.slave_installer.SlaveInstallerFactory.createIfApplicable(SlaveInstallerFactory.java:29) at org.jenkinsci.modules.slave_installer.SlaveInstallerFactory.createFor(SlaveInstallerFactory.java:46) at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:30) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:573) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:381) at hudson.plugins.ec2.win.EC2WindowsLauncher.launch(EC2WindowsLauncher.java:69) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:1074) at hudson.remoting.Channel$CloseCommand.(Channel.java:1072) at hudson.remoting.Channel.close(Channel.java:1156) at hudson.remoting.Channel.close(Channel.java:1138) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1079) ... 2 more hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) at ..remote call to Jenkins Slave (i-0f31fdf7)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
[JIRA] [script-security-plugin] (JENKINS-32661) workflow scripts can't use String.substring(int)
Title: Message Title Andrew Bayer commented on JENKINS-32661 Re: workflow scripts can't use String.substring(int) PR up at https://github.com/jenkinsci/script-security-plugin/pull/75 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] [script-security-plugin] (JENKINS-35191) Add Map.keySet() and Map.values() to whitelist
Title: Message Title Jesse Glick commented on JENKINS-35191 Re: Add Map.keySet() and Map.values() to whitelist Currently will not work anyway outside a @NonCPS block. 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] [script-security-plugin] (JENKINS-33049) Groovy left-shift operator not whitelisted
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-33049 Groovy left-shift operator not whitelisted Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [script-security-plugin] (JENKINS-33049) Groovy left-shift operator not whitelisted
Title: Message Title Andrew Bayer commented on JENKINS-33049 Re: Groovy left-shift operator not whitelisted PR up at https://github.com/jenkinsci/script-security-plugin/pull/74 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] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List
Title: Message Title Andrew Bayer commented on JENKINS-32676 Re: Workflow scripts can't modify a List PR up at https://github.com/jenkinsci/script-security-plugin/pull/73 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] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-32676 Workflow scripts can't modify a List Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [script-security-plugin] (JENKINS-34592) unclassified method java.lang.String[] getAt java.lang.Integer
Title: Message Title
Andrew Bayer commented on JENKINS-34592
Re: unclassified method java.lang.String[] getAt java.lang.Integer
Jesse Glick - I can't figure out how to add this to the generic whitelist - I get {method java.lang.String[] getAt java.lang.Integer does not exist (or is an override)}
and when I try {int}
or {java.lang.Object[]}
, same thing. Any ideas on arrays?
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] [script-security-plugin] (JENKINS-35191) Add Map.keySet() and Map.values() to whitelist
Title: Message Title Andrew Bayer commented on JENKINS-35191 Re: Add Map.keySet() and Map.values() to whitelist PR up at https://github.com/jenkinsci/script-security-plugin/pull/72 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-35190) Improper PingThread handling
Title: Message Title Jesse Glick started work on JENKINS-35190 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-29932) Docker build publish plugin throws error "Please login prior to push" after build the image
Title: Message Title D KA commented on JENKINS-29932 Re: Docker build publish plugin throws error "Please login prior to push" after build the image I have the same issue, I can't push the layer, it keep retrying. 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] [script-security-plugin] (JENKINS-35191) Add Map.keySet() and Map.values() to whitelist
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-35191
Add Map.keySet() and Map.values() to whitelist
Issue Type:
Task
Assignee:
Andrew Bayer
Components:
script-security-plugin
Created:
2016/May/27 6:56 PM
Priority:
Minor
Reporter:
Andrew Bayer
Like it says on the tin - this would enable things like:
def someMap = [a: "b", c: "d"]
for (def key : someMap.keySet()) {
echo "${key}: ${someMap.get(key)}"
}
Add Comment
[JIRA] [core] (JENKINS-35190) Improper PingThread handling
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-35190 Improper PingThread handling Issue Type: Bug Assignee: Jesse Glick Components: core Created: 2016/May/27 6:55 PM Labels: remoting Priority: Major Reporter: Jesse Glick There are several problems with the way ping threads are set up. ChannelPinger sets up a master → agent ping, and also an agent → master ping. But Launcher sets up another slave → master ping for JNLP agents (not for master-initiated ones)...and is more awkward to disable, since you must pass a system property to each agent's launch line. As noted here, the agent → master ping from ChannelPinger does not work at all, due to a mistake in usage of PingFailureAnalyzer. (Oddly, Kohsuke Kawaguchi introduced this extension point claiming it could be implemented in ssh-slaves, but apparently never did so there, or anywhere else!) The Launcher variant fails to override the nondeprecated onDead variant that gets
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title
Ilja Gaitsenja commented on JENKINS-34791
Re: Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits
Sam Van Oort The code is:
node {
stage 'testing'
echo 'before input'
stage 'testing 2'
sleep 60
}
I'm newby with pipelines, maybe I do something wrong. Could you provide reference to documentation where I can read about "user-settable property to configure the hardcoded limits" and other useful properties.
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] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Brendan Stewart commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed Correct, i'm getting it right now with 1.33 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] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Francis Upton commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed Can you make this happen on 1.33 (the current release)? There have been many fixes since 1.31. 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] [pipeline-stage-view-plugin] (JENKINS-33290) First stage is always showing master as run node
Title: Message Title Sam Van Oort commented on JENKINS-33290 Re: First stage is always showing master as run node It's a race between the fast fix (removing this) and the better fix (doing it correctly) which is getting very close. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Brendan Stewart commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed I'm seeing this also, occurs frequently enough that i can't get my builds completed. I'm using the aws cli s3 for copying files to my slaves (as a powershell build step) when this occurs. 14:25:27 Agent went offline during the build 14:28:45 ERROR: Connection was broken: java.io.IOException: Pipe closed 14:28:45 at java.io.PipedInputStream.checkStateForReceive(Unknown Source) 14:28:45 at java.io.PipedInputStream.receive(Unknown Source) 14:28:45 at java.io.PipedOutputStream.write(Unknown Source) 14:28:45 at java.io.OutputStream.write(Unknown Source) 14:28:45 at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:93) 14:28:45 at hudson.remoting.ChunkedOutputStream.drain(ChunkedOutputStream.java:89) 14:28:45 at hudson.remoting.ChunkedOutputStream.write(ChunkedOutputStream.java:58) 14:28:45 at java.io.OutputStream.write(Unknown Source) 14:28:45 at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:45) 14:28:45 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) 14:28:45 at hudson.remoting.Channel.send(Channel.java:582) 14:28:45 at hudson.remoting.Channel.close(Channel.java:1156) 14:28:45 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:119) 14:28:45 at hudson.remoting.PingThread.run(PingThread.java:96) 14:28:45 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] [jira-ext-plugin] (JENKINS-35154) Jira-ext Plugin does not set Servername for SNI Hosts
Title: Message Title Dan Alvizu commented on JENKINS-35154 Re: Jira-ext Plugin does not set Servername for SNI Hosts Need to investigate - one route: https://wiki.apache.org/HttpComponents/SNISupport 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] [jira-ext-plugin] (JENKINS-35154) Jira-ext Plugin does not set Servername for SNI Hosts
Title: Message Title
Dan Alvizu updated an issue
Jenkins / JENKINS-35154
Jira-ext Plugin does not set Servername for SNI Hosts
Change By:
Dan Alvizu
The jira-ext Plugin does not set the servername parameter for ssl requests. Our Jira is behind SNIProxy and SNIProxy needs the servername to find the correct route. Without the following error occurs. The Jira Plugin works.Error finding FieldIds for issueKey: VITAL-1 {code} net.rcarz.jiraclient.JiraException: Exception getting fields for JIRA issue at org.jenkinsci.plugins.jiraext.svc.impl.JiraClientSvcImpl.getJiraFields(JiraClientSvcImpl.java:212) at org.jenkinsci.plugins.jiraext.view.UpdateField$DescriptorImpl.doQueryJiraFields(UpdateField.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at javax.servlet.FilterChain$doFilter.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.ExceptionLoggingFilter.doFilter(ExceptionLoggingFilter.groovy:22) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [durable-task-plugin] (JENKINS-33749) jenkins pipeline dsl.bat does not return
Title: Message Title Christoph Vogtländer commented on JENKINS-33749 Re: jenkins pipeline dsl.bat does not return Not yet. I'm still at 1.7. I will give 1.10 a try and report back. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6
Title: Message Title Oliver Gondža commented on JENKINS-35134 Re: Large numbers of ATH tests failing against 2.6 To my understanding the stacktrace reported is caused by credentials plugin (family) refactoring the UI and all tests configuring credentials are having these problems. The situation get more weird as the plugin installation algorithm doe not seem to install latest credentials plugin version when running CredentialsPluginTest, but it does when tests are run against a plugin that depends on plugin credentials 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] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Andrew Bayer commented on JENKINS-33721 Re: Hard kill links could be in the build sidepanel Preliminary PR up at https://github.com/jenkinsci/workflow-job-plugin/pull/4 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] [credentials-plugin] (JENKINS-35187) Cant install the credentials plugin
Title: Message Title Fábio Luciano commented on JENKINS-35187 Re: Cant install the credentials plugin Thank you. 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] [credentials-plugin] (JENKINS-35187) Cant install the credentials plugin
Title: Message Title stephenconnolly resolved as Not A Defect You are probably waiting for the mirrors to sync up. Give it 24h. If still not resolved by then perhaps consider re-opening Jenkins / JENKINS-35187 Cant install the credentials plugin Change By: stephenconnolly 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] [plugin-proposals] (JENKINS-35189) Spigot-Essentials Updates for 1.9.4 ?
Title: Message Title Steve Mekkelsen Madden created an issue Jenkins / JENKINS-35189 Spigot-Essentials Updates for 1.9.4 ? Issue Type: Improvement Assignee: Unassigned Components: plugin-proposals Created: 2016/May/27 4:41 PM Environment: Spigot 1.9.4 / Windows 10 Pro x64 / Java 8 (1.8.0_92 x64) Labels: plugin user-experience windows Priority: Minor Reporter: Steve Mekkelsen Madden Using the current versions of Essentials-2.x-SNAPSHOT.jar files (including AntiBuild, Chat, GeoIP, GroupManager and Protect), I ran into an issue where using the oversized-stacksize value of greater than 127 results in the item becoming lost if you right mouse click on the block. If you left mouse click to place "1" block, the count of 128 turns from RED to WHITE. This has been like this since 1.8.8 (since I started), but could be earlier. It took a long time just to get to a point I could even submit a request to get help on this plugin as there are no comment fields anywhere allowing for
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: pom.xml src/main/java/de/tracetronic/jenkins/plugins/ecutest/ETPlugin.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/ETPluginException.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/env/view/TestEnvActionView.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/env/view/ToolEnvActionView.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ReportPublisherDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/TestBuilderDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ToolBuilderDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/log/TTConsoleLogger.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/log/TTConsoleNote.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractArchiveFileReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractRequestHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractTestReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReportUploader.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXReportHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/AbstractReportGeneratorAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitTestResultParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/AbstractETLogAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/AbstractTRFAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/AbstractTestBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilder.java
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java http://jenkins-ci.org/commit/ecutest-plugin/045dff380913d9be0e8756ca9841672d03295b43 Log: JENKINS-31999 set Windows only restriction to some publishers 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] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/ETPluginException.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ReportPublisherDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/AbstractTestBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/PackageClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/ProjectClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/TestClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/AbstractToolClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ETClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/TSClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ToolClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/DllUtil.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/ProcessUtil.java src/main/resources/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher/config.properties http://jenkins-ci.org/commit/ecutest-plugin/a0f563284762957b497ded81d5a4104c02e6cd4b Log: JENKINS-31999 massive improvements and refactoring replaced boolean return values with equivalent ETPluginException when performing SimpleBuildStep operations to catch build errors improved DataBoundSetter by adding null checks muted process launcher output properly catch tool timeout exceptions workaround missing workspace directory in pipeline node allocation fixed NPE when using
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ReportPublisherDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/TestBuilderDslExtension.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ToolBuilderDslExtension.java http://jenkins-ci.org/commit/ecutest-plugin/e3db05f198dae5af2d1082aefdc920c125859d29 Log: JENKINS-31999 adjusted Job DSL extensions to use SimpleBuildStep 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-4409) Hudson test case leaks temp folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-4409 Re: Hudson test case leaks temp folders Code changed in jenkins User: Christian Pönisch Path: src/test/java/de/tracetronic/jenkins/plugins/ecutest/SystemTestBase.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/TestPluginManagerCleanUp.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilderTest.java http://jenkins-ci.org/commit/ecutest-plugin/189cbd8a033bb7fb204ff7a68ad38cd0e5e90bf1 Log: JENKINS-31999 added more tests avoid JENKINS-4409 in system tests removed unnecessary TestPluginManagerCleanUp added more unit tests added more system tests validating pipeline steps
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: pom.xml http://jenkins-ci.org/commit/ecutest-plugin/7229b19c53227be495903dda4e4d61efe0c9b998 Log: JENKINS-31999 run Jenkins system tests with failsafe 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] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/test/java/de/tracetronic/jenkins/plugins/ecutest/SystemTestBase.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/TestPluginManagerCleanUp.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisherST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilderTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilderST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilderTest.java http://jenkins-ci.org/commit/ecutest-plugin/189cbd8a033bb7fb204ff7a68ad38cd0e5e90bf1 Log: JENKINS-31999 added more tests avoid JENKINS-4409 in system tests removed unnecessary TestPluginManagerCleanUp added more unit tests added more system tests validating pipeline steps
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilder.java http://jenkins-ci.org/commit/ecutest-plugin/af0331844a3c6682a4e6331356ac092addcc1730 Log: JENKINS-31999 fixed deprecated unit tests 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] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/env/view/TestEnvActionView.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/AbstractTestBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestPackageBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestProjectBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/AbstractTestClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/PackageClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/ProjectClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/TestClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ETClient.java http://jenkins-ci.org/commit/ecutest-plugin/c883004ba182c3316c384b5393fd6f612e053bce Log: JENKINS-31999 added Pipeline compatibility for test-related builders replaced AbstractBuild with Run replaced BuildListener with TaskListener added new DataBoundConstructor for mandatory parameters added DataBoundSetters for optional parameters with defaults made custom console logger compatible Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractArchiveFileReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractRequestHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractTestReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReport.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXReportUploader.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXReportHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/AbstractReportGeneratorAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGeneratorPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitTestResultParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/AbstractETLogAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/AbstractTRFAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFBuildAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFProjectAction.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/trf/TRFPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/TestFolderBuilder.java src/main/resources/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher/config.jelly src/test/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ReportPublisherDslExtensionST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/extension/jobdsl/ReportPublisherParamInstallDslExtensionST.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisherTest.java src/test/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitTestResultParserST.java http://jenkins-ci.org/commit/ecutest-plugin/19baf576b578d65e18ff800ed45ef3f91ba61307 Log: JENKINS-31999 added Pipeline compatibility for report publishers replaced AbstractBuild with Run replaced BuildListener with TaskListener
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: pom.xml src/main/java/de/tracetronic/jenkins/plugins/ecutest/ETPlugin.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXReportHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitTestResultParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/AbstractTestBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/AbstractTestClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/PackageClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/ProjectClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/scan/AbstractTestScanner.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ETClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/TSClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/installation/AbstractToolInstallation.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/installation/ETInstallation.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/DllUtil.java src/main/resources/index.jelly http://jenkins-ci.org/commit/ecutest-plugin/68e246d40f408a8c594662203c5e9d8fa68abf8d Log: JENKINS-31999 bumped Jenkins baseline version to 1.580.1 adapted Callable/FileCallable to according MasterToSlave(File)Callable fixed NPE when configuring tool installations bumped TEST-GUIDE compatible version Add Comment
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: pom.xml src/main/java/de/tracetronic/jenkins/plugins/ecutest/env/view/ToolEnvActionView.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/log/TTConsoleLogger.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/log/TTConsoleNote.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StartTSBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopETBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/StopTSBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/AbstractToolClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ETClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/TSClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ToolClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/ProcessUtil.java http://jenkins-ci.org/commit/ecutest-plugin/6ef4aa7521926d6fca8b92a20be73003faa0206f Log: JENKINS-31999 added Pipeline compatibility for tool-related build steps replaced AbstractBuild with Run replaced BuildListener with TaskListener added new DataBoundConstructor for mandatory parameters added DataBoundSetters for optional parameters with defaults made custom console logger compatible Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ecutest-plugin] (JENKINS-31999) Pipeline support for ECU-TEST plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31999 Re: Pipeline support for ECU-TEST plugin Code changed in jenkins User: Christian Pönisch Path: pom.xml src/main/java/de/tracetronic/jenkins/plugins/ecutest/ETPlugin.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/AbstractReportPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/ATXPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/atx/AbstractATXReportHandler.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/generator/ReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitReportGenerator.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/junit/JUnitTestResultParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogParser.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/report/log/ETLogPublisher.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/AbstractTestBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/AbstractTestClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/PackageClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/client/ProjectClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/test/scan/AbstractTestScanner.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/AbstractToolBuilder.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/ETClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/client/TSClient.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/installation/AbstractToolInstallation.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/tool/installation/ETInstallation.java src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/DllUtil.java src/main/resources/index.jelly http://jenkins-ci.org/commit/ecutest-plugin/50098236b6fe022fdbc2aaa51645b6bc629577e4 Log: JENKINS-31999 bumped Jenkins baseline version to 1.580.1 adapted Callable/FileCallable to according MasterToSlave(File)Callable fixed NPE when configuring tool installations bumped TEST-GUIDE compatible version Add Comment
[JIRA] [batch-task-plugin] (JENKINS-35188) Invoke Batch Tasks must support Folders
Title: Message Title Julien Carsique created an issue Jenkins / JENKINS-35188 Invoke Batch Tasks must support Folders Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: batch-task-plugin, cloudbees-folder-plugin Created: 2016/May/27 4:19 PM Environment: Jenkins 1.642.2 Folders Plugin 5.11 Batch Task Plugin 1.17 Priority: Minor Reporter: Julien Carsique When using folders (plugin), the batch tasks to be triggered must be referenced with an absolute path: while the task suggestion field works fine with a relative job path during configuration, the batch task is not properly configured in the later screens. Let's consider a folder named aFolder with a job named aJob; that job has a batch task named aBatchTask On http://.../jenkins/job/aFolder/job/aJob/configure : Add an Invoke batch tasks post build step with two tasks, one absolute and one relative: Project: /aFolder/aJob Task: aBatchTask
[JIRA] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-34791 Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits Change By: Sam Van Oort Plugin shows only last 10 active builds. I have not found in documentation where this amount could be increased. After this, if active build number is more then 10 (I created input to test this), then plugin shows "Data not available...". I attached screenshot too. Full stage view shows the same. As user I expect some pagination in "Full stage view" or at least some configuration where I can increase amount of builds to show. Added:For the hardcoded limits used in stage view, it would be helpful to provide documented system properties that override defaults where users wish to display more items, despite the performance impacts. 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] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-34791 Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits Change By: Sam Van Oort Summary: Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits 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] [pipeline-stage-view-plugin] (JENKINS-33840) All stages colored red, after last stage failed.
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-33840 All stages colored red, after last stage failed. Change By: Sam Van Oort Priority: Minor Trivial 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] [bitbucket-build-status-notifier-plugin] (JENKINS-34788) Build status notification fails with "Enter a valid URL"
Title: Message Title
Neil Whitworth commented on JENKINS-34788
Re: Build status notification fails with "Enter a valid URL"
I have been looking into a similar issues, where I was getting 'BAD REQUEST' responses from BitBucket.
In my case I was using the 'Multi-Branch Project' Plugin, which creates a folder, with a job per branch.
I traced the BAD REQUEST response back to the value of the "name" field in the build update request. This includes a '»' character from the call to getFullDisplayName in function createBitbucketBuildStatusFromBuild
String buildName = build.getProject().getFullDisplayName() + " #" + build.getNumber();
failing log:-
May 27, 2016 2:30:48 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus
This request was sent:
Unknown macro: { "state"}
May 27, 2016 2:30:48 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus
This response was received: Bad Request
changing to use getFullName (which uses a '/' char) fixed my issues.
String buildName = build.getProject().getFullName() + " #" + build.getNumber();
May 27, 2016 2:32:46 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus
This request was sent:
Unknown macro: { "state"}
This response was received: {"name": "Jenkins Test/master #21", "links": {"commit":
Unknown macro: {"href"}
, "self": {"href": "https://api.bitbucket.org/2.0/repositories/rivdevteam/jenkinstest/commit/7fce0b1f41e4f10cdd4faa7a62dd68a38e575e89/statuses/build/b7fa1a78ad87d07cfe5413bbc34e0d84"}}, "url": "http://localhost:8080/job/Jenkins%20Test/branch/master/21/", "created_on": "2016-05-27T13:32:41.883282+00:00", "repository": {"links": {"self":
Unknown macro: {"href"}
, "html":
Unknown macro: {"href"}
, "avatar": {"href":
[JIRA] [core] (JENKINS-35174) Modify cloud API when several shared clouds are defined with the same label
Title: Message Title Elliot Weiser commented on JENKINS-35174 Re: Modify cloud API when several shared clouds are defined with the same label Thanks for opening this Félix Belzunce Arcos. Distributing load across clouds would be very desirable. To your point about "expensive" versus "cheap" clouds, there are a number of load balancing algorithms that are potentially worth pursuing (all of which have their merits): Round Robin Weighted Balance Least Used Least (Current) Load I'll try to poke at the source code in my spare time to see what's feasible. I have a picture in my head of how it could 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] [pipeline-stage-view-plugin] (JENKINS-35089) Reflecting the result programmatically set to the build using currentBuild.result
Title: Message Title Sam Van Oort closed an issue as Fixed Closing this since it really duplicates JENKINS-33700 (the same fix for both will work – more direct read of the build result in stage view where possible). Jenkins / JENKINS-35089 Reflecting the result programmatically set to the build using currentBuild.result Change By: Sam Van Oort Status: Open 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] [pipeline-stage-view-plugin] (JENKINS-34538) Pipeline Stage View duplicates rows if displayName is changed
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-34538 Pipeline Stage View duplicates rows if displayName is changed Change By: Sam Van Oort Assignee: Antonio Muñiz Sam Van Oort 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-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title Gijs Kunze commented on JENKINS-33020 Re: Unable to Trigger builds remotely (e.g., from scripts) I'm affected by this as well (both in Jenkins 2.0 and 2.6, multibranch plugin 2.4) using a github source but even if I specify no source at all the trigger setting doesn't persist. 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] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained
Title: Message Title Michiel Hendriks commented on JENKINS-23066 Re: Allow cleaning up parts of Jacoco report artifcats retained Ignore my previous comment. I had a config error, I had a trailing ** one of the paths. 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-33721) Hard kill links could be in the build sidepanel
Title: Message Title Andrew Bayer commented on JENKINS-33721 Re: Hard kill links could be in the build sidepanel Thinking about this some... So as best as I can tell, doStop() results in a one-off executor getting used and then interrupted, which I assume leads to the interrupt(boolean forShutdown) method of the AsynchronousExecution getting called, and that prints the "Click here to forcibly terminate running steps" link in the console (and clicking that calls doTerm(), which tries to terminate any FlowNode running and prints the "Click here to forcibly kill entire build" link, and clicking that results in everything getting killed). Is it viable to track that process, i.e., have a transient variable marking whether doStop() has been called, whether doTerm() has been called, and whether doKill() has been called, and then have a transient action that renders the appropriate link in the side panel depending on state? i.e., isBuilding() needs to be true to have any link show up there, if doStop() hasn't been called, the link says "Abort the build" and calls doStop(), if doStop() has been called but doTerm() has not, the link says "Forcibly terminate running steps" and calls doTerm(), and if doTerm() has been called but doKill() has not, the link says "Forcibly kill entire build" and calls doKill(). Thoughts? 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] [s3-plugin] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Jason Milley commented on JENKINS-34216 Re: Failed to reset the request input stream Just confirming that I'm also seeing the same thing since upgrading to 0.10.3 yesterday. 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] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained
Title: Message Title
Michiel Hendriks edited a comment on JENKINS-23066
Re: Allow cleaning up parts of Jacoco report artifcats retained
This disk eating feature makes the plugin pretty much unusable for us. Build jobs went up from around 70MiB to over 900MiB.The classes directory is close to 500MiB even though the actual produced class files is less than 100MiB.It's storing files more than once is different directories, once per path element:{code}./SomeCensoredClass.class./action/SomeCensoredClass.class./shipmenttype/action/SomeCensoredClass.class./control/shipmenttype/action/SomeCensoredClass.class./oms/control/shipmenttype/action/SomeCensoredClass.class./foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class./com/foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class{code} The same happens in the source directory. So there is something seriously wrong with copying the files.
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] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained
Title: Message Title Michiel Hendriks commented on JENKINS-23066 Re: Allow cleaning up parts of Jacoco report artifcats retained This disk eating feature makes the plugin pretty much unusable for us. Build jobs went up from around 70MiB to over 900MiB. The classes directory is close to 500MiB even though the actual produced class files is less than 100MiB. It's storing files more than once is different directories, once per path element: ./SomeCensoredClass.class ./action/SomeCensoredClass.class ./shipmenttype/action/SomeCensoredClass.class ./control/shipmenttype/action/SomeCensoredClass.class ./oms/control/shipmenttype/action/SomeCensoredClass.class ./foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class ./com/foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class 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.
