[JIRA] [extra-columns-plugin] (JENKINS-23583) Column Test Result has incorrect link
Matthieu Ouellette-Vachon commented on JENKINS-23583 Column Test Result has incorrect link @stephenthornhill made a PR on github to fix this issue PR #11. I tested it in my instance and it works like a charm. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
J John commented on JENKINS-25115 Recognize failures indicated by JUnit test result file Does this release also parse mstest result files? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26099) Configurable ID for Credentials
SCM/JIRA link daemon commented on JENKINS-26099 Configurable ID for Credentials Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/plaincredentials/impl/FileCredentialsImpl.java src/main/java/org/jenkinsci/plugins/plaincredentials/impl/StringCredentialsImpl.java src/main/resources/org/jenkinsci/plugins/plaincredentials/impl/FileCredentialsImpl/credentials.jelly src/main/resources/org/jenkinsci/plugins/plaincredentials/impl/StringCredentialsImpl/credentials.jelly http://jenkins-ci.org/commit/plain-credentials-plugin/0ba4a8ae2df3e43bafcd8fd14519c974c18a1bdf Log: JENKINS-26099 Permit StringCredentialsImpl.id and FileCredentialsImpl.id to be configured. Compare: https://github.com/jenkinsci/plain-credentials-plugin/compare/846644ae21ff^...0ba4a8ae2df3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26020) Will not start builds even though there are available slots on executor
Oleg Nenashev commented on JENKINS-26020 Will not start builds even though there are available slots on executor Dec 15, 2014 8:40:10 AM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #150398 with /10.33.21.14:62740 is aborted: generic_AESL-JENKINS07 is already connected to this master. Rejecting this connection. It seems to be unrelated. Such issue usually happens when you have two jenkins-slave processes. On Windows machines it rarely happens on improper service termination, etc. You can also configure Jenkins slave to have a bigger reconnect attempt interval. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-12950) pom.xml not deploying to Artifactory
John McCullough commented on JENKINS-12950 pom.xml not deploying to Artifactory To avoid the chance of leftovers from previous builds getting deployed our jobs use a pre-build step to call a script to just delete the local maven repository on the build nodes. Easiest way to be sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Jesse Glick commented on JENKINS-26426 Browse the tree for all steps (not only running) while the flow is running When the job is stopped all of the steps are displayed but when running only the running ones are visible. Definitely smells like a bug, though not one I can remember seeing or hearing of before now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-file-provider-plugin] (JENKINS-26339) Workflow integration for Config File Provider
Jesse Glick updated JENKINS-26339 Workflow integration for Config File Provider Change By: Jesse Glick (14/Jan/15 8:11 PM) Summary: Workflowintegration forConfigFileProvider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24673) Build wrappers in Workflow plugin
Jesse Glick started work on JENKINS-24673 Build wrappers in Workflow plugin Change By: Jesse Glick (14/Jan/15 8:12 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-binding-plugin] (JENKINS-26051) Workflow integration for Credentials Binding
Jesse Glick updated JENKINS-26051 Workflow integration for Credentials Binding Change By: Jesse Glick (14/Jan/15 8:11 PM) Summary: Workflowintegration forCredentialsBinding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26411) Improve error reporting when channel closed
Oliver Gondža commented on JENKINS-26411 Improve error reporting when channel closed https://github.com/jenkinsci/jenkins/pull/1529 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26433) Permalinks not usable by others when accessed via me/my-views
Mathieu Gervais created JENKINS-26433 Permalinks not usable by others when accessed via me/my-views Issue Type: Improvement Assignee: Unassigned Components: core Created: 14/Jan/15 9:34 PM Description: When accessing jobs via "my-views" you end up with un-canonical URLs (that actually only work for yourself) like http://jenkins2/jenkins/webapp/me/my-views/view/bobview/job/someproject/ . When looking at a page/job inside a my-views, it would be good to have a way to get a ‘canonical link’. This would help in exchanging links between each other (IM, email) etc. Right now, the "permalinks" are still going view the "my-views" structure, hence are unusable by others. Possibly the simplest solution would be for the permalinks to just be direct links, with the "views" removed from the url, but I'm not sure if this would clash with things like nested folders. Environment: I believe this to be a core jenkins feature (so, independent of installed plugins). Tested on Jenkins ver. 1.554.2 Project: Jenkins Priority: Minor Reporter: Mathieu Gervais This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin commented on JENKINS-26426 Browse the tree for all steps (not only running) while the flow is running When the job is stopped all of the steps are displayed but when running only the running ones are visible. I'll send you the requested info tomorrow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Daniel Beck commented on JENKINS-19934 Add Job Create permission to project roles Actually, the job should be created, but the user has no permission to access it, as it does not match the name pattern. This seems to be a limitation inherent in how Role Strategy works. A friendlier error message would be nice, as well. May be possible if you give the user the Discover permission globally. Otherwise, Jenkins will simply deny there is such a job, as the user is not allowed to see it, and not allowed to learn of its existence. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-26032) Prefer BuildStepMonitor.NONE
Sandeep Dhingra edited a comment on JENKINS-26032 Prefer BuildStepMonitor.NONE Hi Daniel , The issue is performance summariser doesn't work if we change BuildStepMonitor.BUILD to Build.NONE.We want the report to get published after the test is over.Though we see *.jtl files,the report doesn't get published. Thanks Sandeep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Richard Lavoie commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm trying to convert the tests to the new recipe and fixture and I'm having some problems with that. I'll also try to add more tests to this plugin as it's coverage is really suffering.. However, in a few days, maybe weeks I believe, this should be done. I'm mostly working on this part time outside of my job so I'm not able to put alot of time in this. I'm doing the best I can because I know I put this plugin aside for way too long before fixing this issue. I'll probably end up release this after manually validating it in a real installation so I can release it even if the tests and the coverage is not how I'd like it to be. Stay tuned ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-26402) system-out in result XML file not being displayed in the Test result Section
Phuong Hoang commented on JENKINS-26402 system-out in result XML file not being displayed in the Test result Section I'm using Jenkins v1.552. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-26402) system-out in result XML file not being displayed in the Test result Section
Phuong Hoang updated JENKINS-26402 system-out in result XML file not being displayed in the Test result Section Changed to Components to "junit-plugin". Change By: Phuong Hoang (15/Jan/15 12:40 AM) Component/s: junit-plugin Component/s: jenkins-tag-cloud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows Not run
maidhili mandava commented on JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows Not run I have Jenkins Testlink Plugin -3.10 TestLink Version -1.9.12 Jenkins Version - 1.574 We are using maven job with POM.xml The test cases run and pass. But on TestLink it says test cases not executed. Why is it not updating the TestLink? We followed all the steps in the tutorial o create project in test link and create job in Jenkins. are the versions we are using not compatible? We are struck with this issue and we really need some help here. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [skype-notifier] (JENKINS-13255) I am not able to save skype ids of users.
Pablob P commented on JENKINS-13255 I am not able to save skype ids of users. Any update? I tried latest jenkins with skype plugin and I cannot assign skype IDs to people. GUI is there to enter skype id, but when I save it the ID is discarded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openjdk-native-plugin] (JENKINS-26434) Update for latest OpenJDK 8
vjuranek created JENKINS-26434 Update for latest OpenJDK 8 Issue Type: New Feature Assignee: vjuranek Components: openjdk-native-plugin Created: 14/Jan/15 10:32 PM Description: See https://github.com/vjuranek/openJDK-native-plugin/issues/1 Project: Jenkins Priority: Minor Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [skype-notifier] (JENKINS-26435) Skype Plugin modifies mood/tag line in skype and doesn't provide an option to avoid doing that.
Pablob P created JENKINS-26435 Skype Plugin modifies mood/tag line in skype and doesnt provide an option to avoid doing that. Issue Type: Bug Assignee: jarlebh Components: skype-notifier, skype-plugin Created: 15/Jan/15 12:21 AM Description: I configured jenkins to run on my workstation and I made it to use my personal skype to send messages to comitters. I totally hate that skype plugin sets my tag line (mood) to some lame BS and I don't see a way to disable that behavior. Project: Jenkins Priority: Critical Reporter: Pablob P This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25237) Add Sauce connect version to console log when launching Sauce Connect
Ross Rowe started work on JENKINS-25237 Add Sauce connect version to console log when launching Sauce Connect Change By: Ross Rowe (15/Jan/15 3:37 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-18860) Add support for Sauce Connect tunnel identifier
Ross Rowe resolved JENKINS-18860 as Fixed Add support for Sauce Connect tunnel identifier This issue should be fixed in the latest version of the plugin Change By: Ross Rowe (15/Jan/15 3:52 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-24642) Latest Browsers on Sauce On Demand Plugin
Ross Rowe resolved JENKINS-24642 as Fixed Latest Browsers on Sauce On Demand Plugin My apologies for taking so long to update this issue, the latest version of the Sauce Jenkins plugins includes a 'Use latest version of selected browser' checkbox, which should resolve this issue Change By: Ross Rowe (15/Jan/15 3:39 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-19985) Flexible Publish NPE
Steven Christou reopened JENKINS-19985 Flexible Publish NPE Re-opening issue I have encountered this issue. Steps to reproduce: 1. Create a new freestyle project 2. Add the Flexible publish as a post build action. 3. Save the project without any conditional publishers. 4. It will throw an exception, however the save happens! 5. Execute a build and it will throw the NPE. Another way you can get this NPE: 1. Same steps as 1, 2, 3, 4. 2. Restarting Jenkins throws this NPE, however the project will fail to load and show an error about project actions. c3eb1c protects against errors coming from jobs failing to load properly. I created PR 7 to fix this issue. Change By: Steven Christou (15/Jan/15 4:42 AM) Resolution: CannotReproduce Status: Resolved Reopened Assignee: ikedam StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26325) Invalid test results link
Dirk Thomas updated JENKINS-26325 Invalid test results link Change By: Dirk Thomas (15/Jan/15 4:41 AM) Description: Adashboard-viewwiththecolumnTestResult(withTestformat2)showsinvalidlinkstothetestresults.InthecaseoftheexampleviewreferencedastheURLthelinkpointsto:http://54.183.26.131:8080/view/wrong_test_result_link/view/wrong_test_result_link/job/ IdevS32__catkin__ubuntu_saucy_i386 Idev__twist_mux__ubuntu_trusty_amd64 /lastCompletedBuild/testReport/TheURLcontainstheview/VIEWNAMEparttwiceandisthereforeinvalid. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25756) Use latest version of selected browsers? not working with Selenium RC
Ross Rowe started work on JENKINS-25756 Use latest version of selected browsers? not working with Selenium RC Change By: Ross Rowe (15/Jan/15 3:23 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Ross Rowe started work on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Change By: Ross Rowe (15/Jan/15 3:33 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-23230) SauceOnDemandReportPublisher processBuildOutput - wrong build number, not getting job-name
Ross Rowe resolved JENKINS-23230 as Fixed SauceOnDemandReportPublisher processBuildOutput - wrong build number, not getting job-name Apologies for taking so long to close this ticket, the issue was resolved by version 1.94 of the Sauce plugin Change By: Ross Rowe (15/Jan/15 4:03 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-22897) Implement Sauce On demand publisher
Ross Rowe resolved JENKINS-22897 as Fixed Implement Sauce On demand publisher Apologies for taking so long to update this issue, the plugin was updated to make the Sauce test publisher available for all build types, and the logs should be less verbose now Change By: Ross Rowe (15/Jan/15 4:01 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rake-plugin] (JENKINS-26436) Rake Plugin Does Not Find All RVM Installed Ruby Instances
Jesse Bowes created JENKINS-26436 Rake Plugin Does Not Find All RVM Installed Ruby Instances Issue Type: Bug Assignee: david_calavera Components: rake-plugin Created: 15/Jan/15 2:26 AM Description: When RVM looks for rubies, it searches in the specifications. It appears that sometimes, ruby adds a 'default' subdirectory to specifications that holds the rake specifications. I don't know what causes RVM to do this, but it happens. Pull request on the way. Project: Jenkins Priority: Minor Reporter: Jesse Bowes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
Ross Rowe commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings My apologies for taking so long to respond to this issue...I'm not familiar with the cainfo and capath options, would you be able to provide me an example of the options which you are setting? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26433) Permalinks not usable by others when accessed via me/my-views
Daniel Beck resolved JENKINS-26433 as Duplicate Permalinks not usable by others when accessed via me/my-views Duplicates JENKINS-10595. Change By: Daniel Beck (15/Jan/15 4:20 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25067) Embed Sauce OnDemand reports option doesn't exist for Publish NUnit test result report section
Ross Rowe resolved JENKINS-25067 as Fixed Embed Sauce OnDemand reports option doesnt exist for Publish NUnit test result report section Apologies for taking so long to update this issue, I think this was resolved in version 1.104, but please let me know if it's still an issue Change By: Ross Rowe (15/Jan/15 3:48 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25067) Embed Sauce OnDemand reports option doesn't exist for Publish NUnit test result report section
Ross Rowe started work on JENKINS-25067 Embed Sauce OnDemand reports option doesnt exist for Publish NUnit test result report section Change By: Ross Rowe (15/Jan/15 3:47 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
edited a comment on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's an issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name
//Then lots of messy code to queue the configure job with nodeLabel being passed in as a parameter.
This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
edited a comment on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's a bug/issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name // Since each of our nodes has a label with its name. You could also just pass on the node name.
// Then lots of messy code to queue the configure job with nodeLabel being passed in as a parameter.
This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Basically, I want to mimic GitHub/CloudBees BuildHive feature. When a MR is adressed, job should be triggered with merged contents and results provided. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26429) after about 24 hours, slaves no longer auto provisioned in EC2
Ryan Schneider created JENKINS-26429 after about 24 hours, slaves no longer auto provisioned in EC2 Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 14/Jan/15 2:41 PM Description: After Jenkins has been running for a certain amount of time (don't have an exact number but it appears to be about one day) it will no longer automatically provision new slaves. Using the manual button to create slaves from the nodes page works fine however. There are no instance limits specified in the configuration. After a restart it will start auto provisioning again. Environment: awt.toolkit sun.awt.X11.XToolkit executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/java/jdk1.8.0_11/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.8.0_11/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.8.0_11/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_11-b12 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_11 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.11-b03 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna7548063523265110062.tmp lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate lib.svnkit.ssh2.persistent false line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.42-52.145.amzn1.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/java/jdk1.8.0_11/jre/lib/resources.jar:/usr/java/jdk1.8.0_11/jre/lib/rt.jar:/usr/java/jdk1.8.0_11/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_11/jre/lib/jsse.jar:/usr/java/jdk1.8.0_11/jre/lib/jce.jar:/usr/java/jdk1.8.0_11/jre/lib/charsets.jar:/usr/java/jdk1.8.0_11/jre/lib/jfr.jar:/usr/java/jdk1.8.0_11/jre/classes sun.boot.library.path /usr/java/jdk1.8.0_11/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Etc/UTC Environment Variables Name ↓ Value _ /usr/bin/java HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 TERM xterm-256color USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned analysis-collector 1.42 true false analysis-core 1.67 true false ant 1.2 true false antisamy-markup-formatter 1.3 true true build-user-vars-plugin 1.4 true false buildtriggerbadge 1.3 false false chucknorris 0.5 true false cobertura 1.9.6 true false conditional-buildstep 1.3.3 true false config-file-provider 2.7.5 true false copyartifact
[JIRA] [sonargraph-plugin] (JENKINS-26360) User should be able to define the metrics to be displayed as charts
SCM/JIRA link daemon commented on JENKINS-26360 User should be able to define the metrics to be displayed as charts Code changed in jenkins User: Esteban Angee Path: src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/AbstractSonargraphRecorder.java src/main/resources/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphReportBuilder/config.jelly http://jenkins-ci.org/commit/sonargraph-plugin/76f25c9e67b20d06aa1bccafe5f05264e18ac6f9 Log: JENKINS-26360: Sonargraph Plugin. Now the 'Append' options describes the default metrics. Compare: https://github.com/jenkinsci/sonargraph-plugin/compare/0096253371a5...76f25c9e67b2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22829) Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1
Daniel Sundberg commented on JENKINS-22829 Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1 We have this problem too, although this only happens sometimes. Running on 2.11.1. Triggering manually through the "Query and Trigger Gerrit patches" command actually triggers the build in our case. Haven't tried to downgrade to 2.11.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error
siddharth kumar edited a comment on JENKINS-26425 Jenkins subversion authentication error Daniel - All I want to know is why after LINUX Kernel PATCH upgrade its not working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
commented on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's an issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name
and we pass nodeLabel into the job as a parameter for the NodeLabel Parameter Plugin. This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-26431) Create permalinks from stages
Jesse Glick created JENKINS-26431 Create permalinks from stages Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 14/Jan/15 3:27 PM Description: To help replace the Promoted Builds plugin when dealing with inter-flow dependencies (or, generally, flows as upstream projects), as well as for general use by scripted automation and so on, it would be useful if when running a stage step you could ask to create a permalink (perhaps just taken from the stage name?) if the stage completes successfully. This would give you a URL that could be used to refer to the last build which got at least to a given stage. Project: Jenkins Labels: permalink Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
edited a comment on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's a bug/issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name
//Then lots of messy code to queue the configure job with nodeLabel being passed in as a parameter.
This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22829) Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1
Daniel Sundberg commented on JENKINS-22829 Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1 Sorry, I can't tell you exactely how to reproduce since it only happens sometimes (~1 of 3). For no appearant reason. I have two jobs: triggers on commits anywhere in the repo triggers on commits to certain paths in my git repo (shared/libs/**) Today I had two consecutive gerrit commits in the same directory that should have triggered both jobs, only one did trigger both. Perhaps there are some logs I can turn on to get more information about how builds are triggered? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error
siddharth kumar commented on JENKINS-26425 Jenkins subversion authentication error Thanks Daniel.In that case I will check this with latest version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26360) User should be able to define the metrics to be displayed as charts
SCM/JIRA link daemon commented on JENKINS-26360 User should be able to define the metrics to be displayed as charts Code changed in jenkins User: Esteban Angee Path: src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/AbstractSonargraphRecorder.java src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphChartAction.java src/main/java/com/hello2morrow/sonargraph/jenkinsplugin/persistence/CSVChartsForMetricsHandler.java src/main/resources/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphChartAction/index.jelly http://jenkins-ci.org/commit/sonargraph-plugin/6e671501511c108a049115b6b41b105fd7eff27f Log: JENKINS-26360: Sonargraph Plugin. Fixed NullPointerExceptions and added notification message when the chart configuration displays no charts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Jesse Glick resolved JENKINS-26426 as Incomplete Browse the tree for all steps (not only running) while the flow is running I see a tree of all the running steps (and their parents) but no finished steps are displayed. Finished steps are certainly displayed in this view. Can you describe how to reproduce the situation you see from scratch? Or at least attach your flow script and a screenshot, plus a ZIP of the build directory (which will include some *.xml files listing flow node states)? Also take note of any errors/warnings in your log file which might be related. It would be even greater (if it is possible to do that) if the whole tree with the pending steps could be browsed. Not possible without solving the Halting Problem! Change By: Jesse Glick (14/Jan/15 3:05 PM) Resolution: Incomplete Status: Open Resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Well, I experimented a bit with gitlab plugin (https://github.com/jenkinsci/gitlab-plugin) and this plugin does the works (job triggered on MR). I'm now using gitlab plugin for post build on push and MR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez edited a comment on JENKINS-25267 Gitlab hook not building on merge request object Well, I experimented a bit with gitlab plugin (https://github.com/jenkinsci/gitlab-plugin) and this plugin does the works (job triggered on MR). I'm now using gitlab plugin for build on push and MR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26430) non-administrators unable to manually provision new slaves
Ryan Schneider created JENKINS-26430 non-administrators unable to manually provision new slaves Issue Type: Bug Assignee: Francis Upton Attachments: Screen Shot 2015-01-14 at 9.43.49 AM.png Components: ec2-plugin Created: 14/Jan/15 2:45 PM Description: I have the attached matrix security policy configured, however members of the "engineering" group are unable to see or press the "Provision via EC2" button from the /computer page of Jenkins. Environment: awt.toolkit sun.awt.X11.XToolkit executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/java/jdk1.8.0_11/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.8.0_11/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.8.0_11/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_11-b12 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_11 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.11-b03 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna7548063523265110062.tmp lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate lib.svnkit.ssh2.persistent false line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.42-52.145.amzn1.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/java/jdk1.8.0_11/jre/lib/resources.jar:/usr/java/jdk1.8.0_11/jre/lib/rt.jar:/usr/java/jdk1.8.0_11/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_11/jre/lib/jsse.jar:/usr/java/jdk1.8.0_11/jre/lib/jce.jar:/usr/java/jdk1.8.0_11/jre/lib/charsets.jar:/usr/java/jdk1.8.0_11/jre/lib/jfr.jar:/usr/java/jdk1.8.0_11/jre/classes sun.boot.library.path /usr/java/jdk1.8.0_11/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Etc/UTC Environment Variables Name ↓ Value _ /usr/bin/java HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 TERM xterm-256color USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned analysis-collector 1.42 true false analysis-core 1.67 true false ant 1.2 true false antisamy-markup-formatter 1.3 true true build-user-vars-plugin 1.4 true false buildtriggerbadge 1.3 false false chucknorris 0.5 true false cobertura 1.9.6 true false conditional-buildstep 1.3.3 true false config-file-provider 2.7.5 true false copyartifact 1.32.1 true false credentials 1.20 true true cvs 2.12 true true
[JIRA] [ldap-plugin] (JENKINS-21475) Multiple LDAP OU support
Sean Robinson commented on JENKINS-21475 Multiple LDAP OU support Any chance anyone is ever going to fix this? This is a big pain for my organization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object @Henri as you probably read in previous comments, the plugin currently does not support this. I am a bit ambivalent to the idea in the first place. Why would you need such a thing when the above described flow works nicely? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object Ah, ok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22829) Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1
rsandell commented on JENKINS-22829 Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1 Hmm, It works when I test on my local machine. Could you provide some steps to reproduce it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object BTW, gitlab hook plugin could be usefull too. Do you consider some merge/share effort with gitlab plugin ? For newcomers, having different plugins for Gitlab could be a bit confusing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-25464) Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration
Connor Gilbert commented on JENKINS-25464 Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration There's a great post on Stack Overflow with steps for setting up a Master/Slave environment. http://stackoverflow.com/questions/27438928/running-hp-load-runeer-from-jenkins This may not directly relate to your issue, but maybe there is some helpful info. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object Not at this point. Processing MR's requires a lot of communication with Gitlab, not just processing it's payload. And we have other more pressing topics to solve. I am still fishing for a right use case to solve though. If you can describe why you need MR to be built, e.g. a bit more detailed flow, that could be helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [locale-plugin] (JENKINS-26437) Display problem in localization dialog
tdtappe created JENKINS-26437 Display problem in localization dialog Issue Type: Bug Assignee: Unassigned Attachments: localization-dialog.png Components: locale-plugin Created: 15/Jan/15 7:20 AM Description: There seems to be some display problem with the close button in the localization dialog. See attached image. Environment: 1.596 Project: Jenkins Priority: Minor Reporter: tdtappe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin updated JENKINS-26426 Browse the tree for all steps (not only running) while the flow is running Screenshots taken at ~30sec interval while the job was running. Change By: Timur Batyrshin (15/Jan/15 7:47 AM) Attachment: ScreenShot2015-01-15at10.22.43.png Attachment: ScreenShot2015-01-15at10.23.18.png Attachment: ScreenShot2015-01-15at10.23.55.png Attachment: ScreenShot2015-01-15at10.24.18.png Attachment: ScreenShot2015-01-15at10.24.50.png Attachment: ScreenShot2015-01-15at10.25.20.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin updated JENKINS-26426 Browse the tree for all steps (not only running) while the flow is running The test project workdir (with program.dat removed) Change By: Timur Batyrshin (15/Jan/15 7:49 AM) Attachment: test-flow.tgz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin
edited a comment on JENKINS-26426
Browse the tree for all steps (not only running) while the flow is running
I've created a small workflow specially to identifying this bug.
The workflow code:
node {
parallel flow1: {
sh "sleep 30"
}, flow2: {
sh "sleep 60"
}, flow3: {
sh "sleep 90"
}, flow4: {
sh "sleep 120"
}, flow5: {
sh "sleep 150"
}
}
Please find the screenshots and the archive of the job dir attached. I've removed the program.dat files from that dir as I wouldn't share it in public place, if you need these too please let me know and I'll drop them to you be e-mail.
When running this flow at first all of the parallel branches have appeared but later when the "sleep" command finished working they've disappeared one by one (not sure why the first branch still didn't disappear here). After the job was finished all of them instantly reappeared again.
I'm running Jenkins 1.595 and workflow plugin v1.1.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin reopened JENKINS-26426 Browse the tree for all steps (not only running) while the flow is running Change By: Timur Batyrshin (15/Jan/15 7:53 AM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-12473) Subversion option vanishes under Source-Code-Management in project configuration
Benjamin Mahr commented on JENKINS-12473 Subversion option vanishes under Source-Code-Management in project configuration Have the same issue on a virtual Windows 7, Wildfly, enviroment. Happend afetr upgrading jenkins 1.596 plugins. Absolute no SCM left at project configuration. For me it's an absolute blocker. Jenkins is usles in that way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26438) Keep this build forever button not visible if BuildDiscarder other than LogRotator is configured
Matthias Moers
created JENKINS-26438
Keep this build forever button not visible if BuildDiscarder other than LogRotator is configured
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
15/Jan/15 7:53 AM
Description:
The button "Keep this build forever" is not visible in the build summary page when a BuildDiscarder other than LogRotator is configured. I don't think this is intentionally.
The problem is in Jelly file core\src\main\resources\hudson\model\Run\logKeep.jelly, line 30:
j:if test="${it.parent.logRotator!=null and it.canToggleLogKeep()}"
Should be fixed to:
j:if test="${it.parent.buildDiscarder!=null and it.canToggleLogKeep()}"
Environment:
Jenkins 1.565.1
Project:
Jenkins
Priority:
Minor
Reporter:
Matthias Moers
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-26426) Browse the tree for all steps (not only running) while the flow is running
Timur Batyrshin
commented on JENKINS-26426
Browse the tree for all steps (not only running) while the flow is running
I've created a small workflow specially to identifying this bug.
The workflow code:
node {
parallel flow1: {
sh "sleep 30"
}, flow2: {
sh "sleep 60"
}, flow3: {
sh "sleep 90"
}, flow4: {
sh "sleep 120"
}, flow5: {
sh "sleep 150"
}
}
Please find the screenshots and the archive of the job dir attached. I've removed the program.dat files from that dir as I wouldn't share it in public place, if you need these too please let me know and I'll drop them to you be e-mail.
When running this flow at first all of the parallel branches have appeared but later when the "sleep" command finished working they've disappeared one by one (not sure why the first branch still didn't disappear here). After the job was finished all of them instantly reappeared again.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Seán Dunne commented on JENKINS-12092 Allow a job to completely block a category I would like to see this feature also. We have, Multiple jobs setup in a pipeline, some of which run on labelled slaves A job that refreshes the labelled slave (i.e. deletes and creates a new one) The refresh job and the pipeline jobs cannot run at the same time or disaster will ensue. So some way to throttle the refresh job from executing while the pipeline jobs are running would be very useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26398) Fix createSlave for RestartableJenkinsRule
SCM/JIRA link daemon commented on JENKINS-26398 Fix createSlave for RestartableJenkinsRule Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java http://jenkins-ci.org/commit/workflow-plugin/dd5eaf7aa09cc509fb98f46816fad2b2b337b5ea Log: Merge pull request #34 from jenkinsci/JENKINS-26398-comment Linking to a filed issue Compare: https://github.com/jenkinsci/workflow-plugin/compare/375c1db37f91...dd5eaf7aa09c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
mwebber commented on JENKINS-19934 Add Job Create permission to project roles This is simply not possible, as the permission to create items is given by the future item's container independent of the name of what you will create. You get access to the 'Create Item' page before having to specify a name, after all. Of course! Thanks. That explains what I see. There is a bug in the current handling, but it's not what I originally reported. Here's what I did: Created a global role called "job-create", which has ONLY the "Job / Create" (and "Overall / Read") privileges. Assigned user X to that global role. Created a project role called "Dials-Administrator" with a jobname pattern of "(cctbx|dials|xia2).*". The role has all job permissions set. Assigned user X to that project role. What I wanted to happen: User X could create a job whose name matched "(cctbx|dials|xia2).*" User X could not create a job whose name did not match "(cctbx|dials|xia2).*" What actually happend: User X could see and click on "New Item" User X attempted to created a new project with the name "dummy job" User X got HTTP ERROR 404 Problem accessing /job/dummy%20job/configure. Reason: Not Found It looks like the user was prevented creating a job with a name they are not authorised to access. However, Jenkins actually went ahead and created the job (it's visible in the "All" tab), so it looks like the authorisation test is being done too late. A friendlier error message would be nice, as well. Hope that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
mwebber edited a comment on JENKINS-19934 Add Job Create permission to project roles This is simply not possible, as the permission to create items is given by the future item's container independent of the name of what you will create. You get access to the 'Create Item' page before having to specify a name, after all. Of course! Thanks. That explains what I see. There is a bug in the current handling, but it's not what I originally reported. Here's what I did: Created a global role called "job-create", which has ONLY the "Job / Create" (and "Overall / Read") privileges. Assigned user X to that global role. Created a project role called "Dials-Administrator" with a jobname pattern of "(cctbx|dials|xia2).*". The role has all job permissions set. Assigned user X to that project role. What I wanted to happen: User X could create a job whose name matched "(cctbx|dials|xia2).*" User X could not create a job whose name did not match "(cctbx|dials|xia2).*" What actually happend: User X could see and click on "New Item" User X could successfully create a new job whose name matched "(cctbx|dials|xia2).*" User X attempted to created a new project with the name "dummy job" User X got HTTP ERROR 404 Problem accessing /job/dummy%20job/configure. Reason: Not Found It looks like the user was prevented creating a job with a name they are not authorised to access. However, Jenkins actually went ahead and created the job (it's visible in the "All" tab), so it looks like the authorisation test is being done too late. A friendlier error message would be nice, as well. Hope that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-22829) Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1
rsandell commented on JENKINS-22829 Gerrit Trigger plugin should trigger all jobs for Gerrit project, but triggers only one on 2.11.1 2.13 that hopefully gets a beta release today or tomorrow has a lot of changes in this general area. Lets see if it continues to appear in that version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26137) Mysterious serialization errors
SCM/JIRA link daemon commented on JENKINS-26137 Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-plugin/9186a512e4ecf901217bc3f4b219810322e84db9 Log: Merge pull request #33 from jenkinsci/JENKINS-26137-no-pickle-factories Make a test involving Jenkins restart pass Compare: https://github.com/jenkinsci/workflow-plugin/compare/dd5eaf7aa09c...9186a512e4ec This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21953) NodeJs plugin doesn't work on windows based Jenkins machine
Zlatan Masic commented on JENKINS-21953 NodeJs plugin doesnt work on windows based Jenkins machine Hello, I have just found a workaround for this issue. Simply create in your nodejs installation folder on Windows, a new folder called "bin" and copy the node.exe into this folder. Then it should work! Kind regards, Zlatan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-parameter-plugin] (JENKINS-23188) Tag List Empty
Immo Huneke edited a comment on JENKINS-23188 Tag List Empty I have just tried this with the latest versions (Git plugin 2.3.4, Git client plugin 1.15.0, Git parameter plugin 0.3.2) and still get a 401 (unauthorized) status back from github: Jenkins is fully up and running Jan 14, 2015 3:45:03 PM INFO hudson.model.DownloadService$Downloadable load Obtained the updated data file for hudson.tasks.Maven.MavenInstaller Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:04 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:47:46 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents generateContents contenttype PT_TAG RemoteConfig [https://github.com//.git] Jan 14, 2015 3:47:47 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.tagMap in /jenkins/job/auth-prototype-CI/build. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) ... at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com//.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Invalid username or password. fatal: Authentication failed for 'https://github.com//.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:325) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getTagMap(GitParameterDefinition.java:392) ... 161 more Jan 14, 2015 3:47:55 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default The parameter plugin does not seem to pick up the credentials configured for git access in the project. The git plugin itself however does so successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
edited a comment on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's a bug/issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node. We have the NodeLabel Parameter plugin installed.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name // Since each of our nodes has a label with its name. If this isn't the case for you, you can do some regex on the it.name to convert each node's name into whatever the unique label is.
params_with_label += new org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterValue('NODE_LABEL', nodeLabel)
// Then lots of messy code to queue the configure job with nodeLabel being passed in as a parameter.
This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Josh Shapiro
edited a comment on JENKINS-22185
Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Hello Christian,
I have dealt with this issue. I am actually giving a presentation on it later this month.
I don't believe it's a bug/issue as much as a design decision, with the idea being that if a single machine can pass a build, why run it on an identical machine?
Here is my solution:
Summary: We have a parent job that finds all online nodes that match a certain label, then foreach node, pass a downstream job a label specific to that node. We have the NodeLabel Parameter plugin installed.
Details:
We have 40 nodes named 'hl-combo-##' where ## is 01-40. Each of those nodes is also labelled 'harnesslab' and 'hl-combo-##'. In a parent job, using groovy, we search all online nodes that have that label:
jenkins.model.Jenkins.instance.nodes.each {
if (it.toComputer().online it.assignedLabels.contains(new hudson.model.labels.LabelAtom('harnesslab'))) {
harnesslabOnlineNodes += it
Then after some other code, we do:
harnesslabOnlineNodes.each {
println 'Starting configure job for: ' + it.name
def nodeLabel = it.name // Since each of our nodes has a label with its name. If this isn't the case for you, you can do some regex on the it.name to convert each node's name into whatever the unique label is.
params_with_label += new org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterValue('NODE_LABEL', nodeLabel)
def paramsAction = new hudson.model.ParametersAction(params_with_label)
// Then other code to get the cause and job
boolean targetBuildQueued = job.scheduleBuild(5, cause, paramsAction);
This way, we end up queueing 40 parallel jobs, each pointing at 1 node, but if we were change anything about the node configuration or number, we wouldn't need to alter any code.
Hope this helps!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-parameter-plugin] (JENKINS-23188) Tag List Empty
Immo Huneke commented on JENKINS-23188 Tag List Empty I have just tried this with the latest versions (Git plugin 2.3.4, Git client plugin 1.15.0, Git parameter plugin 0.3.2) and still get a 401 (unauthorized) status back from github: Jenkins is fully up and running Jan 14, 2015 3:45:03 PM INFO hudson.model.DownloadService$Downloadable load Obtained the updated data file for hudson.tasks.Maven.MavenInstaller Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:04 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:47:46 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents generateContents contenttype PT_TAG RemoteConfig [https://github.com/elektron-technology/cloud-handheld.git] Jan 14, 2015 3:47:47 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.tagMap in /jenkins/job/auth-prototype-CI/build. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) ... at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com/elektron-technology/cloud-handheld.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/elektron-technology/cloud-handheld.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:325) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getTagMap(GitParameterDefinition.java:392) ... 161 more Jan 14, 2015 3:47:55 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default The parameter plugin does not seem to pick up the credentials configured for git access in the project. The git plugin itself however does so successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shelve-project-plugin] (JENKINS-26432) Allow shelving of Workflow
nadav mavor created JENKINS-26432 Allow shelving of Workflow Issue Type: Bug Assignee: ashlux Components: shelve-project-plugin Created: 14/Jan/15 5:14 PM Description: we need to shelving Workflow some as job : https://github.com/jenkinsci/workflow-plugin Environment: Jenkins 1.580.1 Shelve 1.5 Project: Jenkins Labels: Shelve workflow-plugin Priority: Major Reporter: nadav mavor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-23550) Pipeline view distorted in Internet Explorer
Curt Connell
commented on JENKINS-23550
Pipeline view distorted in Internet Explorer
I ran into the same issue and resolved it by commenting a line in my local plugins/build-pipeline-plugin/css/main.css file:
#pipelines {
width: 100%;
text-align: center;
/*border-collapse: collapse; removed to support IE - cjc 20150114*/
}
It now looks good in Chrome, IE, and Firefox.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26408) Sauce connect fails to start
Ross Rowe assigned JENKINS-26408 to Ross Rowe Sauce connect fails to start Change By: Ross Rowe (14/Jan/15 8:07 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
Ross Rowe assigned JENKINS-25236 to Ross Rowe Add support for cainfo and capath in Sauce global settings Change By: Ross Rowe (14/Jan/15 8:08 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Ross Rowe assigned JENKINS-25435 to Ross Rowe Embedded Sauce Report does not show up when session ID present in xunit file Change By: Ross Rowe (14/Jan/15 8:08 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25757) Windows 2003 is an unknown platform
Ross Rowe assigned JENKINS-25757 to Ross Rowe Windows 2003 is an unknown platform Change By: Ross Rowe (14/Jan/15 8:11 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26288) Sauce connect remains running when test job is cancelled
Ross Rowe assigned JENKINS-26288 to Ross Rowe Sauce connect remains running when test job is cancelled Change By: Ross Rowe (14/Jan/15 8:11 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Ross Rowe assigned JENKINS-25411 to Ross Rowe With latest updates, sauce-ondemand no longer works; gives an error Change By: Ross Rowe (14/Jan/15 8:11 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25756) Use latest version of selected browsers? not working with Selenium RC
Ross Rowe assigned JENKINS-25756 to Ross Rowe Use latest version of selected browsers? not working with Selenium RC Change By: Ross Rowe (14/Jan/15 8:12 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25237) Add Sauce connect version to console log when launching Sauce Connect
Ross Rowe assigned JENKINS-25237 to Ross Rowe Add Sauce connect version to console log when launching Sauce Connect Change By: Ross Rowe (14/Jan/15 8:11 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25627) Support for available resolutions
Ross Rowe assigned JENKINS-25627 to Ross Rowe Support for available resolutions Change By: Ross Rowe (14/Jan/15 8:12 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14798) Git Plugin: Umlaute are not displayed correctly
Michael Hofer commented on JENKINS-14798 Git Plugin: Umlaute are not displayed correctly I have experienced the same issue with Jenkins 1.596 / git plugin 2.3.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26422) Improve LOGGER so we can better understand why a job was not triggered
Félix Belzunce Arcos created JENKINS-26422 Improve LOGGER so we can better understand why a job was not triggered Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: bitbucket-plugin Created: 14/Jan/15 8:54 AM Description: Right now it is difficult to track why a git push was not triggered. Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26408) Sauce connect fails to start
Ross Rowe resolved JENKINS-26408 as Fixed Sauce connect fails to start Hi, apologies for the inconvenience, I've released version 1.112 of the plugin which should include the 64-bit version of Sauce Connect, please let me know if you have any further problems Change By: Ross Rowe (14/Jan/15 9:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-24816) deviceName attribute missing on JSON for Android platforms
Ross Rowe resolved JENKINS-24816 as Fixed deviceName attribute missing on JSON for Android platforms I think this issue has already been resolved and a fix should be in the latest version of the plugin, but please let me know if it's still an issue Change By: Ross Rowe (14/Jan/15 9:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25757) Windows 2003 is an unknown platform
Ross Rowe started work on JENKINS-25757 Windows 2003 is an unknown platform Change By: Ross Rowe (14/Jan/15 9:34 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error
siddharth kumar commented on JENKINS-26425 Jenkins subversion authentication error Daniel -I didn't expect this language from you. All I want to know is why after LINUX Kernel PATCH upgrade its not working.What has went wrong?you should n't run away by saying this used to happen with old version of Jenkins and Subversion plugin.Tell me the root cause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26099) Configurable ID for Credentials
SCM/JIRA link daemon commented on JENKINS-26099 Configurable ID for Credentials Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java src/main/resources/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey/credentials.jelly src/main/resources/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey/credentials_de.properties src/main/resources/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey/credentials_ja.properties http://jenkins-ci.org/commit/ssh-credentials-plugin/ab9245809aa854544d144c90a4ca4835cdafb4f9 Log: JENKINS-26099 Permit BasicSSHUserPrivateKey.id to be configured. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-recipients-column-plugin] (JENKINS-21794) Email-ext Plugin : Connection time out
Roman Isko edited a comment on JENKINS-21794 Email-ext Plugin : Connection time out Sumit Chudasama uses wrong SMTP port for smtp.office365.com. Sumit, please visit this page https://support.office.com/en-US/Article/Settings-for-POP-and-IMAP-access-for-Office-365-for-business-or-Microsoft-Exchange-accounts-7fc677eb-2491-4cbc-8153-8e7113525f6c?ui=en-US for correct settings. As you can compare, you specified 567 port but it should be 587. Please set correct port and try again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error
Daniel Beck commented on JENKINS-26425 Jenkins subversion authentication error This is an issue tracker, not a support site. So when you're reporting an issue here, it needs to be relevant to the current state of the project. Otherwise developers spend effort trying to reproduce a problem (in this case that's quite a bit of effort, if possible at all given how little information you provide) that may have been fixed long ago. Subversion plugin 1.45 is obsolete since May 2013, Jenkins 1.534 unsupported since October 2014. On the other hand, it shouldn't take you more than ten minutes to launch a current version of Jenkins on the affected machine (different port and Jenkins home of course), update SVN plugin to the current release, and confirm it still occurs with new versions in your environment. It makes the devs' job much easier without being a significant burden for you. I'm not the only one with that view, see JENKINS-26011 for a similar example (it may also provide a hint as to what may be the problem here). To get assistance in resolving this problem, rather than report an issue, email the jenkinsci-users list, or ask in #jenkins on Freenode. Alternatively, contact one of the commercial Jenkins support vendors, such as Cloudbees, about a Jenkins support contract. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error
Daniel Beck edited a comment on JENKINS-26425 Jenkins subversion authentication error This is an issue tracker, not a support site. So when you're reporting an issue here, it needs to be relevant to the current state of the project. Otherwise developers spend effort trying to reproduce a problem (in this case that's quite a bit of effort, if possible at all given how little information you provide) that may have been fixed long ago. Subversion plugin 1.45 is obsolete since May 2013, Jenkins 1.534 unsupported since October 2013. On the other hand, it shouldn't take you more than ten minutes to launch a current version of Jenkins on the affected machine (different port and Jenkins home of course), update SVN plugin to the current release, and confirm it still occurs with new versions in your environment. It makes the devs' job much easier without being a significant burden for you. I'm not the only one with that view, see JENKINS-26011 for a similar example (it may also provide a hint as to what may be the problem here). To get assistance in resolving this problem, rather than report an issue, email the jenkinsci-users list, or ask in #jenkins on Freenode. Alternatively, contact one of the commercial Jenkins support vendors, such as Cloudbees, about a Jenkins support contract. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-26428) After Upgrading to Jenkins 1.594 version, Console Output does not print the latest log as and when it gets updated.
nanjappa mk created JENKINS-26428 After Upgrading to Jenkins 1.594 version, Console Output does not print the latest log as and when it gets updated. Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-Console-output-issue.jpg Components: console-tail-plugin Created: 14/Jan/15 1:59 PM Description: After Upgrading to Jenkins 1.594 version, Console Output does not print the latest log as and when it gets updated. That is if I click on any build job in progress through Jenkins console and in the left pane if I click on Console Output, it does not sow the bottom of the log which is in progress, it instead stalls on top of the log and user need to scroll down to see what is latest happening in the log. Project: Jenkins Labels: jenkins Priority: Minor Reporter: nanjappa mk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
