[JIRA] [pollscm-plugin] (JENKINS-28710) Poll source from tfs to jenkins slave showing "no change"
Title: Message Title Vincent Latombe closed an issue as Not A Defect Please use the jenkins users mailing list in order to get support. Jenkins / JENKINS-28710 Poll source from tfs to jenkins slave showing "no change" Change By: Vincent Latombe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/f63e20a7f7c3f1d347d0357e61e2612ee40a983d Log: [FIX JENKINS-28506] restore support fo refs/heads/branch branch specifier Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/BranchSpec.java src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/CliGitSCMTriggerRemotePollTest.java src/test/java/hudson/plugins/git/JGitSCMTriggerRemotePollTest.java src/test/java/hudson/plugins/git/SCMTriggerTest.java src/test/java/hudson/plugins/git/TestBranchSpec.java src/test/resources/namespaceBranchRepo.ls-remote src/test/resources/namespaceBranchRepo.zip http://jenkins-ci.org/commit/git-plugin/c9a8e11fd7f63f6bda64c0cefd430e1a9ae32db5 Log: Merge pull request #324 from ndeloof/ JENKINS-28506 [FIXED JENKINS-28506] - Git fails to trigger from polling for refs/heads/ style branch name Compare: https://github.com/jenkinsci/git-plugin/compare/06415b9b9d3d...c9a8e11fd7f6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Code changed in jenkins User: Mark Waite Path: src/test/java/hudson/plugins/git/CliGitSCMTriggerLocalPollTest.java src/test/java/hudson/plugins/git/CliGitSCMTriggerRemotePollTest.java src/test/java/hudson/plugins/git/JGitSCMTriggerLocalPollTest.java src/test/java/hudson/plugins/git/JGitSCMTriggerRemotePollTest.java src/test/java/hudson/plugins/git/SCMTriggerTest.java http://jenkins-ci.org/commit/git-plugin/5b5a00458f98055fa294713e2cf0a8fd67d8c88c Log: Add additional SCM trigger tests to show JENKINS-28506 Reduce special cases in trigger tests to 1 isChangeExpected() method. Several of the tests show known existing remote polling issues. Those known issues cannot be resolved without significant risk to backward compatibility, so they are intentionally not being fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28506 [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Code changed in jenkins User: Mark Waite Path: src/test/resources/namespaceBranchRepo.ls-remote src/test/resources/namespaceBranchRepo.zip http://jenkins-ci.org/commit/git-plugin/97fdec59c3ee3cbb6bfccaf5f88fb9a5fad7f194 Log: Add branches to namespace branch repository zip file for tests Branches now look like: 74ae8c2 (b_namespace3/feature4) Add file b_namespace3/feature4 on branch b_namespace3/feature4 73d4779 (a_tests/b_namespace3/feature3) Add file a_tests/b_namespace3/feature3 on branch a_tests/b_namespace3/feature3 / b00d0c5 (tag: TagA, branchForTagA) Local branch 'branchForTagA' / dde47cb (tag: TagBAnnotated, branchForTagBAnnotated) Local branch 'branchForTagBAnnotated' /
[JIRA] [websphere-deployer-plugin] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Title: Message Title Ashwani Raj commented on JENKINS-21643 Re: Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) I tried everything suggested by you all but I am still not through. I added certificates. I have successful connection through websphere deployer plugin. I can access my remote WAS console on port 9043. I can also tenet it. I can manually deploy application but when I try to do that using Jenkins it gives the error specified in ticket. Am I missing something? Need help on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pollscm-plugin] (JENKINS-28710) Poll source from tfs to jenkins slave showing "no change"
Title: Message Title Ajit Nair assigned an issue to Vincent Latombe Jenkins / JENKINS-28710 Poll source from tfs to jenkins slave showing "no change" Change By: Ajit Nair Assignee: Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pollscm-plugin] (JENKINS-28710) Poll source from tfs to jenkins slave showing "no change"
Title: Message Title Ajit Nair assigned an issue to Unassigned Jenkins / JENKINS-28710 Poll source from tfs to jenkins slave showing "no change" Change By: Ajit Nair Assignee: Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Title: Message Title Antoine Aumjaud commented on JENKINS-27938 Re: Unable to expand collapsed SLIM tables Hi Serge, Could you please send me your HTML page, I will test the Mark's recommendation. Do you use FitNesse scenario ? Regards, Antoine Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Title: Message Title Antoine Aumjaud commented on JENKINS-27940 Re: Consider using jUnit output from FitNesse Hi Serge, What is the benefit for this plugin ? If it returns JUnit results, we will lose HTML pages result, links to jenkins details and history... Regards, Antoine Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again
Title: Message Title Antoine Aumjaud closed an issue as Fixed Jenkins / JENKINS-28316 Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again Change By: Antoine Aumjaud Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again
Title: Message Title Antoine Aumjaud resolved as Fixed fixed in version 1.13 (backward compatibility was broken) Jenkins / JENKINS-28316 Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again Change By: Antoine Aumjaud Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28739) Remote triggering job could also be shown in pipeline
Title: Message Title Jerry Yu created an issue Jenkins / JENKINS-28739 Remote triggering job could also be shown in pipeline Issue Type: Improvement Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Jun/15 4:55 AM Priority: Minor Reporter: Jerry Yu Hello, I'm using parameterized remote trigger plugin to trigger job in another Jenkins. Here is the introduction about the plugin: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin I hope in the build pipeline view, there is also a box represent a remote Jenkins job. Is it possible to do that? Thanks! Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-28739) Remote triggering job could also be shown in pipeline
Title: Message Title Jerry Yu updated an issue Jenkins / JENKINS-28739 Remote triggering job could also be shown in pipeline Change By: Jerry Yu Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28733) Performance Plugin not showing URI's details in Graph
Title: Message Title Kristopher Kleva commented on JENKINS-28733 Re: Performance Plugin not showing URI's details in Graph I get the same result using XML based reports. I tried with apache-jmeter-2.13 and apache-jmeter-2.9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dry-plugin] (JENKINS-28669) Dry-plugin crashing with GC exception
Title: Message Title Debashis Prusty commented on JENKINS-28669 Re: Dry-plugin crashing with GC exception Yes. I think you are right. When I run it for Java (about 1200 warnings), it's working fine. But failing for cpp may be due to huge number of warnings. I tried even with -Xmx2048M still it failed. So I left it for cpp now and publishing for Java only. Hope the enhancement will come someday. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-28738) AC Dynamic Reference: Missing Reference Parameter when rendered as D3 Graph
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28738 AC Dynamic Reference: Missing Reference Parameter when rendered as D3 Graph Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 3:10 AM Priority: Minor Reporter: Bruno P. Kinoshita From https://github.com/biouno/uno-choice-plugin/issues/74 Ioannis has a scenario where a parameter rendering D3.js doesn't seem to be working as expected. Add Comment
[JIRA] [active-choices-plugin] (JENKINS-28737) Value changes of Dynamic Reference are cascaded erratically
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28737 Value changes of Dynamic Reference are cascaded erratically Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 3:04 AM Priority: Major Reporter: Bruno P. Kinoshita From https://github.com/biouno/uno-choice-plugin/issues/73 " Sometimes they do and sometimes they don't. I have noticed this with a specific sequence of uno-choice parameters and I have reproduced a test case for you here: http://162.243.246.75:8080/job/issue-73/ Notice that when you first load a page the entire cascade works as it should image You can explore other ACTIVITY options which propagate updates to the MESSAGE which correctly propagate updates to the PLACES_FOR_ACTIVITY (which just references the Dynamic Reference parameter MESSAGE). image Now, we change the MONTH and this updates the MESSAGE. However, the PLACES_FOR_ACTIVITY are now not updated correctly (still showing the previous values) image However, if you continue to select an ACTIVITY, updates again work. So it is the MESSAGE change cascaded from the MONTH parameter that does not cascade to PLACES_FOR_ACTIVITY "
[JIRA] [active-choices-plugin] (JENKINS-28736) DB Based choice provider
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28736 DB Based choice provider Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 2:52 AM Priority: Minor Reporter: Bruno P. Kinoshita From https://github.com/biouno/uno-choice-plugin/issues/63 " There is a group that has reported the availability of a database based choice provider. https://issues.jenkins-ci.org/browse/JENKINS-24274 image The code is for extending the Extensible Choice Parameter plugin but it seems that this feature would also be a great addition to the uno-choice parameter types. What do you think? Would it be worth contacting the developer and see if they would like to contribute to uno-choice? " Add Comment
[JIRA] [active-choices-plugin] (JENKINS-28735) Supporting Jobs triggered by plug-ins, API and scripts
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28735 Supporting Jobs triggered by plug-ins, API and scripts Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 2:49 AM Priority: Minor Reporter: Bruno P. Kinoshita From https://github.com/biouno/uno-choice-plugin/issues/60 Investigate the possibility of having Active Choices parameters being triggered/used from the Jenkins API or by other plug-ins, and document it (be it viable or not). Add Comment
[JIRA] [active-choices-plugin] (JENKINS-28734) Maintain Uno-Choice selections between filter applications
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28734 Maintain Uno-Choice selections between filter applications Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 2:42 AM Priority: Minor Reporter: Bruno P. Kinoshita From https://github.com/biouno/uno-choice-plugin/issues/36 When you select Active Choice parameters in the Jenkins UI, and then filter the selections, your previous choices are gone. Add Comment
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Implemented in the JENKINS-28732 branch. We need more testing before releasing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/org/biouno/unochoice/model/GroovyScript.java src/main/resources/org/biouno/unochoice/model/GroovyScript/config.jelly http://jenkins-ci.org/commit/active-choices-plugin/fe1e201057f084b363586c21ceb0daa43ac3d2c4 Log: JENKINS-28732 Add Script Security support to Active Choices Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28733) Performance Plugin not showing URI's details in Graph
Title: Message Title madhu cheepati created an issue Jenkins / JENKINS-28733 Performance Plugin not showing URI's details in Graph Issue Type: Bug Assignee: Manuel Carrasco Attachments: PERFORMANCEREPORT.png, PerfResults.csv, THROUGHPUT.png Components: performance-plugin Created: 04/Jun/15 1:42 AM Environment: Linux, Jenkins version : Jenkins ver. 1.616 Perfromance Plugin version: 1.13 Priority: Critical Reporter: madhu cheepati Below are steps to reproduce this issue 1. Create job and In "Build" , "Execute shell", then place sleep 16 2. From "Post Build Actions", Click "Publish Performance test results Report" option , then Then Select "Performance Report" as "JmeterCSV" from dropdown list. 3. Pass PerfResults.csv as an input to "Report files" and "CSV Pattern" values as timestamp,elapsed,URL,responseCode,responseMessage,threadName,dataType,success,failureMessage,bytes,grpThreads,allThreads,label,Latency,SampleCount,ErrorCount,Hostname 4.Save and Build the project Je
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Complete example being used as basis: https://github.com/jenkinsci/groovy-postbuild-plugin/pull/11/files Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier started work on JENKINS-28311 Change By: William Gautier Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from "api" domain
Title: Message Title William Gautier resolved as Fixed Fixed in https://github.com/jenkinsci/cloudfoundry/commit/9f2693ee5953baf6c2f0f30f4bb99119c8ed06a9 Will be in v1.4, with the service creation feature. Jenkins / JENKINS-28602 Error: Default domain calculated from "api" domain Change By: William Gautier Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Some background information: https://groups.google.com/forum/#!searchin/jenkinsci-dev/jesse$20bruno$20security$20groovy/jenkinsci-dev/17--9NhoFJA/odGXD-UOQ18J Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Fixed in 1.23 Jenkins / JENKINS-28508 Broken link on Tap Results Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28732 Add support to the script security plug-in to Active Choices Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 12:08 AM Priority: Minor Reporter: Bruno P. Kinoshita We can use the existing Script Security Plug-in to let users be able to secure their scripts. Add Comment This message was sent by Atlassian JIRA (
[JIRA] [git-client-plugin] (JENKINS-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job thanks Daniel but in our situation right now polling is more relevant? (as far as I know) To give you an idea In our project, For every bug fix or new feature we are going to create a new git branch to isolate code changes And for every branch we are going to create a new Jenkins job to build that particular branch Therefore setting up a git hook for every job is tedious rather than having a job generator with preset values Thank you Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28731) Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state
Title: Message Title Matt Taylor created an issue Jenkins / JENKINS-28731 Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Jun/15 11:50 PM Environment: Jenkins 1.616 Windows 8.1 64bit VirtualBox 4.3.28 Labels: jenkins windows build job gui virtualbox Priority: Major Reporter: Matt Taylor == Symptom == Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes. == Details == Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state. However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. Also another workaround is to have
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at: http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title André Pereira updated an issue Jenkins / JENKINS-28730 GitLab plugin archived versions not available at: http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Change By: André Pereira Summary: GitLab plugin archived versions not available at GitLab : http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title André Pereira assigned an issue to Unassigned Jenkins / JENKINS-28730 GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Change By: André Pereira Assignee: Daniel Brooks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title
A C edited a comment on JENKINS-28604
Re: Parallel step will create 2nd executor on single-executor slaves
I don't have the time right now to write a full test case, but here's a cut-down version of the idiom I am trying to use, hopefully helpful:- 1 restricted master executor with no labels, 2 restricted slaves with labels and 1 executor each (restricted = only run jobs with matching labels)try { parallel {node( 'slave' ) { } }} catch( Exception e ) { node( 'slave' ) { } throw e }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title
A C commented on JENKINS-28604
Re: Parallel step will create 2nd executor on single-executor slaves
I don't have the time right now to write a full test case, but here's a cut-down version of the idiom I am trying to use, hopefully helpful:
1 restricted master executor with no labels, 2 restricted slaves with labels and 1 executor each (restricted = only run jobs with matching labels)
try { parallel { node( 'slave' ) { }
} } catch( Exception e ) { node( 'slave' ) { }
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title André Pereira created an issue Jenkins / JENKINS-28730 GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Issue Type: Bug Assignee: Daniel Brooks Components: gitlab-plugin Created: 03/Jun/15 10:44 PM Priority: Minor Reporter: André Pereira It seems GitLab plugin archived versions are not available at updates.jenkins title. Unfortunatelly jenkins official docker image do not work properly since plugin installation requires this. Can you tell why is not there? Can be fixed? Add Comment
[JIRA] [join-plugin] (JENKINS-28709) Join Plugin ignores dependencies wrapped with flexible-publish
Title: Message Title ikedam commented on JENKINS-28709 Re: Join Plugin ignores dependencies wrapped with flexible-publish Promoted Builds Plugin might be an alternate solution for you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-28709) Join Plugin ignores dependencies wrapped with flexible-publish
Title: Message Title ikedam assigned an issue to mdonohue It is just because join plugin fails to find out dependencies wrapped with flexible-publish. You can also see project D is displayed in the project status page when you configure a project with "Join Trigger" without "Build other projects". To be exact, JoinTrigger#getAllDownstream fails to find out them: https://github.com/jenkinsci/join-plugin/blob/join-1.15/src/main/java/join/JoinTrigger.java#L216 This results not only project D is displayed but also project D is always triggered just after project A is finished. That means, join doesn't work at all. Jenkins / JENKINS-28709 Join Plugin ignores dependencies wrapped with flexible-publish Change By: ikedam Summary: Wrong Downstream project where Join Plugin is used ignores dependencies wrapped with flexible-publish Component/s: flexible-publish-plugin Assignee: ikedam mdonohue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28703 Re: add the pinned status of a plugin to the support bundle Code changed in jenkins User: christ66 Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/766dce94fbc6de4afa8215ed631328d48546c1f0 Log: JENKINS-28703 Add pinned status for plugins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-28703 add the pinned status of a plugin to the support bundle Change By: Steven Christou Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28703 Re: add the pinned status of a plugin to the support bundle Code changed in jenkins User: Steven Christou Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/a8001e90328b14d7c7a9bdebe22a934c69400a1f Log: Merge pull request #34 from christ66/ JENKINS-28703 JENKINS-28703 Add pinned status for plugins. Compare: https://github.com/jenkinsci/support-core-plugin/compare/0a69bdb3b7df...a8001e90328b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title Jesse Glick commented on JENKINS-28604 Re: Parallel step will create 2nd executor on single-executor slaves Sounds like a core bug. Any steps to reproduce? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Title: Message Title A C commented on JENKINS-25727 Re: Occasional exit status -1 with long latencies OK. WF 1.7 seems to have made this problem worse, tracking a possibly related symptom in JENKINS-28604. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26036) Wall Display folder support
Title: Message Title Jesse Glick resolved as Fixed If the fix is in fact merged, then this should be Resolved/Fixed. Jenkins / JENKINS-26036 Wall Display folder support Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26036) Wall Display folder support
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26036 Wall Display folder support Change By: Jesse Glick Labels: folders Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title A C commented on JENKINS-28604 Re: Parallel step will create 2nd executor on single-executor slaves Workflow 1.7 has made this problem worse. Now whenever a slave fails a long running process, Workflow tries to run all the queued parallel builds at once when the node is freed, and generates a new workspace for each one - so I end up with 6 workspaces on a slave machine that only has 1 executor. This is sometimes, but not always correlated with Workflow hanging on a batchfile step that failed. From the outside, this partly looks like a race condition in node assignment for parallel steps. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26178 Ability to run docker-exec etc. from a workflow Change By: Jesse Glick Component/s: docker-workflow-plugin Component/s: docker-build-step-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title Jesse Glick resolved as Fixed The CloudBees Docker Workflow plugin offers this feature. Jenkins / JENKINS-26178 Ability to run docker-exec etc. from a workflow Change By: Jesse Glick Status: Open Resolved Assignee: vjuranek Jesse Glick Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-6097 Update Center could upgrade plugins to latest-release-for-my-Hudson Change By: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
Title: Message Title Jesse Glick resolved as Fixed Fixed in 1.8. Jenkins / JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Title: Message Title Jesse Glick resolved as Fixed A C I am not sure what bug you are seeing but it sounds different than this one. Better to file separately. Note that 1.7 included a fix in a related area. Jenkins / JENKINS-25727 Occasional exit status -1 with long latencies Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-27717) CVS/Workflow integration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27717 Re: CVS/Workflow integration Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/1f919e4a60824804cba6508d7470df7f6fdd03bd Log: JENKINS-27717 Noting fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28191) Job configuration screen stuck on LOADING due to a JavaScript TypeError
Title: Message Title Daniel Beck resolved as Incomplete No response to comment asking for additional information in a month, so resolving as Incomplete. Jenkins / JENKINS-28191 Job configuration screen stuck on LOADING due to a _javascript_ TypeError Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl commented on JENKINS-28729 Re: Exception raised during template rendering: getAffectedFiles() is not implemented This is not a bug in the email-ext plugin, the template requires that the SCM implements that based on what template you are using. You could edit your template to remove the call to getAffectedFiles(). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Change By: Alex Earl Component/s: email-ext-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl assigned an issue to redsolo Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Change By: Alex Earl Assignee: Alex Earl redsolo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Santosh Akuthota created an issue Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin, tfs-plugin Created: 03/Jun/15 7:46 PM Environment: Jenkins ver. 1.598, Windows Server, TFS 2013 Priority: Minor Reporter: Santosh Akuthota The Email is having issues and throws exception when a build is triggered by SCM poll. We are using TFS as our version tool. Please find the below email content for reference. Exception raised during template rendering: getAffectedFiles() is not implemented by this SCM java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by this SCM at hudson.scm.ChangeLogSet$Entry.getAffectedFiles(ChangeLogSet.java:242) 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 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl$GetBeanMethodMetaProperty.getProperty(MetaClassImpl.java:3500) at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEff
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Daniel Beck Labels: envinronment-variables lts-candidate slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28693) docker-java dependency should be shaded
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28693 docker-java dependency should be shaded Change By: Oleg Nenashev Reasons Issues :* docker-java does not guarantee the backward compatibility across versions (there're binary compatibility violations in the latest releases)* sharing of incompatible lib as a plugin is not safe, so we want to setup the shading of the entire docker-java lib * if we leave the plugin as is, there's may be a conflict with other plugins using docker-javaSolution:* Shade the docker-java library in the pluginI'm aware that this issue is a blocker for 1.0 release. Need some help to elaborate it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28726) Default matrix execution strategy produces NPE in latest p4 plugin
Title: Message Title Matt Hauck updated an issue Jenkins / JENKINS-28726 Default matrix execution strategy produces NPE in latest p4 plugin Change By: Matt Hauck I recently upgraded to the latest P4 Plugin version (1.2.3), and it started erroring out with a null pointer exception whenever a matrix build would attempt to run. The essence of the problem is PerforceScm#getMatrixOptions (PerforceScm..java, line 330). This function returns null if the execution strategy is not an instance of MatrixOptions. The only thing this appears to be used for is to figure out the "buildParent" configuration option. It seems to me better in this scenario to assume buildParent is meant to be false if it is not explicitly turned on, and if the " Class Classic " execution strategy is used instead. If instead you want to absolutely require people use the perforce execution strategy, then you should document this in an obvious place (like your README?). It was not immediately obvious to us how to fix this. Even better: there should be some kind of validation / warning somewhere in the UI if you don't have "Perforce: Matrix options" set. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave Unfortunately, I do not know how long this has been an issue and am not currently in a position to try and roll back for testing. I do wonder though - is it only windows, or is it anything launched with JNLP/WebStart/Client initiated? If the latter, it should be significantly easier to test for. All my linux slaves start with SSH, so never really came up there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Jeff Dege commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials We're seeing this, intermittently, when checking out projects that contain several externals. Generally, we're seeing a build fail with this error, and then, when we retry the build it succeeds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title A C commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master This issue is independent of EnvInject - I consistently reproduce this on Jenkins 1.6.09+ without EnvInject. This is a very annoying bug indeed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Bullhorn RelEng commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master Recreating the slave picked up the new PATH settings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28728) Support Pretty JSON outputs in Docker Traceability API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28728 Support Pretty JSON outputs in Docker Traceability API Change By: Oleg Nenashev The current plugin version supports ram JSONs only. It would be great to add an XML format by adding an additional converter. support human-readable JSON outputs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28728) Support Pretty JSON outputs in Docker Traceability API
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28728 Support Pretty JSON outputs in Docker Traceability API Issue Type: New Feature Assignee: Unassigned Components: docker-traceability-plugin Created: 03/Jun/15 5:19 PM Priority: Minor Reporter: Oleg Nenashev The current plugin version supports JSONs only. It would be great to add an XML format by adding an additional converter. Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28727) Support XML outputs in Docker Traceability API
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28727 Support XML outputs in Docker Traceability API Issue Type: New Feature Assignee: Unassigned Components: docker-traceability-plugin Created: 03/Jun/15 5:19 PM Priority: Minor Reporter: Oleg Nenashev The current plugin version supports JSONs only. It would be great to add an XML format by adding an additional converter. Add Comment
[JIRA] [cloudbees-folder-plugin] (JENKINS-28725) Triggering build on all projects in a folder
Title: Message Title Daniel Beck commented on JENKINS-28725 Re: Triggering build on all projects in a folder Not sure this is useful as it would need to exclude parameterized projects (or have a very sophisticated UI that would probably be similar to a sequence of tabs anyway). There's a 'Build Now' column in list views, which means you only need to click a few times within the same tab today if the jobs aren't parameterized. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28726) Default matrix execution strategy produces NPE in latest p4 plugin
Title: Message Title Matt Hauck commented on JENKINS-28726 Re: Default matrix execution strategy produces NPE in latest p4 plugin Created pull request: https://github.com/jenkinsci/p4-plugin/pull/13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-27717) CVS/Workflow integration
Title: Message Title Chris Vogel closed an issue as Fixed Jenkins / JENKINS-27717 CVS/Workflow integration Change By: Chris Vogel Status: Open Closed Assignee: Chris Vogel Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28726) Default matrix execution strategy produces NPE in latest p4 plugin
Title: Message Title Matt Hauck created an issue Jenkins / JENKINS-28726 Default matrix execution strategy produces NPE in latest p4 plugin Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 03/Jun/15 4:41 PM Environment: P4 Plugin 1.2.3 Jenkins 1.609.1 Labels: scm Priority: Minor Reporter: Matt Hauck I recently upgraded to the latest P4 Plugin version (1.2.3), and it started erroring out with a null pointer exception whenever a matrix build would attempt to run. The essence of the problem is PerforceScm#getMatrixOptions (PerforceScm..java, line 330). This function returns null if the execution strategy is not an instance of MatrixOptions. The only thing this appears to be used for is to figure out the "buildParent" configuration option. It seems to me better in this scenario to assume buildParent is meant to be false if it is not explicitly turned on, and if the "Class" execution strategy is used instead.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Title: Message Title Quentin Nerden reopened an issue Jenkins / JENKINS-27229 Docker publish plugin throws error "Please login prior to push" after publishing the image Change By: Quentin Nerden Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-28725) Triggering build on all projects in a folder
Title: Message Title Timothee Besset created an issue Jenkins / JENKINS-28725 Triggering build on all projects in a folder Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 03/Jun/15 4:31 PM Priority: Minor Reporter: Timothee Besset As a user, I expect to trigger a build for all projects in a folder easily. Would save time in some situations where you need to manually trigger ... really useful instead of opening 10 tabs and clicking build now on all of them. Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Title: Message Title Quentin Nerden commented on JENKINS-27229 Re: Docker publish plugin throws error "Please login prior to push" after publishing the image I have the same problem, with the registry "https://registry-1.docker.io/v2" (official v2 registry for Dockerhub). Docker 1.6.2 is used, and the jenkins .dockercfg file was deleted before running the job. The error in the job's console is: (...) workspace] $ docker login -u jenkinsuser -e jenkins-u...@compcom -p https://registry-1.docker.io/v2/ WARNING: login credentials saved in /opt/jenkins/.dockercfg. Login Succeeded [workspace] $ docker build -t mydocker/repo:873 $WORKSPACE/target Sending build context to Docker daemon 557.1 kB (...) Sending build context to Docker daemon 98.04 MB Sending build context to Docker daemon 98.59 MB Sending build context to Docker daemon 98.59 MB Sending build context to Docker daemon Step 0 : FROM mydocker/repo:base2 ---> 55604c2a11e7 Step 1 : ADD comp-web.war /server/standalone/deployments/ ---> e1a25eef96e3 Removing intermediate container 0118fd978788 Successfully built e1a25eef96e3 [workspace] $ docker push mydocker/repo:873 The push refers to a repository [mydocker/repo] (len: 1) e1a25eef96e3: Buffering to Disk e1a25eef96e3: Image push failed Please login prior to push: Username: EOF Build step 'Docker Build and Publish' marked build as failure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-27741) Jenkins fails to report gerrit notifications spontaneously and on restart.
Title: Message Title Piotr Bartosiewicz updated an issue Jenkins / JENKINS-27741 Jenkins fails to report gerrit notifications spontaneously and on restart. +1 The same problem. Gerrit 2.11, Jenkins 1.616, Gerrit Trigger 2.13.0 I've attached some logs with log level set to fine. Change By: Piotr Bartosiewicz Attachment: gerrit-trigger-bug.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title Raphael CHAUMIER commented on JENKINS-28709 Re: Wrong Downstream project where Join Plugin is used Exactly, but I a normal way (without flexible plugin), Jenkins well handles downstream jobs. On the job dashboard only project B and C appears. Why does it seems different with flexible plugin ? Thks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Bullhorn RelEng commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master We have envinject 1.91.2 and jenkins 1.606 here (CentOS master, windows 7 slave) and I see the same behaviors. The path the node has is clearly onle from an earlier configuration, and doesn't include some new items from the system path. I have changed the configuration to NOT unset the system environment variables at the global and node/slave level, to no avail. I have not tried recreating the slave (I will try that now). Actually, I just tried to reset the node configuration settings, and I see under "Prepare jobs environment" that the "Unset System Environment Variables" setting is checked. Same for the global "Prepare jobs environment" -> "Unset System Environment Variables" check box. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-28681) mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled
Title: Message Title Daniel Beck commented on JENKINS-28681 Re: mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled No need. UI/UX improvements related to this are tracked independently as JENKINS-21486 and the issues linked from there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28724) logRotator: logs for modules in multi-module maven project not removed
Title: Message Title Kevin Priest created an issue Jenkins / JENKINS-28724 logRotator: logs for modules in multi-module maven project not removed Issue Type: Bug Assignee: Unassigned Attachments: job.png, module.png Components: core Created: 03/Jun/15 3:59 PM Environment: Windows 2008 R2 Jenkins 1.581 Labels: jenkins log-rotator Priority: Minor Reporter: Kevin Priest The number of builds to keep is set to 12 for all our jobs and the number listed for the job is correct. However, these are Maven multi-module projects and the logs for every module are retained from the beginning of time. See job.png and module.png
[JIRA] [matrix-project-plugin] (JENKINS-28681) mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled
Title: Message Title spong man commented on JENKINS-28681 Re: mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled OK, so then the bug is that if it's non-optional then why does it allow me to disable it? This is definitely not expected, not for a non-expert user, anyway. This is a usability issue. And you should reopen if you care about such things. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28723) Better sorting of events in Facets
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28723 Better sorting of events in Facets Issue Type: Improvement Assignee: Unassigned Components: docker-traceability-plugin Created: 03/Jun/15 3:47 PM Priority: Minor Reporter: Oleg Nenashev Sorting by time is not enough, because docker events prints seconds only. We need a better approach taking state sequences into the account. Docker traceability table output: 2015-06-03T18:41:51Z create running: true, paused: false, exit code:0 2015-06-03T18:41:51Z die running: false, paused: false, exit code:0 2015-06-03T18:41:51Z start running: false, paused: false, exit code:0 Add Comment
[JIRA] [claim-plugin] (JENKINS-28722) Integrate the Build Failure Analyzer plugin with Claim plugin
Title: Message Title Scott Hebert updated an issue Jenkins / JENKINS-28722 Integrate the Build Failure Analyzer plugin with Claim plugin Change By: Scott Hebert *Given* a failed build * When And * the Build Failure Analyzer plugin is installed on the Jenkins instance* And When * a user navigates to the failed build*And* the user claims the build*Then* the user is presented with the defined Failure Causes in the BFA KnowledgeBase *And* a Failure Cause can be selected*And* the Indication is stored by BFA Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-28722) Integrate the Build Failure Analyzer plugin with Claim plugin
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28722 Integrate the Build Failure Analyzer plugin with Claim plugin Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 03/Jun/15 3:28 PM Priority: Minor Reporter: Scott Hebert Given a failed build When the Build Failure Analyzer plugin is installed on the Jenkins instance And a user navigates to the build And the user claims the build Then the user is presented with the defined Failure Causes in the BFA KnowledgeBase And a Failure Cause can be selected And the Indication is stored by BFA Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-28721) Ability for a user to mark a build with a failure cause AFTER a build is completed
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28721 Ability for a user to mark a build with a failure cause AFTER a build is completed Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 03/Jun/15 3:26 PM Priority: Minor Reporter: Scott Hebert Given a build which has failed for an obscure reason which CANNOT be determined by a build log message. When a user navigates to the build Then the user can choose to mark the build with a known Failure Cause from the Knowledge Base And the indication is stored to the configured BFA storage type. Add Comment
[JIRA] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title Daniel Spilker commented on JENKINS-28701 Re: Script runs in Script Console but not with Job DSL groovy Always glad to help. You can donate for the Jenkins project (https://wiki.jenkins-ci.org/display/JENKINS/Donation) and there is a donation button on my page. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title
Sam Gleske edited a comment on JENKINS-28701
Re: Script runs in Script Console but not with Job DSL groovy
Just following up. The solution you gave wasn't entirely correct but it was a great hint for what I needed to do. Here's the working string.{code}Jenkins.instance.getExtensionList('com.cloudbees.jenkins.GitHubPushTrigger$DescriptorImpl')[0].getCredentials(){code} Thanks again!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title
Sam Gleske commented on JENKINS-28701
Re: Script runs in Script Console but not with Job DSL groovy
Just following up. The solution you gave wasn't entirely correct but it was a great hint for what I needed to do. Here's the working string.
Jenkins.instance.getExtensionList('com.cloudbees.jenkins.GitHubPushTrigger$DescriptorImpl')[0].getCredentials()
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title ikedam commented on JENKINS-28709 Re: Wrong Downstream project where Join Plugin is used I don't know much about join plugin, but that sounds the expected behavior. You mean Project A triggers project B and project C in some conditions. Project A triggers project D after B,C finished (join). That means A triggers B,C,D, doesn't it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-28709 Wrong Downstream project where Join Plugin is used Change By: ikedam Assignee: bap ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Title: Message Title James Judd commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Francis Upton Just curious when 1.28 will be released. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifact-promotion-plugin] (JENKINS-28720) Job runs succesfully but getting the following error in Jenkins console = Fatal Error :5:1: XML document structures must start and end within the sam
Title: Message Title Kaavya Priya created an issue Jenkins / JENKINS-28720 Job runs succesfully but getting the following error in Jenkins console = Fatal Error :5:1: XML document structures must start and end within the same entity Issue Type: Bug Assignee: Unassigned Attachments: successfulReport.png Components: artifact-promotion-plugin, junit-plugin Created: 03/Jun/15 2:37 PM Environment: OpenUI Web Application automation using selenium web driver Labels: jenkins exception plugin Priority: Critical Reporter: Kaavya Priya D:\workspace_NewOpenUI\NewOpenUI>gradle runSingleTest -DtestName=DisconnectPSTNServiceTest -DtestEnv=sit1 -Dsmart_stub=on :compileJava :processResources :classes :co
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title ikedam commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job https://github.com/jenkinsci/flexible-publish-plugin/pull/14 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title ikedam started work on JENKINS-28585 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28719) Store environment variable values for CoreWrapperStep as Secret
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28719 Store environment variable values for CoreWrapperStep as Secret Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 03/Jun/15 2:27 PM Labels: security api Priority: Major Reporter: Jesse Glick withCredentials stores values encrypted. wrap currrently does not, but it should. (For compatibility, need to readResolve the old map.) withCredentials also masks secrets accidentally printed to the log. It would perhaps be undesirable for wrap to do so unconditionally, since there may be legitimate reasons to see non-secret variables in build output. Discriminating between the two cases mechanically is unfortunately not possible without an API change to SimpleBuildWrapper, such as making makeSensitiveBuildVariables take Run rather than AbstractBuild, or adding a variant to Context.env. If both issues are addressed, withCredentials could probably be deprecated (marked isAdvanced), with SecretBuildWrapper made a SimpleBuildWrapper.
[JIRA] [dry-plugin] (JENKINS-28669) Dry-plugin crashing with GC exception
Title: Message Title Ulli Hafner commented on JENKINS-28669 Re: Dry-plugin crashing with GC exception Hmm, still no dry plugin class in stack trace visible. However, this looks like JENKINS-1960. The plug-in is not made for such large amount of warnigs... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Kevin Phillips commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs It's different as it should be easier to default to a large value without negative effects.. Yeah - that's what I suspected. ...large requests will still happen depending on plugin. Yeah - this is I guess one of the unfortunate down-sides to the modular / plugin design of Jenkins. When something like this form size limit changes it takes time for that news to propagate out to all of the different maintainers of the different plugins, and even longer for them all to fix their plugins to compensate for the change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title ikedam commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job Reproduced in my environment. Looks a regression in 0.15. I'll prepare a new release to fix the issue soon. For now, any of following ways works as a workaround. A. Downgrade flexible-publish to 0.14.1 or ealier. B. Open "Advanced..." and select "Don't run" for "On evaluation failure" C. Check "Condition for Matrix Aggregation" and select "Never" for "Run on Parent?". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
