[JIRA] [git-plugin] (JENKINS-7423) Git polling doesn't execute concurrent builds if necessary
Jan Klass commented on JENKINS-7423 Git polling doesnt execute concurrent builds if necessary Why was this closed as won’t fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jan Klass commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace I still don’t see why a polling workspace would be necessary. Most of the use-case described here seems like a bug report rather than an improvement. What are the actions to be taken that would make a workspace or repository clone necessary? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-26895) Exception if Dashboard View plugin is not installed
ikedam updated JENKINS-26895 Exception if Dashboard View plugin is not installed That looks caused by release-plugin. Uninstalling release-plugin or installing dashboard-view plugin should resolve the problem. Change By: ikedam (13/Feb/15 9:48 AM) Assignee: PeterHayes Component/s: release-plugin Component/s: copyartifact-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-22581) Git Publisher - please allow ordering of actions
Kanstantsin Shautsou commented on JENKINS-22581 Git Publisher - please allow ordering of actions I have exact the same issue, have in plans to fix. The only thing i think that this Publisher should be splitted to multiple publishers because there are cases when you want reorder post-build actions and you can't do it with monolith publisher. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars-plugin] (JENKINS-26953) Support for workflow-plugin
Jean Detoeuf created JENKINS-26953 Support for workflow-plugin Issue Type: Improvement Assignee: Jesse Glick Components: build-user-vars-plugin, workflow-plugin Created: 13/Feb/15 9:02 AM Description: The user build vars plugin is not available for a workflow job. This plugin should either be made available to workflow jobs or the variables could be directly generated in the workflow plugin, just as the job parameters are made available as variables inside workflow jobs. Environment: 1.598 workflow-plugin 1.2 user-build-vars-plugin 1.4 Project: Jenkins Labels: workflow-plugin build-user-vars-plugin Priority: Minor Reporter: Jean Detoeuf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy updated JENKINS-26952 build selector last successful matrix sub-build Change By: lode leroy (13/Feb/15 9:04 AM) Description: Iwouldliketoknowhowtobettertousethematrixreloadedfeatureincombinationwiththecopyartefacts.Ihaveamatrixbuildthathas 3 2 dimensions:component,platformserver,win=OK,build=1client,win,=OK,build=1client,mac=OK,build=1attheend,theartefactsarearchived.server,win=OK,build=2client,win=FAILclient,mac=OK,build=2whenoneofthose6fails,Iwouldliketobeabletodoanewbuild,torebuildthefailedcomponentclient,win=OK,build=3now,Ihaveanotherbuildthatdoesacopyartefactsfromthismatrixbuild.Iwouldlikeabuildselectortousethefollowingbuilds:server,win=OK,build=2client,win=OK,build=3client,mac=OK,build=2now,thefailedbuild(2nd)doesnotcopytheartifacts,andthelastsuccessfulbuild(3rd)onlycopiesthearchivedartefactsfromthatbuild.soIendupwithserver,win=OK,build=1client,win=OK,build=3client,mac=OK,build=1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26897) Specify true/false values for boolean parameter
elygre commented on JENKINS-26897 Specify true/false values for boolean parameter In our use case, there is no external build script. Instead, everything is handled by the "Invoke Gradle Script" build step. First, the parameters section specifies two input parameters: "version" and "refreshDependencies". They are both string parameter, even though the use case calls for the second one to be boolean (refresh or not). Second in the "Invoke Gradle Script" build step, there is an input box named "switches". In this box we currently put "Pversion=$version $refreshDependencies". There is no external script before, and since the parameter "-refresh-dependencies" is parsed by gradle before the script itself starts, we have no way of translating the value ourselves. In short: 1) As far as I can tell, it is today not possible to use a boolean parameter to decide whether to pass a switch or not to the built-in gradle support, even though that is the perfect use case for a boolean parameter. 2) The workaround is simple, but kinda removes the motivation for a boolean parameter. After all, everybody could use a string parameter and tell users to enter "true" or "false" themselves Therefore, I respectfully disagree. Jenkins should have a built-in mechanism for translating a boolean parameter to the string value required later on, if you need something else than "true" and "false". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26662) Sauce connect options does not allow the use of more than one environment variable at a time
Ross Rowe started work on JENKINS-26662 Sauce connect options does not allow the use of more than one environment variable at a time Change By: Ross Rowe (13/Feb/15 9:10 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26662) Sauce connect options does not allow the use of more than one environment variable at a time
Ross Rowe assigned JENKINS-26662 to Ross Rowe Sauce connect options does not allow the use of more than one environment variable at a time Change By: Ross Rowe (13/Feb/15 9:10 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy closed JENKINS-26952 as Not A Defect build selector last successful matrix sub-build Change By: lode leroy (13/Feb/15 9:20 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Daniel Beck commented on JENKINS-26947 Unattended wait in the remoting code Is this a security issue? E.g. is this exploitable by third parties to disrupt network reachable Jenkins service? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Jan Klass commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Is this bug the cause for the following issue? Through defining the refspec we fetch tags into the local branches directory, so we can build any release tags with a branch-wildcard-trigger. Occasionaly, a tag will be built again. It seems to only be the second most recent one though, when the most recent one is built after a notify-trigger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working with plugin version 1.0.16 and Jenkins 1.563. Should we update? Or need to be fixed in the plugin! Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Daniel Beck commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin This may look like progress, but it's not IMO. Just see INFRA-234, severe issue (for both core devs and users) open for almost a week that should have a really simple fix. FWIW the last two scheduled weekly releases of Jenkins didn't happen either. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:25 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK What bothers me is that the behaviour of the job is changed unexpectedly. When I configure a job to use a specific JVM, I expect that it will always use that JVM. This is especially important for test jobs. Logging it would already be a big improvement. BTW, I do think the fact that JAVA_HOME is set empty is an actual bug. If Jenkins falls back to the system JDK, JAVA_HOME should be set accordingly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:29 AM) Description: InoticedthatwhenthereisnoinstalleravailableforaJDK,theJAVA_HOMEenvironmentvariablewillbeemptyintheenvironmentofabuild.ThiswillhappenforexamplewhenthereisnoinstallerconfiguredforaJDK.Inthatcaseitsnothardtofindthecause.ButforthecaseIdescribebelowitsmuchhardertofindoutwhyJAVA_HOMEisempty.ThereforeIthink abuild logging should failorJAVA_HOMEshouldnot be set improved whenaspecificJDKisconfiguredforthatbuildandnoinstallerisavailableforthatJDK. FurthermoreJAVA_HOMEshouldbesettomatchthedefaultJVM. Herearethestepstoreproduce:-ConfiguretwoJDKs,namedJDK1andJDK2(becauseifyouhaveonlyoneJDKyoucantselectoneinajob)-AddanExtract*.zip/*.tar.gzinstallertoJDK1andsetthelabelforthisinstallertojdk1,soitwontbeavailableforinstallationonnodestowhichthislabelisnotassigned-CreateafreestylejobandselectJDK1asJDK-RunthejobandcheckthatJAVA_HOMEisempty This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy created JENKINS-26952 build selector last successful matrix sub-build Issue Type: New Feature Assignee: Unassigned Components: copyartifact-plugin Created: 13/Feb/15 8:28 AM Description: I would like to know how to better to use the "matrix reloaded" feature in combination with the "copy artefacts". I have a matrix build that has 3 dimensions: component, platform server, win = OK , build=1 client, win, = OK , build=1 client, mac = OK , build=1 at the end, the artefacts are archived. server, win = OK , build=2 client, win = FAIL client, mac = OK , build=2 when one of those 6 fails, I would like to be able to do a new build, to rebuild the failed component client, win = OK , build=3 now, I have another build that does a "copy artefacts" from this matrix build. I would like a build selector to use the following builds: server, win = OK , build=2 client, win = OK , build=3 client, mac = OK , build=2 now, the failed build (2nd) does not copy the artifacts, and the "last successful build" (3rd) only copies the archived artefacts from that build. so I end up with server, win = OK , build=1 client, win = OK , build=3 client, mac = OK , build=1 Environment: Jenkins ver. 1.594 Project: Jenkins Labels: plugin Priority: Minor Reporter: lode leroy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-26954) add ability to put out special message if max retries is hit with no successful build
william schilp created JENKINS-26954 add ability to put out special message if max retries is hit with no successful build Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator-plugin Created: 13/Feb/15 12:56 PM Description: it would be very helpful if naginator could put out a message, or set an environment variable, when the maximum number of retries has been hit without a successful build. at this point, i cannot tell when a job has been completely abandoned due to max retries being exhausted. we use git for version control and i have a sippy straw connection to the main servers at HQ, so the git update tends to fail due to dropped connections. i need to know when the max number of retries has failed so i can know when the build of the product was not attempted because it could not update the code base. Project: Jenkins Labels: enhancement Priority: Minor Reporter: william schilp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Kenneth Baltrinic updated JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Change By: Kenneth Baltrinic (13/Feb/15 1:45 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Kenneth Baltrinic edited a comment on JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Both renaming jobs and deleting them (JENKINS-26652) result in a poisoned queue. Likely other errors also lead to this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
Thomas Kuchel commented on JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job Same here. I'm running 1.580.3 started with "java -jar jenkins.war" call on Windows 7 64-bit running, Maven 3.2.5, jdk1.7.0_67. I have installed just the task-scanner plugin in version 4.44, activated and configured it (files to scan: "src/*/.java"). INFO maven-clean-plugin:2.6.1:clean (default-clean) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-resources-plugin:2.6:resources (default-resources) @ agents-impl INFO Using 'UTF-8' encoding to copy filtered resources. INFO Copying 2 resources WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-compiler-plugin:2.3.1:compile (default-compile) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO INFO maven-surefire-plugin:2.18.1:test (default-test) @ agents-impl ... --- T E S T S --- Running testclass log4j:ERROR Could not connect to remote log4j server at localhost. We will try again later. could not load log4j properties file: /log4j.properties Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.608 sec - in de.biotronik.agents.AbstractAgentServiceImplTest Results : Tests run: 11, Failures: 0, Errors: 0, Skipped: 0 WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-jar-plugin:2.5:jar (default-jar) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-source-plugin:2.4:jar (attach-sources) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; I found out that the Tests weren't recorded by Jenkins: Line "JENKINS Recording test results" is missing, so no test result overview is presented when opening the job url. Same happening for other plugins like checkstyle or findbugs... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Mark Waite resolved JENKINS-20512 as Fixed Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Fixed earlier, then reopened by Marco Lovato with a different bug. Closing it again Change By: Mark Waite (13/Feb/15 12:56 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Mark Waite closed JENKINS-20512 as Fixed Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Change By: Mark Waite (13/Feb/15 12:56 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-line-plugin] (JENKINS-23960) Not able to configure Test report configuration
Michael Stauder commented on JENKINS-23960 Not able to configure Test report configuration Hi, I've encountered the similar issue: Recording NUnit tests results ERROR: Publisher hudson.plugins.nunit.NUnitPublisher aborted due to exception hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:60) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: org.xml.sax.SAXParseException; systemId: file:/C:/Workspace/JenkinsWorkspace/smoketest-ZpiReferenceSwitch/temporary-junit-reports/temp-junit.xml; lineNumber: 3; columnNumber: 9; Content is not allowed in prolog. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.splitJUnitFile(NUnitReportTransformer.java:100) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:71) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55) ... 13 more The temp-junit.xml (partly printed) looks like: ?xml version="1.0" encoding="UTF-8"? nunit.framework Attribute used to apply a category to a test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Christopher Orr commented on JENKINS-26893 Unable to run emulator-arm to start emulator That's JENKINS-11952, for which I'm going to publish a fix today and try and get people to test it out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-23694) git clean fails with submodules (failed to fetch)
Mark Waite updated JENKINS-23694 git clean fails with submodules (failed to fetch) Change By: Mark Waite (13/Feb/15 12:54 PM) Summary: gitclean doesnotwork failswithsubmodules (failedtofetch) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-12804) Promote When the following upstream promotions are promoted does not happen
fransflippo commented on JENKINS-12804 Promote When the following upstream promotions are promoted does not happen Same issue here. I have two qualifications for a promotion: one is that another (upstream) promotion passes, the other is that the promotion is manually approved. However, when I manually approve (and the upstream promotions have already passed), Jenkins still lists the upstream promotions under "Unmet qualifications" even though the have been met! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-26895) Exception if Dashboard View plugin is not installed
Paolo Borelli commented on JENKINS-26895 Exception if Dashboard View plugin is not installed I confirm the execption goes away if I remove the release-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-line-plugin] (JENKINS-23960) Not able to configure Test report configuration
Michael Stauder commented on JENKINS-23960 Not able to configure Test report configuration I see that the spaces are removed, "lineNumber: 3; columnNumber: 9; Content is not allowed in prolog." is at the start of the text "nunit.framework" (8 spaces were removed in the preview comment) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26830) Git plugin using wrong username for committer different from user running build set in user.name and user.email
Mark Waite commented on JENKINS-26830 Git plugin using wrong username for committer different from user running build set in user.name and user.email Does this stackoverflow article on committer vs. author apply in this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-26934) Never ending threads
Vladimir Pavlovic commented on JENKINS-26934 Never ending threads same with for example when view needs to be populated with jobs and for example connection from user perspective is broken: Handling GET /main/view/ : http-10080-101" daemon prio=10 tid=0x7feef40bb000 nid=0x4964 waiting for monitor entry 0x7fef8a8e4000 5014java.lang.Thread.State: BLOCKED (on object monitor) 5015 at hudson.model.View.getActions(View.java:525) 5016 - waiting to lock 0x000742ce9af8 (a hudson.model.ListView) 5017 at sun.reflect.GeneratedMethodAccessor6974.invoke(Unknown Source) 5018 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 5019 at java.lang.reflect.Method.invoke(Method.java:601) Those threads are blocked and only restart of JVM help is this known issue ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26652) SCM Sync fails after deleting a project
Kenneth Baltrinic commented on JENKINS-26652 SCM Sync fails after deleting a project I can confirm, this is still an issue with 0.0.8., moreover it leads to the poisoned queue reported in JENKINS-25786. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
Simon Schlachter started work on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Change By: Simon Schlachter (13/Feb/15 4:54 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-26957) Metadata tag names containing underscores or dots break metadata searching
Ioannis Moutsatsos created JENKINS-26957 Metadata tag names containing underscores or dots break metadata searching Issue Type: Bug Assignee: rsandell Components: metadata-plugin Created: 13/Feb/15 5:12 PM Description: Metadata tag names either from the global metadata configuration or the local one that contain underscores or dots are not searchable. Since metadata are frequently in hierarchies that can be depicted as a series of sub-tags, it would be useful to support these characters in the tag name. Environment: Jenkins-CI v1.593, Windows Server 2008 Project: Jenkins Labels: configuration user-experience search Priority: Major Reporter: Ioannis Moutsatsos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26713) P4Jenkins - Modifying Cilentspec Root
Ryan Hummer commented on JENKINS-26713 P4Jenkins - Modifying Cilentspec Root ah, ok. I'll happily ignore that text. Thanks for the explanation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
SCM/JIRA link daemon commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Code changed in jenkins User: Simon Schlachter Path: pom.xml http://jenkins-ci.org/commit/ci-game-plugin/c8cceef5532af5c8ac167818a97c88cd960371cc Log: JENKINS-24478: bump version numbers of dependencies the version updates are necessary due to api changes in jenkins that break old implementations. in order to support the new api, the min version of jenkins core had to be bumped - and with it the plugins we use (checkstyle, findbugs et. al) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
SCM/JIRA link daemon commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Code changed in jenkins User: Simon Schlachter Path: pom.xml src/test/java/hudson/plugins/cigame/GamePublisherTest.java http://jenkins-ci.org/commit/ci-game-plugin/c773f247881b4d59c67f2ef2d8e5dd49d7853774 Log: JENKINS-24478: fix failing due to new jenkins-core dependencies Compare: https://github.com/jenkinsci/ci-game-plugin/compare/cd6c3b9dfcf4...c773f247881b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
Simon Schlachter assigned JENKINS-24478 to Simon Schlachter Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Change By: Simon Schlachter (13/Feb/15 4:54 PM) Assignee: redsolo SimonSchlachter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Daniel Beck commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK BTW, I do think the fact that JAVA_HOME is set empty is an actual bug. If Jenkins falls back to the system JDK, JAVA_HOME should be set accordingly. The 'Default' or 'System' option of all tools means it uses whatever is on PATH. This has been discussed to death before. For reference see e.g. JENKINS-755, https://github.com/jenkinsci/jenkins/pull/1528, https://github.com/jenkinsci/jenkins/pull/1451. When I configure a job to use a specific JVM, I expect that it will always use that JVM. This is especially important for test jobs. Logging it would already be a big improvement. Try the following: Configure a JDK, set it to NOT auto-install, and leave the path empty. That's what you're effectively doing here. I would be very surprised if the behavior is different from what you're seeing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26897) Specify true/false values for boolean parameter
Daniel Beck commented on JENKINS-26897 Specify true/false values for boolean parameter Jenkins should have The problem is that this actually is a rather specialized use case not a lot of users will face. (And the few interested in this will have a slightly different problem, like wanting to translate the numbers 1-6 to percentages 16, 33, 50, 67, 83, 100).) Adding support for it in core will result in additional clutter for almost everyone while helping very few. There's numerous parameter-related plugins already that can probably do this for you, not to mention env-inject rewriting build parameters in a script. Me saying "This should be done in a plugin" does not mean "This should not be done at all". It just means it makes no sense to add it to Jenkins core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
Sebastian Fischer updated JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job Change By: Sebastian Fischer (13/Feb/15 3:23 PM) Description: WhenIrunamavenmultimodulebuildtherearefrequentwarningsintheconsolelog.[INFO]---maven-clean-plugin:2.5:clean(default-clean)@com.acme.prod.sto---[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---build-helper-maven-plugin:1.9.1:add-source(add-source)@com.acme.prod.sto---[INFO]Sourcedirectory:E:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\stoadded.[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-resources-plugin:2.6:resources(default-resources)@com.acme.prod.sto---[INFO]UsingCp1252encodingtocopyfilteredresources.[INFO]skipnonexistingresourceDirectoryE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\src\main\resources[INFO]skipnonexistingresourceDirectoryE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\src\main\java[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-compiler-plugin:3.2:compile(default-compile)@com.acme.prod.sto---[INFO]Changesdetected-recompilingthemodule![INFO]Compiling132sourcefilestoE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\target\classes[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-checkstyle-plugin:2.13:checkstyle(default)@com.acme.prod.sto---[INFO][WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-resources-plugin:2.6:testResources(default-testResources)@com.acme.prod.sto---[INFO]UsingCp1252encodingtocopyfilteredresources.[INFO]skipnonexistingresourceDirectoryE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\src\test\resources[INFO]skipnonexistingresourceDirectoryE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\src\test\java[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-compiler-plugin:3.2:testCompile(default-testCompile)@com.acme.prod.sto---[INFO]Nosourcestocompile[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-surefire-plugin:2.18.1:test(default-test)@com.acme.prod.sto---[INFO]Testsareskipped.[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-jar-plugin:2.5:jar(default-jar)@com.acme.prod.sto---[INFO]Buildingjar:E:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\target\com.acme.prod.sto-5.4.2-SNAPSHOT.jar[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator;[INFO][INFO]---maven-install-plugin:2.4:install(default-install)@com.acme.prod.sto---[INFO]InstallingE:\Jenkins\workspace\ vCDM_Server_TRUNK prod \com.acme.prod.sto\target\com.acme.prod.sto-5.4.2-SNAPSHOT.jartoE:\MavenRepository\com\acme\collab\common\com.acme.prod.sto\5.4.2-SNAPSHOT\com.acme.prod.sto-5.4.2-SNAPSHOT.jar[INFO]InstallingE:\Jenkins\workspace\ vCDM_Server_TRUNK prod
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
thedug commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue +1 I also noticed that the plugin is only committing changes when I save jenkins settings not when saving changes to projects (I don't even get the commit message popup). I'm not sure when that happened but I have a suspicion that it was related to this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-26955) API token can be extracted from config page after save
Dmitry P created JENKINS-26955 API token can be extracted from config page after save Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 13/Feb/15 4:11 PM Description: Hi everyone, I've noticed that after I save API token at settings page, I can access the token under asterisk using browser's developer console. This is very insecure, token can be seen by anyone who has access to settings. I suspect GitHub shows token only once due to security risks as well. Environment: Jenkins 1.598 ghprb-plugin 1.16-8 Project: Jenkins Labels: plugin security configuration Priority: Major Reporter: Dmitry P This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
SCM/JIRA link daemon commented on JENKINS-25203 support embedded content in json Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java http://jenkins-ci.org/commit/cucumber-testresult-plugin/6f76c44df6160072b84ff60f38f2ff0f6bb56ff3 Log: ISSUE JENKINS-25203 remove redundant import This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26956) perforce timeout option in the plugin
arazauci created JENKINS-26956 perforce timeout option in the plugin Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 13/Feb/15 4:22 PM Description: sometimes, we that our jobs hangs forever because there are some communication issues with perforce. It could be networking issues, p4 servers issues, etc. It would be very helpful to have some timeout option in the P4 SCM section so that the job can be exit out with abort state Project: Jenkins Priority: Major Reporter: arazauci This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26787) Upgrade p4java to 2014.1
Brandon Koepke commented on JENKINS-26787 Upgrade p4java to 2014.1 Hey Paul, any word on when p4-plugin 1.2.0 will be released? Is there anything I can do to help here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26960) Provide support for Integrity 2009 SP6 - 10.4
Cletus DSouza created JENKINS-26960 Provide support for Integrity 2009 SP6 - 10.4 Issue Type: New Feature Assignee: Cletus DSouza Attachments: integrity-plugin.hpi Components: integrity-plugin Created: 13/Feb/15 6:18 PM Description: With the release of integrity-plugin 1.29, there is no support for Integrity 2009 SP6 thru Integrity 10.4. This special one-off integrity-plugin.hpi version has been compiled with Java 1.6 u27 Integrity 2009 SP6 mksapi.jar (4.10.9049) IMPORTANT This version cannot run with Jenkins running on a JRE 1.7 u40 (and higher) due to limitations in the mksapi.jar No additional fixes or updates will be provided to this version. Please use this as a temporary fix to upgrade your Integrity environments to 10.5 (or higher) Environment: Jenkins 1.546 Integrity 2009 SP6, SP7 Integrity 10, 10.1, 10.2, 10.3, 10.4 Project: Jenkins Priority: Minor Reporter: Cletus DSouza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26960) Provide support for Integrity 2009 SP6, SP7, 10, 10.1, 10.2, 10.3 and 10.4
Cletus DSouza updated JENKINS-26960 Provide support for Integrity 2009 SP6, SP7, 10, 10.1, 10.2, 10.3 and 10.4 Change By: Cletus DSouza (13/Feb/15 6:20 PM) Summary: ProvidesupportforIntegrity2009SP6 - ,SP7, 10 ,10 . 1,10.2,10.3and10. 4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26856) Internal Server Error with integrity-plugin version 1.30
Cletus DSouza commented on JENKINS-26856 Internal Server Error with integrity-plugin version 1.30 You might want to try the one off version that is created for versions older than 10.5. While you are on a much older that the one the one off supports, if you were able to use the past versions, then this might still work for you https://issues.jenkins-ci.org/secure/attachment/28595/integrity-plugin.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-20113) Unable to delete metadata job
Ioannis Moutsatsos updated JENKINS-20113 Unable to delete metadata job Metadata configuration and search results are shown in the screenshots demonstrating that searches fail when metadata tag names contain dots or underscores. Change By: Ioannis Moutsatsos (13/Feb/15 5:19 PM) Attachment: Untitled_Clipping_021315_121325_PM.jpg Attachment: Untitled_Clipping_021315_121608_PM.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zentimestamp-plugin] (JENKINS-26958) ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin
Jan-Olav Eide created JENKINS-26958 ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin Issue Type: Bug Assignee: Gregory Boissinot Components: zentimestamp-plugin Created: 13/Feb/15 5:26 PM Description: Using the new workflow plugin, the ZenTimestamper fails with a class cast exception, since it seems to assume that this cast never fails https://github.com/jenkinsci/zentimestamp-plugin/blob/master/src/main/java/hudson/plugins/zentimestamp/ZenTimestampEnvironmentContributor.java#L23 Running: Allocate node : Start Running on master in C:\Jenkins\workspace\Demo workflow Running: Allocate node : Body : Start Running: Subversion Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild at hudson.plugins.zentimestamp.ZenTimestampEnvironmentContributor.buildEnvironmentFor(ZenTimestampEnvironmentContributor.java:23) at hudson.model.Run.getEnvironment(Run.java:2224) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:827) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:106) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at WorkflowScript.run(WorkflowScript:2) Project: Jenkins Priority: Minor Reporter: Jan-Olav Eide This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26830) Git plugin using wrong username for committer different from user running build set in user.name and user.email
Bret Askeland commented on JENKINS-26830 Git plugin using wrong username for committer different from user running build set in user.name and user.email Unfortunately it doesn't. I did some research that also suggested that, but that doesn't seem to be the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26960) Provide support for Integrity 2009 SP6, SP7, 10, 10.1, 10.2, 10.3 and 10.4
Cletus DSouza resolved JENKINS-26960 as Fixed Provide support for Integrity 2009 SP6, SP7, 10, 10.1, 10.2, 10.3 and 10.4 Change By: Cletus DSouza (13/Feb/15 6:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26959) Waiting Job blocks executor causing deadlock
Wofgang Bauer created JENKINS-26959 Waiting Job blocks executor causing deadlock Issue Type: Bug Assignee: Unassigned Attachments: deadlock.png Components: parameterized-trigger-plugin Created: 13/Feb/15 5:59 PM Description: the job "parent_job" has a param. trigger build-step, which called the job "child_job" and blocks "parent_job" till "child_job" is finished. This causes a deadlock, because the one executor is consumed by the "parent_job", although it is just waiting. So the "child_job" will never get an available executor. Is it possible to release the executor during the waiting time to make it available for other jobs? Environment: Jenkins Version: jenkins-1.598-1.1 OS: CentOs 6.6 x86_64 Parameterized Trigger Plugin Version: 2.25 Nr of Executors: 1 Project: Jenkins Labels: plugin jenkins Priority: Critical Reporter: Wofgang Bauer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-20113) Unable to delete metadata job
Ioannis Moutsatsos edited a comment on JENKINS-20113 Unable to delete metadata job SORRY!! It seems that my attachments destined for JENKINS-26957 were attached here by mistake. Could somebody delete please! Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-26957) Metadata tag names containing underscores or dots break metadata searching
Ioannis Moutsatsos updated JENKINS-26957 Metadata tag names containing underscores or dots break metadata searching Metadata configuration and search results are shown in the screenshots demonstrating that searches fail when metadata tag names contain dots or underscores. Change By: Ioannis Moutsatsos (13/Feb/15 5:24 PM) Attachment: Untitled_Clipping_021315_121608_PM.jpg Attachment: Untitled_Clipping_021315_121325_PM.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26713) P4Jenkins - Modifying Cilentspec Root
Paul Allen closed JENKINS-26713 as Fixed P4Jenkins - Modifying Cilentspec Root Resolved 1.1.4 Change By: Paul Allen (13/Feb/15 5:15 PM) Status: Resolved Closed Assignee: PaulAllen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26713) P4Jenkins - Modifying Cilentspec Root
Paul Allen commented on JENKINS-26713 P4Jenkins - Modifying Cilentspec Root No problem, it had me confused for a while. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26788) Integrity Plugin cannot complete connection to MKS Integrity 2009
Cletus DSouza commented on JENKINS-26788 Integrity Plugin cannot complete connection to MKS Integrity 2009 I've created a one-off version for folks on versions older than 10.5. Please try this one and see disclaimer on the wiki - https://issues.jenkins-ci.org/secure/attachment/28595/integrity-plugin.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
SCM/JIRA link daemon commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java http://jenkins-ci.org/commit/android-emulator-plugin/7949052acba9181ede1ecfed630b0059f113e9de Log: JENKINS-11952 Return to the "localhost:" style of connecting to emulators. For some reason, connecting to the emulator in this manner appears to be somwehat more reliable than connecting with the regular "emulator-" style. From the various JIRA issues opened against the most recent plugin releases, this instability seems to affect Mac OS X more than other operating systems. Now we use "localhost:", while sticking to a four-digit port number, as some tools seem to assume that the emulator port is always four-digits. While it's still a problem that ddmlib — as used by tools like the Maven Android plugin — only recognise emulators with the "emulator-" scheme, this should not be a problem, as the emulator itself at startup registers with adb in this style. While this means that running "adb devices" may show two connected devices (e.g. "emulator-5554" and "localhost:"), libraries like ddmlib will use the "emulator" variant, while build steps that call `adb` will automatically read the ANDROID_SERIAL environment vairable and use the "localhost" variant. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
SCM/JIRA link daemon commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java http://jenkins-ci.org/commit/android-emulator-plugin/5bdae99c654d40416a37af1bd3cca30f9db11543 Log: Revert "JENKINS-11952 Remove redundant (dis)connect calls while waiting for startup." This reverts commit f2fcd2f7d9c12cfd9b8de7cb3ae18049ef056db7. This is required as, per the previous commit, we're using the "localhost" style of emulator connection string once again. Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/bd2fbec33e6f...5bdae99c654d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: ORACLE DBA
Hi Greetings from *SREE INFOTECH LLC*!!! Hope you are doing great. It was nice talking to you .Please find the below hot list and let me know if you have any matching requirement for my consultants. Please send your requirements to *suni...@sreeinfotech.com* suni...@sreeinfotech.com *Oracle DBA* Consultant Name :* SARADHI* Location:* Chicago , IL* Relocation : *Yes * Visa : *H1B * Availability : *Immediately* Please add my id suni...@sreeinfotech.com in your mailing list and send me your requirements on a daily basis. For further info, please contact me immediately!! Looking forward to work with you… *Thanks Regards,* *Sunitha * *Sree Infotech LLC || **9901 E. Valley Ranch Parkway, Suite 3008,* * Irving, TX 75063 || Phone: 972-332-3471 Extn 114 **Email Id: * suni...@sreeinfotech.com *Gtalk/YM: **archana.sreeinfo* *Note:** We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your email address in the body. Include Complete Address and/or Domain/Aliases to be removed.* -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. Saradhi.Resume.docx Description: MS-Word 2007 document
[JIRA] [warnings-plugin] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
Ulli Hafner resolved JENKINS-11225 as Fixed Add aggregation and subview for multi-configuration projects Closing this issue since the initial request is fixed. Two additional issues are still open: JENKINS-26913: add the configuration names to the warnings and visualize these properties in the detail view JENKINS-25905: add additional configuration options to the aggregated graph that (one graph per configuration). Please use one of these issues for comments. Change By: Ulli Hafner (13/Feb/15 8:19 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb So.. I switched back to the seemingly more reliable "localhost-" way of connecting to emulators, while also making sure we stick to four-digit port numbers for compatibility with (older) tools that depend on that. While I've often found these problems hard to reproduce, I've been doing lots of testing on a MacBook Pro, as Mac OS X seemed to be the OS worst affected by various "device offline" issues. The current code seems to work fairly reliably on OS X (and on Linux), and I've made a bunch of other improvements to the plugin recently. Everything tends to work pretty smoothly in my large test Jenkins jobs, where I set up a matrix of about ten different Android OS versions and get them to start up, and run an adb command. However, I still very often see unexplained failures on OS X when making the job do something useful, like installing an APK. I've tried running the jobs in serial, and disabling the background logcat thread (i.e. to minimise any disruptions to the emulator and adb), yet APK installation will either time out, or the adb connection will vanish. Anyway, it would be great if as many people as possible could test the latest build of the plugin. Download the ".hpi" file from the following link, then you can upload it to your Jenkins instance via the Plugin Manager Advanced Upload; you will then need to restart Jenkins: https://jenkins.ci.cloudbees.com/job/plugins/job/android-emulator-plugin/lastStableBuild/org.jenkins-ci.plugins$android-emulator/ I would like to do a plugin release within the next week or so, though the Jenkins infrastructure for releasing is currently down (INFRA-240). All the more reason to get testing. Thanks, everyone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
Ernestas Lukoševičius commented on JENKINS-26558 createSlave Node name collision avoidance creates dead nodes That's actually of a high priority... All it takes to take down a cluster is plug out the wire for a second, Jenkins swarm clients loose connections and then try to reconnect, while Jenkins has not yet forgot about the previous slaves. I think that checking if a node (slave in my dictionary) is online should be done more often and better, especially when there are name collisions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Yoann Dubreuil commented on JENKINS-26947 Unattended wait in the remoting code You must be on the path of the network stream to be able to change the packet content. Even if you are able to get there, the SSH protocol protects the content of the stream. You would only be able to trigger a disconnection, but at this stage, I bet a lot of other network services are in danger. So for me, it's not a security issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)
Daniel Beck commented on JENKINS-12543 CliAuthenticator (username/password) called too late to parse arguments (like job names) Having all jobs that need to be run from Jenkins-cli.jar to have read access for anonymous, is not a good thing Is anything preventing anyone from just using SSH key authentication instead of username/password? (Real restrictions, not "My IT department won't allow it") https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI#JenkinsCLI-1.419andlater This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
Ernestas Lukoševičius edited a comment on JENKINS-26558 createSlave Node name collision avoidance creates dead nodes That's actually of a high priority to some... All it takes to take down a cluster is plug out the wire for a second, Jenkins swarm clients loose connections and then try to reconnect, while Jenkins has not yet forgot about the previous slaves. I think that checking if a node (slave in my dictionary) is online should be done more often and better, especially when there are name collisions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Daniel Beck commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Workaround: Disable this plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
Ulli Hafner edited a comment on JENKINS-11225 Add aggregation and subview for multi-configuration projects Closing this issue since the initial request is fixed. Two additional issues are still open: JENKINS-26913: add the configuration names to the warnings and visualize these properties in the detail view JENKINS-25905: add additional configuration options to the aggregated graph that (one graph per configuration). Please use one of these issues for comments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-26962) When adding a second JIRA site, none of the sites is working anymore
Michael Rumpf created JENKINS-26962 When adding a second JIRA site, none of the sites is working anymore Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 13/Feb/15 11:31 PM Description: We have one site and the plugin works. IDs in the SVN commit comments are replaced by a link to the JIRA issue. As soon as I add a second site, none of the sites is working anymore, so the already working links get removed again. Project: Jenkins Priority: Blocker Reporter: Michael Rumpf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-10727) hudson-cli.jar login does not work together with Collabnet TeamForge
Roy Wright commented on JENKINS-10727 hudson-cli.jar login does not work together with Collabnet TeamForge Generated pull request (https://github.com/jenkinsci/collabnet-plugin/pull/5) to add Basic Authentication to support CLI and web API access. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-26961) build statistics which only consider the latest build of each job
Dirk Thomas created JENKINS-26961 build statistics which only consider the latest build of each job Issue Type: New Feature Assignee: Peter Hayes Components: dashboard-view-plugin Created: 13/Feb/15 9:25 PM Description: Currently the build statistics aggregate the numbers from the last ten builds of each job. But I would like to see only the "current" stats - it doesn't matter to be if a build had a different state before. If the max number of builds could be configured to e.g. "1" that would enable this use case. Project: Jenkins Priority: Minor Reporter: Dirk Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26662) Sauce connect options does not allow the use of more than one environment variable at a time
SCM/JIRA link daemon commented on JENKINS-26662 Sauce connect options does not allow the use of more than one environment variable at a time Code changed in jenkins User: Ross Rowe Path: pom.xml src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/4deb1a2774c6bca9e007cdb0029bbefc82072d68 Log: JENKINS-26662 Use Jenkins utility method to resolve variables Compare: https://github.com/jenkinsci/sauce-ondemand-plugin/compare/2b75a34c1857...4deb1a2774c6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas created JENKINS-26963 Form too large when applying changes Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 14/Feb/15 12:08 AM Description: After upgrading Jenkins and all my plugins to the latest versions, I can no longer commit changes to certain jobs due to their size. Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 21354920 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
P Oh commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb forgot to add, plugin version: 2.13-SNAPSHOT (private-5bdae99c-jenkins) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas commented on JENKINS-26963 Form too large when applying changes Seems like a duplicate of JENKINS-20327. I was able to workaround this by adding -Dorg.eclipse.jetty.server.Request.maxFormContentSize=50 in the arguments XML node of my jenkins.xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-12815) Add an option to select Build status when no Test is found
Dirk Thomas commented on JENKINS-12815 Add an option to select Build status when no Test is found +1 since I generate jobs from a template from thousands of projects I simply don't know if a project will generate test results files or not. Using the `xunit` plugin instead (which has the requested configuration option) does not work for me either since it is much stricter when validating the xml files. As a temporary fix I conditionally generate a dummy result file. But that "pollutes" all test statistics. I do understand the fine line of flexibility vs. bloated but this seems to break a use case several users are having. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
P Oh
commented on JENKINS-11952
Emulator occasionally hangs indefinitely on startup, unable to connect adb
Master server:
ubuntu 14.04
jenkins version 1.596
slave:
ubuntu 14.04
java version "1.7.0_72"
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)
android sdk tools 24.0.2
android platform tools 21
android sdk build-tools 21.1.2
It seems to connect at some point but does not validate the connection correctly. Heres my semi-sanitized build log. Let me know where I can locate any other logs which may be of help.
Started by upstream project "ad-pipeline" build number 36
originally caused by:
Started by an SCM change
EnvInject - Loading node environment variables.
Building remotely on android-slave (android) in workspace *
Cloning the remote Git repository
Cloning repository *
/usr/bin/git init * # timeout=10
Fetching upstream changes from *
/usr/bin/git --version # timeout=10
using GIT_SSH to set credentials *
/usr/bin/git -c core.askpass=true fetch --tags --progress * +refs/heads/:refs/remotes/origin/
/usr/bin/git config remote.origin.url * # timeout=10
/usr/bin/git config remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
/usr/bin/git config remote.origin.url * # timeout=10
Fetching upstream changes from *
using GIT_SSH to set credentials *
/usr/bin/git -c core.askpass=true fetch --tags --progress * +refs/heads/:refs/remotes/origin/
/usr/bin/git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
/usr/bin/git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision * (refs/remotes/origin/develop)
/usr/bin/git config core.sparsecheckout # timeout=10
/usr/bin/git checkout -f *
/usr/bin/git rev-list * # timeout=10
Allocating TCP port AD_PIPELINE_INSTRUMENTATION_PORT
- Assigned 48374
TCP port allocation complete
$ /opt/android-sdk-linux/tools/android list target
android Using Android SDK: /opt/android-sdk-linux
android Creating Android AVD: */ad-pipeline-instrumentation/19/.android/avd/hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins.avd
android /opt/android-sdk-linux/tools/android create avd -f -a -c 200M -s 1080x1920 -n hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins -t "Google Inc.:Google APIs:18" --abi armeabi-v7a
android Waiting 10 seconds before starting emulator...
$ /opt/android-sdk-linux/platform-tools/adb start-server
daemon not running. starting it now on port 7700 *
daemon started successfully *
$ /opt/android-sdk-linux/platform-tools/adb start-server
android Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator64-arm -no-boot-anim -ports 7698,7699 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_320_1080x1920_Google_Inc._Google_APIs_18_armeabi-v7a_jenkins -no-snapshot-load -no-snapshot-save -no-window -no-audio -gpu off
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
connected to localhost:7699
android Waiting for emulator to finish booting...
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
error: device offline
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$ /opt/android-sdk-linux/platform-tools/adb -s localhost:7699 shell getprop init.svc.bootanim
$ /opt/android-sdk-linux/platform-tools/adb connect localhost:7699
$
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml execution idcheck-coverage/id goals goalcheck/goal /goals configuration rules rule elementBUNDLE/element excludes exclude*api*/exclude /excludes limits limit counterLINE/counter valueCOVEREDRATIO/value minimum0.25/minimum /limit /limits /rule /rules /configuration /execution And the plugin works well. No api is wisible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml execution idcheck-coverage/id goals goalcheck/goal /goals configuration rules rule elementBUNDLE/element excludes exclude*api*/exclude /excludes limits limit counterLINE/counter valueCOVEREDRATIO/value minimum0.25/minimum /limit /limits /rule /rules /configuration /execution And the plugin works well. No api is visible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-17662) Sometime Jenkins could not checkout code from SVN
Stephan Grimm commented on JENKINS-17662 Sometime Jenkins could not checkout code from SVN Does anybody have any news? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26944) Subversion plugin does not resolve environment variables for SCM polling
Tim Bradt commented on JENKINS-26944 Subversion plugin does not resolve environment variables for SCM polling In the Jenkins system configuration, under Global Properties. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25565) data.buildDuration always 0
Rusty Gerard closed JENKINS-25565 as Fixed data.buildDuration always 0 Change By: Rusty Gerard (14/Feb/15 4:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25673) Add test results to the output
Rusty Gerard closed JENKINS-25673 as Fixed Add test results to the output Change By: Rusty Gerard (14/Feb/15 4:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Rusty Gerard closed JENKINS-25944 as Fixed Version 1.0.2 fails with stacktrace Change By: Rusty Gerard (14/Feb/15 4:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25674) version and @version duplicates
Rusty Gerard closed JENKINS-25674 as Fixed version and @version duplicates Change By: Rusty Gerard (14/Feb/15 4:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4409) Hudson test case leaks temp folders
ikedam commented on JENKINS-4409 Hudson test case leaks temp folders I verified URLConnection.setDefaultUseCaches(false) works as expected. I wrote workarounds on https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test+on+Windows#UnitTestonWindows-Jenkinscorecachesandkeepfilehandles We'd better to consider not to modify sezpoz and localizer but to modify test classes in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26891) copyartifact 1.34 requires update matrix-project plugin
SCM/JIRA link daemon resolved JENKINS-26891 as Fixed copyartifact 1.34 requires update matrix-project plugin Change By: SCM/JIRA link daemon (14/Feb/15 2:06 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-20546) Preserve symlinks when copying artifacts
SCM/JIRA link daemon commented on JENKINS-20546 Preserve symlinks when copying artifacts Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/085c4c9f1860df993a4617741b6b36fe9441b3a0 Log: FIXED JENKINS-20546 Preserve symlinks when copying artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-20546) Preserve symlinks when copying artifacts
SCM/JIRA link daemon commented on JENKINS-20546 Preserve symlinks when copying artifacts Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/5cfa07b8bac9caeb664b9c99c1891e206a89fd3d Log: Merge pull request #57 from jglick/symlinks-JENKINS-20546 JENKINS-20546 Preserve symlinks when copying artifacts Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/68a64c09a744...5cfa07b8bac9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26891) copyartifact 1.34 requires update matrix-project plugin
SCM/JIRA link daemon commented on JENKINS-26891 copyartifact 1.34 requires update matrix-project plugin Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/copyartifact-plugin/fcda946a4321cf30657cdcbda5756f0c1fe6f240 Log: FIXED JENKINS-26891 Now depends on matrix-project plugin 1.3, which is bundled in Jenkins 1.580.1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26891) copyartifact 1.34 requires update matrix-project plugin
SCM/JIRA link daemon commented on JENKINS-26891 copyartifact 1.34 requires update matrix-project plugin Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/copyartifact-plugin/47e05f2703db981af163f7144f0e657822fea275 Log: Merge pull request #58 from ikedam/feature/JENKINS-26891_downgradeMatrixPlugin JENKINS-26891 Depends on matrix-project plugin bundled in Jenkins core Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/5cfa07b8bac9...47e05f2703db This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-20546) Preserve symlinks when copying artifacts
SCM/JIRA link daemon resolved JENKINS-20546 as Fixed Preserve symlinks when copying artifacts Change By: SCM/JIRA link daemon (14/Feb/15 2:06 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas updated JENKINS-26963 Form too large when applying changes Reducing Priority since there is a workaround. Change By: Arun Thomas (14/Feb/15 2:15 AM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
ikedam started work on JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Change By: ikedam (14/Feb/15 2:33 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
SCM/JIRA link daemon commented on JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/6eab69d0972fdd508da88a39b7a90e9a2042cb65 Log: JENKINS-14999 Enabled tests for QueueItemAuthenticator as copyartifact now targets for Jenkins 1.580.1 1.521. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
SCM/JIRA link daemon commented on JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/ec41cbdd914d33d606734b8f36460efc25913af4 Log: Merge pull request #60 from ikedam/feature/JENKINS-14999_EnableTestsForQueueItemAuthentication JENKINS-14999 Enabled tests for QueueItemAuthenticator Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/47e05f2703db...ec41cbdd914d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-26918) Add workflow support
ikedam commented on JENKINS-26918 Add workflow support You can write groovy scripts in workflows. What feature of groovy-postbuild do you want use in workflows? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
