[JIRA] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title Pavel Pigalov created an issue Jenkins / JENKINS-34159 Ability to manage shown columns in multijob view Issue Type: New Feature Assignee: Unassigned Components: multijob-plugin Created: 2016/Apr/12 7:05 AM Priority: Major Reporter: Pavel Pigalov I use several multijobs and certain jobs are invoked at certain phases of a "parent multijob". Current multijob view shows all the jobs, so it would be nice to have a regexp selector of jobs included into multijob view. Add Comment
[JIRA] [artifactory-plugin] (JENKINS-34160) Getting ERROR: Failed to parse POMs while trying to build
Title: Message Title amit kamate created an issue Jenkins / JENKINS-34160 Getting ERROR: Failed to parse POMs while trying to build Issue Type: Bug Assignee: yossis Components: artifactory-plugin, cobertura-plugin, deploy-plugin Created: 2016/Apr/12 7:08 AM Environment: ubuntu 14.04LTS Priority: Major Reporter: amit kamate ERROR: Failed to parse POMs hudson.maven.MavenEmbedderException: 2 problems were encountered while building the effective settings [FATAL] Non-readable settings /usr/share/maven3: /usr/share/maven3 (Is a directory) @ /usr/share/maven3 [FATAL] Non-readable settings /usr/share/maven3: /usr/share/maven3 (Is a directory) @ /usr/share/maven3 at hudson.maven.MavenEmbedder.(MavenEmbedder.java:128) at hudson.maven.MavenEmbedder.(MavenEmbedder.java:109) at hudson.maven.MavenEmbedder.(MavenEmbedder.java:136) at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:212) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1285) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1088) at hudson.FilePath.act(FilePath.java:990) at hudson.FilePath.act(FilePath.java:968) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:950) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:677) at hudson.m
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Title: Message Title Mariska Tallandtree updated an issue Jenkins / JENKINS-16345 CLI does not work through reverse proxy @Daniel, please see attached my dumpfiles. The client connects from ip: 172.19.0.6. Jenkins master ip is: 172.19.0.5. Hope you can figure out what is wrong. If you need more info, please let me know. Change By: Mariska Tallandtree Attachment: 16345-threadDump-client.txt Attachment: 16345-threadDump-Master.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] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title Pavel Pigalov updated an issue Jenkins / JENKINS-34159 Ability to manage shown columns in multijob view Change By: Pavel Pigalov Priority: Major Minor I use several multijobs customized column set on all my views (e.g. I remove "Weather" column everywhere and certain jobs are invoked at certain phases of a add " parent multijob Description " column - the latter one with the help of Extra Columns Plugin) and want to be able to do the same for MultiJob view .Current multijob view shows all the jobs default Jenkins columns , so it would be nice to have a regexp selector of jobs included into multijob Columns section where I can add/remove/reorder the columns to be shown on the view just like for usual List View . Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title Pavel Pigalov updated an issue Jenkins / JENKINS-34159 Ability to manage shown columns in multijob view Change By: Pavel Pigalov I use customized column set on all my views (e.g. I remove "Weather" column everywhere and add "Description" column - the latter one with the help of Extra Columns Plugin) and want to be able to do the same for MultiJob view.Current multijob view shows all the default Jenkins columns, so it would be nice to have a Columns section on the Edit View page, where I can add/remove/reorder the columns to be shown on the view just like for usual List View.Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34161) Build Button doesn't work for jobs that require "Build with Parameters"
Title: Message Title Pavel Pigalov created an issue Jenkins / JENKINS-34161 Build Button doesn't work for jobs that require "Build with Parameters" Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 2016/Apr/12 7:14 AM Labels: regression Priority: Critical Reporter: Pavel Pigalov I just upgraded to 1.535. Handling of jobs that require parameters to build is broken. This works: I go to the job page http://jenkins/job/jobname I see an option "Build with Parameters" I click the button, I enter the parameters The job is submitted. This doesn't work:
[JIRA] [multijob-plugin] (JENKINS-34161) Build Button doesn't work for jobs that require "Build with Parameters"
Title: Message Title Pavel Pigalov assigned an issue to Unassigned Jenkins / JENKINS-34161 Build Button doesn't work for jobs that require "Build with Parameters" Change By: Pavel Pigalov Component/s: multijob-plugin Component/s: core Priority: Critical Major Labels: regression Assignee: Oliver Gondža 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
[JIRA] [core] (JENKINS-20080) Build Button fails for jobs that require "Build with Parameters"
Title: Message Title Pavel Pigalov commented on JENKINS-20080 Re: Build Button fails for jobs that require "Build with Parameters" Thanks for your reply, Oliver Gondža! I've raised JENKINS-34161 - seems to be related to multijob view only. 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-directory-plugin] (JENKINS-34143) Test Active Directory connection button reports success if the search operation doesn't have any result
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34143 Re: Test Active Directory connection button reports success if the search operation doesn't have any result Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java src/main/resources/hudson/plugins/active_directory/Messages.properties http://jenkins-ci.org/commit/active-directory-plugin/8a86022e18cb81dd4bc0e7ae9afd5a8cf048d894 Log: Merge pull request #29 from fbelzunc/ JENKINS-34143 [FIXED JENKINS-34143] Test Active Directory connection button reports success if the search operation doesn't have any result Compare: https://github.com/jenkinsci/active-directory-plugin/compare/313942cef58e...8a86022e18cb 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-directory-plugin] (JENKINS-34143) Test Active Directory connection button reports success if the search operation doesn't have any result
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34143 Test Active Directory connection button reports success if the search operation doesn't have any result 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] [throttle-concurrent-builds-plugin] (JENKINS-33919) Add option to choose path delimiter
Title: Message Title Maciej Wolniewicz assigned an issue to Unassigned Jenkins / JENKINS-33919 Add option to choose path delimiter Change By: Maciej Wolniewicz Assignee: Oleg Nenashev 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] [throttle-concurrent-builds-plugin] (JENKINS-33919) Add option to choose path delimiter
Title: Message Title Maciej Wolniewicz commented on JENKINS-33919 Re: Add option to choose path delimiter Hello, Any update on this? Br, Maciek 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-33919) Add option to choose path delimiter
Title: Message Title Oleg Nenashev commented on JENKINS-33919 Re: Add option to choose path delimiter It is being managed by Jenkins core, not by the plugin. Changed the component 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-33919) Add option to choose path delimiter
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-33919 Add option to choose path delimiter Change By: Oleg Nenashev Component/s: core Component/s: throttle-concurrent-builds-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] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Title: Message Title Mariska Tallandtree commented on JENKINS-16345 Re: CLI does not work through reverse proxy Daniel Beck, It seems I've got it working after all. What I did wrong (obviously , I found out after I tried the same without reverse proxy and using basic Jenkins authentication: I assumed, that copying the public key to $JENKINS_HOME/.ssh/authorized_keys, would be the way tell jenkins which keys are allowed. But I needed to copy the public key to https://mydockerhost/cm-jenkins/me/configure. As jenkins is not a 'real' ssh-daemon, only acts as one. And the way to connect is to port 8080 and not 5. Although I did try that yesterday as well. The big issue was not loading the public key at the correct way. java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://cm-jenkins:8080/cm-jenkins/ -i /var/jenkins_home/.ssh/id_rsa version Enter passphrase for /var/jenkins_home/.ssh/id_rsa: So, thanks for your help even though I was finally able to figured it out myself . Hope this will help someone else. Maybe just close the issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-32898) Disable Strict Forbidden File Verification option always causes trigger
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-32898 Disable Strict Forbidden File Verification option always causes trigger Change By: Andy Wang 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] [copyartifact-plugin] (JENKINS-24892) Copyartifact 2.0
Title: Message Title Tom Ghyselinck commented on JENKINS-24892 Re: Copyartifact 2.0 Hi ikedam, Is there any progress on CopyArtifact 2.0? I'm waiting impatiently for some of it's features 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] [sidebar-link-plugin] (JENKINS-34162) Missing sidebar on Jenkins 1.656
Title: Message Title Lukasz Ceran created an issue Jenkins / JENKINS-34162 Missing sidebar on Jenkins 1.656 Issue Type: Bug Assignee: Unassigned Attachments: 2016-04-12 11-10-54.png Components: sidebar-link-plugin Created: 2016/Apr/12 9:13 AM Environment: 1.656 Jenkins, Sidebar component https://wiki.jenkins-ci.org/display/JENKINS/Sidebar-Link+Plugin Priority: Major Reporter: Lukasz Ceran Hi On our jenkins after upgrade version. Sidebar are missing. Can you please help us with this ??
[JIRA] [workflow-plugin] (JENKINS-34163) Retry block in Jenkins workflow script is executed in a different context
Title: Message Title
Dries Elliott created an issue
Jenkins / JENKINS-34163
Retry block in Jenkins workflow script is executed in a different context
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Apr/12 9:15 AM
Labels:
git workflow
Priority:
Major
Reporter:
Dries Elliott
I set up a workflow script using a Git repository. The workflow script performs some Git actions using SSH.
sh "git checkout develop"
//Retry pushing to develop several times because it could be that a developer pushes before this finishes retry(5) { sh 'git pull --no-edit' sh "git push origin develop" }
This script fails however with the error message that there is no remote branch tracked by the current branch.
We've been using this script for a long time now on release 1.10.1 of the workflow plugin, but this issue started occurring after the upgrade to release 2.
I downgraded to release 1.10.1 again and everything started working again.
[JIRA] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title BBVA commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message @See https://issues.tmatesoft.com/issue/SGT-451 Slaves need to force load of jna classes at startup. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Title: Message Title Daniel Beck resolved as Cannot Reproduce Jenkins / JENKINS-16345 CLI does not work through reverse proxy Change By: Daniel Beck Status: Reopened Resolved Resolution: Cannot 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] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Title: Message Title Daniel Beck commented on JENKINS-16345 Re: CLI does not work through reverse proxy As jenkins is not a 'real' ssh-daemon, only acts as one. And the way to connect is to port 8080 and not 5. The CLI is exposed both as standalone service for use with jenkins-cli.jar (for which you specify the HTTP URL of Jenkins and then it either goes through HTTP, or connects to the TCP agent listener port), as well as SSH daemon for use with an SSH client. 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] [parameterized-trigger-plugin] (JENKINS-34112) Invoke one build with all matching files
Title: Message Title Edgars B. commented on JENKINS-34112 Re: Invoke one build with all matching files I need this too. All we need is that "Current build parameters" does pass all parameters and that passing the files by name in parameter list also passes them. It's self-explanatory. Note that in another JIRA issue the question was entirely misunderstood and closed prematurely: https://issues.jenkins-ci.org/browse/JENKINS-28958 That issue should be 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] [parameterized-trigger-plugin] (JENKINS-34112) Invoke one build with all matching files
Title: Message Title Edgars B. edited a comment on JENKINS-34112 Re: Invoke one build with all matching files I need this too. All we need is that "Current build parameters" does pass all parameters and that passing the files by name in parameter list also passes them. It's self-explanatory.Note that in another JIRA issue the question was entirely misunderstood and closed prematurely: https://issues.jenkins-ci.org/browse/JENKINS-28958That issue should be 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] [parameterized-trigger-plugin] (JENKINS-34112) Invoke one build with all matching files
Title: Message Title Edgars B. edited a comment on JENKINS-34112 Re: Invoke one build with all matching files I need this too. All we need is that "Current build parameters" does pass all parameters and that passing the files by name in parameter list also passes them. It's self-explanatory.Note that in another JIRA issue the question was misunderstood and closed prematurely: https://issues.jenkins-ci.org/browse/JENKINS-28958 That issue should be 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] [parameterized-trigger-plugin] (JENKINS-34112) Invoke one build with all matching files
Title: Message Title Edgars B. edited a comment on JENKINS-34112 Re: Invoke one build with all matching files I need this too. All we need is that "Current build parameters" does pass all parameters and that passing the files by name in parameter list also passes them. It's self-explanatory.Note that in another JIRA issue the question was misunderstood and closed prematurely: https://issues.jenkins-ci.org/browse/JENKINS- 28958 27255 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/junit/Native.java src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/606bec45844ffac7a460c60510613d946886474b Log: JENKINS-33382 Fix potential NPE and extra checks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/junit/WithOS.java src/main/java/org/jenkinsci/test/acceptance/po/CapybaraPortingLayerImpl.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java http://jenkins-ci.org/commit/acceptance-test-harness/9fdb064d06cf746581f7f9c0596c15a0bf586210 Log: JENKINS-33382 Improving javadoc. Copy file only supported for LocalController. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/po/Job.java http://jenkins-ci.org/commit/acceptance-test-harness/7e4f10579ca832572b8745fe67130b6bfe7c6f05 Log: JENKINS-33382 Resolve more conflicts Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/f1de8bf734b082b09fecd6a558e7ad2181f4c9cd Log: JENKINS-33382 Fix assertion. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/junit/WithOS.java src/main/java/org/jenkinsci/test/acceptance/po/CapybaraPortingLayerImpl.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/af4ad71d98da83a297eace2d87a08fbe971d6011 Log: JENKINS-33382 Add WithOS annotation. Copying files in Windows with remote controller should fail (for now) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/e7426c608c2a5da688471c711e7ade64b8338de3 Log: JENKINS-33382 Use of WithOS annotation Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/3e340c11a995a7658137030d451f3348f9c6cd63 Log: JENKINS-33382 Add new test and static import hamcrests method Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/test/acceptance/junit/WithOS.java src/main/java/org/jenkinsci/test/acceptance/msbuild/MSBuildInstallation.java src/main/java/org/jenkinsci/test/acceptance/msbuild/MSBuildStep.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/MSBuildPluginTest.java src/test/resources/msbuild_plugin/projProject/HelloWorld.cs src/test/resources/msbuild_plugin/projProject/project.proj src/test/resources/msbuild_plugin/slnProject/HelloWorld.cs src/test/resources/msbuild_plugin/slnProject/project.proj src/test/resources/msbuild_plugin/slnProject/project.sln http://jenkins-ci.org/commit/acceptance-test-harness/6c8327763b36974fa5cc3f57998f7fc75fa81247 Log: Merge pull request #83 from armfergom/JENKINS-33382 JENKINS-33382 MSBuild acceptance tests. Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/2d593b8ebe62...6c8327763b36 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/msbuild/MSBuildInstallation.java src/main/java/org/jenkinsci/test/acceptance/msbuild/MSBuildStep.java src/main/java/org/jenkinsci/test/acceptance/po/BatchBuildStep.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/MSBuildPluginTest.java src/test/resources/msbuild_plugin/projProject/HelloWorld.cs src/test/resources/msbuild_plugin/projProject/project.proj src/test/resources/msbuild_plugin/slnProject/HelloWorld.cs src/test/resources/msbuild_plugin/slnProject/project.proj src/test/resources/msbuild_plugin/slnProject/project.sln http://jenkins-ci.org/commit/acceptance-test-harness/ea3cea53854b3003ff0182a8e8d5b912c3e6d39b Log: JENKINS-33382 Tests for MSBuild to be executed only on Windows Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/junit/Native.java src/main/java/org/jenkinsci/test/acceptance/junit/WithOS.java src/main/java/org/jenkinsci/test/acceptance/po/CapybaraPortingLayerImpl.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/MSBuildPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/6fedca8c8d1fa21f7fd8154423ef6e5d7c95de7b Log: JENKINS-33382 WithOS - runtime error if no LocalController in use. Native - change impl to support win too Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/junit/Native.java http://jenkins-ci.org/commit/acceptance-test-harness/0f69c25662c3bd70ec627542c81e2e8af2952ec1 Log: JENKINS-33382 Tiny refactor. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33382) ATH: Tests for MSBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33382 Re: ATH: Tests for MSBuild Code changed in jenkins User: Armando Fernandez Path: src/main/java/org/jenkinsci/test/acceptance/po/BatchBuildStep.java http://jenkins-ci.org/commit/acceptance-test-harness/bf380a93445bd1b39c018556afe99677b0acc856 Log: JENKINS-33382 Remove unused BatchBuildStep (duplicated from merge) 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] [parameterized-trigger-plugin] (JENKINS-27255) Pass a file parameter to downstream job
Title: Message Title Edgars B. edited a comment on JENKINS-27255 Re: Pass a file parameter to downstream job I do not think the mentioned "ParameterFactories" feature is what this feature request is about. There's currently no way to pass specific files to specific builds and "Current build paramters" doesn't even pass any files, which would be very self-explanatory and intuitive. For me the "ParameterFactories" suggestion is useless. See https://issues.jenkins-ci.org/browse/JENKINS-34112 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] [parameterized-trigger-plugin] (JENKINS-27255) Pass a file parameter to downstream job
Title: Message Title Edgars B. commented on JENKINS-27255 Re: Pass a file parameter to downstream job I do not think the mentioned "ParameterFactories" feature is what this feature request is about. There's currently no way to pass specific files to specific builds and "Current build paramters" doesn't even pass any files, which would be very self-explanatory and intuitive. See https://issues.jenkins-ci.org/browse/JENKINS-34112 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34004 Re: Git Plugin ATH Tests may fail if global identity not configured Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/plugins/git/GitRepo.java http://jenkins-ci.org/commit/acceptance-test-harness/e8bc83c05d04857cc2fcc2139e02959f34a7ff4c Log: JENKINS-34004 Add identity configuration when creating repo. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34004 Re: Git Plugin ATH Tests may fail if global identity not configured Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/test/acceptance/plugins/git/GitRepo.java http://jenkins-ci.org/commit/acceptance-test-harness/58040e4a8b979f28a090c8f57b8dccfb3e246956 Log: Merge pull request #93 from andresrc/JENKINS-34004 JENKINS-34004 Add identity configuration when creating repo. Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/6c8327763b36...58040e4a8b97 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] [parameterized-trigger-plugin] (JENKINS-27255) Pass a file parameter to downstream job
Title: Message Title Edgars B. commented on JENKINS-27255 Re: Pass a file parameter to downstream job Both issues rely on the fact that files are not actually treated as real parameters when triggering downstream jobs. 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-34164) Jenkins web interface in need of usability and aesthetic improvements
Title: Message Title Alper Cugun created an issue Jenkins / JENKINS-34164 Jenkins web interface in need of usability and aesthetic improvements Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Apr/12 9:57 AM Priority: Major Reporter: Alper Cugun The website that Jenkins offers as an interface to various CI related tasks and results has a design which is substandard and which I believe is the cause of countless communication and usability related issues (most of which won't be reported). Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-28918) Ability to browse previous pipeline with paging
Title: Message Title Tommy Tynjä updated an issue Jenkins / JENKINS-28918 Ability to browse previous pipeline with paging Change By: Tommy Tynjä It would sometimes useful to be able to browse old pipelines. Displaying 50 pipelines brings some load time issues and it would be good to have an ability to use paging (e.g. 5 pipelines on a page and paging to see more). Pagination should only apply to default view and not fullscreen view as it doesn't make sense to use pagination for full screens view since it is intended as an information radiator. 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] [delivery-pipeline-plugin] (JENKINS-28918) Ability to browse previous pipeline with paging
Title: Message Title Tommy Tynjä assigned an issue to Suresh Kumar Jenkins / JENKINS-28918 Ability to browse previous pipeline with paging Change By: Tommy Tynjä Assignee: Patrik Boström Suresh Kumar 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] [delivery-pipeline-plugin] (JENKINS-28918) Ability to browse previous pipeline with paging
Title: Message Title Tommy Tynjä commented on JENKINS-28918 Re: Ability to browse previous pipeline with paging Updated issue description to clarify use case. Assigned issue to Suresh Kumar. Adding feedback to the associated pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page
Title: Message Title Matei Dragu commented on JENKINS-9980 Re: Add the "Publish JUnit test result report" option to maven job configuration page Hey guys, Is there any update on this 5 year-old issue? I can confirm that the behaviour is the same for Jenkins 1.652. The following 2 oprions are missing from the "Add post-build action" button Publish JUnit test result report Publish Javadoc Would someone from the Jenkins dev team care to comment on this issue? Thank you in advance for your consideration! Matei 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-32455) Artifacts lost when renaming matrix project with custom Build record directory
Title: Message Title
Russell Gallop updated an issue
Jenkins / JENKINS-32455
Artifacts lost when renaming matrix project with custom Build record directory
Change By:
Russell Gallop
Using a custom build record directory means that artifacts are lost when renaming a matrix project.I have set up:Build Record Root Directory d:/artifacts/$\{ITEM_FULL_NAME\}/builds/And a matrix job: "Rename_test" which has one user-defined axis "FOO" with one value "bar".which executes a Windows batch command: "echo %BUILD_TAG% > afile.txt"And Archives the artifact afile.txt.I run this a couple of times to create some artifacts then rename the job to "Rename_test_new_name". The artifacts (and other per-configuration build data) are not moved so the folder: d:/artifacts now has "Rename_test" and "Rename_test_new_name". New artifacts are created in the new name, old artifacts are still in the old folder.I think that this may be to do with how ITEM_FULL_NAME works. With the default "Build record root directory" ($\{ITEM_ROOTDIR\}/builds) the per configuration data is stored in:Rename_test/configurations/axis-FOO/bar/buildsWith the build record root directory changed to "d:/artifacts/$\{ITEM_FULL_NAME\}/builds/" they are stored in:Rename_test/FOO=bar/builds
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://gr
[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory
Title: Message Title Russell Gallop commented on JENKINS-32455 Re: Artifacts lost when renaming matrix project with custom Build record directory > Try with an instance that doesn't have SCM Sync Configuration and try again. I've disabled SCM Sync (+metadata, multijob, envinject and job config history) and still see the same behaviour (now with 1.642.4). Build 1 was before rename, build 2 is after rename. Log: Apr 12, 2016 11:33:45 AM INFO hudson.model.Run execute JENKINS-32455-testd_renamed/FOO=bar #1 main build action completed: SUCCESS Apr 12, 2016 11:33:46 AM INFO hudson.model.Run execute JENKINS-32455-testd_renamed #1 main build action completed: SUCCESS Apr 12, 2016 11:33:56 AM INFO hudson.model.Run execute JENKINS-32455-testd_renamed/FOO=bar #2 main build action completed: SUCCESS Apr 12, 2016 11:33:57 AM INFO hudson.model.Run execute JENKINS-32455-testd_renamed #2 main build action completed: SUCCESS And these are the resulting files (using git bash on Windows): JENKINS-32455-testd/ JENKINS-32455-testd/FOO=bar/ JENKINS-32455-testd/FOO=bar/builds/ JENKINS-32455-testd/FOO=bar/builds/1/ JENKINS-32455-testd/FOO=bar/builds/1/archive/ JENKINS-32455-testd/FOO=bar/builds/1/archive/afile.txt JENKINS-32455-testd/FOO=bar/builds/1/build.xml JENKINS-32455-testd/FOO=bar/builds/1/changelog.xml JENKINS-32455-testd/FOO=bar/builds/1/log JENKINS-32455-testd/FOO=bar/builds/lastStableBuild JENKINS-32455-testd/FOO=bar/builds/lastSuccessfulBuild JENKINS-32455-testd/FOO=bar/builds/legacyIds JENKINS-32455-testd_renamed/ JENKINS-32455-testd_renamed/builds/ JENKINS-32455-testd_renamed/builds/1/ JENKINS-32455-testd_renamed/builds/1/build.xml JENKINS-32455-testd_renamed/builds/1/changelog.xml JENKINS-32455-testd_renamed/builds/1/log JENKINS-32455-testd_renamed/builds/2/ JENKINS-32455-testd_renamed/builds/2/build.xml JENKINS-32455-testd_renamed/builds/2/changelog.xml JENKINS-32455-testd_renamed/builds/2/log JENKINS-32455-testd_renamed/builds/lastFailedBuild JENKINS-32455-testd_renamed/builds/lastStableBuild JENKINS-32455-testd_renamed/builds/lastSuccessfulBuild JENKINS-32455-testd_renamed/builds/legacyIds JENKINS-32455-testd_renamed/FOO=bar/ JENKINS-32455-testd_renamed/FOO=bar/builds/ JENKINS-32455-testd_renamed/FOO=bar/builds/2/ JENKINS-32455-testd_renamed/FOO=bar/builds/2/archive/ JENKINS-32455-testd_renamed/FOO=bar/builds/2/archive/afile.txt JENKINS-32455-testd_renamed/FOO=bar/builds/2/build.xml JENKINS-32455-testd_renamed/FOO=bar/builds/2/changelog.xml JENKINS-32455-testd_renamed/FOO=bar/builds/2/log JENKINS-32455-testd_renamed/FOO=bar/builds/lastStableBuild JENKINS-32455-testd_renamed/FOO=bar/builds/lastSuccessfulBuild Clarified the original description to say that this was a user-defined axis.
[JIRA] [github-plugin] (JENKINS-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Kirill Merkushev commented on JENKINS-34144 Re: Don't fail the job if setting the GitHub status fails Will try to add such handler on weekend 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] [ansible-plugin] (JENKINS-33849) "Authentication failure" when use the "delegate_to" in the task
Title: Message Title
Dmitry S updated an issue
Jenkins / JENKINS-33849
"Authentication failure" when use the "delegate_to" in the task
Change By:
Dmitry S
The problem happen only when I run playbook in the Jenkins. In normal use everything is ok.*The error message*{code:java}TASK [fuel : ...] **task path: /var/lib/jenkins/jobs/Openstack Deploy/workspace/playbooks/openstack-deployment/roles/fuel/tasks/configure-pxe-server.yml:67<192.168.54.11> ESTABLISH SSH CONNECTION FOR USER: None<192.168.54.11> SSH: EXEC sshpass -d14 ssh -C -q -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o ConnectTimeout=10 -o ControlPath=/var/lib/jenkins/.ansible/cp/ansible-ssh-%h-%p-%r -tt 192.168.54.11 '/bin/sh -c '"'"'( umask 22 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1459173837.21-165158381236189 `" && echo "` echo $HOME/.ansible/tmp/ansible-tmp-1459173837.21-165158381236189 `" )'"'"''fatal: [fuel]: UNREACHABLE! => {"changed": false, "msg": "Authentication failure.", "unreachable": true} to retry, use: --limit @/var/lib/jenkins/jobs/Openstack Deploy/workspace/playbooks/openstack-deployment/kvm-fuel.retry{code}*The task*{code:java}- name: ... synchronize:src: /mnt/fueliso/dest: '{{ tftp_root }}/fuel' delegate_to: '{{ delegate_host }}'{code} _I I changed "{{ delegate_host }}" to plain ip address "192.168.54.11" - it didn't help_ help *The variable*{code:java}delegate_host: '{{ ansible_default_ipv4.address }}'{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscrib
[JIRA] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Kirill Merkushev resolved as Fixed Jenkins / JENKINS-33434 no post build step to set status to 'success' Change By: Kirill Merkushev 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Kirill Merkushev commented on JENKINS-33434 Re: no post build step to set status to 'success' Have an idea - just look at next section - after build operations 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] [_unsorted] (JENKINS-29624) Java heap space when using maven.plugin.surefire
Title: Message Title rajesh r reopened an issue I am facing this issue please find below Console output: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2367) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415) at java.lang.StringBuffer.append(StringBuffer.java:237) at java.io.StringWriter.write(StringWriter.java:112) at gherkin.deps.com.google.gson.stream.JsonWriter.string(JsonWriter.java:538) at gherkin.deps.com.google.gson.stream.JsonWriter.value(JsonWriter.java:404) at gherkin.deps.com.google.gson.internal.bind.TypeAdapters$13.write(TypeAdapters.java:353) at gherkin.deps.com.google.gson.internal.bind.TypeAdapters$13.write(TypeAdapters.java:337) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) Jenkins / JENKINS-29624 Java heap space when using maven.plugin.surefire
[JIRA] [git-plugin] (JENKINS-33956) Git Plugin allows removing the last repository entry on the config screen
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-33956 Git Plugin allows removing the last repository entry on the config screen Change By: Mark Waite Assignee: Mark Waite 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-33956) Git Plugin allows removing the last repository entry on the config screen
Title: Message Title Mark Waite stopped work on JENKINS-33956 Change By: Mark Waite Status: In Progress Open 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title Ulli Hafner commented on JENKINS-34157 Re: Warnings plugin doesn't allow environment variables in file names Hmm, this has been implemented in https://github.com/jenkinsci/warnings-plugin/pull/33. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34165) Null pointer exception polling from git job accessing bitbucket repo
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-34165 Null pointer exception polling from git job accessing bitbucket repo Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Apr/12 11:43 AM Environment: Git plugin 2.4.4 Git client plugin 1.19.6 Jenkins 1.642.4 Ubuntu 14.04 master with various slaves Priority: Minor Reporter: Mark Waite A stack trace was reported to /var/log/jenkins/jenkins.log that shows a null pointer exception in pollnig from either the git plugin or the git client plugin. Apr 10, 2016 4:27:00 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.matrix.MatrixProject@4616ca95[JENKINS-22119-bitbucket-credentialed-clone-fails] java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getPollEnvironment(GitUtils.java:220) at hudson.plugins.git.util.GitUtils.getPollEnvironment(GitUtils.java:194) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:684) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:571) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject.pollWithW
[JIRA] [core] (JENKINS-25704) Scheduled triggering stops working until restart
Title: Message Title David Resnick commented on JENKINS-25704 Re: Scheduled triggering stops working until restart I didn't encounter this problem when I had the stash plugin installed. I now have the stash plugin and haven't encountered this problem. 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Eddie Sholl commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job I've submitted a pull request for this issue with a potential solution. It's available at https://github.com/Diabol/delivery-pipeline-plugin/pull/175 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] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title Pavel Pigalov updated an issue Jenkins / JENKINS-34159 Ability to manage shown columns in multijob view Change By: Pavel Pigalov I use customized column set on all my views (e.g. I remove "Weather" column everywhere and add "Description" column - the latter one with the help of Extra Columns Plugin) and want to be able to do the same for MultiJob view.Current multijob view shows all the default Jenkins columns, so it would be nice to have a Columns section on the Edit View page, where I can add/remove/reorder the columns to be shown on the view just like for usual List View. In addition would be just perfect to be able to configure the columns the same way on the MultiJob project page (e.g. ) Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title
Pavel Pigalov updated an issue
Jenkins / JENKINS-34159
Ability to manage shown columns in multijob view
Change By:
Pavel Pigalov
I use customized column set on all my views (e.g. I remove "Weather" column everywhere and add "Description" column - the latter one with the help of Extra Columns Plugin) and want to be able to do the same for MultiJob view.Current multijob view shows all the default Jenkins columns, so it would be nice to have a Columns section on the Edit View page, where I can add/remove/reorder the columns to be shown on the view just like for usual List View.In addition would be just perfect to be able to configure the columns the same way on the MultiJob project page ( i. e. g. which columns to show when you're on {{http://jenkins/job/MultiJobName}} )Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-34166) Allow restart aborted builds for
Title: Message Title Denis Shvedchenko created an issue Jenkins / JENKINS-34166 Allow restart aborted builds for Issue Type: New Feature Assignee: Nicolas De Loof Components: naginator-plugin Created: 2016/Apr/12 12:25 PM Priority: Trivial Reporter: Denis Shvedchenko My customer tries to use https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin and https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin together. They need option : Rerun build for cancelled build Use case: 1. restart builds that was aborted due to timeout I can provide implementation for this Feauture if including such option is accepatbel Add Comment
[JIRA] [naginator-plugin] (JENKINS-34166) Allow restart aborted builds for cancelled builds
Title: Message Title Denis Shvedchenko updated an issue Jenkins / JENKINS-34166 Allow restart aborted builds for cancelled builds Change By: Denis Shvedchenko Summary: Allow restart aborted builds for cancelled builds 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] [multijob-plugin] (JENKINS-34161) Build Button doesn't work for jobs that require "Build with Parameters"
Title: Message Title
Pavel Pigalov updated an issue
Jenkins / JENKINS-34161
Build Button doesn't work for jobs that require "Build with Parameters"
Change By:
Pavel Pigalov
My setup:* Jenkins v1.653* multijob-plugin v1.21What doesn't work:* I see the job listed on a MultiJob view page {{http://jenkins/view/MultiJobViewName}}* I hover over the "Build" button, which displays the hover text "Schedule a build with parameters"* I click the button, and expect to enter the parameters, but instead it immediately says "Build scheduled", but the job is not actually scheduled and nothing happens then. Also the same happens on the MultiJob project page:* I click on the MiltiJob project and {{http://jenkins/job/MultiJobName}} page is loaded (or {{http://jenkins/view/MultiJobViewName/job/MultiJobName}})* I hover over the "Build" button, which displays the hover text "Schedule a build with parameters"* I click the button, and expect to enter the parameters, but instead it immediately says "Build scheduled", but the job is not actually scheduled and nothing happens then. Workaround:* I go to the job page {{http://jenkins/job/ JobName MultiJobName }}* I see an option "Build with Parameters"* I click the button, I enter the parameters* The job is executed.Only happens on MultiJob view tab, works for "All" tab and regular "List View" tabs.Probably somehow connected with JENKINS-20080 which was fixed 2 years ago or so.Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Iss
[JIRA] [multijob-plugin] (JENKINS-34161) Build Button doesn't work for jobs that require "Build with Parameters"
Title: Message Title
Pavel Pigalov updated an issue
Jenkins / JENKINS-34161
Build Button doesn't work for jobs that require "Build with Parameters"
Change By:
Pavel Pigalov
My setup:* Jenkins v1.653* multijob-plugin v1.21What doesn't work:* I see the job listed on a MultiJob view page {{http://jenkins/view/MultiJobViewName}}* I hover over the "Build" button on the right , which displays the hover text "Schedule a build with parameters"* I click the button, and expect to enter the parameters, but instead it immediately says "Build scheduled", but the job is not actually scheduled and nothing happens then.Also the same happens on the MultiJob project page:* I click on the MiltiJob project and {{http://jenkins/job/ MultiJobName Multi_Job_Name }} page is loaded (or {{http://jenkins/view/MultiJobViewName/job/ MultiJobName Multi_Job_Name }})* I hover over the "Build" button on the right , which displays the hover text "Schedule a build with parameters"* I click the button, and expect to enter the parameters, but instead it immediately says "Build scheduled", but the job is not actually scheduled and nothing happens then.Workaround:* I go to the job page {{http://jenkins/job/ MultiJobName Multi_Job_Name }}* I see an option "Build with Parameters" in the left Menu * I click the button, I enter the parameters* The job is executed.Only happens on MultiJob view tab, works for "All" tab and regular "List View" tabs.Probably somehow connected with JENKINS-20080 which was fixed 2 years ago or so.Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
[JIRA] [msbuild-plugin] (JENKINS-30489) msbuild configuration need full path with including msbuild.exe but website shows warning
Title: Message Title Hans van Luttikhuizen commented on JENKINS-30489 Re: msbuild configuration need full path with including msbuild.exe but website shows warning I've also encountered this problem. The configuration doesn't clearly specify whether it requires the folder or the executable. It gives a warning when the executable is given, even though it is actually what is required. Please either fix the warning or the expected behaviour and better communicate what information exactly is required. 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] [multijob-plugin] (JENKINS-34159) Ability to manage shown columns in multijob view
Title: Message Title
Pavel Pigalov updated an issue
Jenkins / JENKINS-34159
Ability to manage shown columns in multijob view
Change By:
Pavel Pigalov
I use customized column set on all my views (e.g. I remove "Weather" column everywhere and add "Description" column - the latter one with the help of Extra Columns Plugin) and want to be able to do the same for MultiJob view.Current multijob view shows all the default Jenkins columns, so it would be nice to have a Columns section on the Edit View page, where I can add/remove/reorder the columns to be shown on the view just like for usual List View.In addition would be just perfect to be able to configure the columns the same way on the MultiJob project page (i.e. which columns to show when you're on {{http://jenkins/job/MultiJobName}})Thanks! p.s. my setup is:* Jenkins v1.653* multijob-plugin v1.21
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-15382) Memory exhaustion parsing large test stdio from Surefire
Title: Message Title rajesh r reopened an issue Still getting the issue while running maven project in jenkins : testcase name="testrunners.CukeTestOne" classname="org.apache.maven.surefire.junit4.JUnit4Provider" time="0.767"> java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2367) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415) at java.lang.StringBuffer.append(StringBuffer.java:237) at java.io.StringWriter.write(StringWriter.java:112) at gherkin.deps.com.google.gson.stream.JsonWriter.string(JsonWriter.java:538) at gherkin.deps.com.google.gson.stream.JsonWriter.value(JsonWriter.java:404) at gherkin.deps.com.google.gson.internal.bind.TypeAdapters$13.write(TypeAdapters.java:353) at gherkin.deps.com.google.gson.internal.bind.TypeAdapters$13.write(TypeAdapters.java:337) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:96) at gherkin.deps.com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:60) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:209) at gherkin.deps.com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.write(MapTypeAdapterFactory.java:146) at gherkin.deps.com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68) Jenkins / JENKINS-15382 Memory exhaustion parsing large test stdio from Surefire
[JIRA] [jobconfighistory-plugin] (JENKINS-30205) metadata-plugin causes garbage change logs in config history lists
Title: Message Title Fathi Boudra commented on JENKINS-30205 Re: metadata-plugin causes garbage change logs in config history lists Metadata plugin doesn't play well with Job Config History plugin. I have a similar issue, caused by metadata time tag always modified (e.g. 1460446330242). As a result, Job Config History records the changes, even when the job configuration isn't modified. 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-33736) HttpParser Full jetty warn
Title: Message Title Nikolay Metchev commented on JENKINS-33736 Re: HttpParser Full jetty warn Something seems to have create a huge number of cookies in Chrome. If I delete all the cookies from chrome they come back! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Leandro Lucarella commented on JENKINS-34144 Re: Don't fail the job if setting the GitHub status fails Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34167) Add Build Step -> Execute Shell returns 500 from render
Title: Message Title Justin Bramley created an issue Jenkins / JENKINS-34167 Add Build Step -> Execute Shell returns 500 from render Issue Type: Bug Assignee: Unassigned Attachments: jenkins_stacktrace.txt Components: core Created: 2016/Apr/12 1:29 PM Environment: Jenkins ver. 1.653 on Red Hat Enterprise Linux Server release 6.7 (Santiago) with java version "1.7.0_85" OpenJDK Runtime Environment (rhel-2.6.1.3.el6_7-x86_64 u85-b01) OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode) Priority: Major Reporter: Justin Bramley When configuring a project, going to Add Build Step and selecting Execute Shell results in a 500 error with a stack trace like this (full trace attached): Caused by: groovy.lang.MissingPropertyException: No such property: command for class: java.lang.String at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeA
[JIRA] [tfs-plugin] (JENKINS-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server
Title: Message Title Joseph Hoppe created an issue Jenkins / JENKINS-34168 TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2016/Apr/12 1:38 PM Environment: Windows 2008 R2 SP 1, Chrome Version 49.0.2623.112 m, Internally hosted TFS 2013, TFS plugin 4.1.0 Priority: Major Reporter: Joseph Hoppe I have a couple projects working in Jenkins with TFS, but a number that also do not. I.e., this one fails: Configure the project. Re-enter my TFS credentials to confirm that they are correct. Wipe out my project's entire existing workspace just to try to make a better test. Click build now. Build fails with message below. However, all
[JIRA] [bulk-builder-plugin] (JENKINS-34169) Bulk Builder builds all jobs in the first view instead of 'All'
Title: Message Title Johann Schmitz created an issue Jenkins / JENKINS-34169 Bulk Builder builds all jobs in the first view instead of 'All' Issue Type: Bug Assignee: Simon Westcott Components: bulk-builder-plugin Created: 2016/Apr/12 1:40 PM Priority: Minor Reporter: Johann Schmitz If you have a view which gets ordered before 'All' (like 'AAA') and leave the "Limit to jobs in view" option unchecked, the Bulk Builder plugin builds all Jobs in the first view instead of 'All' Add Comment
[JIRA] [core] (JENKINS-34170) support a watch REST API for jenkins resources?
Title: Message Title James Strachan created an issue Jenkins / JENKINS-34170 support a watch REST API for jenkins resources? Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Apr/12 1:46 PM Priority: Minor Reporter: James Strachan One thing thats really nice about the kubernetes REST API is for any resource you can append "?watch=true" to the URL and you can upgrade from polling to watching resources over SPDY / websockets which can be a nice way to visualise things in a web page in real time without polling. I wonder has anyone ever tried adding a watch hook into the Jenkins REST API? Add Comment
[JIRA] [git-plugin] (JENKINS-34171) Cannot fetch repo from Stash
Title: Message Title Sunil Gandham created an issue Jenkins / JENKINS-34171 Cannot fetch repo from Stash Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Apr/12 1:47 PM Priority: Major Reporter: Sunil Gandham > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gansu...@stash.staples.com:7990/scm/mobile/mobilehub-ios.git # timeout=10 Fetching upstream changes from http://gansu...@stash.staples.com:7990/scm/mobile/mobilehub-ios.git > git --version # timeout=10 using .gitcredentials to set credentials > git config --local credential.username GanSu001 # timeout=10 > git config --local credential.helper store --file=/Users/Shared/Jenkins/tmp/git791790795510197800.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress http://gansu...@stash.staples.com:7990/scm/mobile/mobilehub-ios.git +refs/heads/:refs/remotes/origin/ ERROR: Timeout after 10 minutes > git config --local --remove-section credential # timeout=10 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gansu...@stash.staples.com:7990/scm/mobile/mobilehub-ios.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.jav
[JIRA] [_unsorted] (JENKINS-34172) Use of file parameter crashes Jenkins jobs sometimes
Title: Message Title Colin Ward created an issue Jenkins / JENKINS-34172 Use of file parameter crashes Jenkins jobs sometimes Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2016/Apr/12 1:54 PM Priority: Major Reporter: Colin Ward In all of our Jenkins jobs we have a file parameter that can be passed in. The file is always called "buildspec.txt" and contains information useful for our build tool. This file parameter is optional. 99% of time this works perfectly but sometimes when triggering a build, Jenkins crashes when trying to copy the file. This is when the file has not been passed in. If I try doing the build again after the crash (again, without passing in any file) then it works. I get the following output on the build console: Copying file to buildspec.txt FATAL: java.lang.NullPointerException java.io.IOException: java.lang.NullPointerException at hudson.FilePath.copyFrom(FilePath.java:900) at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:147) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.NullPointerException at hudson.FilePath.copyFrom(FilePath.java:896) ... 7 more We are using Jenkins 1.580.3. I have Googled and also searched your Jira but cannot find anyo
[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory
Title: Message Title Daniel Beck commented on JENKINS-32455 Re: Artifacts lost when renaming matrix project with custom Build record directory Still cannot reproduce (Jenkins 2.0-rc-1 and Matrix Project Plugin 1.6). I configured the custom builds directory $JENKINS_HOME/builds/$ITEM_FULLNAME mostly for testing convenience. Created matrix project 'foo', with axis FOO and value 'bar', built twice, renamed to foo-renamed, built a third time, and this is on disk: foo-renamed foo-renamed/1 foo-renamed/1/build.xml foo-renamed/1/changelog.xml foo-renamed/1/log foo-renamed/2 foo-renamed/2/build.xml foo-renamed/2/changelog.xml foo-renamed/2/log foo-renamed/3 foo-renamed/3/build.xml foo-renamed/3/changelog.xml foo-renamed/3/log foo-renamed/FOO=bar foo-renamed/FOO=bar/1 foo-renamed/FOO=bar/1/archive foo-renamed/FOO=bar/1/archive/foo foo-renamed/FOO=bar/1/build.xml foo-renamed/FOO=bar/1/changelog.xml foo-renamed/FOO=bar/1/log foo-renamed/FOO=bar/2 foo-renamed/FOO=bar/2/archive foo-renamed/FOO=bar/2/archive/foo foo-renamed/FOO=bar/2/build.xml foo-renamed/FOO=bar/2/changelog.xml foo-renamed/FOO=bar/2/log foo-renamed/FOO=bar/3 foo-renamed/FOO=bar/3/archive foo-renamed/FOO=bar/3/archive/foo foo-renamed/FOO=bar/3/build.xml foo-renamed/FOO=bar/3/changelog.xml foo-renamed/FOO=bar/3/log foo-renamed/FOO=bar/lastStableBuild foo-renamed/FOO=bar/lastSuccessfulBuild foo-renamed/FOO=bar/legacyIds foo-renamed/lastFailedBuild foo-renamed/lastStableBuild foo-renamed/lastSuccessfulBuild Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-utility-steps-plugin] (JENKINS-34173) Pipeline snippet generator - build job with password parameter
Title: Message Title Jan Collijs created an issue Jenkins / JENKINS-34173 Pipeline snippet generator - build job with password parameter Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2016/Apr/12 2:04 PM Environment: Jenkins ver. 1.650 Pipeline plugin 2.0 Labels: plugin Priority: Minor Reporter: Jan Collijs When trying to generate a snippet to build a job which has a password parameter through the pipeline plugin it refuses to generate the snippet. in the jenkins.log an error is logged: Caused by: org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class hudson.util.Secret at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:177) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:105) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate_(De
[JIRA] [git-plugin] (JENKINS-34171) Cannot fetch repo from Stash
Title: Message Title Mark Waite resolved as Not A Defect Please don't use bug reports as a way to request help with repository authentication issues. The Jenkins user mailing list has many more people reading it than are reading bug reports to individual plugins. Please send a description of the problem, and the things you've attempted, and the list of what has succeeded and what has failed to the mailing list. Refer to the Jenkins wiki instructions on how to submit a bug report, if you're confident it is a bug in the plugin. Based on the message in this stack trace, and the continued passing of automated tests that use bitbucket.org, I'm confident this is not a bug in the plugin. Jenkins / JENKINS-34171 Cannot fetch repo from Stash Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you ar
[JIRA] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins
Title: Message Title Russell Gallop created an issue Jenkins / JENKINS-34174 Jenkins 2.0-rc1 - Getting started hangs installing plugins Issue Type: Bug Assignee: Unassigned Attachments: GettingStartedHang.png, threadDump.txt Components: core Created: 2016/Apr/12 2:09 PM Environment: jenkins 2.0-rc1 Windows 7 java version "1.8.0_45" Priority: Major Reporter: Russell Gallop Jenkins 2.0-rc1 hangs for me when installing plugins. I started it with a new jenkins home: set JENKINS_HOME=c:\j2 java -jar jenkins-2.0-rc1.war Copy admin password into localhost:8080 Install suggested plugins Some plugins install, others just sit and spin. I have left if for over an hour. There is an exception in the console: java.lang.InstantiationException: jav
[JIRA] [git-plugin] (JENKINS-34165) Null pointer exception polling from git job to bitbucket repo
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-34165 Null pointer exception polling from git job to bitbucket repo Change By: Mark Waite Summary: Null pointer exception polling from git job accessing to bitbucket repo 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-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins
Title: Message Title Daniel Beck commented on JENKINS-34174 Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins The exception is unrelated. It's a bug in a plugin that results in a minor notification to be presented as a big problem. Is your internet connection unstable? While this plugin download is going on, are you able to reach e.g. updates.jenkins-ci.org from the same host? 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-34167) Add Build Step -> Execute Shell returns 500 from render
Title: Message Title Daniel Beck commented on JENKINS-34167 Re: Add Build Step -> Execute Shell returns 500 from render Are you running Jenkins behind a reverse proxy? Does the URL to Jenkins configured in the global configuration match the URL you use to access Jenkins? Are there other resources returning HTTP error codes in then browser's console (e.g. when loading the form)? 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-34164) Jenkins web interface in need of usability and aesthetic improvements
Title: Message Title Daniel Beck closed an issue as Not A Defect This is not actionable. Also, since we're currently reworking large parts of the UI, it's not clear what version of Jenkins you're talking about. For example, in 2.0, the job config screen gets a facelift to make the hierarchy of options easier to see. Jenkins / JENKINS-34164 Jenkins web interface in need of usability and aesthetic improvements Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title Daniel Beck resolved as Cannot Reproduce Cannot reproduce on 1.642.2. While the page "This build requires parameters" appears, submitting the form does not result in a queue item. Apr 12, 2016 4:31:16 PM hudson.model.Executor finish1 SEVERE: Executor threw an exception java.lang.Error: The null Executable has been created for hudson.model.queue.WorkUnit@35711043[work=jobname]. The task cannot be executed at hudson.model.Executor.run(Executor.java:397) This could probably be improved, but Jenkins does not expose the reported problem (anymore). Please make sure issues you report actually occur in current versions of Jenkins. Jenkins / JENKINS-34146 Disabled parametrized jobs could be build from build URL Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title
Daniel Beck edited a comment on JENKINS-34146
Re: Disabled parametrized jobs could be build from build URL
Cannot reproduce on 1.642.2. While the page "This build requires parameters" appears, submitting the form does not result in a queue item.{noformat}Apr 12, 2016 4:31:16 PM hudson.model.Executor finish1SEVERE: Executor threw an exceptionjava.lang.Error: The null Executable has been created for hudson.model.queue.WorkUnit@35711043[work=jobname]. The task cannot be executed at hudson.model.Executor.run(Executor.java:397){ quote noformat }This could probably be improved, but Jenkins does not expose the reported problem (anymore).Please make sure issues you report actually occur in current versions of Jenkins.
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-34164) Jenkins web interface in need of usability and aesthetic improvements
Title: Message Title Alper Cugun commented on JENKINS-34164 Re: Jenkins web interface in need of usability and aesthetic improvements Maybe then make it actionable? That facelift sounds like a good idea and I look forward to seeing that and a lot more in an upcoming version. 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-34118) long page load times in pluginManager/available
Title: Message Title Daniel Beck commented on JENKINS-34118 Re: long page load times in pluginManager/available Cannot reproduce in 2.0-rc-1. James Nord Could you take a thread dump or two while the page is loading? 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-34167) Add Build Step -> Execute Shell returns 500 from render
Title: Message Title Justin Bramley commented on JENKINS-34167 Re: Add Build Step -> Execute Shell returns 500 from render We're running apache as the frontend with tomcat behind it, so in the words of our SA, "technically yes." The URL in jenkins.model.JenkinsLocationConfiguration.xml is the URL I use to access the site. No other resources return 500 when loading the configuration form (or anywhere else that I've seen). 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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34175) It does not seem possible to execute an orchestrator workflow that requires no user input.
Title: Message Title Bob Kraemer created an issue Jenkins / JENKINS-34175 It does not seem possible to execute an orchestrator workflow that requires no user input. Issue Type: Bug Assignee: Agila Govindaraju Components: vmware-vrealize-orchestrator-plugin Created: 2016/Apr/12 2:43 PM Environment: Jenkins Master (CentOS) 1.609.1 LTS vmware-realize-orchestrator-plugin version 2.0 Java version: JDK1.8 Orchestrator vApp version 7.0.1 Priority: Minor Reporter: Bob Kraemer It does not seem possible to execute an orchestrator workflow that requires no user input. (Example = all orchestrator workflow inputs are set as attributes). When the plugin has nothing to pass, the jenkins console reports there has been a "HTTP/1.1 400 Bad Request" Jenkins Console Output: 07:35:15 Started by user anonymous 07:35:15 [EnvInject] - Loading node environment variables. 07:35:15 Building remotely on anonymous in workspace F:\jenkins\workspace\anonymous_orchestrator_jenkins_send_notification_null 07:35:16 Starting Orchestrator workflow execution : a18ceeea-e29e-4d04-8f73-4733e63f76d4 07:35:19 FATAL: Server responded with status code HTTP/1.1 400 Bad Request 07:35:19 java.io.IOException: Server responded with status code HTTP/1.1 400 Bad Request 07:35:19 at com.vmware.vro.jenkins.plugin.OrchestratorCallable.call(OrchestratorCallable.java:66) 07:35:19 at com.vmw
[JIRA] [github-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level
Title: Message Title Armando Fernandez assigned an issue to Armando Fernandez Jenkins / JENKINS-33305 Ability to configure branch name filters at organization folder level Change By: Armando Fernandez Assignee: Armando Fernandez 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-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level
Title: Message Title Armando Fernandez started work on JENKINS-33305 Change By: Armando Fernandez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34177) Pipeline Multibranch Not Cleaning Workspaces
Title: Message Title Mike Kelly created an issue Jenkins / JENKINS-34177 Pipeline Multibranch Not Cleaning Workspaces Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/12 3:01 PM Labels: workflow Priority: Minor Reporter: Mike Kelly When working with many short-lived feature branches, Jenkins can start to eat up a lot of disk space by leaving old workspaces around from old builds. This seems to be especially true with the Pipeline Multibranch Plugin. When that plugin deletes the job for a branch when the branch is deleted, it should simultaneously clean up any of the workspaces created for that branch job (e.g. "feature-foo", "feature-foo@2", "feature-foo@3", etc). Add Comment
[JIRA] [github-organization-folder-plugin] (JENKINS-34176) Trigger when Github tag is pushed
Title: Message Title Pete Wagner created an issue Jenkins / JENKINS-34176 Trigger when Github tag is pushed Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Apr/12 3:01 PM Priority: Minor Reporter: Pete Wagner As a github-organization-folder-plugin user, I want to trigger a pipeline when a Github tag/release is created, So that I can perform special release tasks. i.e. when 1.0.0 is tagged, publish project:1.0.0 docker image. Add Comment
[JIRA] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.
Title: Message Title Bob Kraemer created an issue Jenkins / JENKINS-34178 There *may* be a problem with the vm@VC:VirtualMachine parameter name. Issue Type: Bug Assignee: Agila Govindaraju Components: vmware-vrealize-orchestrator-plugin Created: 2016/Apr/12 3:02 PM Environment: Jenkins Master (CentOS) 1.609.1 LTS vmware-realize-orchestrator-plugin version 2.0 Java version: JDK1.8 Orchestrator vApp version 7.0.1 Priority: Minor Reporter: Bob Kraemer There may be a problem with the vm@VC:VirtualMachine parameter name. As an example, I have two jenkins jobs, each job passing a single parameter to it's linked orchestrator workflow (Copy file from vCO to guest). The only difference between the two scenarios is that in one case (the failure) Jenkins uses the vm@VC:VirtualMachine parameter name as the sole input to the orchestrator workflow. In the case that succeeds, the VM variable is set in the orchestrator workflow as an attribute, and the jenkins job passes another variable, instead (the VM password) as the sole parameter passed from jenkins to orchestrator. Other than the change to the single input type passed by jenkins (vm@VC:VirtualMachine parameter versus VM Password) all other aspects appear identical. When I manually run the orchestrator workflow from the failed scenario in workflow designer, the workflow runs fine after specifying the VC:VirtualMachine input parameter.
[JIRA] [github-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level
Title: Message Title Armando Fernandez commented on JENKINS-33305 Re: Ability to configure branch name filters at organization folder level Filed PR 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-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins
Title: Message Title Russell Gallop commented on JENKINS-34174 Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins > Is your internet connection unstable? I don't have any other problems with it. > While this plugin download is going on, are you able to reach e.g. updates.jenkins-ci.org from the same host? I can reliably ping updates.jenkins-ci.org while it hangs. I did have both wired and wireless network connections enabled but I've just recreated it with just wired. 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.
