[JIRA] [test-results-analyzer-plugin] (JENKINS-32045) Need support to hide configuration methods
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32045 Re: Need support to hide configuration methods Code changed in jenkins User: Varun Menon Path: src/main/java/org/jenkinsci/plugins/testresultsanalyzer/JsTreeUtil.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerExtension.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/config/UserConfig.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/data/ResultData.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/data/TestCaseResultData.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/ClassInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/Info.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/PackageInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/ResultInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/TestCaseInfo.java src/main/resources/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction/index.jelly src/main/resources/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerExtension/global.jelly src/main/webapp/js/test-result-analyzer-template.js src/main/webapp/js/testresult.js http://jenkins-ci.org/commit/test-results-analyzer-plugin/ae6b9194e15d20a873d1be44703fc65e9e825458 Log: JENKINS-32045: Hide configuration methods for testng Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-32045) Need support to hide configuration methods
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32045 Re: Need support to hide configuration methods Code changed in jenkins User: Varun Menon Path: src/main/java/org/jenkinsci/plugins/testresultsanalyzer/JsTreeUtil.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerExtension.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/config/UserConfig.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/data/ResultData.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/data/TestCaseResultData.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/ClassInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/Info.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/PackageInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/ResultInfo.java src/main/java/org/jenkinsci/plugins/testresultsanalyzer/result/info/TestCaseInfo.java src/main/resources/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction/index.jelly src/main/resources/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerExtension/global.jelly src/main/webapp/js/test-result-analyzer-template.js src/main/webapp/js/testresult.js http://jenkins-ci.org/commit/test-results-analyzer-plugin/ce331e4085056981a17d038b3c96b2dab839e662 Log: Merge pull request #34 from menonvarun/JENKINS-32045 JENKINS-32045: Hide configuration methods for testng Compare: https://github.com/jenkinsci/test-results-analyzer-plugin/compare/a5414e94dbca...ce331e408505 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Title: Message Title Jesse Glick commented on JENKINS-28119 Re: Link to log of failed step Should rather return a Serializable struct with @Whitelisted properties that can be used to customize error handling: original exception (e.g., for calling .message) full stack trace of exception (as a convenience) URL of LogAction tail of log file leading up to error label associated with failing step (using FlowNodeSerialWalker from JENKINS-26132, and especially useful in conjunction with JENKINS-26107) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-34138) jenkins jobs are failing at maven installation
Title: Message Title Gangadhar Rayudu created an issue Jenkins / JENKINS-34138 jenkins jobs are failing at maven installation Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Apr/09 1:40 AM Priority: Critical Reporter: Gangadhar Rayudu we started seeing issue with maven installation failed which resulted job fail. Until we re-launch the slave we are not able to execute the job. Please find exception details... [EnvInject] - Loading node environment variables. Building remotely on STPSlave305 in workspace /workspace/SamyakTest java.io.IOException: Failed to install https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.0.3/apache-maven-3.0.3-bin.zip to /tools/hudson.tasks.Maven_MavenInstallation/MavenMaster1QDC at hudson.FilePath.installIfNecessaryFrom(FilePath.java:822) at hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:70) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:182) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:965) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title Luis Silva edited a comment on JENKINS-34135 Re: Plugin unable to find jobs configured with JiraChangelogTrigger That works. The only required permission is Anonymous -> Job Read.It can either be set globally on 'Manage Jenkins' - 'Configure Global Security' or directly on the job(s) which we're configuring to use the jira-trigger-plugin by ticking 'Enable project-based security' and setting the Anonymous -> Job Read permission. Worth adding that to the plugin docs / github README. I don't know much about writing Jenkins plugins, but is there any chance you can require auth in the form of https://user:password:jenkins_url/jira-trigger-webhook-receiver/ (since the jira payload is not modifiable) to even trigger the plugin execution? And maybe even use those creds in the plugin itself to run as a non anonymous user?And why would you need perms to read a job settings but not to trigger the actual build? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title Luis Silva commented on JENKINS-34135 Re: Plugin unable to find jobs configured with JiraChangelogTrigger That works. The only required permission is Anonymous -> Job Read. It can either be set globally on 'Manage Jenkins' - 'Configure Global Security' or directly on the job(s) which we're configuring to use the jira-trigger-plugin by ticking 'Enable project-based security' and setting the Anonymous -> Job Read permission. I don't know much about writing Jenkins plugins, but is there any chance you can require auth in the form of https://user:password:jenkins_url/jira-trigger-webhook-receiver/ (since the jira payload is not modifiable) to even trigger the plugin execution? And maybe even use those creds in the plugin itself to run as a non anonymous user? And why would you need perms to read a job settings but not to trigger the actual build? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5391) Dubious use of String.toUpperCase()
Title: Message Title Daniel Beck commented on JENKINS-5391 Re: Dubious use of String.toUpperCase() In a different way, yes: https://github.com/jenkinsci/jenkins/blob/d8af38b7e3367f3988ceb1d9e15b2fed4efd7971/core/src/main/java/hudson/model/StringParameterValue.java#L55...L57 It simply defines both. Which is probably hilarious on the case of parameter names such as "User" or "Home". Related insanity is JENKINS-16255. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8627) Can't get slave to work on Windows 7 using 1.395 or older version 1.389 (with Linux master)
Title: Message Title keperry commented on JENKINS-8627 Re: Can't get slave to work on Windows 7 using 1.395 or older version 1.389 (with Linux master) Good question This is back in Hudson days. I have since had 2 more kids (up to 3) and switched jobs. We are using Jenkins successfully on a Windows server as a slave. I think it is safe to close this after 5 years Thanks for checking though! Before the Hudson / Jenkins fork seems like a lifetime ago. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14804) Optional 2D barcodes for encoding artefact URLs
Title: Message Title Alex Earl commented on JENKINS-14804 Re: Optional 2D barcodes for encoding artefact URLs This should definitely be implemented as a plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9512) Make Jenkins job configuration flexible by resolving ${..} expression by Jenkins' core rather by plugins.
Title: Message Title
Alex Earl closed an issue as Not A Defect
token-macro is in use by most, if not all, plugins that have variable substitution.
Jenkins / JENKINS-9512
Make Jenkins job configuration flexible by resolving ${..} _expression_ by Jenkins' core rather by plugins.
Change By:
Alex Earl
Status:
Open Closed
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9512) Make Jenkins job configuration flexible by resolving ${..} expression by Jenkins' core rather by plugins.
Title: Message Title
Alex Earl commented on JENKINS-9512
Re: Make Jenkins job configuration flexible by resolving ${..} _expression_ by Jenkins' core rather by plugins.
Most plugins should be using token-macro plugin for this now.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8627) Can't get slave to work on Windows 7 using 1.395 or older version 1.389 (with Linux master)
Title: Message Title Alex Earl commented on JENKINS-8627 Re: Can't get slave to work on Windows 7 using 1.395 or older version 1.389 (with Linux master) Is this still an issue on newer versions? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7872) Cannot launch a slave as a Windows service on a Win7 VM instance
Title: Message Title Alex Earl closed an issue as Not A Defect Comments say issue is resolved. Jenkins / JENKINS-7872 Cannot launch a slave as a Windows service on a Win7 VM instance Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6056) Install Windows service with Log on As
Title: Message Title Alex Earl commented on JENKINS-6056 Re: Install Windows service with Log on As Can anyone else verify that this is fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5550) Manage Hudson page should give me the option to upgrade to a sepcific version
Title: Message Title Alex Earl commented on JENKINS-5550 Re: Manage Hudson page should give me the option to upgrade to a sepcific version Jenkins provides LTS versions now that are considered much more stable. Does this give you the functionality that you need? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7321) Ability to re-run a past job with the same or similar parameters
Title: Message Title Alex Earl resolved as Fixed Fixed in Rebuild Plugin 1.7 Jenkins / JENKINS-7321 Ability to re-run a past job with the same or similar parameters Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7321) Ability to re-run a past job with the same or similar parameters
Title: Message Title Alex Earl closed an issue as Fixed Jenkins / JENKINS-7321 Ability to re-run a past job with the same or similar parameters Change By: Alex Earl Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34133) workflowJobs cpsScm defaults to sourcing from `JenkinsFile`, not `Jenkinsfile`
Title: Message Title Steven Wagner commented on JENKINS-34133 Re: workflowJobs cpsScm defaults to sourcing from `JenkinsFile`, not `Jenkinsfile` See https://github.com/jenkinsci/job-dsl-plugin/pull/819 for fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5419) Select type of script depending on platform
Title: Message Title Alex Earl commented on JENKINS-5419 Re: Select type of script depending on platform There is the XShell plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5391) Dubious use of String.toUpperCase()
Title: Message Title Alex Earl commented on JENKINS-5391 Re: Dubious use of String.toUpperCase() Is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-33712 Empty parameterized build properties not quoted when passed to ant Change By: Emilio Escobar Assignee: Emilio Escobar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653
Title: Message Title Emilio Escobar commented on JENKINS-33727 Re: Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653 Thanks for the mention @Benapgar I will check it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-33727 Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653 Change By: Emilio Escobar Assignee: Emilio Escobar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4656) "Failed to join the process" upgrading to 1.328 or later on glassfish
Title: Message Title Alex Earl commented on JENKINS-4656 Re: "Failed to join the process" upgrading to 1.328 or later on glassfish Is this still valid? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4923) Bad interaction between slave Windows installation and UAC
Title: Message Title Alex Earl commented on JENKINS-4923 Re: Bad interaction between slave Windows installation and UAC Is this issue still relevant? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title Wisen Tanasa commented on JENKINS-34135 Re: Plugin unable to find jobs configured with JiraChangelogTrigger Thanks for reporting this bug. I have managed to reproduce the issue by not giving anonymous user read access. Seems like the plugin is using anonymous user by default. Can you have a quick test to see if the bug goes away when you grant read access to anonymous user? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26132) Executor should show the current stage the flow run is in
Title: Message Title Jesse Glick started work on JENKINS-26132 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sam Van Oort edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage @ [~jglick] !http://i.kinja-img.com/gawker-media/image/upload/aoz8kgx8pzknypz7z38n.jpg! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sam Van Oort commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-2646) Improved organization of project config page
Title: Message Title Alex Earl commented on JENKINS-2646 Re: Improved organization of project config page I think this is addressed in Jenkins 2.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-480) Installation improvement
Title: Message Title Alex Earl commented on JENKINS-480 Re: Installation improvement Is this resolved with the first run wizard? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4625) update center backend assumes the group ID of the plugin to be org.jvnet.hudson.plugins
Title: Message Title Alex Earl commented on JENKINS-4625 Re: update center backend assumes the group ID of the plugin to be org.jvnet.hudson.plugins Is this still valid? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19) full text search
Title: Message Title Alex Earl commented on JENKINS-19 Re: full text search Is this issue still valid? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34137) Possible to close install wizard during plugin install.
Title: Message Title Patrick Wolf assigned an issue to Keith Zantow Jenkins / JENKINS-34137 Possible to close install wizard during plugin install. Change By: Patrick Wolf Assignee: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34137) Possible to close install wizard during plugin install.
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-34137 Possible to close install wizard during plugin install. Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/08 8:48 PM Environment: jenkins-2.0-rc-1 Labels: 2.0 community-bee Priority: Minor Reporter: Patrick Wolf During the installation of plugins while running the install wizard it is possible to click on the X closing the wizard. This skips the remaining steps of the installation but it is hard to tell if it cancels the plugin install or not.
[JIRA] [core] (JENKINS-33950) Unbundled / implicit plugin dependencies may be installed multiple times
Title: Message Title Daniel Beck commented on JENKINS-33950 Re: Unbundled / implicit plugin dependencies may be installed multiple times Fixed towards 2.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33535) It would be nice to show the Jenkins version during the initial setup wizard
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-33535 It would be nice to show the Jenkins version during the initial setup wizard Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Andrew Bayer commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements Also, this would be handy, particularly with regards to tools, with Plumber - I was planning to put in some try/catch logic once tool management actually becomes a thing (which itself still depends on a consistent way to do version discovery), but if we can just use "require" that'd be smoother. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Andrew Bayer commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements I'm +1 overall - tools will need a fair amount of work to support a real version concept, but I'm actually beginning to kick around ideas for that anyway. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copy-project-link-plugin] (JENKINS-34136) Copy project link fails to find checkJobName
Title: Message Title Will Saxon created an issue Jenkins / JENKINS-34136 Copy project link fails to find checkJobName Issue Type: Bug Assignee: Unassigned Components: copy-project-link-plugin Created: 2016/Apr/08 8:08 PM Environment: Jenkins 1.642.4, Copy Project LInk 1.5, Folders 5.7 Priority: Major Reporter: Will Saxon The copy project link has stopped working for us after a recent update of plugins. When clicking the link, we see an 'ERROR' link under the box for the new project name, and when clicking that or the 'OK' button we get the following: HTTP ERROR 404 Problem accessing /job/Folder//checkJobName. Reason: Not Found We are using the Folders plugin, and there was a recent Folders update which changed some APIs - not sure if related. This prevents us from using the copy project plugin.
[JIRA] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title R. Tyler Croy commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements Jesse Glick I don't see how my proposal and JENKINS-28718 are mutually exclusive, unless you're referring to automatically installing tools (which I think is a fun feature but I would immediately disable it in any production environment). I view a generic require step as a useful way to allow a script to safely declare runtime dependencies and nothing more. Every scripting environment, even _javascript_ these days, has a similar syntax. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title Jesse Glick commented on JENKINS-27395 Re: distinguish test reports filed from different parts of workflow One possibility is to look up the nearest enclosing LabelAction and automatically include that in the test result metadata. Thus running JUnitResultArchiver inside label (JENKINS-26107) or a parallel branch would suffice to differentiate ambiguous test names. Rendering results in a matrix requires more information. Perhaps the convention could be that a label in a format acceptable to hudson.matrix.Combination.fromString (for example, os=win,jdk=7) would be eligible for display by any supporting visualizations in a matrix cell. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jesse Glick commented on JENKINS-26522
Re: Annotated block/stage status
I am already working on JENKINS-26107, which allows you to define a display label for a block (which could contain one step, a series of steps, some function calls, etc.). What I would propose is another step status that could take various parameters such as:
result: 'ABORTED' (or any other hudson.model.Result)
message: 'skipped 5 tests'
tags: [env: 'production', version: 123]
badge: 'url'
error: x (after catch (x))
When run, the step would look up the enclosing BlockStartNode and attach some actions to it. (The BlockEndNode would be more logical, but that is not created until the block is actually closed. Alternately, the step could be placed outside and just after the block, but that makes it harder to access local variables and the like.) So your Jenkinsfile could look like
label('Security tests') {
sh 'make test'
def failureCount = Integer.parseInt(readFile 'failureCount')
if (failureCount == 0) {
status badge: 'http://mycdn.com/checkmark.png'
} else {
status badge: 'http://mycdn.com/redx.png', result: 'UNSTABLE', message: "${failureCount} test(s) failed"
}
}
which I think is reasonably readable, and allows the job to record all relevant information in the flow graph in a way that is recoverable from the Java APIs (and, albeit awkwardly for now, from the REST API). The basic Pipeline Steps UI can certainly show all this information, and some kind of unobtrusive formatted text can be added to the textual build log too.
Then the question becomes how sophisticated you can expect the “stock” stage view visualization to be when it comes to representing this information. JENKINS-33185 proposes a significant overhaul to that view, in the context of which it would make sense to display this status information directly.
The UI you are showing requires more than that, however, since you are displaying multiple results per build according to matrix configurations. JENKINS-27395 requests a way for the Jenkinsfile to scope things like archived test results to a particular configuration of matrix axes, where this information would then become accessible to other plugins. In particular the stage view (or whatever the visualization of Pipeline builds is called by then) would need to render matrices of results when defined.
No matter what gets implemented in Pipeline, you are not going to have a UI as well tuned to your use case as what you currently have in your custom plugin, but perhaps the generic UI would be good enough, or at
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653
Title: Message Title Ben Apgar edited a comment on JENKINS-33727 Re: Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653 [~escoem] I think this is related to the changes in ArgumentListBuilder for your fix for JENKINS-28790 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Jesse Glick commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage While such a view could be implemented using the currently available flow graphs, restricting itself to display of parallel branches, JENKINS-26107 would offer more flexibility. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653
Title: Message Title Ben Apgar commented on JENKINS-33727 Re: Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653 Emilio Escobar I think this is related to your fix for JENKINS-28790 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28293) Display more information about Pipeline steps
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28293 Display more information about Pipeline steps Since there are already labels coming from many steps, and JENKINS-26107 allows you to easily add more labels, I think the only thing really missing here is a way to look at step parameters. Change By: Jesse Glick Summary: Workflow Steps should have better summaries Display more information about Pipeline steps Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28293) Workflow Steps should have better summaries
Title: Message Title Jesse Glick commented on JENKINS-28293 Re: Workflow Steps should have better summaries Would need JENKINS-31582 to capture step arguments. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32535 Re: Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view' Code changed in jenkins User: Ing. Pavel Janousek Path: test/pom.xml test/src/test/java/hudson/cli/AddJobToViewCommandTest.java test/src/test/java/hudson/cli/RemoveJobFromViewCommandTest.java test/src/test/java/hudson/cli/ViewManipulationTest.java test/src/test/java/hudson/cli/ViewManipulationTestBase.java http://jenkins-ci.org/commit/jenkins/c2f1ace15aa74ce05de00471d85a2f79712b4388 Log: JENKINS-32535 Improved test coverage 'add-job-to-view' and 'remove-job-from-view' Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32535 Re: Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view' Code changed in jenkins User: Daniel Beck Path: test/pom.xml test/src/test/java/hudson/cli/AddJobToViewCommandTest.java test/src/test/java/hudson/cli/RemoveJobFromViewCommandTest.java test/src/test/java/hudson/cli/ViewManipulationTest.java test/src/test/java/hudson/cli/ViewManipulationTestBase.java http://jenkins-ci.org/commit/jenkins/ae82f8e93f57b59fe04b0479b26f310409e64f86 Log: Merge pull request #2202 from pjanouse/JENKINS-32535 JENKINS-32535 Improved test coverage 'add-job-to-view' and 'remove-job-from-view' Compare: https://github.com/jenkinsci/jenkins/compare/7901ffb8ab77...ae82f8e93f57 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Jesse Glick commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements -1 on a generic require step. See JENKINS-28718 for the case of tools. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33821) Pipeline job s can`t be disabled
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-33821 Pipeline job s can`t be disabled Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title Jesse Glick resolved as Won't Do No current plans to release this feature as OSS. Jenkins / JENKINS-33846 Restart pipeline from specific stage, after failure Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Bim Paras commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Has this issue been resolved? I am still seeing this issue in version 0.25 of plugin. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-34134) Jenkins crashes with OOM when using this plugin
Title: Message Title Alex Gray commented on JENKINS-34134 Re: Jenkins crashes with OOM when using this plugin Here is an example of parsing a large json file: http://stackoverflow.com/questions/9390368/java-best-approach-to-parse-huge-extra-large-json-file Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33535) It would be nice to show the Jenkins version during the initial setup wizard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33535 Re: It would be nice to show the Jenkins version during the initial setup wizard Code changed in jenkins User: kzantow Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/lib/layout/html.jelly core/src/main/resources/lib/layout/layout.jelly war/src/main/js/pluginSetupWizardGui.js war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/f6822a2583a8399e0d5b512cb91de3518998492e Log: JENKINS-33535 - show Jenkins version on setup wizard Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33535) It would be nice to show the Jenkins version during the initial setup wizard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33535 Re: It would be nice to show the Jenkins version during the initial setup wizard Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/lib/layout/html.jelly core/src/main/resources/lib/layout/layout.jelly war/src/main/js/pluginSetupWizardGui.js war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/49b407c1ce8c81a066140025857085c9965d5096 Log: Merge pull request #2244 from kzantow/JENKINS-33535-show-jenkins-version-on-installer JENKINS-33535 show Jenkins version on setup wizard Compare: https://github.com/jenkinsci/jenkins/compare/49350da2399a...49b407c1ce8c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Title: Message Title Jesse Glick commented on JENKINS-28119 Re: Link to log of failed step inside that global method I lose access to global variables, like JOB_NAME Not true, these are still accessible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title
Luis Silva updated an issue
Jenkins / JENKINS-34135
Plugin unable to find jobs configured with JiraChangelogTrigger
Change By:
Luis Silva
Jira webhooks are working fine but the plugin doesn't seem to find any configured jobs. Check the log output below:{code}Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"timestamp": 1460135096626,"webhookEvent": "jira:issue_updated","issue_event_type_name": "issue_generic","user": {"changelog": {"id": "12684","items": [{"field": "resolution","fieldtype": "jira","from": null,"fromString": null,"to": "1","toString": "Done"},{"field": "status","fieldtype": "jira","from": "3","fromString": "In Progress","to": "10002","toString": "Done"}]}}Apr 08, 2016 5:04:58 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookReceived Webhook callback from changelog. Event type: jira:issue_updatedApr 08, 2016 5:04:58 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.JiraTriggerExecutorCouldn't find any projects that have JiraChangelogTrigger configured{code}But testing it in isolation in jenkins script console returns valid jobs: {code} import com.ceilfors.jenkins.plugins.jiratrigger.JiraChangelogTriggerprojects = Jenkins.instance.getAllItems(AbstractProject).findAll { it.getTrigger(JiraChangelogTrigger) }println(projects)Result[hudson.model.FreeStyleProject@44a9508c[test]] {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title
Luis Silva updated an issue
Jenkins / JENKINS-34135
Plugin unable to find jobs configured with JiraChangelogTrigger
Change By:
Luis Silva
Jira webhooks are working fine but the plugin doesn't seem to find any configured jobs. Check the log output below: {code} Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"timestamp": 1460135096626,"webhookEvent": "jira:issue_updated","issue_event_type_name": "issue_generic","user": {"changelog": {"id": "12684","items": [{"field": "resolution","fieldtype": "jira","from": null,"fromString": null,"to": "1","toString": "Done"},{"field": "status","fieldtype": "jira","from": "3","fromString": "In Progress","to": "10002","toString": "Done"}]}}Apr 08, 2016 5:04:58 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookReceived Webhook callback from changelog. Event type: jira:issue_updatedApr 08, 2016 5:04:58 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.JiraTriggerExecutorCouldn't find any projects that have JiraChangelogTrigger configured {code} But testing it in isolation in jenkins script console returns valid jobs:import com.ceilfors.jenkins.plugins.jiratrigger.JiraChangelogTriggerprojects = Jenkins.instance.getAllItems(AbstractProject).findAll { it.getTrigger(JiraChangelogTrigger) }println(projects)Result[hudson.model.FreeStyleProject@44a9508c[test]]
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-15057) Manual plugin upload should download plugin dependencies
Title: Message Title SCM/JIRA link daemon commented on JENKINS-15057 Re: Manual plugin upload should download plugin dependencies Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginManager.java test/src/test/java/hudson/PluginManagerTest.java test/src/test/resources/plugins/Parameterized-Remote-Trigger.hpi test/src/test/resources/plugins/credentials.hpi test/src/test/resources/plugins/icon-shim.hpi test/src/test/resources/plugins/token-macro.hpi test/src/test/resources/plugins/upload-test-update-center.json http://jenkins-ci.org/commit/jenkins/d5c508dece359f22799acaf84830be9e3a9e2ec3 Log: Merge pull request #2239 from slide/master [FIXED JENKINS-15057] Add dependency resolution to manually uploaded plugins. Compare: https://github.com/jenkinsci/jenkins/compare/274183dba2bc...d5c508dece35 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15057) Manual plugin upload should download plugin dependencies
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-15057 Manual plugin upload should download plugin dependencies Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-trigger-plugin] (JENKINS-34135) Plugin unable to find jobs configured with JiraChangelogTrigger
Title: Message Title
Luis Silva created an issue
Jenkins / JENKINS-34135
Plugin unable to find jobs configured with JiraChangelogTrigger
Issue Type:
Bug
Assignee:
Wisen Tanasa
Components:
jira-trigger-plugin
Created:
2016/Apr/08 6:37 PM
Environment:
Jenkins version: 1.642.4 Plugin version: 0.2.0 Using Jira Atlassian Cloud
Priority:
Blocker
Reporter:
Luis Silva
Jira webhooks are working fine but the plugin doesn't seem to find any configured jobs. Check the log output below:
Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook Webhook event body: Apr 08, 2016 5:04:58 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook { "timestamp": 1460135096626, "webhookEvent": "jira:issue_updated", "issue_event_type_name": "issue_generic", "user": { "changelog": { "id": "12684", "items": [ { "field": "resolution", "fieldtype": "jira", "from": null, "fromString": null, "to": "1", "toString": "Done" }
, { "field": "status", "fieldtype": "jira", "from": "3", "fromString": "In Progress", "to": "10002", "toString": "Done" }
] } } Apr 08, 2016 5:04:58 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook Received Webhook callback from changelog. Event type:
[JIRA] [test-results-analyzer-plugin] (JENKINS-34134) Jenkins crashes with OOM when using this plugin
Title: Message Title Alex Gray created an issue Jenkins / JENKINS-34134 Jenkins crashes with OOM when using this plugin Issue Type: Bug Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 2016/Apr/08 6:24 PM Environment: Jenkins ver. 1.642.4 test-result-analzyer plugin: 0.3.4 Priority: Major Reporter: Alex Gray Ever since we installed this plugin Jenkins has been crashing with an OOM. No settings were tweaked in this plugin (all the defaults have been used). I've monitored the memory usage and the moment I click on "Test Results Analyzer", the memory goes up and up and up and then crashes Jenkins. (Note: It does not always crash Jenkins though. Sometimes I have to click that button a few times AFTER it has rendered) My guess is that the net.sf.json is the culprit. The version is not mentioned in the pom.xml, but older versions of this library had memory leaks, like from this post, back in 2009: link Also, the function createJson is sucking up the entire json tree into memory. I'm not sure if there is a way to optimize this loop (maybe serialize to disk?), but without putting a profile on that bit of code, I'm pretty sure that is where the problem lies. I'm running my master on a
[JIRA] [job-dsl-plugin] (JENKINS-34133) workflowJobs cpsScm defaults to sourcing from `JenkinsFile`, not `Jenkinsfile`
Title: Message Title
Steven Wagner created an issue
Jenkins / JENKINS-34133
workflowJobs cpsScm defaults to sourcing from `JenkinsFile`, not `Jenkinsfile`
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Apr/08 6:14 PM
Priority:
Minor
Reporter:
Steven Wagner
This is easy to reproduce - just create a new workflowJob with a cpsScm definition, i.e.:
{{workflowJob('camelcase') { definition { cpsScm { scm { ... }
} } }}}
The workflowJob test actually already checks the resulting string but expects it to be camel cased, which doesn't seem to be the Cloudbees convention.
Add Comment
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653
Title: Message Title Ben Apgar updated an issue Jenkins / JENKINS-33727 Invoke Ant - Build failed if parameters contain spaces due to changes in quotes since 1.653 Change By: Ben Apgar Summary: Invoke Ant build step does not work - Build failed if parameters contain spaces due to changes in quotes since 1.653 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant build step does not work since 1.653
Title: Message Title Ben Apgar commented on JENKINS-33727 Re: Invoke Ant build step does not work since 1.653 We are getting this too. The problem is related to parameters that contain spaces. Previous behavior: Full command enclosed by single quotes and doublequotes. Parameters containing spaces enclosed by double-quotes. Example: '"ant.bat -DPARAM1=hello "-DPARAM2=hello world" -DPARAM3=world"' Current behavior: Full command enclosed by double quotes. Parameters containing spaces enclosed by single-quotes and double-quotes. "ant.bat -DPARAM1=hello '"-DPARAM2=hello world"' -DPARAM3=world" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [text-file-operations-plugin] (JENKINS-33899) Text-file-operations-plugin failing on versions above 1.2.1
Title: Message Title Sanketh PB resolved as Fixed Jenkins / JENKINS-33899 Text-file-operations-plugin failing on versions above 1.2.1 Change By: Sanketh PB Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()
Title: Message Title Sanketh PB resolved as Fixed Jenkins / JENKINS-32694 NullPointerException at CreateTextFile.CreateFileTask.call() Change By: Sanketh PB Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-33899) Text-file-operations-plugin failing on versions above 1.2.1
Title: Message Title Sanketh PB assigned an issue to Nicky Goethals Jenkins / JENKINS-33899 Text-file-operations-plugin failing on versions above 1.2.1 Change By: Sanketh PB Assignee: Sanketh PB Nicky Goethals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()
Title: Message Title Sanketh PB commented on JENKINS-32694 Re: NullPointerException at CreateTextFile.CreateFileTask.call() Fixed in 1.3.2, please check. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-33899) Text-file-operations-plugin failing on versions above 1.2.1
Title: Message Title Sanketh PB commented on JENKINS-33899 Re: Text-file-operations-plugin failing on versions above 1.2.1 Fixed in 1.3.2, please check. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()
Title: Message Title Sanketh PB assigned an issue to Noam Manos Jenkins / JENKINS-32694 NullPointerException at CreateTextFile.CreateFileTask.call() Change By: Sanketh PB Assignee: Sanketh PB Noam Manos Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Blake MItchell commented on JENKINS-32118 Re: Opening Robot Framework log failed Thank you selur vedu, your work around works for me. But I always get nervous disabling security features, even for private sites behind a firewall. Is there a better long term solution for this issues, will the robot framework people need to be involved? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32694 Re: NullPointerException at CreateTextFile.CreateFileTask.call() Code changed in jenkins User: Sanketh P B Path: src/main/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileBuilder.java src/main/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileTask.java src/test/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileBuilderTest.java http://jenkins-ci.org/commit/text-file-operations-plugin/246f5a0ff1aedba561a32df77a913f28c712d9a6 Log: Fixed JENKINS-33899 and JENKINS-32694 logging caused null exception. Improvements in exception logging. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-file-operations-plugin] (JENKINS-33899) Text-file-operations-plugin failing on versions above 1.2.1
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33899 Re: Text-file-operations-plugin failing on versions above 1.2.1 Code changed in jenkins User: Sanketh P B Path: src/main/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileBuilder.java src/main/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileTask.java src/test/java/com/etas/jenkins/plugins/CreateTextFile/CreateFileBuilderTest.java http://jenkins-ci.org/commit/text-file-operations-plugin/246f5a0ff1aedba561a32df77a913f28c712d9a6 Log: Fixed JENKINS-33899 and JENKINS-32694 logging caused null exception. Improvements in exception logging. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26156) Erroneous handling of BodyInvoker.withDisplayName
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-26156 Erroneous handling of BodyInvoker.withDisplayName Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26156) Erroneous handling of BodyInvoker.withDisplayName
Title: Message Title Jesse Glick started work on JENKINS-26156 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27127) wait/notify steps
Title: Message Title Jesse Glick commented on JENKINS-27127 Re: wait/notify steps Miguel Tadeu is there some reason you assigned this to yourself? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-34096) Fix Findbugs issues.
Title: Message Title Jesse Glick resolved as Fixed FYI you can use the notation [FIXED JENKINS-34096 ] in a commit comment to have the issue be automatically closed when the PR is merged you need not bother filing an issue for something like this with no user impact Jenkins / JENKINS-34096 Fix Findbugs issues. Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [script-security-plugin] (JENKINS-34096) Fix Findbugs issues.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34096 Re: Fix Findbugs issues. Code changed in jenkins User: Andres Rodriguez Path: pom.xml src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/StaticWhitelist.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ApprovalContext.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ScriptApproval.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyShellLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyXmlLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/JellyLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/JexlLanguage.java http://jenkins-ci.org/commit/script-security-plugin/34347ce50fabb48e6290e52729346d663e454a9d Log: JENKINS-34096 Fix Findbugs issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-34096) Fix Findbugs issues.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34096 Re: Fix Findbugs issues. Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/StaticWhitelist.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ApprovalContext.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ScriptApproval.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyShellLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/GroovyXmlLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/JellyLanguage.java src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/languages/JexlLanguage.java http://jenkins-ci.org/commit/script-security-plugin/47ea2833a95d5dc086ca4e6dbe78a9d2a6fcdfd0 Log: Merge pull request #51 from andresrc/JENKINS-34096 JENKINS-34096 Fix Findbugs issues Compare: https://github.com/jenkinsci/script-security-plugin/compare/cf27d253b1d6...47ea2833a95d Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Title: Message Title Mikael Gaunin commented on JENKINS-25583 Re: Unexpected error in launching a slave. This is probably a bug in Jenkins. Richard Lavoie your fix is validated. Any chance to generate a release soon? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports-plugin] (JENKINS-34132) Cucumber Report Plugin does not work on not root jenkins installation
Title: Message Title Ivan Fofanov created an issue Jenkins / JENKINS-34132 Cucumber Report Plugin does not work on not root jenkins installation Issue Type: Bug Assignee: Damian Szczepanik Components: cucumber-reports-plugin Created: 2016/Apr/08 4:18 PM Environment: Jenkins ver. 1.647 Cucumber-jvm reports 2.1.0 Priority: Minor Reporter: Ivan Fofanov If jenkins is installed not on root context like http://hostname:8080/jenkins/ instead of http://hostname:8080/ Then following links on result page are working incorrectly: Jenkins Previous results Last results E.g. link looks like http://hostname:8080/job/jobname/16/cucumber-html-reports/feature-overview.html instead of http://hostname:8080/jenkins/job/jobname/16/cucumber-html-reports/feature-overview.html
[JIRA] [job-dsl-plugin] (JENKINS-34124) job dsl slack integration creates an incompatible config since slack plugin 2.0
Title: Message Title Thomas Whitton commented on JENKINS-34124 Re: job dsl slack integration creates an incompatible config since slack plugin 2.0 yep that looks like it will solve this issue and looks really cool, thanks for the info! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-34131) Upgrade Windows Slaves Plugin to new parent POM
Title: Message Title Armando Fernandez started work on JENKINS-34131 Change By: Armando Fernandez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-34131) Upgrade Windows Slaves Plugin to new parent POM
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-34131 Upgrade Windows Slaves Plugin to new parent POM Issue Type: Improvement Assignee: Armando Fernandez Components: windows-slaves-plugin Created: 2016/Apr/08 3:15 PM Priority: Minor Reporter: Armando Fernandez Upgrade Windows Slaves Plugin to use plugin parent pom version 2.6. See benefits here Add Comment This message was sent by Atlassian JIRA
[JIRA] [core] (JENKINS-33950) Unbundled / implicit plugin dependencies may be installed multiple times
Title: Message Title Keith Zantow started work on JENKINS-33950 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-34130) [skip ci] on git commit message still triggering build
Title: Message Title Alex Gray created an issue Jenkins / JENKINS-34130 [skip ci] on git commit message still triggering build Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 2016/Apr/08 3:07 PM Environment: Jenkins ver. 1.642.4 ghprb-plugin: 1.31.2 Priority: Minor Reporter: Alex Gray We can't get the [skip ci] option to work with this plugin. We put this text, [skip ci], in pretty much everything we can think of and the build still gets triggered when someone does a push to a PR. We tried: putting the [skip ci] text in the commit message. putting the [skip ci] text in the PR message body. putting the [skip ci] text as a message in the PR. We didn't change the default value of:
[JIRA] [script-security-plugin] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
Title: Message Title Andres Rodriguez commented on JENKINS-24399 Re: Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Filed https://github.com/jenkinsci/script-security-plugin/pull/52 preventing the use of class directories as classpath entries. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
Title: Message Title Andres Rodriguez started work on JENKINS-24399 Change By: Andres Rodriguez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
Title: Message Title Andres Rodriguez assigned an issue to Andres Rodriguez Jenkins / JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Change By: Andres Rodriguez Assignee: Jesse Glick Andres Rodriguez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-34099) Build other projects (manual step) can't find and trigger project
Title: Message Title Nicolas Videau closed an issue as Not A Defect Jenkins / JENKINS-34099 Build other projects (manual step) can't find and trigger project Change By: Nicolas Videau Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-34099) Build other projects (manual step) can't find and trigger project
Title: Message Title Nicolas Videau commented on JENKINS-34099 Re: Build other projects (manual step) can't find and trigger project Yes, It was this, Thanks a lot. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-compat-tester] (JENKINS-34129) Cannot release plugin due to injected tests failure
Title: Message Title Andrei Tuicu created an issue Jenkins / JENKINS-34129 Cannot release plugin due to injected tests failure Issue Type: Bug Assignee: Frédéric Camblor Components: plugin-compat-tester Created: 2016/Apr/08 2:50 PM Environment: Apache Maven 3.3.9 Java versions: 1.7.0_79 or 1.8.0_73 (tested with both) Jenkins: 1.609.1 OS El Capitan: 10.11.2 Labels: release-plugin Priority: Critical Reporter: Andrei Tuicu We cannot perform a plugin release, because two injected tests fail in the Jenkins job[0]. The code can be found on github here[1]. Steps to reproduce: You can reproduce the problem, by cloning the repository and after running mvn clean install. For the first test ( org.jvnet.hudson.test.junit.FailedTest.org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite): We understand that there is a problem with Guava, but we have no idea how to fix it. Our plugin is indirectly dependent on it. For the second
[JIRA] [p4-plugin] (JENKINS-34128) P4 Plugin NODE_NAME is always master for pipeline p4sync step
Title: Message Title
Russell Gallop updated an issue
Jenkins / JENKINS-34128
P4 Plugin NODE_NAME is always master for pipeline p4sync step
Change By:
Russell Gallop
{ ${NODE_NAME} } in p4sync format field appears to always say "master".The default workspace name format is { jenkins-${NODE_NAME}-${JOB_NAME} } .e.g. I have a job "MyPipeline" and nodes "master" and "My_node".{code}node ('My_node') {deleteDir()p4sync charset: 'none', credential: 'my_creds', depotPath: '//depot/myapp'bat 'echo %NODE_NAME%'}{code}In the console output you can see that the workspace name always has the node master but the job can access the correct value of NODE_NAME.{code}[Pipeline] Allocate node : StartRunning on My_node in c:\j\w\MyPipeline[Pipeline] node {[Pipeline] deleteDir[Pipeline] p4sync... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: ... p4 client -o jenkins-master-MyPipeline +... p4 client -i +... client: jenkins-master-MyPipeline... p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 counter change +... p4 changes -m1 -ssubmitted //jenkins-master-MyPipeline/... +Building on Node: master... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: P4 Task: reverting all pending and shelved revisions p4 revert c:\j\w\MyPipeline/... +... rm [abandoned files]duration: (14ms)P4 Task: cleaning workspace to match have list p4 reconcile -w -f c:\j\w\MyPipeline/... +duration: (79ms)P4 Task: syncing files at change: 1234... p4 sync c:\j\w\MyPipeline/...@1234 +duration: (10ms)P4 Task: saving built changes p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 client -o jenkins-master-MyPipeline +... p4 info +... done[Pipeline] bat[MyPipeline] Running batch scriptc:\j\w\MyPipeline>echo My_node My_node[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipeline{code}Using p4 plugin scm in freestyle jobs works okay.
Add Comment
[JIRA] [p4-plugin] (JENKINS-34128) P4 Plugin NODE_NAME is always master for pipeline p4sync step
Title: Message Title
Russell Gallop updated an issue
Jenkins / JENKINS-34128
P4 Plugin NODE_NAME is always master for pipeline p4sync step
Change By:
Russell Gallop
{ $ \ {NODE_NAME \ } } in p4sync format field appears to always say "master".The default workspace name format is {jenkins-${NODE_NAME}-${JOB_NAME}}.e.g. I have a job "MyPipeline" and nodes "master" and "My_node".{code}node ('My_node') {deleteDir()p4sync charset: 'none', credential: 'my_creds', depotPath: '//depot/myapp'bat 'echo %NODE_NAME%'}{code}In the console output you can see that the workspace name always has the node master but the job can access the correct value of NODE_NAME.{code}[Pipeline] Allocate node : StartRunning on My_node in c:\j\w\MyPipeline[Pipeline] node {[Pipeline] deleteDir[Pipeline] p4sync... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: ... p4 client -o jenkins-master-MyPipeline +... p4 client -i +... client: jenkins-master-MyPipeline... p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 counter change +... p4 changes -m1 -ssubmitted //jenkins-master-MyPipeline/... +Building on Node: master... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: P4 Task: reverting all pending and shelved revisions p4 revert c:\j\w\MyPipeline/... +... rm [abandoned files]duration: (14ms)P4 Task: cleaning workspace to match have list p4 reconcile -w -f c:\j\w\MyPipeline/... +duration: (79ms)P4 Task: syncing files at change: 1234... p4 sync c:\j\w\MyPipeline/...@1234 +duration: (10ms)P4 Task: saving built changes p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 client -o jenkins-master-MyPipeline +... p4 info +... done[Pipeline] bat[MyPipeline] Running batch scriptc:\j\w\MyPipeline>echo My_node My_node[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipeline{code}Using p4 plugin scm in freestyle jobs works okay.
Add Comment
[JIRA] [p4-plugin] (JENKINS-34128) P4 Plugin NODE_NAME is always master for pipeline p4sync step
Title: Message Title
Russell Gallop updated an issue
Jenkins / JENKINS-34128
P4 Plugin NODE_NAME is always master for pipeline p4sync step
Change By:
Russell Gallop
$\{NODE_NAME\} in p4sync format field appears to always say "master".The default workspace name format is { jenkins-$ \ {NODE_NAME \ }-$ \ {JOB_NAME \ } } .e.g. I have a job "MyPipeline" and nodes "master" and "My_node".{code}node ('My_node') {deleteDir()p4sync charset: 'none', credential: 'my_creds', depotPath: '//depot/myapp'bat 'echo %NODE_NAME%'}{code}In the console output you can see that the workspace name always has the node master but the job can access the correct value of NODE_NAME.{code}[Pipeline] Allocate node : StartRunning on My_node in c:\j\w\MyPipeline[Pipeline] node {[Pipeline] deleteDir[Pipeline] p4sync... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: ... p4 client -o jenkins-master-MyPipeline +... p4 client -i +... client: jenkins-master-MyPipeline... p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 counter change +... p4 changes -m1 -ssubmitted //jenkins-master-MyPipeline/... +Building on Node: master... p4 client -o jenkins-master-MyPipeline +... p4 info +P4 Task: establishing connection server: p4server:1666... node: P4 Task: reverting all pending and shelved revisions p4 revert c:\j\w\MyPipeline/... +... rm [abandoned files]duration: (14ms)P4 Task: cleaning workspace to match have list p4 reconcile -w -f c:\j\w\MyPipeline/... +duration: (79ms)P4 Task: syncing files at change: 1234... p4 sync c:\j\w\MyPipeline/...@1234 +duration: (10ms)P4 Task: saving built changes p4 client -o jenkins-master-MyPipeline +... p4 info +... p4 client -o jenkins-master-MyPipeline +... p4 info +... done[Pipeline] bat[MyPipeline] Running batch scriptc:\j\w\MyPipeline>echo My_node My_node[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipeline{code}Using p4 plugin scm in freestyle jobs works okay.
Add Comment
[JIRA] [p4-plugin] (JENKINS-34128) P4 Plugin NODE_NAME is always master for pipeline p4sync step
Title: Message Title
Russell Gallop created an issue
Jenkins / JENKINS-34128
P4 Plugin NODE_NAME is always master for pipeline p4sync step
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Apr/08 2:41 PM
Environment:
jenkins 1.642.4 p4-plugin 1.3.8 workflow-aggregator 2.0
Priority:
Major
Reporter:
Russell Gallop
$ {NODE_NAME} in p4sync format field appears to always say "master". The default workspace name format is jenkins-${NODE_NAME}
-$ {JOB_NAME}
.
e.g. I have a job "MyPipeline" and nodes "master" and "My_node".
node ('My_node') {
deleteDir()
p4sync charset: 'none', credential: 'my_creds', depotPath: '//depot/myapp'
bat 'echo %NODE_NAME%'
}
In the console output you can see that the workspace name always has the node master but the job can access the correct value of NODE_NAME.
[JIRA] [core] (JENKINS-20617) Remove old versions of optional plugins from Jenkins core: CVS, LDAP, possibly others
Title: Message Title Daniel Beck commented on JENKINS-20617 Re: Remove old versions of optional plugins from Jenkins core: CVS, LDAP, possibly others Effectively implemented towards 2.0 as part of JENKINS-9598 : https://jenkins.io/2.0/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
