[JIRA] [build-pipeline-plugin] (JENKINS-20672) Different priorities from different build type
Libero Scarcelli commented on JENKINS-20672 Different priorities from different build type You might have to change the core to get this one done 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-26969) I like it is possible to select that BFA set failed build status as ABORTED
Tomas Westling commented on JENKINS-26969 I like it is possible to select that BFA set failed build status as ABORTED Changing a build that failed to ABORTED after it is done building doesn't make sense to me. Even if the cause of the failure was the environment, the build did fail and BFA shouldn't change that. I understand that you want the functionality for your use case but I think it's a way too tailor-made solution that doesn't make sense in any other context. 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-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Libero Scarcelli edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline This one should be fixed now... but you need to update Core and pipeline plugin: I can see most of you are using a very old version of Jenkins and Pipeline plugin. I am pretty sure an update would fix this. I would recommend you to run at least Jenkins version 1.580.3 + Build Pipeline Plugin 1.4.5 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-pipeline-plugin] (JENKINS-20672) Different priorities from different build type
Libero Scarcelli edited a comment on JENKINS-20672 Different priorities from different build type You might have to change the core to get this one done... not sure what would happen when a job is triggered by a timer 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-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Libero Scarcelli edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline This one should be fixed now... but you need to update Core and pipeline plugin: I can see most of you are using a very old version of Jenkins and Pipeline plugin. I am pretty sure an update would fix this 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] [promoted-builds-plugin] (JENKINS-20492) Re-Execute promotion button is gone
Damien Nozay
commented on JENKINS-20492
Re-Execute promotion button is gone
Fixed/Workaround in version 2.20.
https://github.com/jenkinsci/promoted-builds-plugin/commit/8e0e17b1e21624cb3db68f23b868fb15d280aae3
The fix was to remove the button display condition which was `isManuallyApproved()`.
Promotions that are "Forced" are not the same as "manually approved".
It is now displayed unconditionally.
There are many use cases for re-executing the promotion, two of them are:
1. it didn't work the first time, duh!
2. side-effects that you want to re-execute.
The "Force promotion" workflow may very well be broken.
You may be able to get more data using/adapting the following groovy script:
Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javaimport hudson.plugins.promoted_builds.*;
jobs = hudson.model.Hudson.instance.getAllItems(FreeStyleProject)
job = jobs[0]
build = job.lastSuccessfulBuild
println build.actions
build.getAction(PromotedBuildAction.class).promotions.each {
p -
println "promotion:" + p.name + ", manual:" + p.manuallyApproved + ", success:" + p.promotionSuccessful
println p.badges
}
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] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Oleg Nenashev commented on JENKINS-26999 Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) @Caleb I definitely should check it on my own, because I've never thought such case may work Build wrappers should not inject variables outside the build in general, but there could be hacks in EnvInject plugin or missed routines in Perforce plugin. On the other hand, in 1.3.27 polling used to ignore missing variables, so probably you polling procedures weren't completely correct.. Have you updated Jenkins core or EnvInject plugin together with Perforce plugin? 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] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Oleg Nenashev started work on JENKINS-26999 Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) Change By: Oleg Nenashev (18/Feb/15 8: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] [testfairy-plugin] (JENKINS-26991) jarsigner failing with Invalid keystore format
Gil Tselsnchuk commented on JENKINS-26991 jarsigner failing with Invalid keystore format Thanks for the bug report. We are looking into it. Gil, Team TestFairy 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-23396) SSH credentials not supported
Amedee Van Gasse commented on JENKINS-23396 SSH credentials not supported The workaround suggested in #1 only works if you have shell access to the server that runs Jenkins, and if you can login with the user that runs Jenkins (either directly or with sudo). In a hosted environment, this will not be possible. As a workaround, I used another plugin: Extensible Choice. In that plugin I have a Groovy script that calls a PHP script on another server that is under my control. That PHP script executes `git ls-remote -t` on the webserver, which gets a list of tags. Some strings parsing is then done and the Extensible Choice plugin is fed with a list of tags that is presented as a dropdown list in Jenkins. More details in this StackOverflow question: http://stackoverflow.com/questions/28543482/jenkins-git-parameter-plugin-cannot-fetch-tags 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-26616) Multi-config project concurrent build race
rsandell commented on JENKINS-26616 Multi-config project concurrent build race Of the gerrit trigger plugin. 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-26616) Multi-config project concurrent build race
Daniel Beck commented on JENKINS-26616 Multi-config project concurrent build race In fact, it's probably a core issue and unrelated to matrix projects, see linked JENKINS-26739. 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-16627) Fail to parse jmeter report
Manuel Carrasco resolved JENKINS-16627 as Fixed Fail to parse jmeter report Change By: Manuel Carrasco (18/Feb/15 10:38 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] [core] (JENKINS-27005) Service/JavaRuntime crashes on Windows
Heiko Tappe created JENKINS-27005 Service/JavaRuntime crashes on Windows Issue Type: Bug Assignee: Unassigned Attachments: hs_err_pid6012.log, [thread 4520 also had an error].txt Components: core Created: 18/Feb/15 10:51 AM Description: The jenkins service every now and then stops without obvious reason. Yesterday with a file "hs_err_pid6012.log" being created. Today it was the file "thread 4520 also had an error". See attachments. Environment: Windows 7 Professional SP1, Jenkins 1.599 Project: Jenkins Labels: windows jenkins Priority: Major Reporter: Heiko Tappe 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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
James Nord commented on JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() The code is susceptable to the clock changing when is about to send the first Ping. Using System.nanoTime will have performance implications for Windows systems - so I am going to attempt a more conservative fix first. 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-26616) Multi-config project concurrent build race
Dmitry Maslakov commented on JENKINS-26616 Multi-config project concurrent build race @rsandell, beta release of what product? 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-16627) Fail to parse jmeter report
SCM/JIRA link daemon commented on JENKINS-16627 Fail to parse jmeter report Code changed in jenkins User: Manuel Carrasco Moñino Path: .gitignore src/main/java/hudson/plugins/performance/AbstractParser.java src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterCsvParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/JUnitParser.java src/main/java/hudson/plugins/performance/JmeterSummarizerParser.java src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/WrkSummarizerParser.java src/test/java/hudson/plugins/performance/JMeterParserTest.java src/test/java/hudson/plugins/performance/JUnitParserTest.java src/test/java/hudson/plugins/performance/WrkSummarizerParserTest.java src/test/resources/JENKINS-16627_CSV_instead_of_XML.jtl src/test/resources/TEST-JUnitResults.xml.serialized src/test/resources/emptyfile.jtl src/test/resources/jUnitIssue5571.xml.serialized src/test/resources/whitespace-followed-by-xml.jtl http://jenkins-ci.org/commit/performance-plugin/d5d4c8797a0c13a051d010b380a3d6346c1db3d2 Log: Merge pull request #45 from guusdk/master FIXED JENKINS-26988 FIXED JENKINS-16627FIXED JENKINS-15736 Compare: https://github.com/jenkinsci/performance-plugin/compare/3e0f37953c07...d5d4c8797a0c 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-plugin] (JENKINS-27004) email-ext escapes html to xml
Marco Spinola Durante
created JENKINS-27004
email-ext escapes html to xml
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
18/Feb/15 9:44 AM
Description:
I include results of my jobs via:
${FILE,path="my.html"}
if the text file contains the apostrophes ', the mail shows apos; instead.
The source of the mail contains amp;apos;
I think there is some sort of XML/HTML escaping going on.
Environment:
Jenkins ver. 1.598
REDHAT 6.5 64Bit
Project:
Jenkins
Priority:
Minor
Reporter:
Marco Spinola Durante
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-26616) Multi-config project concurrent build race
rsandell commented on JENKINS-26616 Multi-config project concurrent build race This sounds like having the same root cause as JENKINS-23152, have you tried the new beta release? 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-15736) Viewing performance report changes jvm locale
SCM/JIRA link daemon commented on JENKINS-15736 Viewing performance report changes jvm locale Code changed in jenkins User: Guus der Kinderen Path: src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/PerformanceReport.java http://jenkins-ci.org/commit/performance-plugin/2e7c03f4415b640919104397004808726a628d62 Log: Fixes a problem with rounding numbers that was introduced by JENKINS-15736. 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-26988) Responding time graphs should not ignore samples with errors
SCM/JIRA link daemon resolved JENKINS-26988 as Fixed Responding time graphs should not ignore samples with errors Change By: SCM/JIRA link daemon (18/Feb/15 8:55 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] [performance-plugin] (JENKINS-15736) Viewing performance report changes jvm locale
SCM/JIRA link daemon commented on JENKINS-15736 Viewing performance report changes jvm locale Code changed in jenkins User: Manuel Carrasco Moñino Path: .gitignore src/main/java/hudson/plugins/performance/AbstractParser.java src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterCsvParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/JUnitParser.java src/main/java/hudson/plugins/performance/JmeterSummarizerParser.java src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/WrkSummarizerParser.java src/test/java/hudson/plugins/performance/JMeterParserTest.java src/test/java/hudson/plugins/performance/JUnitParserTest.java src/test/java/hudson/plugins/performance/WrkSummarizerParserTest.java src/test/resources/JENKINS-16627_CSV_instead_of_XML.jtl src/test/resources/TEST-JUnitResults.xml.serialized src/test/resources/emptyfile.jtl src/test/resources/jUnitIssue5571.xml.serialized src/test/resources/whitespace-followed-by-xml.jtl http://jenkins-ci.org/commit/performance-plugin/d5d4c8797a0c13a051d010b380a3d6346c1db3d2 Log: Merge pull request #45 from guusdk/master FIXED JENKINS-26988 FIXED JENKINS-16627FIXED JENKINS-15736 Compare: https://github.com/jenkinsci/performance-plugin/compare/3e0f37953c07...d5d4c8797a0c 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-26988) Responding time graphs should not ignore samples with errors
SCM/JIRA link daemon commented on JENKINS-26988 Responding time graphs should not ignore samples with errors Code changed in jenkins User: Guus der Kinderen Path: src/main/java/hudson/plugins/performance/PerformanceProjectAction.java http://jenkins-ci.org/commit/performance-plugin/d249f7c02a8d5e2103788d6217d2e1b9e8540a37 Log: FIXED JENKINS-26988 Graphs should include errors. Generated graphs currently ignore sample-sets that contain even one error. This gives a skewed view of the data, and should not occur. Please refer to https://issues.jenkins-ci.org/browse/JENKINS-26988 for details. 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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
James Nord edited a comment on JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() The code is susceptable to the clock changing when it is about to send the first Ping. Using System.nanoTime will have performance implications for Windows systems - so I am going to attempt a more conservative fix first. 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-26988) Responding time graphs should not ignore samples with errors
SCM/JIRA link daemon commented on JENKINS-26988 Responding time graphs should not ignore samples with errors Code changed in jenkins User: Manuel Carrasco Moñino Path: .gitignore src/main/java/hudson/plugins/performance/AbstractParser.java src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterCsvParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/JUnitParser.java src/main/java/hudson/plugins/performance/JmeterSummarizerParser.java src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/WrkSummarizerParser.java src/test/java/hudson/plugins/performance/JMeterParserTest.java src/test/java/hudson/plugins/performance/JUnitParserTest.java src/test/java/hudson/plugins/performance/WrkSummarizerParserTest.java src/test/resources/JENKINS-16627_CSV_instead_of_XML.jtl src/test/resources/TEST-JUnitResults.xml.serialized src/test/resources/emptyfile.jtl src/test/resources/jUnitIssue5571.xml.serialized src/test/resources/whitespace-followed-by-xml.jtl http://jenkins-ci.org/commit/performance-plugin/d5d4c8797a0c13a051d010b380a3d6346c1db3d2 Log: Merge pull request #45 from guusdk/master FIXED JENKINS-26988 FIXED JENKINS-16627FIXED JENKINS-15736 Compare: https://github.com/jenkinsci/performance-plugin/compare/3e0f37953c07...d5d4c8797a0c 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-26988) Responding time graphs should not ignore samples with errors
SCM/JIRA link daemon commented on JENKINS-26988 Responding time graphs should not ignore samples with errors Code changed in jenkins User: Guus der Kinderen Path: src/main/java/hudson/plugins/performance/AbstractParser.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterCsvParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/JUnitParser.java src/main/java/hudson/plugins/performance/JmeterSummarizerParser.java src/main/java/hudson/plugins/performance/WrkSummarizerParser.java src/test/java/hudson/plugins/performance/JMeterParserTest.java src/test/resources/JENKINS-16627_CSV_instead_of_XML.jtl src/test/resources/emptyfile.jtl src/test/resources/whitespace-followed-by-xml.jtl http://jenkins-ci.org/commit/performance-plugin/7e1559fc45ed4bea5cadbfd9eae7aaa5b30e0f5a Log: FIXED JENKINS-26988 At some point in the release history, JMeter switched from XML to CSV as a default for data persistency. The performance plugin should determine if a JTL file is either XML or CSV, and parse the data accordingly. See https://issues.jenkins-ci.org/browse/JENKINS-16627 for more details. 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-16627) Fail to parse jmeter report
SCM/JIRA link daemon commented on JENKINS-16627 Fail to parse jmeter report Code changed in jenkins User: Guus der Kinderen Path: src/main/java/hudson/plugins/performance/AbstractParser.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterCsvParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/JUnitParser.java src/main/java/hudson/plugins/performance/JmeterSummarizerParser.java src/main/java/hudson/plugins/performance/WrkSummarizerParser.java src/test/java/hudson/plugins/performance/JMeterParserTest.java src/test/resources/JENKINS-16627_CSV_instead_of_XML.jtl src/test/resources/emptyfile.jtl src/test/resources/whitespace-followed-by-xml.jtl http://jenkins-ci.org/commit/performance-plugin/7e1559fc45ed4bea5cadbfd9eae7aaa5b30e0f5a Log: FIXED JENKINS-26988 At some point in the release history, JMeter switched from XML to CSV as a default for data persistency. The performance plugin should determine if a JTL file is either XML or CSV, and parse the data accordingly. See https://issues.jenkins-ci.org/browse/JENKINS-16627 for more details. 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-plugin] (JENKINS-27004) email-ext escapes html to xml
Marco Spinola Durante updated JENKINS-27004 email-ext escapes html to xml Change By: Marco Spinola Durante (18/Feb/15 9:45 AM) Environment: Jenkinsver.1.598 Email-Ext2.39 REDHAT6.564Bit 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-26616) Multi-config project concurrent build race
Dmitry Maslakov commented on JENKINS-26616 Multi-config project concurrent build race I do not use gerrit. More likely, stack trace shows, this problem in matrix plug-in. 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-26616) Multi-config project concurrent build race
Daniel Beck commented on JENKINS-26616 Multi-config project concurrent build race Since the build number isn't duplicated, but skipped, this seems to be a different failure mode than Gerrit Trigger. 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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
James Nord assigned JENKINS-21251 to James Nord Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Change By: James Nord (18/Feb/15 11:22 AM) Assignee: JamesNord 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-27006) Broken URL in ContextMenu after adding Actions
Markus Schwabeneder created JENKINS-27006 Broken URL in ContextMenu after adding Actions Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Feb/15 11:36 AM Description: In the function jenkins.model.ModelObjectWithContextMenu.ContextMenu.add(Action a) StaplerRequest .findAncestor(ModelObject.class).getUrl() is called, which as far as i see always returns a URL starting with "/". With this URL as argument Function.getActionUrl is called, which in case of a relative Url Name of Action a adds a "/" again, resulting in "//" so the URL in the ContextMenu does not work. Environment: Jenkins 1.598, Windows 7, Chrome Project: Jenkins Priority: Minor Reporter: Markus Schwabeneder 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-25146) When the anonymous user has no access rights, userContent is inaccessible
Christian Galsterer updated JENKINS-25146 When the anonymous user has no access rights, userContent is inaccessible Change By: Christian Galsterer (18/Feb/15 5:49 PM) Description: Hello,Ivetriedthefollowing:*IhaveaJenkinsinstallationonDebianstablewiththemostrecentJenkinsrelease(viatheofficialJenkinsrepository)*Ihaveenabledsecurity*Theanonymoususerdoesnothaveanyrights(notevenRead),becauseIdontwanttoshowwhichnodesareactiveorwhichusersareconfigured.*Nobodyisloggedin*Ibrowsetohttp://localhost:8080/userContent/Achievedresult:Iseealoginprompt.Expectedresult:Iveseentickethttps://issues.jenkins-ci.org/browse/JENKINS-23259,whichhandlesexactlytheoppositesituation.AccordingtotheWikipageathttps://wiki.jenkins-ci.org/display/JENKINS/User+ContenttheuserContentfoldershouldbeaccessible.quoteNotethatthesefilesarenotsubjecttoanyaccesscontrols./quoteVersionsaffected:1.565.3,1.580,1.584 ,1.588 IstheWikipageincompleteandshoulditmentionthatwhentheanonymoushasnorightsatall,userContentisprotected,orshouldtheuserContentfolderalwaysbeunprotected? 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] [jenkins-tracker] (JENKINS-27015) Java Web Start fails to launch
Kent East created JENKINS-27015 Java Web Start fails to launch Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 18/Feb/15 5:51 PM Description: Wanted to try out Jenkins by using the web start link on the Meet Jenkins page. It downloads successfully, but then an error message appears that says the Java Application is blocked. Reason: Your security settings have blocked an application from running due to missing a "Permissions" manifest attribute in the main ja. Environment: Java 1.8_31 Project: Jenkins Labels: jenkins webstart Priority: Minor Reporter: Kent East 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] [github-oauth-plugin] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories
Pedro Algarvio commented on JENKINS-23324 GitHub OAuth 0.17 requires private access to all repositories Why is the required scope so broad? I'm just using this plugin to authenticate users, just that, so I really only need to ask my users the `user:email` scope... 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-27016) Jenkins runs as LOCAL SYSTEM privilege on Windows
Michael Cramer created JENKINS-27016 Jenkins runs as LOCAL SYSTEM privilege on Windows Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Feb/15 5:58 PM Description: By default, the Jenkins service wrapper is configured to launch as the local system account on Windows. This is an elevated privilege (i.e. root) account. The installer should prompt users to choose an account (similar to how Microsoft SQL Server does) under which the Jenkins service and associated java process should run. This is a highly insecure default configuration which encourages bad practice and implementation by less experienced users. Environment: Jenkins 1.599, Windows Server Project: Jenkins Priority: Major Reporter: Michael Cramer 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-name-setter-plugin] (JENKINS-26574) Allow distinct template for matrix head build
Jesse Glick assigned JENKINS-26574 to Tracy Kennedy Allow distinct template for matrix head build Change By: Jesse Glick (18/Feb/15 5:59 PM) Assignee: KohsukeKawaguchi TracyKennedy 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] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Caleb Mayeux commented on JENKINS-26999 Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) @Oleg Thanks for the quick response! Wow, I feel pretty stupid. So turns out, it always worked previously because the first time it went to poll, it'd find no prior builds and thus start a build. Subsequently, the polling process would just reuse the ticket acquired from the login of the previous build, never actually relying on the credentials in the job. When I updated the perforce plugin, I also rebooted the Jenkins instance, for the first time in a very long time, which apparently cleared all the cached tickets, breaking polling across all my jobs. When I reverted the plugin and retried with the old plugin, first I had manually hit some builds, which refreshed the stored tickets, giving the illusion of it working with the old version but not the new version. Sorry for the misdirection! And yep, you were right that my polling procedures weren't completely correct. Can close as invalid. 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] [extended-choice-parameter-plugin] (JENKINS-27013) Add support for the Jenkins Credentials plugin
James Graf assigned JENKINS-27013 to vimil Add support for the Jenkins Credentials plugin Change By: James Graf (18/Feb/15 5:09 PM) Assignee: JamesGraf vimil 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] [extended-choice-parameter-plugin] (JENKINS-27013) Add support for the Jenkins Credentials plugin
James Graf started work on JENKINS-27013 Add support for the Jenkins Credentials plugin Change By: James Graf (18/Feb/15 5:09 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] [core] (JENKINS-27016) Jenkins runs as LOCAL SYSTEM privilege on Windows
Michael Cramer commented on JENKINS-27016 Jenkins runs as LOCAL SYSTEM privilege on Windows This also allows all processes and scripts that Jenkins runs to elevate under the local system (root) privilege. This may be undesirable in situations where developers may have unintended elevated system privileges. 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] [extended-choice-parameter-plugin] (JENKINS-27011) Exceptions swallowed in ExtendedChoiceParameterDefinition.java
James Graf assigned JENKINS-27011 to vimil Exceptions swallowed in ExtendedChoiceParameterDefinition.java Change By: James Graf (18/Feb/15 5:08 PM) Assignee: JamesGraf vimil 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] [extended-choice-parameter-plugin] (JENKINS-27013) Add support for the Jenkins Credentials plugin
James Graf commented on JENKINS-27013 Add support for the Jenkins Credentials plugin A fix is ready for review: https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/14 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] [slave-setup-plugin] (JENKINS-16418) Cannot start Windows Server 2012 slave.
Dane Kantner commented on JENKINS-16418 Cannot start Windows Server 2012 slave. I tried the above it didn't seem to resolve (the class ID exists in both the 32 bit WOW6432 location as well as the 64 bit location, changed both; additionally strangely in Windows 7 SP 1 64 bit, I have not been able to restore the TrustedInstaller as the owner of the registry keys. I did select the local computer as the object, and even when I do a "find" of all accounts I see all the built-in accounts with the exception of TrustedInstaller. I tried "NT Service\TrustedInstaller" in quotes and every variation as well. If I try to do the same ownership change on a file object (as opposed to registry), it works no problem. 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] [extended-choice-parameter-plugin] (JENKINS-27011) Exceptions swallowed in ExtendedChoiceParameterDefinition.java
James Graf commented on JENKINS-27011 Exceptions swallowed in ExtendedChoiceParameterDefinition.java A fix is ready for review: https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/12 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] [extended-choice-parameter-plugin] (JENKINS-27012) Add @Grab grape support to facilitate dependency injection
James Graf commented on JENKINS-27012 Add @Grab grape support to facilitate dependency injection A fix is ready for review: https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/13 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] [extended-choice-parameter-plugin] (JENKINS-27012) Add @Grab grape support to facilitate dependency injection
James Graf assigned JENKINS-27012 to vimil Add @Grab grape support to facilitate dependency injection Change By: James Graf (18/Feb/15 5:08 PM) Assignee: JamesGraf vimil 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-name-setter-plugin] (JENKINS-26574) Allow distinct template for matrix head build
Jesse Glick started work on JENKINS-26574 Allow distinct template for matrix head build Change By: Jesse Glick (18/Feb/15 5:59 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] [core] (JENKINS-27017) Jenkins ships with known vulnerable Java 7 Update 25
Michael Cramer created JENKINS-27017 Jenkins ships with known vulnerable Java 7 Update 25 Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Feb/15 5:59 PM Description: Jenkins ships with a known insecure version of Java. When combined with the previously filed bug of running as system access, it's theoretically possible that vulnerabilities in the shipping version of Java to elevate privilege on the machine where Jenkins operates. Environment: Jenkins 1.599, Windows Server Project: Jenkins Priority: Major Reporter: Michael Cramer 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] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Caleb Mayeux resolved JENKINS-26999 as Not A Defect Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) User configuration error, not a defect. Change By: Caleb Mayeux (18/Feb/15 6:21 PM) Status: InProgress Resolved Resolution: NotADefect 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] [beaker-builder-plugin] (JENKINS-27003) NullPointerException XMLEscapingVariableResolver.java:15
SCM/JIRA link daemon commented on JENKINS-27003 NullPointerException XMLEscapingVariableResolver.java:15 Code changed in jenkins User: Dan Callaghan Path: src/main/java/org/jenkinsci/plugins/beakerbuilder/XMLEscapingVariableResolver.java src/test/java/org/jenkinsci/plugins/beakerbuilder/StringJobSourceTest.java http://jenkins-ci.org/commit/beaker-builder-plugin/9cfac716c2d72b15f392c53e150de51a6957e084 Log: FIXED JENKINS-27003 handle null for unresolved variables 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] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
Juan Sotuyo commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Working for me 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] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Caleb Mayeux closed JENKINS-26999 as Not A Defect Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) Change By: Caleb Mayeux (18/Feb/15 6:21 PM) Status: Resolved Closed 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] [maven-plugin] (JENKINS-25406) MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED
Robert Hook commented on JENKINS-25406 MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED Still broken as at 1.599 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] [beaker-builder-plugin] (JENKINS-27003) NullPointerException XMLEscapingVariableResolver.java:15
SCM/JIRA link daemon resolved JENKINS-27003 as Fixed NullPointerException XMLEscapingVariableResolver.java:15 Change By: SCM/JIRA link daemon (18/Feb/15 7:00 PM) 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] [postbuild-task-plugin] (JENKINS-12303) Post build task - 'Add another task' does not work
b2jrock commented on JENKINS-12303 Post build task - Add another task does not work Same here. I've found that you can work around by deleting all the tasks and adding them all at the same time rather than adding on an existing config. 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] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
Simon Schlachter commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction OK, changes are included in version 1.21 - can you please verify? 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-26887) git polling/web hooks will not start concurrent builds
Jeremiah Norris commented on JENKINS-26887 git polling/web hooks will not start concurrent builds Perhaps you are right I don't think that we need to have a separate workspace for polling to resolve this issue. I've updated this issue and converted it to a bug. 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-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Jacob Weber commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy I'm seeing this same error, on a remote node with a SVN 1.8 client, SVN plugin version 2.5, on a new project. Changing the working copy format to 1.8 in Jenkins settings fixes it. Is the plugin using something other than the native SVN client on the remote note, when doing the initial checkout? It seems like it's not creating valid working copies when you use the 1.7 format. 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-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Jacob Weber edited a comment on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy I'm seeing this same error, on a remote node with a SVN 1.8 client, SVN plugin version 2.5, on a new project. Changing the working copy format to 1.8 in Jenkins settings fixes it. Is the plugin using something other than the native SVN client on the remote node, when doing the initial checkout? It seems like it's not creating valid working copies when you use the 1.7 format. 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-approve-plugin] (JENKINS-27019) unstable builds must not approve a commit
Dominik Bartholdi created JENKINS-27019 unstable builds must not approve a commit Issue Type: Bug Assignee: Björn Hurling Components: bitbucket-approve-plugin Created: 18/Feb/15 9:26 PM Description: The bitbucket-approve-plugin approves a commit even though the build ended as unstable. I think this is wrong, e.g. if test cases fail, usually the build does not fail, but is marked as unstable only. Project: Jenkins Priority: Major Reporter: Dominik Bartholdi 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-approve-plugin] (JENKINS-27020) integrate credentials plugin
Dominik Bartholdi created JENKINS-27020 integrate credentials plugin Issue Type: Bug Assignee: Björn Hurling Components: bitbucket-approve-plugin Created: 18/Feb/15 9:29 PM Description: The bitbucket-approve-plugin hold username/password in its own configuration. This should be removed and the credentials plugin 1 should be integrated. This way credentials are stored at one single location and can also be shared between plugins. 1 https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin Project: Jenkins Priority: Minor Reporter: Dominik Bartholdi 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-approve-plugin] (JENKINS-27020) integrate credentials plugin
Dominik Bartholdi updated JENKINS-27020 integrate credentials plugin Change By: Dominik Bartholdi (18/Feb/15 9:30 PM) Issue Type: Bug Improvement Priority: Minor Major 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-26887) git polling/web hooks will not start concurrent builds
Jeremiah Norris updated JENKINS-26887 git polling/web hooks will not start concurrent builds Change By: Jeremiah Norris (18/Feb/15 8:33 PM) Summary: gitpolling/webhooks needtooccurinaseparatepollingworkspace willnotstartconcurrentbuilds Description: Themainissue I mtryingtosolveisI needawebhooktobeabletokickoffconcurrentbuilds.Whereasrightnowifacommitcomesintoajobthatisalreadybuildingthatcommitwilljustbeignoredandwillneverbebuilt .Essentiallythewaythecurrentgitactivitiesworkarealittleunintuitivesincetheydepend evenifconcurrentbuildsisturned on alocalgitrepositorytobesittingintheworkspacefromapreviousbuild . InsteadwhenanewjobiscreatedthathasagitrepositorylistedinSCMalocalrepositoryshouldbeimmediatelypulled Inaddition to beusedforpollingand webhooks thatiscompletelyindependantofthe notworkingwhena job workspace isalreadyrunning . Thereareprobablymoreelegantorlightweightsolutionstothisissueto Pollingwillnoteven be explored.Iwanttoseehowmuchinterestthereisinthissubjectand attempted if there ajob is anyonemoreexperiencedwhowantstocontributethatwouldbegreat currentlyrunning.Whichmakessinceformostbuilds ,but myteamisindireneedofthissoIwilllookintocodingitifnooneelsehasvalue not for asolution buildswithconcurrentbuildsenabled . 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-27018) Provide either 'branch' or 'tag' in git step
Yuriy Kryshchuk created JENKINS-27018 Provide either branch or tag in git step Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 18/Feb/15 8:10 PM Description: Hi, the 'git' step is one of the most important steps implemented for workflow. However, there are many cases where I need to checkout the particular git tag, instead of the branch. currently I have to do something like: checkout scm: [$class: 'GitSCM', userRemoteConfigs: [[url: 'g...@github.com:MYCOMPANY/cd-workflow.git']], branches: [[name: 'refs/tags/workflow-1.0']]], changelog: false, poll: false the main reason is I want to keep versioned workflow scripts on my repo and load a specific version of it. But I have also several other use cases when I need a tag from the git repository. The notation above is actually too long and overcomplicated. Instead, I would expect to use the code like: git url: 'g...@github.com:MYCOMPANY/cd-workflow.git', tag: 'workflow-1.0', changelog: false, poll: false which is much shorter and similar to a typical git usage. By other words, the step might support either 'branch' or 'tag' parameter. In some rare cases it would be nice also to have possibility to checkout a particular commit. Would it be possible to add such a feature? Project: Jenkins Priority: Minor Reporter: Yuriy Kryshchuk 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] [cobertura-plugin] (JENKINS-23183) Add precision option for the Stability auto update/Health auto update options
Fadel Wanssa commented on JENKINS-23183 Add precision option for the Stability auto update/Health auto update options Maybe an option to set build unstable if coverage decreases by a certain percentage compared to previous build (ex: if code coverage drops by 2% from previous build, set build to unstable). 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] [cobertura-plugin] (JENKINS-23183) Add precision option for the Stability auto update/Health auto update options
Fadel Wanssa edited a comment on JENKINS-23183 Add precision option for the Stability auto update/Health auto update options Maybe an option to set build unstable if coverage decreases by a certain percentage or value compared to previous build (ex: if code coverage drops by 2% from previous build, set build to unstable). 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-26887) git polling/web hooks will not start concurrent builds
Jeremiah Norris updated JENKINS-26887 git polling/web hooks will not start concurrent builds Change By: Jeremiah Norris (18/Feb/15 8:34 PM) Issue Type: Improvement Bug 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] [jacoco-plugin] (JENKINS-19915) Support specifying one or more JARs in the classPattern
Josh Landin commented on JENKINS-19915 Support specifying one or more JARs in the classPattern This feature would be particularly useful where an upstream job did the actual build and passed the final artifact(s) to a job performing integration (or functional) tests. This is quite common and the workaround mentioned above is rather messy. I'll look into getting a patch together for this. 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] [durable-task-plugin] (JENKINS-27014) Job name with spaces breaks workflow bat step
Jesse Glick resolved JENKINS-27014 as Duplicate Job name with spaces breaks workflow bat step Change By: Jesse Glick (18/Feb/15 10:13 PM) 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] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Rob Winch commented on JENKINS-5303 Upgrade Acegi Security to the latest Spring Security release Acegi Security's last commit was over 7 years ago. There have been many CVE's reported and fixed within the maintained versions of Spring Security. For this reason I believe this issue should be considered a high priority. Note that it appears that the Hudson team has already updated to Spring Security 3.2.x. 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-26582) Unexpected Executor Death - build already existed - 1.597
Mark Sinclair commented on JENKINS-26582 Unexpected Executor Death - build already existed - 1.597 There were many jobs in the queue and some running when the reload happened. Maybe it is safer quietDown, clear the queue, then reload? 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-27018) Provide either 'branch' or 'tag' in git step
Jesse Glick resolved JENKINS-27018 as Wont Fix Provide either branch or tag in git step The git step is intended to just cover the most common cases with a highly simplified syntax. Building a tag is probably out of scope. Use the checkout step with GitSCM for all uses cases it does not cover. Change By: Jesse Glick (18/Feb/15 10:11 PM) Status: Open Resolved Resolution: WontFix 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-26582) Unexpected Executor Death - build already existed - 1.597
Jesse Glick commented on JENKINS-26582 Unexpected Executor Death - build already existed - 1.597 No, nextBuildNumber is incremented the moment a new build is created, before it even really starts (right after it leaves the queue). Reloading from disk is a plausible explanation; perhaps there are two copies of the Job sitting around temporarily, each with its own version of the field. 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-pipeline-plugin] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Ladislav Toldy commented on JENKINS-21422 Jenkins crashing due to out of memory when rebuilding jobs Yes it occurs also in 1.580.3 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-27006) Broken URL in ContextMenu after adding Actions
Daniel Beck resolved JENKINS-27006 as Not A Defect Broken URL in ContextMenu after adding Actions See e.g. http://javadoc.jenkins-ci.org/hudson/model/Item.html#getUrl%28%29 for how Jenkins defines item URLs. These are consistent (no leading slash), and distinct from Ancestor.getUrl(). If you can find a class in Jenkins that behaves differently, please reopen this issue and provide more specific information. Change By: Daniel Beck (19/Feb/15 7:26 AM) Status: Open Resolved Resolution: NotADefect 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] [copy-to-slave-plugin] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Daniel Beck commented on JENKINS-25346 Copy files back to master node doesnt copy to workspace https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L498 @deprecated as of 1.319 This will not guarantee to point to the master node anyway. I'd try Jenkins.getInstance().getWorkspaceFor(project) as that'll return a workspace on the master node. Not sure whether it's correct in all cases in the context of this plugin as I don't use 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] [copy-to-slave-plugin] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Vivekanand SV commented on JENKINS-25346 Copy files back to master node doesnt copy to workspace @Daniel, I have done the following code based on your comment ... - DIFF START LINE 57 projectWorkspaceOnMaster = new FilePath(new File(freeStyleProject.getRootDir(), "workspace")); +projectWorkspaceOnMaster = freeStyleProject.getWorkspace(); LINE 61 projectWorkspaceOnMaster = new FilePath(new File(project.getRootDir(), "workspace")); +projectWorkspaceOnMaster = project.getWorkspace(); - DIFF END Can I know your review comments for this please ? 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] [copy-to-slave-plugin] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Vivekanand SV edited a comment on JENKINS-25346 Copy files back to master node doesnt copy to workspace @Daniel, I have done the following code based on your comment ... - DIFF START LINE 57 DELprojectWorkspaceOnMaster = new FilePath(new File(freeStyleProject.getRootDir(), "workspace")); ADDprojectWorkspaceOnMaster = freeStyleProject.getWorkspace(); LINE 61 DELprojectWorkspaceOnMaster = new FilePath(new File(project.getRootDir(), "workspace")); ADDprojectWorkspaceOnMaster = project.getWorkspace(); - DIFF END Can I know your review comments for this please ? 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] [extended-choice-parameter-plugin] (JENKINS-27013) Add support for the Jenkins Credentials plugin
James Graf created JENKINS-27013 Add support for the Jenkins Credentials plugin Issue Type: New Feature Assignee: James Graf Components: extended-choice-parameter-plugin Created: 18/Feb/15 4:14 PM Description: Add support for the Jenkins Credentials plugin (https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin) to leverage its ability to securely store and access credentials that are needed when accessing secured APIs. Project: Jenkins Priority: Minor Reporter: James Graf 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] [durable-task-plugin] (JENKINS-27014) Job name with spaces breaks workflow bat step
Andy Neebel created JENKINS-27014 Job name with spaces breaks workflow bat step Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 18/Feb/15 4:21 PM Description: If the job name has spaces in it, then it appears that the generated files for the bat step in the workflow plugin do not correctly escape the file paths and as a result the build ends up hanging. I chased around the code some, and it appears that this is coming from WindowsBatchScript in the durable task plugin. Also, when the build does hang, it does not seem to be possible to terminate it, I ended up having to delete the job folder manually while Jenkins was not running in order to get rid of the active build. The workaround is to not have spaces in your job names, but our current naming patterns tend to have spaces and since everything else appears to handle them correctly, it seems like this plugin should as well. Environment: Jenkins 1.580.1, durable-task-plugin 1.2 Project: Jenkins Labels: windows workflow Priority: Minor Reporter: Andy Neebel 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] [repository-connector-plugin] (JENKINS-27007) Repository Connector configuration using in slave node
John Holmes created JENKINS-27007 Repository Connector configuration using in slave node Issue Type: Improvement Assignee: Unassigned Components: repository-connector-plugin Created: 18/Feb/15 11:56 AM Description: It would be nice if Repository Connector configuration can be delivered from master jenkins to slave nodes. It is possible to get this improvement? Project: Jenkins Priority: Minor Reporter: John Holmes 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-27006) Broken URL in ContextMenu after adding Actions
Markus Schwabeneder commented on JENKINS-27006 Broken URL in ContextMenu after adding Actions The problem is exactly in the part of code you highlighted. the itUrl is a String of the form "/foo", in line 1501 (which is reached if a.getUrlName() returns a relative Url (without leading /)) Stapler.getCurrentRequest().getContextPath()+'/'+itUrl is called which results in a String of form "contextPath//foo". I dont see any reason why not changing line 1501 into: "return joinPath(Stapler.getCurrentRequest().getContextPath(),itUrl,urlName);" then the handling of slashes is up to the joinPath function, which i think is a safer approach 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-18935) Make Subversion plugin support Subversion 1.8
Daniel Beck commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ? No. It just means there's no longer a fork of SVNKit by the Jenkins Project team in use. Subversion plugin does not use the natively installed Subversion client (it doesn't even require one), as it bundles the SVNKit library. I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in. It is. Jenkins works without Subversion Plugin. You can disable it and lose its functionality. It's just bundled and enabled by default for historical reasons (to not break installations upgrading from really ancient versions from before Subversion plugin was detached from core Jenkins it started life as a part of core Jenkins). I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default. It's the same plugin, just a newer version of it. Plugins can be updated independently from core versions. The versions of plugins bundled with Jenkins are updated occasionally, but as Subversion 2.0 contained a major, possibly breaking, change to authentication (integration with Credentials plugin) it hasn't been chosen for bundling so far. I didn't want to leave your comment unanswered, but please direct any follow-up questions/discussions that aren't directly related to this issue to #jenkins on Freenode, or the jenkinsci-users mailing list. 200 people get an email notification every time you (or anyone) add or edit a comment to this issue. 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-27006) Broken URL in ContextMenu after adding Actions
Daniel Beck commented on JENKINS-27006 Broken URL in ContextMenu after adding Actions Right, now it makes a bit more sense. But itUrl (or generally Item.getUrl()) should never start with a slash, those are defined as relative URLs starting from the context root, e.g. "job/foo". 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] [metrics-plugin] (JENKINS-27005) Service/JavaRuntime crashes on Windows
Daniel Beck updated JENKINS-27005 Service/JavaRuntime crashes on Windows Change By: Daniel Beck (18/Feb/15 12:36 PM) Labels: jenkinswindows Component/s: metrics-plugin Component/s: core 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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
SCM/JIRA link daemon resolved JENKINS-21251 as Fixed Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Change By: SCM/JIRA link daemon (18/Feb/15 1:20 PM) 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] [core] (JENKINS-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
SCM/JIRA link daemon commented on JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Code changed in jenkins User: James Nord Path: src/main/java/hudson/remoting/AtmostOneThreadExecutor.java src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/PingThread.java src/main/java/hudson/remoting/Request.java src/main/java/hudson/remoting/SingleLaneExecutorService.java src/main/java/hudson/remoting/SynchronousExecutorService.java http://jenkins-ci.org/commit/remoting/29ec965650bba57145df14f0fee73acbd8ce5248 Log: FIXED JENKINS-21251 Initial calculation of wait time was susseptable to clock drift. The calculation on how long to wait in various places on the code was suseptable to the clock changing as multiple calls where made to System.currentTimeMillis() for the initial calculation. Changed this so that for the initial calculation only one call will be made to System.currentTimeMillis(). WHilst this does not guarantee that the actuall amount of time will have been waited for (and subsequent calculations are suseptable) at least on the hotstop VM Object.wait() will not have spurious wake-ups. Therefore the overhead of moving to System.nanoTime() is currently not considered to be worth the performance overhead. Compare: https://github.com/jenkinsci/remoting/compare/ff1a0669d363^...29ec965650bb 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] [release-plugin] (JENKINS-27009) Default versioning mode maven-release-plugin issue
alexis olior updated JENKINS-27009 Default versioning mode maven-release-plugin issue Change By: alexis olior (18/Feb/15 2:38 PM) Description: IencounteredanissuethatisobstructingmydevelopmentonJenkins.Afterinstallingthemaven-release-pluginonJenkinsIvetestedit.Thefactisthatforaprojectwithoutanydependencies,thepluginworkswell.ButsinceIhavesomeprojectdependenciesitdoesnt.IndeedafterselectingtheDefaultversioningmodeasSpecifyversion(s),whenIsave the he configurationandtrytoperformmavenreleasebuild,theDefaultversioningmodeparameterkeepsitsstate,whateverIchangeittoandsimplygoesbacktononestate.Thereisnowaytomodifyit!!!Mymaingoalhereistospecifymyreleaseversionofadependencyandthis iswhattheDefaultversioningmodeisdoneforbecausemaven-release-plugincantworkwithSNAPSHOTdependencies!!Doesexistanytipstogetaroundthisproblem?anotherwaytodo?orafixofthemaven-release-plugin?ThanksforthehelpJenkins1.596maven-release-plugin0.14 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-27010) javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.multiplescms.MultiSCM from {value:4}
R. Tyler Croy
moved JENKINS-27010
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.multiplescms.MultiSCM from {value:4}
Change By:
R. Tyler Croy
(18/Feb/15 2:46 PM)
Project:
Infrastructure
Jenkins
Key:
INFRA
JENKINS
-
245
27010
Workflow:
jira
JNJira
Component/s:
core
Component/s:
ci
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-client-plugin] (JENKINS-27008) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
Shyam Reddy created JENKINS-27008 hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 18/Feb/15 2:25 PM Description: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:914) at jenkins.model.Jenkins.init(Jenkins.java:813) at hudson.model.Hudson.init(Hudson.java:83) at hudson.model.Hudson.init(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 8 more Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(Unknown Source) at java.util.ArrayList.get(Unknown Source) at hudson.ExtensionList.get(ExtensionList.java:158) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1248) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more Project: Jenkins Priority: Blocker Reporter: Shyam Reddy 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-client-plugin] (JENKINS-27008) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
Shyam Reddy commented on JENKINS-27008 hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException Hi, Can any one help me on this i was stuck on this. 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-27006) Broken URL in ContextMenu after adding Actions
Markus Schwabeneder commented on JENKINS-27006 Broken URL in ContextMenu after adding Actions sorry i only took a look at http://stapler.kohsuke.org/apidocs/org/kohsuke/stapler/Ancestor.html#getUrl() as far as i understand, if my Plugin is deployed under myplugin, Ancestor.getUrl returns /myplugin, which is exactly the behavior i experience now and which causes problems when adding actions to the ContextMenu. But tbh i don't have a clue about Ancestor, only read the javadoc. 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] [release-plugin] (JENKINS-27009) Default versioning mode maven-release-plugin issue
alexis olior created JENKINS-27009 Default versioning mode maven-release-plugin issue Issue Type: Bug Assignee: Peter Hayes Attachments: Problème default versioning mode maven release plugin JENKINS 1.jpg Components: release-plugin Created: 18/Feb/15 2:33 PM Description: I encountered an issue that is obstructing my development on Jenkins. After installing the maven-release-plugin on Jenkins I've tested it. The fact is that for a project without any dependencies, the plugin works well. But since I have some project dependencies it doesn't. Indeed after selecting the "Default versioning mode" as "Specify version(s)" ,when I save the configuration and try to perform maven release build, the "Default versioning mode" parameter keeps its state, whatever I change it to and simply goes back to ''none'' state. There is no way to modify it !!! My main goal here is to specify my release version of a dependency and this is what the "Default versioning mode" is done for because maven-release-plugin can't work with SNAPSHOT dependencies !! Does exist any tips to get around this problem ? an other way to do ? or a fix of the maven-release-plugin ? Thanks for the help Jenkins 1.596 maven-release-plugin 0.14 Environment: Jenkins 1.596 maven release plugin 0.14 Project: Jenkins Labels: jenkins release-plugin default mode versioning Priority: Blocker Reporter: alexis olior 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-27006) Broken URL in ContextMenu after adding Actions
Markus Schwabeneder edited a comment on JENKINS-27006 Broken URL in ContextMenu after adding Actions sorry i only took a look at http://stapler.kohsuke.org/apidocs/org/kohsuke/stapler/Ancestor.html#getUrl() as far as i understand, if my Plugin is deployed under myplugin, Ancestor.getUrl returns /myplugin, which is exactly the behavior i experience now and which causes problems when adding actions to the ContextMenu. But tbh i don't have a clue about Ancestor, only read the javadoc, all i can say that in my Plugin i never use any absolute Urls but always relative ones without any slashes. 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] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: alexis oliot (18/Feb/15 2:51 PM) Summary: Defaultversioningmodemaven - release - pluginissue 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] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
alexis oliot assigned JENKINS-27009 to alexis oliot Default versioning mode maven release plugin issue Change By: alexis oliot (18/Feb/15 2:53 PM) Assignee: PeterHayes alexisoliot 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] [m2release-plugin] (JENKINS-15298) Default versioning mode is not getting picked while invoking the maven release build
alexis oliot assigned JENKINS-15298 to alexis oliot Default versioning mode is not getting picked while invoking the maven release build Change By: alexis oliot (18/Feb/15 2:52 PM) Assignee: JamesNord alexisoliot 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-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
Daniel Beck commented on JENKINS-26982 On MacOSX, pkg installation doesnt set newsyslog permissions properly Does your commit fix this issue? 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-26126) DSLD and/or GDSL
Jesse Glick updated JENKINS-26126 DSLD and/or GDSL Change By: Jesse Glick (18/Feb/15 12:41 PM) Summary: DSLD and/orGDSL Description: Forpeoplewritingflowsin IDEs Eclipse ,[DSLD|http://groovy.codehaus.org/DSL+Descriptors+for+Groovy-Eclipse]wouldbeausefulcomplementtothesnippetgenerator. IDEAusesGDSL.Itseemsthereisnoacknowledgedstandard;wouldapparentlyhavetobuildsupportforboth.(IcanfindnoDSLsystemforNetBeans.) Assignee: JesseGlick 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.
