[JIRA] [core] (JENKINS-28493) test results not displaying properly
Title: Message Title Mikolaj R created an issue Jenkins / JENKINS-28493 test results not displaying properly Issue Type: Bug Assignee: Unassigned Attachments: testdisplay.png Components: core Created: 20/May/15 6:58 AM Environment: Jenkins 1.613 Priority: Major Reporter: Mikolaj R When clicking Test Result in a Build view, the new page does not display properly - Test Result is displayed under the menu (screen shot attached). This happens only when the user is logged in. If logged out the layout is good. Any idea what could be the cause?
[JIRA] [rqm-plugin] (JENKINS-28483) Zero test cases found when running against RQM 4.0.5 (Praqma case 13042)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-28483 Zero test cases found when running against RQM 4.0.5 (Praqma case 13042) Change By: Bue Petersen Summary: ZerotestcasesfoundwhenrunningagainstRQM4.0.5 (Praqmacase13042) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-21169) ClassCastException from MultiSCMRevisionState to CloneWorkspaceSCM
Title: Message Title Sebastian Schuberth edited a comment on JENKINS-21169 Re: ClassCastException from MultiSCMRevisionState to CloneWorkspaceSCM [~rodrigc]Whatmakesyou thing think thisisadupeofJENKINS-27638as1)thestacktraceisdifferent,i.e.theexceptionoccursinanothercodearea,2)thisisabout castign casting *from*MultiSCMRevisionStatewhileJENKINS-27638isaboutcasting*to*MultiSCMRevisionState. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28494) Incorrect value of WARNINGS_NEW token
Title: Message Title Jochen Ulrich updated an issue Jenkins / JENKINS-28494 Incorrect value of WARNINGS_NEW token Change By: Jochen Ulrich Environment: Jenkinsver.1.554.3WarningsPlug-in4.47StaticAnalysis Utilies Utilities 1.71 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28306) Add title to test graph
Title: Message Title Alberto Fanjul Alonso started work on JENKINS-28306 Change By: Alberto Fanjul Alonso Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28494) Incorrect value of WARNINGS_NEW token
Title: Message Title Jochen Ulrich created an issue Jenkins / JENKINS-28494 Incorrect value of WARNINGS_NEW token Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 20/May/15 7:22 AM Environment: Jenkins ver. 1.554.3 Warnings Plug-in 4.47 Static Analysis Utilies 1.71 Priority: Minor Reporter: Jochen Ulrich I am using the $WARNINGS_NEW token in my email notifications but (most of the time?) its value does not match the one shown in the warning results page of the build. Instead, the new $WARNINGS_NEW seems to be equal to $WARNINGS_COUNT. For example: I get a mail reporting 118 warnings in total and 118 new warnings. When I open the warnings result page it shows 118 warnings in total and 0 new warnings (which is correct). I remember that I already had mails where the values were not equal but I can't recognize any pattern and again, most of the time, the new warnings value is wrong.
[JIRA] [multiple-scms-plugin] (JENKINS-21169) ClassCastException from MultiSCMRevisionState to CloneWorkspaceSCM
Title: Message Title Sebastian Schuberth commented on JENKINS-21169 Re: ClassCastException from MultiSCMRevisionState to CloneWorkspaceSCM Craig Rodrigues What makes you thing this is a dupe of JENKINS-27638 as 1) the stack trace is different, i.e. the exception occurs in another code area, 2) this is about castign from MultiSCMRevisionState while JENKINS-27638 is about casting to MultiSCMRevisionState. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-28495) Expose .csv or .xml reports
Title: Message Title Flix Belzunce Arcos created an issue Jenkins / JENKINS-28495 Expose .csv or .xml reports Issue Type: New Feature Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 20/May/15 8:25 AM Environment: Actually JaCoCo provides .csv and .xml reports but the JaCoCo plugin does not. Html reports might be too slow in large projects. Priority: Minor Reporter: Flix Belzunce Arcos Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title Nick Palmer created an issue Jenkins / JENKINS-28498 Null Pointer when publishing assets and server is down Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 20/May/15 10:20 AM Environment: Jenkins: 1.613 p4-plugin: 1.2.1 Priority: Minor Reporter: Nick Palmer I was attempting to publish assets as a post build action in one of my jobs and didn't realise the perforce server that it would publish to wasn't online. The error I got was not helpful, but a Null Pointer instead: ERROR: Publisher 'Perforce: Publish assets' aborted due to exception: java.lang.InterruptedException: P4: Unable to setup workspace: java.lang.NullPointerException at org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:63) at org.jenkinsci.plugins.p4.asset.AssetNotifier.perform(AssetNotifier.java:87) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at
[JIRA] [cucumber-testresult-plugin] (JENKINS-27731) Exception while parsing result file
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27731 Re: Exception while parsing result file For debugging save final json, create job that will have this json in workspace, do touch this.json to update file metadata. And then start cutting pieces of steps in this json. According to trace issue will be somewhere in step that contains Double number. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28489) Build does not fail if docker build fails
Title: Message Title Andy Smith commented on JENKINS-28489 Re: Build does not fail if docker build fails Vaclav, sorry I didn't see your comment until I closed. May be worth opening a new issue unless your issue is also fixed by the pull request linked above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28489) Build does not fail if docker build fails
Title: Message Title Andy Smith closed an issue as Duplicate Looks like this issue has already been fixed here: https://github.com/jenkinsci/docker-build-publish-plugin/pull/19 Just not released yet Jenkins / JENKINS-28489 Build does not fail if docker build fails Change By: Andy Smith Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28499) tcpSlaveAgentListener not found
Title: Message Title James Howe created an issue Jenkins / JENKINS-28499 tcpSlaveAgentListener not found Issue Type: Bug Assignee: Unassigned Components: core, remoting Created: 20/May/15 10:28 AM Priority: Blocker Reporter: James Howe Upgraded from 1.599 to 1.614. JNLP slaves now fail to connect with following error, where HOST is my actual host. SSH slaves are unaffected. May 20, 2015 10:57:51 AM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://HOST/tcpSlaveAgentListener/ is invalid: 404 Not Found java.lang.Exception: https://HOST/tcpSlaveAgentListener/ is invalid: 404 Not Found at hudson.remoting.Engine.run(Engine.java:214) Add Comment
[JIRA] [active-directory-plugin] (JENKINS-16257) Active Directory Plugin - Credential exception tying to authenticate
Title: Message Title James Jamieson commented on JENKINS-16257 Re: Active Directory Plugin - Credential exception tying to authenticate We are having a similar issue with the / character in our LDAP query string. Our OU has a / in it and active directory login will not work, as soon as that character is removed we are able to login successfully. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25203 Re: support embedded content in json Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/EmbeddedItem.java http://jenkins-ci.org/commit/cucumber-testresult-plugin/3b68644d94b18d9a26a0654b116be8a7930bd855 Log: JENKINS-25203 Make EmbeddedItem serializable. Should fix the issue when the plugin is not run on the master. Compare: https://github.com/jenkinsci/cucumber-testresult-plugin/compare/b50b86c7dcd1...3b68644d94b1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-25203 support embedded content in json Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25203 Re: support embedded content in json Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParser.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberModelException.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberPluginException.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberUtils.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/DefaultTestResultParserImpl.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/EmbeddedItem.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/GherkinCallback.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioToHTML.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/cucumber-embedded-item.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/3f6844ee4777030e2f0b5f1741d201d6b6aece60 Log: [FIXED JENKINS-25203] Add support for embedded items in the json result. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title Nick Palmer assigned an issue to Paul Allen Jenkins / JENKINS-28498 Null Pointer when publishing assets and server is down Change By: Nick Palmer Assignee: PaulAllen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28499) tcpSlaveAgentListener not found
Title: Message Title James Howe commented on JENKINS-28499 Re: tcpSlaveAgentListener not found Downgraded to 1.611, and issue is resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28460) Failed to connect to repository in project
Title: Message Title Dusan Susic commented on JENKINS-28460 Re: Failed to connect to repository in project Still presented on git 2.3.5 and git-client 1.17.1. Jenkins 1.609. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title James Nord commented on JENKINS-25203 Re: support embedded content in json Updated build at https://jenkins.ci.cloudbees.com/job/plugins/job/cucumber-testresult-plugin/54/org.jenkins-ci.plugins$cucumber-testresult-plugin/artifact/org.jenkins-ci.plugins/cucumber-testresult-plugin/0.8-SNAPSHOT/cucumber-testresult-plugin-0.8-SNAPSHOT.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27625) Git submodules, option for reseting local changes on submodules
Title: Message Title Tomasz Śniatowski commented on JENKINS-27625 Re: Git submodules, option for reseting local changes on submodules I believe this bug is more serious and could use more attention. Right now submodules behave differently from top-level repositories and builds can run with a broken or stale submodule checkout. It doesn't even take a misbehaving build step – if a build is aborted while checking out submodules, it will leave the submodule dirty. Subsequent builds in this workspace will then to not update the submodule at all, while not producing any useful diagnostics. This can be reproduced with a simple job restricted to one node, and a helper git repository with a submodule: # create submodule repository (mkdir sub cd sub git init echo subfile git commit -a -msub) # create outer repository (mkdir outer cd outer git init echo outerfile submodule add ../sub git commit -a -mouter) Configure a job to use the outer repository with git advanced behavior Recursively update submodules checked and the following execute shell build step: cat file cat sub/file # simulate modified workspace / aborted checkout rm file rm sub/file When the job is run the first time, the output is as expected; outer and sub. The second time outer is printed because the plugin issued a checkout -f, but the build fails because sub/file is still gone. There is no error message during the git step. This means currently it's very risky to use submodules with the git plugin unless workspaces or checkouts are force-cleaned: at best you'll sometimes get a build error, at worst – silent build corruption by using stale sources. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-11021) Changelog will ignore peg revisions; whole build fails if peg revision element has disappeared
Title: Message Title Alexander Ost closed an issue as Won't Fix Not sure if the problem still exists. We don't use peg revisions any longer for a long time already. As there's no votes nor watchers, let's close this issue. Jenkins / JENKINS-11021 Changelog will ignore peg revisions; whole build fails if peg revision element has disappeared Change By: Alexander Ost Status: Open Closed Resolution: Won'tFix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-14781) Maven Release Plugin performs build without goals
Title: Message Title Ren Sonntag commented on JENKINS-14781 Re: Maven Release Plugin performs build without goals We also have an user with '$' in his password. He is not able to do anything ... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-26840) GitHub Pull request plugin v1.16-8 builds master instead of PR
Title: Message Title Louis Jacomet edited a comment on JENKINS-26840 Re: GitHub Pull request plugin v1.16-8 builds master instead of PR Inoticedtodaythat1.20and1.20.1werereleased.Unfortunately,1.20.1doesnotfixtheissue.Seehttps://terracotta-oss.ci.cloudbees.com/job/statistics-pull-requests/1/Onceagainthecheckedoutrevisionmatchesmaster'sheadinsteadofthecommitannouncedatthetop. Updatedenvironment:CloudbeesJenkins1.580.3.3ghprb-plugin:1.20.1Gitplugin2.3.5GitHubAPIplugin1.67GitHubplugin1.11.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-28497) xUnit does not check for activation status of JUnit
Title: Message Title Jennifer Hofmeister updated an issue Jenkins / JENKINS-28497 xUnit does not check for activation status of JUnit Change By: Jennifer Hofmeister Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28497) xUnit does not check for activation status of JUnit
Title: Message Title Jennifer Hofmeister created an issue Jenkins / JENKINS-28497 xUnit does not check for activation status of JUnit Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin, xunit-plugin Created: 20/May/15 10:07 AM Environment: Jenkins 1.596.2 xUnit 1.95 JUnit 1.2 JobDSL 1.34/1.32 Debian Jessie, Windows 7 Priority: Major Reporter: Jennifer Hofmeister When accessed through a JobDSL script, the xUnit plugin will cause the job generation to effectively fail if the JUnit plugin is installed but disabled. (effectively fail means that the job resulting from the generated XML does not include all elements specified in the DSL, while the spawn job exits as SUCCESS.) I investigated this effect with Daniel from the JobDSL team (https://groups.google.com/forum/#!topic/job-dsl-plugin/n1GgzesLebA) and it seems clear it's not a JobDSL issue in the first instance. Apparently, xUnit needs JUnit to be active, but it checks only on the installation status of JUnit, not on whether it is activated. Activating JUnit solves the above problem.
[JIRA] [publish-over-cifs-plugin] (JENKINS-28496) Publish over CIFS: Change cifs share name is not recognized by jobs
Title: Message Title T. Mock created an issue Jenkins / JENKINS-28496 Publish over CIFS: Change cifs share name is not recognized by jobs Issue Type: Bug Assignee: bap Components: publish-over-cifs-plugin Created: 20/May/15 8:33 AM Environment: Jenkins v1.614 Publish over CIFS 0.3 os.name Linux os.version 3.16.0-4-amd64 java.runtime.version 1.8.0_45-b14 Priority: Minor Reporter: T. Mock Hi, i had a cifs share working with jenkins using the Publish Over CIFS plugin. I needed a second cifs share with a similar name and changed the name of the current cifs share in the global configuration. old name of cifs share: server1 new name : server1 trunk share After changing the name i added the second cifs share with name server1 tags share Now all jobs who used the old server1 share are showing the correct new server1 trunk share in their config. But these jobs are marked UNSTABLE after running because they could not find the old cifs share with name server1. Problem: The jobs showing the correct cifs share name in their config page but are using the old name internally. Workaround: go to jobs config page and select another cifs share, press save. Now change the cfis share back to what it should be. Then save the config again. Now it's using the correct
[JIRA] [xunit-plugin] (JENKINS-28497) xUnit does not check for activation status of JUnit
Title: Message Title Jennifer Hofmeister assigned an issue to Gregory Boissinot Jenkins / JENKINS-28497 xUnit does not check for activation status of JUnit Change By: Jennifer Hofmeister Assignee: DanielSpilker GregoryBoissinot Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Dirk von Husen commented on JENKINS-28376 Re: jobs get stuck in queue from time to time We upgraded to Jenkins 1.614 yesterday. Looks like the problem still exists also in this version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Dirk von Husen updated an issue Jenkins / JENKINS-28376 jobs get stuck in queue from time to time Change By: Dirk von Husen Environment: Jenkins1.611-1.614= , ...,BuildBlockerPlugin1.6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Dirk von Husen updated an issue Jenkins / JENKINS-28376 jobs get stuck in queue from time to time Change By: Dirk von Husen Environment: Jenkins1. 613 611-1.614= , ..., BuildBlockerPlugin1.6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-26840) GitHub Pull request plugin v1.16-8 builds master instead of PR
Title: Message Title Louis Jacomet commented on JENKINS-26840 Re: GitHub Pull request plugin v1.16-8 builds master instead of PR I noticed today that 1.20 and 1.20.1 were released. Unfortunately, 1.20.1 does not fix the issue. See https://terracotta-oss.ci.cloudbees.com/job/statistics-pull-requests/1/ One again the checked out revision matches master's head instead of the commit announced at the top. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-26840) GitHub Pull request plugin v1.16-8 builds master instead of PR
Title: Message Title Louis Jacomet edited a comment on JENKINS-26840 Re: GitHub Pull request plugin v1.16-8 builds master instead of PR Inoticedtodaythat1.20and1.20.1werereleased.Unfortunately,1.20.1doesnotfixtheissue.Seehttps://terracotta-oss.ci.cloudbees.com/job/statistics-pull-requests/1/ One Once againthecheckedoutrevisionmatchesmaster'sheadinsteadofthecommitannouncedatthetop. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28489) Build does not fail if docker build fails
Title: Message Title Vaclav Rehak commented on JENKINS-28489 Re: Build does not fail if docker build fails There is similar problem if docker login fails (e.g. due to frequent outages of Docker Hub) - I would expect the build to stop immediately but it goes on with building. [myproject] $ docker login -u myusername -e m...@mycompany.com -p time=2015-05-20T06:01:23-04:00 level=fatal msg=Error response from daemon: /html (Code: 500; Headers: map[Vary:[Cookie] X-Frame-Options:[SAMEORIGIN] Strict-Transport-Security:[max-age=31536000] Server:[nginx/1.6.2] Date:[Wed, 20 May 2015 10:01:22 GMT] Content-Type:[text/html; charset=utf-8]]) [myproject] $ docker build -t mycompany/myproject:4d20ec41fd2bb0e5d6839e55511815ec9fe89c10 --pull=true . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cluster-stats-plugin] (JENKINS-28500) ClusterStats plugin may mix data from multiple builds
Title: Message Title Tobias Gruetzmacher created an issue Jenkins / JENKINS-28500 ClusterStats plugin may mix data from multiple builds Issue Type: Bug Assignee: Unassigned Components: cluster-stats-plugin Created: 20/May/15 1:09 PM Priority: Major Reporter: Tobias Gruetzmacher I noticed that the queue length on the cluster stats plugin is sometimes quite long and doesn't match my experience. After some investigation I found this: Using the data export I found this one Job as an example: Run #22, start time Mon May 18 10:11:45 CEST 2015, claimed time in queue: 583482s (so should have entered queue at ~ Monday, May 11, 2015 16:07:00 CEST) Run #21, start time Mon May 11 16:07:02 CEST 2015, claimed time in queue: 861s (~ Monday, May 11, 2015 15:52:41 CEST) Run #20, Mon May 11 15:52:41 CEST 2015, etc. So it seems one entry of the RunStats might end up with the info of different runs of the same project. Idea: Would it be possible to always use the (non-legacy) QueueId when finding entries in edenStats? So change StatsData.popUnInitializedItem to take a queue ID and use getQueueId (http://javadoc.jenkins-ci.org/hudson/model/Run.html#getQueueId%28%29) to look up the correct queue item? (Probably needs to depend on a quite new Jenkins base version [1.601]...)
[JIRA] [core] (JENKINS-24433) Searchbox cannot be used inside a folder
Title: Message Title Aviv Yam updated an issue Jenkins / JENKINS-24433 Searchbox cannot be used inside a folder Change By: Aviv Yam Labels: 1.609.1-fixedfoldersgui lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zentimestamp-plugin] (JENKINS-26958) ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin
Title: Message Title Per stman commented on JENKINS-26958 Re: ZenTimestamper throws ClassCastException when used in combination with the new Workflow plugin Bumping this. We use Zen timestamper, and wish to use workflow plugin, but this bug effectively prevents this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-28497) xUnit does not check for activation status of JUnit
Title: Message Title Jennifer Hofmeister updated an issue Jenkins / JENKINS-28497 xUnit does not check for activation status of JUnit Change By: Jennifer Hofmeister WhenaccessedthroughaJobDSLscript,thexUnitpluginwillcausethejobgenerationtoeffectivelyfailiftheJUnitpluginisinstalledbutdisabled.(effectivelyfailmeansthatthejobresultingfromthegeneratedXMLdoesnotincludeallelementsspecifiedintheDSL,whilethespawnjobexitsasSUCCESS withoutanyerroroutput .)IinvestigatedthiseffectwithDanielfromtheJobDSLteam([https://groups.google.com/forum/#!topic/job-dsl-plugin/n1GgzesLebA])anditseemsclearit'snotaJobDSLissueinthefirstinstance.Apparently,xUnitneedsJUnittobeactive,butitchecksonlyontheinstallationstatusofJUnit,notonwhetheritisactivated.ActivatingJUnitsolvestheaboveproblem ,butitwouldbebetterifxUnitcheckedbackontheactivationstatusofJUnitandthrewacorrespondingerror . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Title: Message Title Roberto Andrade commented on JENKINS-18578 Re: Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Another workaround I've found that worked better for me both on master and slave is changing the `user.home` System property by setting the `_JAVA_OPTIONS` environment variable as described [here](http://stackoverflow.com/questions/1501235/change-user-home-system-property). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18956) Cache location should be configurable through the GUI
Title: Message Title Roberto Andrade commented on JENKINS-18956 Re: Cache location should be configurable through the GUI Another workaround I've found that worked better for me both on master and slave is changing the `user.home` System property by setting the `_JAVA_OPTIONS` environment variable as described [here](http://stackoverflow.com/questions/1501235/change-user-home-system-property). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-12097) Using Jabber Plugin with Google Talk logs VCARD Exception
Title: Message Title James Howe commented on JENKINS-12097 Re: Using Jabber Plugin with Google Talk logs VCARD Exception IfNeeded suggests it's a bug, as it's failed to determine whether it's needed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28504) Add Folder Support To the Parameterized Remote Trigger Plugin
Title: Message Title James Sweet created an issue Jenkins / JENKINS-28504 Add Folder Support To the Parameterized Remote Trigger Plugin Issue Type: Improvement Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 20/May/15 4:35 PM Environment: Jenkins using the Folders Plugin and the Parameterized Remote Trigger Plugin Labels: plugin Priority: Blocker Reporter: James Sweet The Parameterized Remote Trigger Plugin does not currently support Jenkins environments that use Folders. Set up a Jenkins environment to trigger a job located in a remote folder using the Parameterized Remote Trigger Plugin to recreate this issue.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling
Title: Message Title Thomas Suckow created an issue Jenkins / JENKINS-28506 [REGRESSION] Git fails to trigger from polling Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 20/May/15 5:34 PM Environment: Git-Plugin: 2.3.5 Labels: git polling pollscm regression Priority: Major Reporter: Thomas Suckow Expected: ``` [poll] Last Built Revision: Revision abcdef1234 (refs/remotes/origin/feature/myfeature) using GIT_SSH to set credentials Git Credentials git --version # timeout=10 git ls-remote -h ssh://we16705.pnl.gov/git/watchmen.git refs/heads/feature/myfeature # timeout=10 [poll] Latest remote head revision is: defabc4321 Done. Took 1.8 sec Changes found ``` Actual: ``` [poll] Last Built Revision: Revision abcdef1234 (refs/remotes/origin/feature/myfeature) using GIT_SSH to set credentials Git Credentials git --version # timeout=10 git ls-remote -h ssh://we16705.pnl.gov/git/watchmen.git # timeout=10 Done. Took 1.8 sec ``` Workaround: Downgrade to
[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall commented on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Am also experiencing similar, in 1.596.2
{{17:13:41 GMT+01:00 Archiving artifacts 17:13:43 GMT+01:00 ERROR: Failed to archive artifacts: LOGS/,target/**/LOGS/,target/robotframework/ 17:13:43 GMT+01:00 java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: request to write '3085' bytes exceeds size in header of '2581956' bytes for entry 'target/path/to/file_20_05_2015.log' 17:13:43 GMT+01:00 at hudson.FilePath.copyRecursiveTo(FilePath.java:2213) 17:13:43 GMT+01:00 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 17:13:43 GMT+01:00 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218) 17:13:43 GMT+01:00 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206) 17:13:43 GMT+01:00 at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124) 17:13:43 GMT+01:00 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:13:43 GMT+01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) 17:13:43 GMT+01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) 17:13:43 GMT+01:00 at hudson.model.Build$BuildExecution.post2(Build.java:183) 17:13:43 GMT+01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) 17:13:43 GMT+01:00 at hudson.model.Run.execute(Run.java:1784) 17:13:43 GMT+01:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 17:13:43 GMT+01:00 at hudson.model.ResourceController.execute(ResourceController.java:89) 17:13:43 GMT+01:00 at hudson.model.Executor.run(Executor.java:240) 17:13:43 GMT+01:00 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '3085' bytes exceeds size in header of '2581956' bytes for entry 'target/path/to/file_20_05_2015.log' 17:13:43 GMT+01:00 at hudson.remoting.Channel$3.adapt(Channel.java:784) 17:13:43 GMT+01:00 at hudson.remoting.Channel$3.adapt(Channel.java:779) 17:13:43 GMT+01:00 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 17:13:43 GMT+01:00 at hudson.FilePath.copyRecursiveTo(FilePath.java:2211) 17:13:43 GMT+01:00 ... 19 more 17:13:43 GMT+01:00 Caused by: java.io.IOException: request to write '3085' bytes exceeds size in header of '2581956' bytes for entry 'target/path/to/file_20_05_2015.log' 17:13:43 GMT+01:00 at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284) 17:13:43 GMT+01:00 at hudson.util.io.TarArchiver.visit(TarArchiver.java:114) 17:13:43 GMT+01:00 at hudson.util.DirScanner.scanSingle(DirScanner.java:49) 17:13:43 GMT+01:00 at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764) 17:13:43 GMT+01:00 at hudson.FilePath.writeToTar(FilePath.java:2249) 17:13:43 GMT+01:00 at hudson.FilePath.access$2100(FilePath.java:191) 17:13:43 GMT+01:00 at hudson.FilePath$45.invoke(FilePath.java:2190)
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title Kanstantsin Shautsou commented on JENKINS-25203 Re: support embedded content in json I built myself this commit and it looks working. Accessing screenshot requires additional clicks, but it can be redesigned later. Will it be also possible to backport this feature for 1.580 core? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-28501) onEnterBlocked warnings during startup
Title: Message Title James Howe created an issue Jenkins / JENKINS-28501 onEnterBlocked warnings during startup Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 20/May/15 3:33 PM Environment: Jenkins 1.611, prioritysorter 3.2 Priority: Minor Reporter: James Howe May 20, 2015 4:18:13 PM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs May 20, 2015 4:18:13 PM jenkins.advancedqueue.PrioritySorterPlugin init2 INFO: Sorting existing Queue ... May 20, 2015 4:18:13 PM jenkins.advancedqueue.sorter.AdvancedQueueSorter init INFO: Initialized the QueueSorter with 0 Buildable Items May 20, 2015 4:18:13 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Download metadata May 20, 2015 4:18:13 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Download metadata. 1 ms May 20, 2015 4:18:14 PM jenkins.advancedqueue.sorter.AdvancedQueueSorterQueueListener onEnterBlocked WARNING: onEnterBlocked() called without prior call to onEnterWaiting() for 'MyJob'
[JIRA] [core] (JENKINS-28486) Disable SCM polling until Jenkins is fully up and running
Title: Message Title James Howe commented on JENKINS-28486 Re: Disable SCM polling until Jenkins is fully up and running In fact, I get jobs building, completing, sending notifications, etc. long before the UI is ready and I can control anything. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28503) White Buttons
Title: Message Title Tobias Kck created an issue Jenkins / JENKINS-28503 White Buttons Issue Type: Bug Assignee: Unassigned Attachments: jenkins_white_buttons.png Components: core Created: 20/May/15 4:12 PM Environment: Debian Linux, Linux ci 3.14-1-amd64, java -version java version 1.7.0_75 Labels: white button Priority: Minor Reporter: Tobias Kck Jenkins Package from apt sources: deb http://pkg.jenkins-ci.org/debian binary/ Jenkins
[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall edited a comment on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Amalsoexperiencingsimilar,in1.596.2{ quote code } 17:13:41GMT+01:00Archivingartifacts17:13:43GMT+01:00ERROR:Failedtoarchiveartifacts:LOGS/,target/**/LOGS/,target/robotframework/17:13:43GMT+01:00java.io.IOException:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2213)17:13:43GMT+01:00 atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)17:13:43GMT+01:00 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)17:13:43GMT+01:00 athudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124)17:13:43GMT+01:00 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)17:13:43GMT+01:00 athudson.model.Build$BuildExecution.post2(Build.java:183)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)17:13:43GMT+01:00 athudson.model.Run.execute(Run.java:1784)17:13:43GMT+01:00 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:13:43GMT+01:00 athudson.model.ResourceController.execute(ResourceController.java:89)17:13:43GMT+01:00 athudson.model.Executor.run(Executor.java:240)17:13:43GMT+01:00Causedby:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:784)17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:779)17:13:43GMT+01:00 athudson.remoting.FutureAdapter.get(FutureAdapter.java:55)17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2211)17:13:43GMT+01:00 ...19more17:13:43GMT+01:00Causedby:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)17:13:43GMT+01:00 athudson.util.io.TarArchiver.visit(TarArchiver.java:114)17:13:43GMT+01:00 athudson.util.DirScanner.scanSingle(DirScanner.java:49)17:13:43GMT+01:00 athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764)17:13:43GMT+01:00 athudson.FilePath.writeToTar(FilePath.java:2249)17:13:43GMT+01:00 athudson.FilePath.access$2100(FilePath.java:191)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2190)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2186)17:13:43GMT+01:00 athudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)17:13:43GMT+01:00 athudson.remoting.UserRequest.perform(UserRequest.java:121)17:13:43GMT+01:00
[JIRA] [versionnumber-plugin] (JENKINS-28505) Version Number plugin fails with Java 8
Title: Message Title Kalle Lehtonen created an issue Jenkins / JENKINS-28505 Version Number plugin fails with Java 8 Issue Type: Bug Assignee: Unassigned Components: versionnumber-plugin Created: 20/May/15 4:59 PM Environment: jenkins-1.613 versionnumber-1.5 Priority: Critical Reporter: Kalle Lehtonen After updating to version 1.5 and using Java 8 as the build environment JDK the plugin started to throw null pointer exception. Downgrading to 1.4.1 fixed the problem. ERROR: java.lang.NullPointerException Version 1.5 worked fine when using Java 7.
[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall edited a comment on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Amalsoexperiencingsimilar,in1.596.2{ { quote} 17:13:41GMT+01:00Archivingartifacts17:13:43GMT+01:00ERROR:Failedtoarchiveartifacts:LOGS/,target/**/LOGS/,target/robotframework/17:13:43GMT+01:00java.io.IOException:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2213)17:13:43GMT+01:00 atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)17:13:43GMT+01:00 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)17:13:43GMT+01:00 athudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124)17:13:43GMT+01:00 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)17:13:43GMT+01:00 athudson.model.Build$BuildExecution.post2(Build.java:183)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)17:13:43GMT+01:00 athudson.model.Run.execute(Run.java:1784)17:13:43GMT+01:00 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:13:43GMT+01:00 athudson.model.ResourceController.execute(ResourceController.java:89)17:13:43GMT+01:00 athudson.model.Executor.run(Executor.java:240)17:13:43GMT+01:00Causedby:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:784)17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:779)17:13:43GMT+01:00 athudson.remoting.FutureAdapter.get(FutureAdapter.java:55)17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2211)17:13:43GMT+01:00 ...19more17:13:43GMT+01:00Causedby:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)17:13:43GMT+01:00 athudson.util.io.TarArchiver.visit(TarArchiver.java:114)17:13:43GMT+01:00 athudson.util.DirScanner.scanSingle(DirScanner.java:49)17:13:43GMT+01:00 athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764)17:13:43GMT+01:00 athudson.FilePath.writeToTar(FilePath.java:2249)17:13:43GMT+01:00 athudson.FilePath.access$2100(FilePath.java:191)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2190)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2186)17:13:43GMT+01:00 athudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)17:13:43GMT+01:00 athudson.remoting.UserRequest.perform(UserRequest.java:121)17:13:43GMT+01:00
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling
Title: Message Title
Thomas Suckow updated an issue
Jenkins / JENKINS-28506
[REGRESSION] Git fails to trigger from polling
Change By:
Thomas Suckow
Expected: ``` {code} [poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh:// we16705.pnl.gov server /git/ watchmen project .gitrefs/heads/feature/myfeature#timeout=10[poll]Latestremoteheadrevisionis:defabc4321Done.Took1.8secChangesfound ``` {code} Actual: ``` {code} [poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh:// we16705.pnl.gov server /git/ watchmen project .git#timeout=10Done.Took1.8sec ``` {code} Workaround:DowngradetoGit-Plugin2.3.4
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-28501) onEnterBlocked warnings during startup
Title: Message Title Magnus Sandberg closed an issue as Not A Defect You will get these warnings during start-up if you start with an existing queue. If you get them during normal operation then is is more of a problem. Will remove this logging in the future when the handling of queue-events seems to be stable. Jenkins / JENKINS-28501 onEnterBlocked warnings during startup Change By: Magnus Sandberg Status: Open Closed Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-13494) JIRA issue not commented if issue TAG is not on first line of commit message
Title: Message Title Rom Freiman commented on JENKINS-13494 Re: JIRA issue not commented if issue TAG is not on first line of commit message Do you have any estimation when the issue would be fixed? Any suggested workaround? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-24411) HP ALI plugin not available to download
Title: Message Title Mark Nejman commented on JENKINS-24411 Re: HP ALI plugin not available to download The HP ALI Integration Plugin is available on the HP Live Network as part of the ALI utilities bundle: https://hpln.hp.com/group/ali-bundle It is only available for people who have an HP service agreement. It is maintained by HP and not available through the Jenkins CI site. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Kieran Shaw created an issue Jenkins / JENKINS-28502 Install from http://groovy.codehaus.org installer method failing Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 20/May/15 3:53 PM Environment: Jenkins 1.608 groovy-plugin 1.24 Labels: groovy installer tools Priority: Major Reporter: Kieran Shaw The install automatically from http://groovy.codehaus.org option has now stopped working at codehaus.org has shut down. We get the following error: Unpacking http://dist.groovy.codehaus.org/distributions/groovy-binary-2.2.1.zip to c:\jenkins\slave\tools\hudson.plugins.groovy.GroovyInstallation\Groovy on Pure_Internal ERROR: Failed to download http://dist.groovy.codehaus.org/distributions/groovy-binary-2.2.1.zip from slave; will retry from master java.io.IOException: remote file operation failed: c:\jenkins\slave\tools\hudson.plugins.groovy.GroovyInstallation\Groovy at hudson.remoting.Channel@5ad475c:Pure_Internal:
[JIRA] [core] (JENKINS-28503) White Buttons
Title: Message Title Tobias Kck updated an issue Jenkins / JENKINS-28503 White Buttons Change By: Tobias Kck -JenkinsPackagefromaptsources:debhttp://pkg.jenkins-ci.org/debianbinary/-JenkinsVersion:1.614Sinceupdateto1.612(andtoday1.614)somebuttons apear appear white(asshowninthescreenshot).WetrieddifferentBrowser(Firefox30.0.1andChrome44.0.2)withthesameresult. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28507) Email Extension Plugin throwing a MullPointerException at startup
Title: Message Title Justin Ellis created an issue Jenkins / JENKINS-28507 Email Extension Plugin throwing a MullPointerException at startup Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 20/May/15 6:06 PM Environment: CentOS 6.5, Jenkins 1.614, Email Extension Plugin 2.40.2 Priority: Minor Reporter: Justin Ellis I recently upgraded Jenkins to 1.614 and possibly also recently upgraded the Email Extension Plugin as well (not sure). Now when Jenkins starts up I see a plugin-generated NullPointerException in the Jenkins log: INFO: Started all plugins May 20, 2015 5:53:40 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions May 20, 2015 5:53:40 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect Slave 1 May 20, 2015 5:53:40 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect Slave 2 May 20, 2015 5:53:45 PM hudson.model.Descriptor load WARNING: Failed to load /var/lib/jenkins/hudson.plugins.emailext.ExtendedEmailPublisher.xml java.io.IOException: Unable to read /var/lib/jenkins/hudson.plugins.emailext.ExtendedEmailPublisher.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.model.Descriptor.load(Descriptor.java:783) at
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Alberto Fanjul Alonso created an issue Jenkins / JENKINS-28508 Broken link on Tap Results Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: tap extended results .jpg, tap results.jpg Components: tap-plugin Created: 20/May/15 6:47 PM Priority: Minor Reporter: Alberto Fanjul Alonso Tap results generate broken links. I don't know exactly de content is expected to be on those links Related code is here: https://github.com/jenkinsci/tap-plugin/blob/master/src/main/resources/org/tap4j/plugin/model/TapStreamResult/body.jelly#L66 e.g. Task for https://github.com/albfan/git-ignore test stream are generated with $ git clone https://github.com/albfan/git-ignore $ cd t/ $ make DEFAULT_TEST_TARGET=jenkins test are on tapout/ dir. This is it's output t/tapout/t0001-exclude.sh ok 1 - exclude a single file ok 2 - exclude a bunch of files
[JIRA] [jacoco-plugin] (JENKINS-22776) Jacoco: spaces don't work when listing multiple class/source folders
Title: Message Title Maninder Singh updated an issue Jenkins / JENKINS-22776 Jacoco: spaces don't work when listing multiple class/source folders Change By: Maninder Singh Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Title: Message Title
Oleksii Khilkevych edited a comment on JENKINS-26326
Re: Boot up Vagrant VM not using relative path
Toaddup,Ifounditseemslikeittriestousedifferentdirectoryforeachofthedifferentbuildstepsitprovides Itried$workspaceandthelikes,triedtospecifyrelativepaths,butendedupusingshellscriptbuildstepwithsimplevagrantup,thatworkedlikeitshould Consoleoutputcut:{code:java}[workspace]$vagrant-vVagrant1.7.2[vagrant]:Executingcommand:[vagrant,up,--destroy-on-error]infolder/Users/oleksii[oleksii]$vagrantup--destroy-on-errorAVagrantenvironmentortargetmachineisrequiredtorunthiscommand.Run`vagrantinit`tocreateanewVagrantenvironment.Or,getanIDofatargetmachinefrom`vagrantglobal-status`torunthiscommandon.AfinaloptionistochangetoadirectorywithaVagrantfileandtotryagain.Buildstep'BootupVagrantVM'markedbuildasfailureFinished:FAILURE{code}Consoleoutputcut#2{code:java}[workspace]$vagrant-vVagrant1.7.2[vagrant]:Executingcommand:[vagrant,provision]infolder/Users/oleksii/Downloads[Downloads]$vagrantprovisionAVagrantenvironmentortargetmachineisrequiredtorunthiscommand.Run`vagrantinit`tocreateanewVagrantenvironment.Or,getanIDofatargetmachinefrom`vagrantglobal-status`torunthiscommandon.AfinaloptionistochangetoadirectorywithaVagrantfileandtotryagain.Buildstep'ProvisionaVagrantVM'markedbuildasfailureFinished:FAILURE{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Christopher Orr commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing Groovy downloads have been moved to bintray, where, for some reason, the older versions aren't easily accessible, like they were on codehaus: https://bintray.com/groovy/maven/groovy/view https://dl.bintray.com/groovy/maven/ If somebody can figure it out, they can submit a pull request for https://github.com/jenkinsci/backend-crawler/blob/master/groovy.groovy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Alberto Fanjul Alonso updated an issue Jenkins / JENKINS-28508 Broken link on Tap Results Change By: Alberto Fanjul Alonso Tapresultsgeneratebrokenlinks.Idon'tknowexactlydecontentisexpectedtobeonthoselinks!tapresults.jpg|thumbnail!Relatedcodeishere:https://github.com/jenkinsci/tap-plugin/blob/master/src/main/resources/org/tap4j/plugin/model/TapStreamResult/body.jelly#L66 https://github.com/jenkinsci/tap-plugin/blob/65b57b2cbbea64c033cd07511ad71f46a370bcee/src/main/java/org/tap4j/plugin/model/TapTestResultResult.java#L171 e.g.Taskforhttps://github.com/albfan/git-ignoreteststreamaregeneratedwith$gitclonehttps://github.com/albfan/git-ignore$cdt/$makeDEFAULT_TEST_TARGET=jenkinstest are streamoutputs ontapout/dir. Thisisit'soutput Heretheyare: t/tapout/t0001-exclude.shok1-excludeasinglefileok2-excludeabunchoffiles#passedall2test(s)1..2t/tapout/t0002-ignore.shok1-Ignoringasinglefileok2-Ignoringabunchoffiles#passedall2test(s)1..2Hereisageneratedlinkforoneofthese4testjenkins-url/job/git-ignore/10/tapTestReport/t%2Ftapout%2Ft0001-exclude.sh-1/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Title: Message Title
Oleksii Khilkevych commented on JENKINS-26326
Re: Boot up Vagrant VM not using relative path
To add up, I found it seems like it tries to use different directory for each of the different build steps it provides
Console output cut: {{[workspace] $ vagrant -v Vagrant 1.7.2 [ vagrant ]: Executing command :[vagrant, up, --destroy-on-error] in folder /Users/oleksii [oleksii] $ vagrant up --destroy-on-error A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again. Build step 'Boot up Vagrant VM' marked build as failure Finished: FAILURE}}
Console output cut #2
{{[workspace] $ vagrant -v Vagrant 1.7.2 [ vagrant ]: Executing command :[vagrant, provision] in folder /Users/oleksii/Downloads [Downloads] $ vagrant provision A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again. Build step 'Provision a Vagrant VM' marked build as failure Finished: FAILURE}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Title: Message Title
Oleksii Khilkevych edited a comment on JENKINS-26326
Re: Boot up Vagrant VM not using relative path
Toaddup,IfounditseemslikeittriestousedifferentdirectoryforeachofthedifferentbuildstepsitprovidesConsoleoutputcut: { { code:java} [workspace]$vagrant-vVagrant1.7.2[vagrant]:Executingcommand:[vagrant,up,--destroy-on-error]infolder/Users/oleksii[oleksii]$vagrantup--destroy-on-errorAVagrantenvironmentortargetmachineisrequiredtorunthiscommand.Run`vagrantinit`tocreateanewVagrantenvironment.Or,getanIDofatargetmachinefrom`vagrantglobal-status`torunthiscommandon.AfinaloptionistochangetoadirectorywithaVagrantfileandtotryagain.Buildstep'BootupVagrantVM'markedbuildasfailureFinished:FAILURE {code } } Consoleoutputcut#2{ { code:java} [workspace]$vagrant-vVagrant1.7.2[vagrant]:Executingcommand:[vagrant,provision]infolder/Users/oleksii/Downloads[Downloads]$vagrantprovisionAVagrantenvironmentortargetmachineisrequiredtorunthiscommand.Run`vagrantinit`tocreateanewVagrantenvironment.Or,getanIDofatargetmachinefrom`vagrantglobal-status`torunthiscommandon.AfinaloptionistochangetoadirectorywithaVagrantfileandtotryagain.Buildstep'ProvisionaVagrantVM'markedbuildasfailureFinished:FAILURE {code } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28510) Reflection Error Defining Step Param
Title: Message Title Flvio Augusto Valones created an issue Jenkins / JENKINS-28510 Reflection Error Defining Step Param Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 20/May/15 9:24 PM Environment: Jenkins 1.609 workflow-plugin 1.6 Labels: workflow step plugin Priority: Minor Reporter: Flvio Augusto Valones I'm working on implementing a new step in a plugin, and came across the following error: If one argument step is a Map, and it is a field annotated with @DataBoundSetter, Ok, no problems. But if it is a Setter annotated with @DataBoundSetter the following error occurs during instantiation: java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl cannot be cast to java.lang.Class at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:214) at
[JIRA] [p4-plugin] (JENKINS-28301) P4 workflow checkout should accept a changelist parameter
Title: Message Title A C commented on JENKINS-28301 Re: P4 workflow checkout should accept a changelist parameter Ah ok, yes please update the docs with this info, I was confused as to what pin was since it's not in my normal p4 lexicon. Pin does appear to do what I want. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title
Shaishav Parekh edited a comment on JENKINS-28509
Re: Deployer Plugin doesn't support ruby deployments
Whydoesthe'GitDeploy'optionrequirea'DeploymentPackage'?!git_deploy.png|thumbnail!Whydoes'GitDeploy'deleteallsourcecodeanddeploya.gzartifact?{{[OPENSHIFT]Deploymentsfound:[/home/jenkins/workspace/ruby/repo.tar.gz][OPENSHIFT]DeployingtoOpenShiftat.Bepatient!Itmighttakeaminute...[OPENSHIFT]Copyingthedeploymentfromslavenodeto'/var/jenkins_home/jobs/ruby/builds/234/workspace/openshift-deployer-workdir/repo.tar.gz'[OPENSHIFT]Cloning.git/]togit[OPENSHIFT]Deleting'tmp'[OPENSHIFT]Deleting'config.ru'[OPENSHIFT]Deleting'public'[OPENSHIFT]Deleting'README.md'[OPENSHIFT]Deployment'repo.tar.gz'copiedto'ROOT.gz'[OPENSHIFT]Committingrepo[OPENSHIFT]Pushingtoupstream[OPENSHIFT]Applicationdeployedto/}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title
Shaishav Parekh edited a comment on JENKINS-28509
Re: Deployer Plugin doesn't support ruby deployments
Whydoesthe'GitDeploy'optionrequirea'DeploymentPackage'?!git_deploy.png|thumbnail!Whydoes'GitDeploy'deleteallsourcecodeanddeploya.gzartifact? { { quote} [OPENSHIFT]Deploymentsfound:[/home/jenkins/workspace/ruby/repo.tar.gz][OPENSHIFT]DeployingtoOpenShiftat.Bepatient!Itmighttakeaminute...[OPENSHIFT]Copyingthedeploymentfromslavenodeto'/var/jenkins_home/jobs/ruby/builds/234/workspace/openshift-deployer-workdir/repo.tar.gz'[OPENSHIFT]Cloning.git/]togit[OPENSHIFT]Deleting'tmp'[OPENSHIFT]Deleting'config.ru'[OPENSHIFT]Deleting'public'[OPENSHIFT]Deleting'README.md'[OPENSHIFT]Deployment'repo.tar.gz'copiedto'ROOT.gz'[OPENSHIFT]Committingrepo[OPENSHIFT]Pushingtoupstream[OPENSHIFT]Applicationdeployedto/ {quote } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25468) Add a Verbosity option to allow detailed p4 info
Title: Message Title Robby Pocase commented on JENKINS-25468 Re: Add a Verbosity option to allow detailed p4 info Is this still an issue? I believe this is the default in the latest version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25468) Add a Verbosity option to allow detailed p4 info
Title: Message Title Robby Pocase edited a comment on JENKINS-25468 Re: Add a Verbosity option to allow detailed p4 info Isthisstillanissue?Ibelievethisisthedefaultinthelatestversion (1 . 2.1). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28507) Email Extension Plugin throwing a MullPointerException at startup
Title: Message Title Alex Earl resolved as Duplicate Jenkins / JENKINS-28507 Email Extension Plugin throwing a MullPointerException at startup Change By: Alex Earl Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title garethbowles updated an issue Jenkins / JENKINS-28502 Install from http://groovy.codehaus.org installer method failing Bumped priority to blocker as there appears to be no way to get builds working again short of modifying the plugin or installing Groovy locally. Change By: garethbowles Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28507) Email Extension Plugin throwing a MullPointerException at startup
Title: Message Title Justin Ellis updated an issue Jenkins / JENKINS-28507 Email Extension Plugin throwing a MullPointerException at startup Change By: Justin Ellis Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title garethbowles updated an issue Jenkins / JENKINS-28502 Install from http://groovy.codehaus.org installer method failing Change By: garethbowles Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title garethbowles commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing Downgraded priority, forgot there's a way to specify the download URL in the list of Groovy installations. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling
Title: Message Title
Thomas Suckow updated an issue
Jenkins / JENKINS-28506
[REGRESSION] Git fails to trigger from polling
Change By:
Thomas Suckow
Pollingdoesnotworkwhenthespecifiedbranchisoftheformrefs/heads/feature/myfeature Expected:{code}[poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.gitrefs/heads/feature/myfeature#timeout=10[poll]Latestremoteheadrevisionis:defabc4321Done.Took1.8secChangesfound{code}Actual:{code}[poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.git#timeout=10Done.Took1.8sec{code}Workaround:DowngradetoGit-Plugin2.3.4
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title Shaishav Parekh created an issue Jenkins / JENKINS-28509 Deployer Plugin doesn't support ruby deployments Issue Type: Bug Assignee: Unassigned Components: openshift-deployer-plugin Created: 20/May/15 7:17 PM Environment: Jenkins v1.607 OS Deployer v1.2 RHEL 6.6 Labels: plugin jenkins openshift Priority: Major Reporter: Shaishav Parekh Both deployment options offered don't correctly deploy a ruby project. Git Deployment Option: Git deployment of ruby source code is completely broken. It deletes all of the local files and folders and places a .gz file in Openshift repository. Instead, the deployer plugin should copy the source code into the app-root/repo folder and run bundle install after to activate the project.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title
Shaishav Parekh commented on JENKINS-28509
Re: Deployer Plugin doesn't support ruby deployments
Why does the 'Git Deploy' option require a 'Deployment Package'?
Why does 'Git Deploy' delete all source code and deploy a .gz artifact?
{{[OPENSHIFT] Deployments found: [/home/jenkins/workspace/ruby/repo.tar.gz] [OPENSHIFT] Deploying to OpenShift at . Be patient! It might take a minute... [OPENSHIFT] Copying the deployment from slave node to '/var/jenkins_home/jobs/ruby/builds/234/workspace/openshift-deployer-workdir/repo.tar.gz' [OPENSHIFT] Cloning .git/] to git [OPENSHIFT] Deleting 'tmp' [OPENSHIFT] Deleting 'config.ru' [OPENSHIFT] Deleting 'public' [OPENSHIFT] Deleting 'README.md' [OPENSHIFT] Deployment 'repo.tar.gz' copied to 'ROOT.gz' [OPENSHIFT] Committing repo [OPENSHIFT] Pushing to upstream [OPENSHIFT] Application deployed to /}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title Shaishav Parekh updated an issue Jenkins / JENKINS-28509 Deployer Plugin doesn't support ruby deployments Change By: Shaishav Parekh Attachment: git_deploy.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28440) Allow to reject specific configurations via REST and CLI
Title: Message Title ikedam commented on JENKINS-28440 Re: Allow to reject specific configurations via REST and CLI https://github.com/jenkinsci/jenkins/pull/1715 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28440) Allow to reject specific configurations via REST and CLI
Title: Message Title ikedam started work on JENKINS-28440 Change By: ikedam Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-lambda-plugin] (JENKINS-28443) invoke lambda function as build-step and post-build-action
Title: Message Title Michael Willemse started work on JENKINS-28443 Change By: Michael Willemse Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28511) Trigger builds remotely is started but nothing changes
Title: Message Title kean Luke created an issue Jenkins / JENKINS-28511 Trigger builds remotely is started but nothing changes Issue Type: Bug Assignee: Nicolas De Loof Attachments: upload.JPG, upload002.JPG Components: git-plugin Created: 21/May/15 1:07 AM Environment: Jenkins ver. 1.596.2 jdk 1.8 git plugin 1.17.1 Atlassian Stash v3.6.0 Labels: git jenkins plugin Priority: Critical Reporter: kean Luke closely issue Jenkins triggers builds on Git SCM changes, but nothing changed https://issues.jenkins-ci.org/browse/JENKINS-17614 when users merge their commit to master branch the build action is triggered. And changes log should be dispalyed e.g. change logs: Merge pull request #number
[JIRA] [multiple-scms-plugin] (JENKINS-9291) Plugin does not allow the URL SCM plugin to save it's configuration
Title: Message Title Craig Rodrigues resolved as Cannot Reproduce Jenkins / JENKINS-9291 Plugin does not allow the URL SCM plugin to save it's configuration Change By: Craig Rodrigues Status: Open Resolved Resolution: CannotReproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24433) Searchbox cannot be used inside a folder
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-24433 Searchbox cannot be used inside a folder Change By: Daniel Beck Labels: 1.609.1-fixedfoldersgui lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-lambda-plugin] (JENKINS-28441) refactor project for future feature additions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28441 Re: refactor project for future feature additions Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/invoke/JsonParameter.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvocationResult.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvoker.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaOutputInjectionAction.java src/main/java/com/xti/jenkins/plugin/awslambda/service/JsonPathParser.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploader.java src/main/resources/com/xti/jenkins/plugin/awslambda/LambdaVariables/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/JsonParameter/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables/config.jelly http://jenkins-ci.org/commit/aws-lambda-plugin/560d1e513f2d177fc0538395a75121187b019154 Log: JENKINS-28441 Added Lambda invoke as build step (untested) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-27423) User ID is non-sensical using saml-plugin
Title: Message Title Matias Charriere edited a comment on JENKINS-27423 Re: User ID is non-sensical using saml-plugin Hi.I'mhavingthesameproblem.EverytimeIloginanewuseriscreated . withthenon-sensicalID Enviroment:Jenkinsver.1.614onDebian7.Anyidea? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-22390) Multiple SCM plugin thinks there are changes when there are not
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-22390 Multiple SCM plugin thinks there are changes when there are not Change By: Craig Rodrigues Summary: Plug-inthings MultipleSCMpluginthinks therearechangeswhentherearenot Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-27423) User ID is non-sensical using saml-plugin
Title: Message Title Matias Charriere commented on JENKINS-27423 Re: User ID is non-sensical using saml-plugin Hi. I'm having the same problem. Every time I login a new user is created. Enviroment: Jenkins ver. 1.614 on Debian 7. Any idea? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Inv
Title: Message Title R. Tyler Croy deleted an issue Jenkins / JENKINS-28470 *Customs Clearance* facilities are very important and the facility provider offers top notch facilities to the user in this respect. The clearance assignments are generally very detailed and require lots of efforts on the part of the clearance agent. This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28512) Using global properties in job description
Title: Message Title
jjrickards created an issue
Jenkins / JENKINS-28512
Using global properties in job description
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
21/May/15 3:55 AM
Priority:
Minor
Reporter:
jjrickards
It would be nice if you could use global properties in the description of a view.
I use a global property to define the branch that is next to be released in production. It would be useful if the corresponding view would automatically reflect this branch in its description, like bNext Release: $ {NEXT_RELEASE_BRANCH}
/b
Add Comment
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title James Judd commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired I resolved the conflicts on (#131) and opened a new pull request (#147. Ran into issues using this fix. I think removing the cached connection in EC2Cloud might cause requests to be made too frequently to the metadata service. Our log file is full of these errors and jenkins stops working. The line INFO: Excess workload after pending Spot instances: 23 is strange, because we are not using spot instances. Going to try applying only the first commit from (#131) and seeing if that works, sans the fix that martin made. com.amazonaws.auth.InstanceProfileCredentialsProvider handleError SEVERE: Unable to load credentials from Amazon EC2 metadata service com.amazonaws.AmazonClientException: Unable to load credentials from Amazon EC2 metadata service at com.amazonaws.auth.InstanceProfileCredentialsProvider.handleError(InstanceProfileCredentialsProvider.java:244) at com.amazonaws.auth.InstanceProfileCredentialsProvider.loadCredentials(InstanceProfileCredentialsProvider.java:225) at com.amazonaws.auth.InstanceProfileCredentialsProvider.getCredentials(InstanceProfileCredentialsProvider.java:124) at com.amazonaws.auth.InstanceProfileCredentialsProvider$1.run(InstanceProfileCredentialsProvider.java:104) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Server returned HTTP response code: 429 for URL: http://169.254.169.254/latest/meta-data/iam/security-credentials/ at sun.reflect.GeneratedConstructorAccessor460.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1676) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1674) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1672) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1245) at com.amazonaws.internal.EC2MetadataClient.readResponse(EC2MetadataClient.java:113) at com.amazonaws.internal.EC2MetadataClient.readResource(EC2MetadataClient.java:92) at com.amazonaws.internal.EC2MetadataClient.getDefaultCredentials(EC2MetadataClient.java:55) at com.amazonaws.auth.InstanceProfileCredentialsProvider.loadCredentials(InstanceProfileCredentialsProvider.java:186) ... 9 more Caused by: java.io.IOException: Server returned HTTP response
[JIRA] [git-plugin] (JENKINS-28511) Trigger builds remotely is started but nothing changes
Title: Message Title Mark Waite commented on JENKINS-28511 Re: Trigger builds remotely is started but nothing changes I'm sorry, but your description is not sufficient for me to understand the issue you are seeing. Can you provide step by step instructions to show the problem, along with a description of the behavior you expect? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title James Judd edited a comment on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired Iresolvedtheconflictson([#131|https://github.com/jenkinsci/ec2-plugin/pull/131])andopenedanewpullrequest([#147|https://github.com/jenkinsci/ec2-plugin/pull/147] )
[JIRA] [core] (JENKINS-28512) Using global properties in job description
Title: Message Title jjrickards updated an issue Jenkins / JENKINS-28512 Using global properties in job description Change By: jjrickards ItwouldbeniceifIcoulduseglobalpropertiesinthedescriptionofajob.Wehaveaglobalvariablethatspecifiesthenameofthebranchforthenextrelease.e.g.2.12 Itwouldbenicetobeabletoexposesomeofthesevariablessowecanseethemwithaquickglance. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28512) Using global properties in job description
Title: Message Title
jjrickards updated an issue
Jenkins / JENKINS-28512
Using global properties in job description
Change By:
jjrickards
Itwouldbeniceif you I coulduseglobalpropertiesinthedescriptionofa view job . Iuse Wehave aglobal propertytodefine variablethatspecifies the nameofthe branch thatis forthe next tobereleasedinproduction release . Itwouldbeusefulifthecorrespondingviewwouldautomaticallyreflectthisbranchinitsdescription,likebNextRelease:${NEXT_RELEASE_BRANCH}/b e.g.2.12
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17290 Re: Category titles in Available Plugins list appear wrong in reverse sort order Code changed in jenkins User: ruoxijiang Path: war/src/main/webapp/scripts/sortable.js http://jenkins-ci.org/commit/jenkins/d739bedc0d5cc42aa28868fa28a709081460671c Log: [FIXED JENKINS-17290] - Corrected sort order of tables - It seems that the sort is for sorting ascending order, thus a descending order should be sorter.reverse (+1 squashed commit) Squashed commits: [a5eb304] [FIXED JENKINS-17290] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17290 Re: Category titles in Available Plugins list appear wrong in reverse sort order Code changed in jenkins User: Oleg Nenashev Path: war/src/main/webapp/scripts/sortable.js http://jenkins-ci.org/commit/jenkins/9cb9a8f63fcab3f909288c9e95d23e68e94d5b2b Log: Merge pull request #1708 from oleg-nenashev/ JENKINS-17290 -fix [FIXED JENKINS-17290] - Corrected sort order of tables Compare: https://github.com/jenkinsci/jenkins/compare/216d3355a256...9cb9a8f63fca Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
