[JIRA] [configurationslicing] (JENKINS-16869) exception when trying to open Configuration Slicing Timestamper Slicer
SCM/JIRA link daemon commented on JENKINS-16869 exception when trying to open Configuration Slicing Timestamper Slicer Code changed in jenkins User: ninian Path: src/main/java/configurationslicing/maven/MavenGoals.java src/main/java/configurationslicing/maven/MavenOptsSlicer.java src/main/java/configurationslicing/prioritysorter/PrioritySorterSlicer.java src/main/java/configurationslicing/timestamper/TimestamperSlicer.java http://jenkins-ci.org/commit/configurationslicing-plugin/712db1a2c2dadbac9a386f8180e064c380759d67 Log: JENKINS-16869: I can't reproduce the problem reported, but I do see that you can see the timestamper configuration slicer even when the timestamper plugin is not installed, which gives you this error. I've made a change so that the button is not enabled if the plugin is not available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16869) exception when trying to open Configuration Slicing Timestamper Slicer
SCM/JIRA link daemon commented on JENKINS-16869 exception when trying to open Configuration Slicing Timestamper Slicer Code changed in jenkins User: ninian Path: src/main/java/configurationslicing/maven/MavenGoals.java src/main/java/configurationslicing/maven/MavenOptsSlicer.java src/main/java/configurationslicing/prioritysorter/PrioritySorterSlicer.java src/main/java/configurationslicing/timestamper/TimestamperSlicer.java http://jenkins-ci.org/commit/configurationslicing-plugin/3373557c10f0e3bb489afa36782911c2e9b137c0 Log: Merge pull request #10 from ninian/master FIXED JENKINS-16869: Exception when clicking on timestamper link Compare: https://github.com/jenkinsci/configurationslicing-plugin/compare/62e9a94a616b...3373557c10f0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18800) Jenkins selects channel to wrong node for build job
Daniel Beck commented on JENKINS-18800 Jenkins selects channel to wrong node for build job Martin, does this issue still occur? If so, which versions of core/relevant plugins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-24998) Introduce 'Make me an owner' button
Oliver Gondža created JENKINS-24998 Introduce Make me an owner button Issue Type: Improvement Assignee: Oleg Nenashev Components: ownership-plugin Created: 05/Oct/14 11:55 AM Description: Users tends to make themselves owners more often than anyone else. Convenient button on .../ownership/manage-owners would be handy. Project: Jenkins Priority: Minor Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects
Doron Shai closed JENKINS-24924 as Not A Defect Gerrit trigger is not wokring with Maven Projects My mistake Change By: Doron Shai (05/Oct/14 12:22 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16869) exception when trying to open Configuration Slicing Timestamper Slicer
Ninian resolved JENKINS-16869 as Cannot Reproduce exception when trying to open Configuration Slicing Timestamper Slicer Can you retest with version 1.39 of configuration slicing, and re-open if it still occurs. Change By: Ninian (05/Oct/14 1:02 PM) Status: Reopened Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink] (JENKINS-23265) TestLink plugin indicates test case as not run and TestLink is not updated with build status
Vincent Piet commented on JENKINS-23265 TestLink plugin indicates test case as not run and TestLink is not updated with build status Hi, if someone is looking for integrate testlink in a CI project, have a look to https://code.google.com/p/testlink-api-java-client/ It have been developed by the same person than the jenkins plugin. You will have to parse your result file (a JUnit test suit one in my case), and to send the results to testlink. Anyway it will work in a matter of minutes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer commented on JENKINS-24860 Allow to disable build trigger Usecase: As mentioned in my second commant, we're using the plugin in combination with the pipeline view to build deployment pipelines, so we'd have deployment jobs (deploy_job1, deplob_job2, deplob_job2) that are chained by the trigger plugin (so job1 triggers job2 and so on). If we want to deploy ONLY to platform 1 (deploy_job1), we need to disable the triggering of deploy_job2. In other words, we regularly need to interrupt a deployment pipeline. And that's where a disabled state would come in very handy. It would be useful because we wouldn't have to delete and re-configer the trigger and we could avoid installing / using additional plugins like the ones recommended by you... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-parameterized-builds-report] (JENKINS-24928) spelling mistake
Nalin Makar resolved JENKINS-24928 as Fixed spelling mistake in v1.4 Change By: Nalin Makar (05/Oct/14 4:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket] (JENKINS-24999) Build triggered by SCM change without activating trigger in the job configuration
Félix Belzunce Arcos created JENKINS-24999 Build triggered by SCM change without activating trigger in the job configuration Issue Type: Bug Assignee: Félix Belzunce Arcos Components: bitbucket Created: 05/Oct/14 4:12 PM Description: In case you use the same repo in different jobs and you check the option "Build when a change is pushed to BitBucket" ONLY in one of them, then the BitBucket plugin will trigger all the jobs that use the same repo even if in the rest of them you didn't check this checkbox. This seems to be due onPost function in BitBucketTrigger that uses GitStatus.onNotifyCommit. . Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-parameterized-builds-report] (JENKINS-24927) no table background colours
Nalin Makar resolved JENKINS-24927 as Fixed no table background colours in v1.4 Change By: Nalin Makar (05/Oct/14 4:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24820) Environment is not fulfilled
Marcin Hawraniak commented on JENKINS-24820 Environment is not fulfilled Webhooks are used to notify Jenkins to start build instantly when there is a change in PR. In your case Pulling approach is ok, but hard to say if it sets SHA1 variable correctly. Have you tried GIT_COMMIT or blank (or even '*') as Branch in Git settings of your Job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-18349) Allow to use @Grab in a Script Console
Daniel Beck commented on JENKINS-18349 Allow to use @Grab in a Script Console Is this about the Groovy plugin (Groovy and system Groovy build steps), or core (Script Console in /manage and for each slave)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Daniel Beck updated JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users Change By: Daniel Beck (05/Oct/14 5:35 PM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20259) Copy Artifact plugin incorrectly copies a non-latest build
Daniel Beck resolved JENKINS-20259 as Incomplete Copy Artifact plugin incorrectly copies a non-latest build No response to comment asking for additional information in over 10 months, so resolving as incomplete. Change By: Daniel Beck (05/Oct/14 5:39 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17735) System directories like 'workspace' lose their exec bit resulting in a permission denial flaw
Daniel Beck resolved JENKINS-17735 as Duplicate System directories like workspace lose their exec bit resulting in a permission denial flaw Change By: Daniel Beck (05/Oct/14 5:43 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24521) Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
Daniel Beck commented on JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer) Linked a few issues that may be related to this. Further investigation is required to be sure though (maybe build a custom Jenkins with 4.x and ask reporters to test?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [associated-files] (JENKINS-18818) Jenkins can't launch a C++ application which uses commandes from Tekvisa Library
Daniel Beck resolved JENKINS-18818 as Incomplete Jenkins cant launch a C++ application which uses commandes from Tekvisa Library No response to comment posted months ago with suggestions what possible solutions to investigate, so resolving as Incomplete. This is more of a support request anyway; any further inquiries related to this should probably be directed to the jenkinsci-users mailing list. It's possible this happens because Jenkins runs as SYSTEM after installed as service on Windows by default (something the report does not mention). Change By: Daniel Beck (05/Oct/14 6:04 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24521) Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
Craig Rodrigues commented on JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer) @daniel: I sent a request for help to test here: https://groups.google.com/forum/#!searchin/jenkinsci-dev/jna/jenkinsci-dev/CmBBY8IPha8/fFKOKalrokQJ Also, I did some basic testing on a few platforms by exercising libpam: https://github.com/jenkinsci/jenkins/pull/1387#issuecomment-57076567 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24521) Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
Craig Rodrigues edited a comment on JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer) @daniel: I sent a request for help to test here: https://groups.google.com/forum/#!searchin/jenkinsci-dev/jna/jenkinsci-dev/CmBBY8IPha8/fFKOKalrokQJ Also, I did some basic testing on a few platforms by exercising libpam4j: https://github.com/jenkinsci/jenkins/pull/1387#issuecomment-57076567 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-17407) IllegalArgumentException: promotion when trying to configure chain of downstream promotions
Daniel Beck updated JENKINS-17407 IllegalArgumentException: promotion when trying to configure chain of downstream promotions Unrelated to core; one of the involved plugins seems to use the UpstreamCause wrong. Change By: Daniel Beck (05/Oct/14 6:47 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Daniel Beck commented on JENKINS-21422 Jenkins crashing due to out of memory when rebuilding jobs After an upgrade to version 1.546 Jenkins became very unstable Which is the last (non LTS) version this did not occur with? 1.545? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Daniel Beck commented on JENKINS-21422 Jenkins crashing due to out of memory when rebuilding jobs May have been caused by fcdf74991226fb6869052caa89ed8d678944b6fc if introduced in 1.545. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7746) Killing processes on Mac OS X/64bit VM does not work
gck commented on JENKINS-7746 Killing processes on Mac OS X/64bit VM does not work I've just checked with 1.583 and there it seems to work, both with 32bit and 64bit VM. So I guess the issue has been fixed in the meanwhile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Daniel Beck edited a comment on JENKINS-21422 Jenkins crashing due to out of memory when rebuilding jobs After an upgrade to version 1.546 Jenkins became very unstable Which is the last (non LTS) version this did not occur with? 1.545? Does this still occur in recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7746) Killing processes on Mac OS X/64bit VM does not work
Daniel Beck resolved JENKINS-7746 as Cannot Reproduce Killing processes on Mac OS X/64bit VM does not work Great, thanks for the info! Change By: Daniel Beck (05/Oct/14 7:11 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to locked (and are difficult to delete)
Daniel Beck commented on JENKINS-10197 Matrix jobs default to locked (and are difficult to delete) Is there an actual bug left to resolve here (rather than an RFE)? I mean, it's quite obvious from e.g. Jesse's comment on 27/Mar/13 that the behavior Courtney Sims describes is intended. Alexander Artemov unfortunately provided no further details what exactly he's seeing for this to be reopened, but it may well be the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7396) Sources of various Hudson pages contain default value of password parameter(s) as plain text
Daniel Beck resolved JENKINS-7396 as Duplicate Sources of various Hudson pages contain default value of password parameter(s) as plain text It seems that this has been resolved in February (possibly config form) and October (possibly build form) this year in the 2014-02-14 and 2014-10-01 security patches. I'm resolving this as duplicate (to the hidden SECURITY-138 and SECURITY-93); if you discover additional locations where passwords are displayed in plain text, please file new issues for those (preferably on the SECURITY project in this tracker, so the reports don't get overlooked as easily). Change By: Daniel Beck (05/Oct/14 7:23 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
Daniel Beck resolved JENKINS-13357 as Fixed Autoinstall JDK from download.oracle.com no longer works In 1.557, Jenkins adjusted to a change in Oracle's web site to be again able to download installers. Tracked as JENKINS-22347. If you encounter an issue similar to this one on a recent Jenkins version, please file a new issue instead of reopening this one. The cause is probably a different one. Thanks! Change By: Daniel Beck (05/Oct/14 7:54 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15996) Parmeterized Job with file upload failing
Daniel Beck commented on JENKINS-15996 Parmeterized Job with file upload failing Is this still a problem in recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17573) Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed
Daniel Beck updated JENKINS-17573 Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed Not a critical issue. Workaround is trivial, just download the war file. Unrelated to Debian Package Builder plugin. Are conflicts like this actually something that usually is resolved in the upstream projects that host their own repository? I'd expect this to be something solved in the distro's repo. Change By: Daniel Beck (05/Oct/14 8:02 PM) Priority: Critical Minor Component/s: debian-package-builder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21301) Jenkins stops responding to HTTP requests outside builds
Daniel Beck commented on JENKINS-21301 Jenkins stops responding to HTTP requests outside builds Does this issue still occur? What's the maximum heap size you assign to Jenkins (Xmx)? I'm a bit concerned given the tiny heap dump (12 files with 9 MB each). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12197) Security hole when using IPS distribution on Solaris
Daniel Beck resolved JENKINS-12197 as Wont Fix Security hole when using IPS distribution on Solaris The Jenkins project decided on September 17 to discontinue the Solaris packages. An official announcement on the users mailing list will follow. Therefore resolving as Won't Fix. Change By: Daniel Beck (05/Oct/14 8:11 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11729) Cannot install Jenkins on a fresh copy of Solaris 11
Daniel Beck resolved JENKINS-11729 as Wont Fix Cannot install Jenkins on a fresh copy of Solaris 11 The Jenkins project decided on September 17 to discontinue the Solaris packages. An official announcement on the users mailing list will follow. Therefore resolving as Won't Fix. Change By: Daniel Beck (05/Oct/14 8:11 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13905) install IPS jenkins package failed
Daniel Beck resolved JENKINS-13905 as Wont Fix install IPS jenkins package failed The Jenkins project decided on September 17 to discontinue the Solaris packages. An official announcement on the users mailing list will follow. Therefore resolving as Won't Fix. Change By: Daniel Beck (05/Oct/14 8:12 PM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15148) OpenIndiana IPS package has permissions conflict with oi_151a6
Daniel Beck resolved JENKINS-15148 as Wont Fix OpenIndiana IPS package has permissions conflict with oi_151a6 The Jenkins project decided on September 17 to discontinue the Solaris packages. An official announcement on the users mailing list will follow. Therefore resolving as Won't Fix. Change By: Daniel Beck (05/Oct/14 8:12 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7084) Unable to cancel build done on slave that disconnected
Daniel Beck resolved JENKINS-7084 as Cannot Reproduce Unable to cancel build done on slave that disconnected Given the age and nature of this issue, I think resolving for now would be best. Please file a new issue if this occurs again on a then-recent version of Jenkins. Provide the requested information so this can actually be investigated: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (05/Oct/14 8:16 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
Daniel Beck commented on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset Would be interesting to know whether this only affects Jenkins, or is an issue with your network being bad. Something like a basic telnet session may work as an indicator if it closes around the same time the slave connection breaks, it's not Jenkins. (While it would be nice to have a disconnect-resistant slave connection, that's a different issue.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14405) When 'Discard old builds' is specified using 'Max # of builds to keep' in matrix job - all job history is deleted on master together with folder for the last label used
Daniel Beck commented on JENKINS-14405 When Discard old builds is specified using Max # of builds to keep in matrix job - all job history is deleted on master together with folder for the last label used in the job Is this still an issue on recent Jenkins versions (when Matrix Project type is in a plugin)? How exactly can this be reproduced? Painfully detailed steps to reproduce the issue could help in getting a solution implemented. Besides the information requested on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue , please also provide the values for the Advanced option 'Build Record Root Directory' on the global config screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-21382) Slave node memory leak
Daniel Beck updated JENKINS-21382 Slave node memory leak Change By: Daniel Beck (05/Oct/14 8:38 PM) Component/s: remoting Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9095) Jenkins crashes with error in D-Bus : arguments to dbus_message_unref() were incorrect, assertion !message-in_cache failed in file dbus-message.c line 1397.
Daniel Beck resolved JENKINS-9095 as Cannot Reproduce Jenkins crashes with error in D-Bus : arguments to dbus_message_unref() were incorrect, assertion !message-in_cache failed in file dbus-message.c line 1397. No response to comment asking for updated information in several months, so resolving as Cannot Reproduce. If this occurs on a then-recent version of Jenkins (and only then) reopen or file a new bug. Change By: Daniel Beck (05/Oct/14 8:52 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19712) [Fingerprint] Excessive Heap consumption during Waiting for Jenkins to finish collecting data
Daniel Beck commented on JENKINS-19712 [Fingerprint] Excessive Heap consumption during Waiting for Jenkins to finish collecting data What's the situation on recent Jenkins versions? Is this issue still as severe? Jesse indicated two issues that seem to be able to improvement the situation in many environments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam resolved JENKINS-24163 as Wont Fix Allow downstream jobs to push artifact updates to upstream jobs Reported usecases should be handled by promoted-builds plugin . Change By: ikedam (05/Oct/14 11:20 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Martín Fernández commented on JENKINS-16345 CLI does not work through reverse proxy I'm having the same issue with jenkins behind an nginx reverse proxy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Mickael Ange commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException Hi, FYI: I have just installed the latest stable Jenkins version (1.565.3 LTS) and I can list plugins using CLI without the above exception. Hudson version from CLI $ java -jar ./cli-1.424.6-jar-with-dependencies.jar -s http://192.168.1.245:8080 version 1.565.3 I have activated security, created a user with admin role and added public ssh keys for my user for 2 different machines (Jenkins host and a workstation) both work. The format of my public SSH key added to my Jenkins user account is: SSH Public Keys ssh-rsa B3NzaC1yc2EDAQABAAABAQD3sZLaPWJNgMlrPlebOOQpublic key truncated 51Nz+IPoDKQ7M8LfT7jquIVTyTM2ncz3oa1HPtbXxtznUe5 mickael@jenkins ssh-rsa B3NzaC1yc2EDAQABAAABAQDvW0XDs8BH+GjY/77gXQ6O5jhGNB9public key truncatedBxc+wWMT+HlrgVB+FxyANa/PvMCNQ5Q82Mz0zrCPCVldK1LrHZJOsxL6zrYs5vG/oRpiybkyqw6Zf0y4IyShlqUCUqrJmy+61oWUrR0PX2xJ8BJuQ/kheEozGQE9K2tZ2nPAFj mickael@desktop Plugins list from CLI $ java -jar ./cli-1.424.6-jar-with-dependencies.jar -s http://192.168.1.245:8080 list-plugins subversionSubversion Plug-in 1.54 (2.4.3) matrix-projectMatrix Project Plugin1.2 (1.3) external-monitor-job External Monitor Job Type Plugin 1.2 cvs CVS Plug-in 2.11 (2.12) ssh-slavesSSH Slaves plugin1.5 (1.7.1) matrix-auth Matrix Authorization Strategy Plugin 1.1 (1.2) ssh-credentials SSH Credentials Plugin 1.6 (1.9) ant Ant Plugin 1.2 translation Translation Assistance plugin1.10 (1.11) credentials Credentials Plugin 1.9.4 (1.16.1) pam-auth PAM Authentication plugin1.1 ldap LDAP Plugin 1.6 (1.10.2) javadoc Javadoc Plugin 1.1 (1.2) windows-slavesWindows Slaves Plugin1.0 maven-plugin Maven Integration plugin 2.3 (2.6) mailerMailer Plugin1.8 (1.11) antisamy-markup-formatter OWASP Markup Formatter Plugin1.1 (1.2) Hoping that could help. Cheers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Mickael Ange edited a comment on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException Hi, FYI: I have just installed the latest stable Jenkins version (1.565.3 LTS) and I can list plugins using CLI without the above exception. Hudson version from CLI $ java -jar ./cli-1.424.6-jar-with-dependencies.jar -s http://192.168.1.245:8080 version 1.565.3 I have activated security, created a user with admin role and added public ssh keys for my user for 2 different machines (Jenkins host and a workstation) both work. The format of my public SSH key added to my Jenkins user account is: SSH Public Keys ssh-rsa B3NzaC1yc2EDAQABAAABAQD3sZLaPWJNgMlrPlebOOQpublic key truncated 51Nz+IPoDKQ7M8LfT7jquIVTyTM2ncz3oa1HPtbXxtznUe5 mickael@jenkins ssh-rsa B3NzaC1yc2EDAQABAAABAQDvW0XDs8BH+GjY/77gXQ6O5jhGNB9public key truncatedBxc+wWMT+HlrgVB+FxyANa/PvMCNQ5Q82Mz0zrCPCVldK1LrHZJOsxL6zrYs5vG/oRpiybkyqw6Zf0y4IyShlqUCUqrJmy+61oWUrR0PX2xJ8BJuQ/kheEozGQE9K2tZ2nPAFj mickael@desktop Plugins list from CLI $ java -jar ./cli-1.424.6-jar-with-dependencies.jar -s http://192.168.1.245:8080 list-plugins subversionSubversion Plug-in 1.54 (2.4.3) matrix-projectMatrix Project Plugin1.2 (1.3) external-monitor-job External Monitor Job Type Plugin 1.2 cvs CVS Plug-in 2.11 (2.12) ssh-slavesSSH Slaves plugin1.5 (1.7.1) matrix-auth Matrix Authorization Strategy Plugin 1.1 (1.2) ssh-credentials SSH Credentials Plugin 1.6 (1.9) ant Ant Plugin 1.2 translation Translation Assistance plugin1.10 (1.11) credentials Credentials Plugin 1.9.4 (1.16.1) pam-auth PAM Authentication plugin1.1 ldap LDAP Plugin 1.6 (1.10.2) javadoc Javadoc Plugin 1.1 (1.2) windows-slavesWindows Slaves Plugin1.0 maven-plugin Maven Integration plugin 2.3 (2.6) mailerMailer Plugin1.8 (1.11) antisamy-markup-formatter OWASP Markup Formatter Plugin1.1 (1.2) Java on the desktop $ java -version java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) Java on Jenkins host $ java -version java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) Hoping that could help. Cheers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9774) Enabling Project Matrix Authorization Strategy without checking any permissions causes config.xml parsing to fail
Mickael Ange commented on JENKINS-9774 Enabling Project Matrix Authorization Strategy without checking any permissions causes config.xml parsing to fail Hi, I have 2 Jenkins instances in testing (1.565.3) with a unique administrator account for username mickael. I configured "Project-based Matrix Authorization Strategy" on both and I don't know why (maybe my bad during the process), one instance failed to restart after installing thinBackup plugin from CLI. Oct 06, 2014 11:50:16 AM hudson.util.BootFailure publish SEVERE: Failed to initialize Jenkins hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:916) at jenkins.model.Jenkins.init(Jenkins.java:815) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at jenkins.model.Jenkins$17.run(Jenkins.java:2565) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.thoughtworks.xstream.converters.ConversionException: only START_TAG can have attributes END_TAG seen ...ategy class="hudson.security.ProjectMatrixAuthorizationStrategy"/... @8:86 : only START_TAG can have attributes END_TAG seen ...ategy class="hudson.security.ProjectMatrixAuthorizationStrategy"/... @8:86 Debugging information message : only START_TAG can have attributes END_TAG seen ...ategy class="hudson.security.ProjectMatrixAuthorizationStrategy"/... @8:86 cause-exception : java.lang.IndexOutOfBoundsException cause-message : only START_TAG can have attributes END_TAG seen ...ategy class="hudson.security.ProjectMatrixAuthorizationStrategy"/... @8:86 class : hudson.security.ProjectMatrixAuthorizationStrategy required-type : hudson.security.ProjectMatrixAuthorizationStrategy converter-type : hudson.util.XStream2$AssociatedConverterImpl path: /hudson/authorizationStrategy line number : 8 class[1]: hudson.model.Hudson converter-type[1] : hudson.util.RobustReflectionConverter version : not available --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:349) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:289) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at hudson.XmlFile.unmarshal(XmlFile.java:163)
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
rin_ne updated JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please get log using attached pom.xml (goal: compile) Change By: rin_ne (06/Oct/14 4:52 AM) Attachment: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-24995) New Swarm Slave Wont Work
Peter Jönsson started work on JENKINS-24995 New Swarm Slave Wont Work Change By: Peter Jönsson (06/Oct/14 5:40 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-24995) New Swarm Slave Wont Work
SCM/JIRA link daemon commented on JENKINS-24995 New Swarm Slave Wont Work Code changed in jenkins User: nico.mommaerts Path: plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/e3bcd9c5ef89466d989d2fd7a6720e5e16e82a84 Log: JENKINS-24995 fixed exception when not passing any toollocations This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-24995) New Swarm Slave Wont Work
Peter Jönsson assigned JENKINS-24995 to Peter Jönsson New Swarm Slave Wont Work Change By: Peter Jönsson (06/Oct/14 5:40 AM) Assignee: KohsukeKawaguchi PeterJönsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-7543) Set tool locations from Swarm plugin CLI
Peter Jönsson resolved JENKINS-7543 as Fixed Set tool locations from Swarm plugin CLI Change By: Peter Jönsson (06/Oct/14 5:40 AM) Status: Open Resolved Assignee: KohsukeKawaguchi PeterJönsson Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Daniel Beck commented on JENKINS-16345 CLI does not work through reverse proxy Martin: Be more specific. Provide the information requested here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-24995) New Swarm Slave Wont Work
Peter Jönsson commented on JENKINS-24995 New Swarm Slave Wont Work New version being released with a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-24995) New Swarm Slave Wont Work
Peter Jönsson resolved JENKINS-24995 as Fixed New Swarm Slave Wont Work Change By: Peter Jönsson (06/Oct/14 5:42 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
