[JIRA] [core] (JENKINS-26977) H/15 * * * * generates random times for builds, not for polls
Albert Albala created JENKINS-26977 H/15 * * * * generates random times for builds, not for polls Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-02-16 at 10.57.32 AM.png Components: core Created: 16/Feb/15 4:10 PM Description: On Jenkins 1.580.2, as per http://htmlpreview.github.io/?https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.html, I am expecting H/15 * * * * to generate random times depending on the project, but to run every fifteen minutes. This works fine for builds, but not for polling, as you can see on the included image. Related: https://issues.jenkins-ci.org/browse/JENKINS-15027 http://stackoverflow.com/questions/26513386 Thanks! Albert. Project: Jenkins Priority: Minor Reporter: Albert Albala 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] [delivery-pipeline-plugin] (JENKINS-25379) Manual trigger execution causes TriggerException using a 32bits jdk
Sune Keller commented on JENKINS-25379 Manual trigger execution causes TriggerException using a 32bits jdk I can reproduce this on Jenkins ver. 1.585 with: JAVA_HOME=C:\tools\Java\jdk1.7.0_25 java -version yields: java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b17) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) 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-plugin] (JENKINS-26403) SNI Support when using Artifactory behind HTTPS
Justin Plock commented on JENKINS-26403 SNI Support when using Artifactory behind HTTPS This doesn't appear to be specific to just artifactory. Anything using the maven-deploy-plugin and trying to upload artifacts to an SSL host that has multiple certificates sharing the same IP address has this problem. 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] [performance-plugin] (JENKINS-24653) Performance plugin JUnitParser.java ignores classname attribute.
SCM/JIRA link daemon commented on JENKINS-24653 Performance plugin JUnitParser.java ignores classname attribute. Code changed in jenkins User: hitesh Path: src/main/java/hudson/plugins/performance/JUnitParser.java src/test/java/hudson/plugins/performance/PerformanceReportTest.java http://jenkins-ci.org/commit/performance-plugin/25c7a1e1740bfc1ff6a953739bfeeea3a82cc1b0 Log: Add classname attribute to URI when parsing JUnit test results. Jenkins-24653 Fixes JENKINS-24653 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-26977) H/15 * * * * generates random times for builds, not for polls
Daniel Beck assigned JENKINS-26977 to Daniel Beck H/15 * * * * generates random times for builds, not for polls Change By: Daniel Beck (16/Feb/15 5:13 PM) Assignee: DanielBeck 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] [performance-plugin] (JENKINS-26515) Concurrent builds using Performance plugin wait for post build task to be finished by the build started earlier which hasn’t finished yet
SCM/JIRA link daemon commented on JENKINS-26515 Concurrent builds using Performance plugin wait for post build task to be finished by the build started earlier which hasn’t finished yet Code changed in jenkins User: Barna Csorogi Path: src/main/java/hudson/plugins/performance/PerformancePublisher.java src/main/java/hudson/plugins/performance/PerformanceReportMap.java http://jenkins-ci.org/commit/performance-plugin/e02e148ff9210c88eaa4e79c8c61dab80a1f8411 Log: Generate performance report even if previous builds are still running Fixes JENKINS-26515 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Manuel Carrasco resolved JENKINS-22011 as Fixed Performance plugin report not failing build based on relative thresholds. Change By: Manuel Carrasco (16/Feb/15 4:34 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] [gradle-jpi-plugin] (JENKINS-26377) exception when running seed job on test server
SCM/JIRA link daemon commented on JENKINS-26377 exception when running seed job on test server Code changed in jenkins User: Stefan Wolf Path: src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiHplManifest.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/6a44e85589990be23e4912c33ea3d444743a0dcd Log: FIXED JENKINS-26377 Use classpath from JPI-Task instead of runtimeClasspath 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] [_test] (JENKINS-26979) Jual Obat Penggugur Kandungan 082282125243 BBM:2A221109
patmo45 motu57 created JENKINS-26979 Jual Obat Penggugur Kandungan 082282125243 BBM:2A221109 Issue Type: New Feature Assignee: Oleg Nenashev Attachments: cytotec.jpg Components: _test, feature-branch-notifier-plugin Created: 16/Feb/15 7:51 PM Description: PEMESANAN : 082282125243 BBM:2a221109 Bila anda mengalami masalah keterlambatan haid yang tidak lancar hingga di cek tes kehamilan hasilnya positif, dan anda belum menginginkannya terlebih dahulu dikarenakan masih ingin mengejar karier atau study anda. kami menyediakan obat aborsi atau menggugurkan kandungan. dengan setiap obat yang disediakan mempunyai tingkat keberhasilan hingga 95%. tingkat keberhasilan tersebut dihasilkan dan diperkirakan berdasarkan hasil dari setiap pengguna obat di situs kami. dan yang setiap pengguna mempunyai keadaan dan kondisi yang berbeda-beda. Adapun macam obat yang kami sediakan dibedakan menurut usia keterlambatan, dan disesuaikan dengan dosis yang sudah ditentukan untuk memberikan hasil yang maksimal bagi pengguna dan aman untuk digunakan. tidak membahayakan dan tidak mempunyai efek berkepanjangan seperti mandul dan sebagainya. karena obat yang kami sediakan ditambahkan dengan obat pembersih untuk mengurangi resiko pada pengguna dan rahim pengguna. Dan pembagaian obat yang kami sediakan serta masih mampu untuk digugurkan atau dilunturkan adalah sebagai berikut Usia 1 bulan ( paket-Cytotec One ) dosis 350mg *** harga : 500.000 Usia 2 bulan ( paket-Cytotec Pra ) dosis 450mg *** harga : 750.000 Usia 3 bulan ( paket-Cytotec Plus ) dosis 600mg *** harga : 950.000 Usia 4 bulan ( paket-Cytotec Gold ) dosis 800mg *** harga : 1.000.000 Usia 5 bulan ( paket Mefirex Plus ) dosis 1000mg *** harga : 1.300.000 Usia 6 bulan ( paket Mefirex+Cytotec ) dosis 1250mg *** harga : 1.600.000 Untuk paket obat diatas, per paket ada 3 macam obat seperti Cytotec/Mefirex, Obat herbal untuk mengeluarkan, Obat pembersih untuk membersihkan pada sesi setelah proses persalinan. dari ketiga macam obat tersebut sudah dibagikan dosis-dosis yang sudah ditentukan dan yang harus digunakan. Proses reaksi yang terjadi setelah dimulai penggunaan membutuhkan waktu kurang lebih 2x24 jam setelah penggunaan obat pertama, dan reaksi yang terjadi mulai dari keluar flek darah, gumpalan darah dan cairan darah. untuk rasa dan sebagainya itu merupakan relatif bagi setiap pengguna, dan menyesuaikan daya tahan tubuh dan sebagainya. yang terpenting sebelum menggunakan obat tersebut dianjurkan untuk melakukan pemeriksaan terlebih dahulu untuk mengetahui kondisi tubuh dan kondisi yang ada di rahim. paling tidak untuk daya tahan tubuh anda mengetahui anda tidak sedang sakit atau kurang darah dan sebagainya. sedangkan pemeriksaan di dalam rahim menentukan usia serta dosis yang akan anda gunakan. proses reaksi yang kami sebutkan berdasarkan perkiraan dari setiap pengguna yang sudah melaluinya dan setiap pengguna mempunyai reaksi yang berbeda-beda berdasarkan usia keterlambatan, kondisi tubuh, kekuatan janin dan yang mungkin dapat menjadikan proses persalinan membutuhkan waktu. PEMESANAN DAN KONSULTASI HUB :082282125243 Untuk pembayaran via transfer bisa melalui bank : BCA,BRI,MANDIRI Setelah anda transfer silahkan anda konfirmasi Ke 0822 8212 5243 NAMA ANDA, ALAMAT ANDA, JENIS PESANAN, TRANSFER KE BANK, JUMLAH TRANSFER. Setelah Uang masuk pesanan langsung kami kirim melalui JASA PENGIRIMAN kilat khusus sesuai dengan kesepakatan. TIKI-JNE-POS * Pesanan dalam waktu singkat Pasti sampai tujuan * * Environment: sehat Project: Jenkins Labels: Obat Pelancar Penggugur Kandungan Aborsi Janin
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=rtyleravatarId=10787;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=rtyler
id=email_rtyler
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=rtyler;
style=color:#355564;R. Tyler Croy/a
deleted img
src=https://issues.jenkins-ci.org/images/icons/newfeature.gif; height=16
width=16 border=0 align=absmiddle alt=New Feature
[JIRA] [core] (JENKINS-26977) H/15 * * * * generates random times for builds, not for polls
Daniel Beck commented on JENKINS-26977 H/15 * * * * generates random times for builds, not for polls Good news, this is only a UI issue. The actual polling times are the ones as reported by the timer trigger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-24782) Clicking Build Now on a Promotion results in a phantom, unkillable build
Jesse Glick commented on JENKINS-24782 Clicking Build Now on a Promotion results in a phantom, unkillable build Customizing the sidepanel seems reasonable, though this seems too high level; there are other build triggers. Not sure what else to suggest, though. This whole plugin is very weird and a lot of things do not behave reasonably. Independently, there seems to be a robustness bug in Promotion.getTarget: should check pta == null. 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] [gradle-jpi-plugin] (JENKINS-26377) exception when running seed job on test server
Daniel Spilker resolved JENKINS-26377 as Fixed exception when running seed job on test server Will be released in gradle-jpi-plugin 0.9.1. Change By: Daniel Spilker (16/Feb/15 7:15 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] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
Raphael CHAUMIER closed JENKINS-26901 as Fixed Not possible to run freestyle job with non-set baseDirectory Change By: Raphael CHAUMIER (16/Feb/15 8:33 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] [promoted-builds-plugin] (JENKINS-24782) Clicking Build Now on a Promotion results in a phantom, unkillable build
recampbell commented on JENKINS-24782 Clicking Build Now on a Promotion results in a phantom, unkillable build The fundamental problem here is that the PromotionProcess must be buildable, but should not have a "Build Now" button. To be more precise PromotionProcess must return true for isBuildable() so that AbstractProject.scheduleBuild2() will actually perform the build. So we can't just return false for isBuildable(). So it seems to me that the simplest approach is just to customize the left-hand menu for this PromotionProcess to avoid displaying the "Build Now" button. 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] [gradle-jpi-plugin] (JENKINS-26377) exception when running seed job on test server
Daniel Spilker updated JENKINS-26377 exception when running seed job on test server I changed the component to gradle-jpi-plugin since the issue is going to be fixed there: https://github.com/jenkinsci/gradle-jpi-plugin/pull/43 Change By: Daniel Spilker (16/Feb/15 7:07 PM) Component/s: gradle-jpi-plugin Component/s: job-dsl-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26978) Wrong capitalization in Build step 'XCode' marked build as failure
Quinn Taylor created JENKINS-26978 Wrong capitalization in Build step XCode marked build as failure Issue Type: Improvement Assignee: Unassigned Components: xcode-plugin Created: 16/Feb/15 7:45 PM Description: The failure message says "Build step 'XCode' marked build as failure", but XCode should be Xcode. Environment: Jenkins 1.583 on OS X Project: Jenkins Priority: Minor Reporter: Quinn Taylor 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] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
Kevin Cheng commented on JENKINS-26797 Zombie instance created by the EC2 plugins I upgraded one of my Jenkins instance plugin to 1.26. I still see the zombie issue (but probably not as severe). From Chris' comment about the master lost connection to slave, I am not sure if that is my original case which I have instances with all the tagging key-value set but not the "name" tag. If the slave has ever connected to the master once, and some how lost the registration, I do not think the behavior observed would fall into this situation. I do have another ticket about "out-of-sync" issue JENKINS-26798 - High occurrence of out-sync EC2 slaves 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-plugin] (JENKINS-26403) SNI Support when using Artifactory behind HTTPS
yossis commented on JENKINS-26403 SNI Support when using Artifactory behind HTTPS We upgraded the http client to support SNI. Please track the issue on the official plugin Jira - https://www.jfrog.com/jira/browse/HAP-556 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] [weblogic-deployer-plugin] (JENKINS-20351) Recursive artifact search
Raphael CHAUMIER started work on JENKINS-20351 Recursive artifact search Change By: Raphael CHAUMIER (16/Feb/15 8:35 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-20351) Recursive artifact search
Raphael CHAUMIER closed JENKINS-20351 as Fixed Recursive artifact search Change By: Raphael CHAUMIER (16/Feb/15 8:36 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] [weblogic-deployer-plugin] (JENKINS-20351) Recursive artifact search
Raphael CHAUMIER resolved JENKINS-20351 as Fixed Recursive artifact search Change By: Raphael CHAUMIER (16/Feb/15 8:36 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-2717) svn polling without checkout or update
Jesse Glick commented on JENKINS-2717 svn polling without checkout or update Unless I am missing something, this is invalid in current plugin code. AbstractProject._poll first checks requiresWorkspaceForPolling. The implementation of this in SubversionSCM returns false unconditionally. (compareRemoteRevisionWith does include code to handle workspace != null, but it seems this will always in fact be null when called from _poll via SCM.poll…meaning that isPollFromMaster, setPollFromMaster, pollFromMaster, and POLL_FROM_MASTER are all dead code.) 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] [robot-plugin] (JENKINS-26980) Enable configuration of Robot Results column in the default job list view
Daniel Beck commented on JENKINS-26980 Enable configuration of Robot Results column in the default job list view Should probably suffice to not make it a default column. Whoever wants it can add it. 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] [robot-plugin] (JENKINS-26980) Enable configuration of Robot Results column in the default job list view
Michael Toothaker created JENKINS-26980 Enable configuration of Robot Results column in the default job list view Issue Type: Improvement Assignee: Unassigned Components: robot-plugin Created: 16/Feb/15 9:14 PM Description: As an administrator of an enterprise Jenkins master server, I would like the ability to configure whether the "Robot Results" column is displayed in the default job list view. The use case for this is a situation where multiple development and QA teams are using the same Jenkins master server and some of those teams may be dependent on using the Robot Framework while others have no interest in it at all (and may be using completely different development tools). It is currently possible to work around this issue by modifying folder views, but it would be nice to have an option to disable the Robot Results column so that the plugin works better in a multi-tenant environment without manually editing views. Environment: Jenkins v1.580 Robot Plugin v1.5.0 Project: Jenkins Priority: Minor Reporter: Michael Toothaker 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] [robot-plugin] (JENKINS-26980) Enable configuration of Robot Results column in the default job list view
Michael Toothaker commented on JENKINS-26980 Enable configuration of Robot Results column in the default job list view I will be submitting a pull request for this soon, I just wanted to get an issue created to track the use case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-2717) svn polling without checkout or update
Jesse Glick commented on JENKINS-2717 svn polling without checkout or update Let me amend that. In 2.4 and earlier, even though compareRemoteRevisionWith was being passed a null workspace (because it affirms it does not requiresWorkspaceForPolling), it nonetheless looked up the slave to run the last build and, if still online, did its polling from there! (Not in any particular working directory, and not locking the workspace, but on the same machine.) So it would have polled from the master despite doing checkouts on a slave only under some conditions: -Dhudson.scm.SubversionSCM.pollFromMaster was passed as a startup option; the slave has since been disconnected; all builds got deleted; etc. Now in 2.5, this change plus this correction mean that polling is unconditionally done on the master, and so the flags to control that are dead code, and CompareAgainstBaselineCallable is passed to a LocalChannel which calls it directly. Thus the issue of polling without requiring a slave was fixed inadvertently. The question remains whether the change was desirable or not. Generally it is cheaper and better to do polling from the master. There are however uncommon reasons why you might want to poll on a slave, for example: the master has no physical access to the Subversion server due to network topology; Subversion credentials are kept in ~/.subversion/auth/ only on slaves, not using the Credentials plugin. Perhaps the ability to poll from the slave ought to be reintroduced, ideally as a per-job UI option. (requiresWorkspaceForPolling probably needs to remain off, since it is not necessary to lock the workspace to poll, merely to run from the same machine and user account.) Anyway, rereading the original description of this issue, it was about something else entirely: the ability to use the Jenkins plugin only for polling, but performing actual checkout operations from the job’s build script. This is simply not supported in Jenkins generally, not the fault of the Subversion plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-26235) Tab customizations
Steve Springett commented on JENKINS-26235 Tab customizations I finally got around to this enhancement again. I've successfully implemented the changing of tab labels in the Dependency-Check plugin. Seems to work fine. 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] [other] (JENKINS-2107) email notification when disk space runs low.
Tim Bradt reopened JENKINS-2107 email notification when disk space runs low. I don't like the fix, personally. And I also don't think it satisfied the original request which allows no room for an offline node. I just implemented Oleg's suggested solution, but my complaint with it is that it takes the node (master or slave) offline in order to achieve the desired notification. That means I could very well have a build in progress when free disk space falls below the setting, and then the node will be taken offline. That's not at all what I want! I want to be proactive, and set a threshold that lets me know I'm running a bit low on disk space so that I can address it BEFORE it impacts a single build. Node monitoring and notification based on online/offline status certainly does not meet that need. At that point it's still too late. Whether I run out of disk space or the node goes offline, the result is the same - I've just failed a build. Please feel free to correct me if I misinterpreted the resolution, as it seemed a bit open to interpretation. Change By: Tim Bradt (16/Feb/15 10:28 PM) Resolution: Fixed Status: Resolved Reopened 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] [other] (JENKINS-2107) email notification when disk space runs low.
Daniel Beck commented on JENKINS-2107 email notification when disk space runs low. if I misinterpreted the resolution Node monitors mark nodes as offline, they don't disconnect. Your build will continue, just no further builds will be started. Have you even tried the solution before commenting on it? 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-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
lacostej created JENKINS-26982 On MacOSX, pkg installation doesnt set newsyslog permissions properly Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Feb/15 5:47 AM Description: Every time I reinstall jenkins I have to reset the /var/log/jenkins permissions Project: Jenkins Priority: Minor Reporter: lacostej 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-26983) On MacOSX, pkg installation reset the daemon defaults values
lacostej created JENKINS-26983 On MacOSX, pkg installation reset the daemon defaults values Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Feb/15 5:51 AM Description: Every time I reinstall jenkins I have to reset the defaults daemon permissions that I have overiden. Project: Jenkins Priority: Minor Reporter: lacostej This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26984) Plugin doesn't resolve variables during form validation
Valentin Baranov created JENKINS-26984 Plugin doesnt resolve variables during form validation Issue Type: Bug Assignee: huybrechts Attachments: ResolveError.png, ResolveError2.png Components: parameterized-trigger-plugin Created: 17/Feb/15 7:08 AM Description: Hello. I have some usability problems while using the following plugin: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin I'm using the reference instead of direct projects comma-separated list. There's no problem with the call itself (references are resolved during the call), but form validator shows the error message. There is an unresolved parameter name on the project page, too (see the attached screenshots). Can you please fix this? Project: Jenkins Priority: Major Reporter: Valentin Baranov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26984) Plugin doesn't resolve variables during form validation
Valentin Baranov updated JENKINS-26984 Plugin doesnt resolve variables during form validation Change By: Valentin Baranov (17/Feb/15 7:10 AM) Description: Hello.Ihavesomeusabilityproblemswhileusingthefollowingplugin:https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+PluginImusingthereferenceinsteadofdirectprojectscomma-separatedlist.Theresnoproblemwiththecallitself(referencesareresolvedduringthecall),butformvalidatorshowstheerrormessage.Thereisanunresolvedparameternameontheprojectpage,too(seetheattachedscreenshots).Canyoupleasefixthis? P.S.SorryforRussianlocaleonscreens,cannotturnitoff. 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] [disk-usage-plugin] (JENKINS-24182) Disk Usage plugin throws NullPointerException preventing Maven jobs from loading
Steven Christou started work on JENKINS-24182 Disk Usage plugin throws NullPointerException preventing Maven jobs from loading Change By: Steven Christou (17/Feb/15 7:58 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] [disk-usage-plugin] (JENKINS-24182) Disk Usage plugin throws NullPointerException preventing Maven jobs from loading
Steven Christou assigned JENKINS-24182 to Steven Christou Disk Usage plugin throws NullPointerException preventing Maven jobs from loading Change By: Steven Christou (17/Feb/15 7:58 AM) Assignee: LucieVotypkova StevenChristou 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Marko Macek commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. Has my patch been applied? I really need support for *.jtl in relative comparisons to work. 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] [disk-usage-plugin] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Steven Christou resolved JENKINS-21259 as Duplicate Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Change By: Steven Christou (16/Feb/15 11:12 PM) Status: Open Resolved Assignee: LucieVotypkova StevenChristou 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] [warnings-plugin] (JENKINS-26913) Add more information about warnings for multi-configuration projects
Ulli Hafner edited a comment on JENKINS-26913 Add more information about warnings for multi-configuration projects As a first workaround I appended the configuration name to the module name. Is the module name normally used in your use case or is it empty? I'm not sure if it is worth the effort to create a new tab or if the existing module tab can be reused here. (As the package tab is used for folders if the project does not support packages). What do you think? Is this already enough? You can grab the latest build from our CI server, see wiki link. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26913) Add more information about warnings for multi-configuration projects
SCM/JIRA link daemon commented on JENKINS-26913 Add more information about warnings for multi-configuration projects Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java http://jenkins-ci.org/commit/warnings-plugin/214ad4fbd7e42b5b74ac415fc31345a3f5a777d5 Log: JENKINS-26913 Append the configuration name to the module name when aggregating the warnings of a matrix build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26981) Git plugin ignores the branch we tell it to build and builds a random branch instead
Nadav Samet
created JENKINS-26981
Git plugin ignores the branch we tell it to build and builds a random branch instead
Issue Type:
Bug
Assignee:
Nicolas De Loof
Attachments:
Selection_024.png
Components:
git-client-plugin
Created:
17/Feb/15 1:29 AM
Description:
I have the "refspec" empty so git plugin fetches all remote branches as documented. We are only interested in building origin/master (but we need the other branches around for the build).
I am trying to put in the branch settings things like "refs/remotes/origin/master" or just "origin/master" but whatever I type in is ignored and some other remote branch gets built. It seems like whatever gets typed in in that input box has no effect whatsoever. Even if I type a reference that does not exists like "ref/foo/bar", it will (a) not give an error, and (b) check the same random branch. Here is a console output that demonstrates:
Started by user User (user)
Building in workspace /var/lib/jenkins/jobs/continuous_test/workspace
git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
git config remote.origin.url ssh://jenki...@gerrit.domain.com:29418/Collectr.git # timeout=10
Fetching upstream changes from ssh://jenki...@gerrit.domain.com:29418/Collectr.git
git --version # timeout=10
git -c core.askpass=true fetch --tags --progress ssh://jenki...@gerrit.domain.com:29418/Collectr.git +refs/heads/*:refs/remotes/origin/*
git rev-parse FETCH_HEAD^{commit} # timeout=10
Checking out Revision 02a1ad8196306911dd4ee6749326c69d549c4cba (refs/foo/bar)
Notice the "refs/foo/bar" at the end? It always checkouts the same commit, no matter what branch I give it.
Environment:
Git client plugin: 1.16.1
Git plugin: 2.3.4
Project:
Jenkins
Labels:
plugin
Priority:
Minor
Reporter:
Nadav Samet
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26981) Git plugin ignores the branch we tell it to build and builds a random branch instead
Nadav Samet commented on JENKINS-26981 Git plugin ignores the branch we tell it to build and builds a random branch instead Hmm. Minutes after submitting this I realized that the "Strategy" of the build was "Gerrit", when I changed it to "Default" it started working correctly. Feel free to close. However, the line that it says it is checking out the branch with the name I've given (but a different commit) got me side tracked. I think the behavior of the plugin could be improve by saying that this option is ignored when a non-default strategy is chosen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26913) Add more information about warnings for multi-configuration projects
Ulli Hafner commented on JENKINS-26913 Add more information about warnings for multi-configuration projects As a first workaround I appended the configuration name to the module name. Is the module name normally used in your use case or is it empty? I'm not sure if it is worth the effort to create a new tab or if the existing module tab can be reused here. (As the package tab is used for folders if the project does not support packages). What do you think? Is this already enough? 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] [chef-plugin] (JENKINS-26972) Chef Plugin | run chef-client remotely under Jenkins CI not working
Mike Mochan commented on JENKINS-26972 Chef Plugin | run chef-client remotely under Jenkins CI not working I also have a number of ruby-runtime plugins that exhibit this same behavior since upgrading to 1.598 and 1.599 As a temporary solution roll back to Jenkins 1.597 and the Chef plugin should work. 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-26973) Support project-specific security in Matrix based security plugin
vikas choudhary commented on JENKINS-26973 Support project-specific security in Matrix based security plugin The following steps produce the issue: 1. I installed the ownership plugin. 2. After I globally configured it like (enable "Assign job creators as owners"), uncheck the option "Setup default permissions for jobs item-specific security" . 3. On the job configuration page, I clicked "Manage Ownership" then "Manage Owners" and add a user as owner. 4. Next, I clicked "Configure specific access rights" in the same page and add the user and assign him some permissions presented in the matrix (after checking the option "Use item-specific security" and then "Enable project-based security" . 5. Now after the user login, the user is not able to see the options in the job page. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-26973) Support project-specific security in Matrix based security plugin
Oleg Nenashev commented on JENKINS-26973 Support project-specific security in Matrix based security plugin If "Configure specific access rights" is designed to work with Role Strategy Plugin only then how one can manage the ownership in case of "Matrix based security" in the global security ?? Is it possible in this case?? No. This control only manages the permission to change ownership configs. You can edit the product-specific security, but it won't affect security checks When I try to add new user/group in Global configuration setttings in Jenkins, it displays the user as ERROR in the screenshot attached in this comment. Yes, it's a bug. See JENKINS-22869 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Sarah Woodall commented on JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Here is my stack trace. I'm executing a freestyle matrix job. My master is on a Mac, and this matrix job runs on multiple heterogeneous slaves (hence the use of the XShell plugin), but on this particular occasion it was a slave instance on a Mac that we wanted to abort. This is what appeared in the Jenkins log (with project name and slave name edited): INFO: TestMatrixMyProjectName/SLAVE=MyMacSlave #308 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:742) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy54.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:961) at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) The processes on the Mac carried on running, even though it appeared from the Jenkins dashboard that the job had been aborted successfully. 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] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Karl Apsite commented on JENKINS-26572 Log Parser incompatible with Jenkins 1.597 (build record change) I pulled the source, and it compiles and loads fine on a personal server... I even parsed output from a WebStart slave. I ran into an access violation when I tried to use an SSH slave, so I'm not certain where that leaves this bug. It's been worked on... but I don't know when we'll see a release. 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-failure-analyzer-plugin] (JENKINS-26969) I like it is possible to select that BFA set failed build status as ABORTED
Kari Sivonen commented on JENKINS-26969 I like it is possible to select that BFA set failed build status as ABORTED There is only possibility to get information that build is failed, if you check only build status. So environment failures is seen as other failures. That why we used this BFA for getting information why it is failed. But in case of environment failure we don't want show those builds on radiators etc. So question is if BFS could abort the build in certain failure causes. Of course because BFA is run after other task so abort can be done only post build phase and in this case I think it is enough to mark build aborted, without really aborting anything. So could this plugin get abort the build if certain failure found? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26944) Subversion plugin does not resolve environment variables for SCM polling
Tim Bradt commented on JENKINS-26944 Subversion plugin does not resolve environment variables for SCM polling Agree that the defects themselves are different. I was just pointing to a comment within that bug that seemed relevant to this subject, though I'm be happy to know I apparently misinterpreted. 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] [hipchat-plugin] (JENKINS-26974) Allow notification background color to be passed from Jenkins
Jim Priest created JENKINS-26974 Allow notification background color to be passed from Jenkins Issue Type: Improvement Assignee: Unassigned Components: hipchat-plugin Created: 16/Feb/15 2:20 PM Description: The current HipChat API supports passing in a color to set the background color of the notification. It would be nice if the Jenkins plugin allowed us to set this color so we could differentiate notifications from Jenkins (JIRA = red, Jenkins = blue) etc. Environment: Current Jenkins hipchat plugin Project: Jenkins Labels: hipchat Priority: Minor Reporter: Jim Priest 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] [gradle-jpi-plugin] (JENKINS-12193) Hook up injected tests
Daniel Spilker closed JENKINS-12193 as Fixed Hook up injected tests Released in 0.9.0. Change By: Daniel Spilker (16/Feb/15 2:31 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] [gradle-jpi-plugin] (JENKINS-25007) Publish Plugin JAR
Daniel Spilker resolved JENKINS-25007 as Fixed Publish Plugin JAR Will be released in 0.9.0. Change By: Daniel Spilker (16/Feb/15 2:03 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] [gradle-jpi-plugin] (JENKINS-25007) Publish Plugin JAR
SCM/JIRA link daemon commented on JENKINS-25007 Publish Plugin JAR Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md build.gradle gradle/wrapper/gradle-wrapper.jar gradle/wrapper/gradle-wrapper.properties src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/fb2b31368ce69c9f695f86e2bdae2e82871b4771 Log: Merge pull request #41 from daspilker/JENKINS-25007 JENKINS-25007 Update to Gradle 2.3, publish JAR Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/0031ffab8800...fb2b31368ce6 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] [gradle-jpi-plugin] (JENKINS-25007) Publish Plugin JAR
SCM/JIRA link daemon commented on JENKINS-25007 Publish Plugin JAR Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/14a2edf34e7398c3f66870effa9a46fdfbdf95bf Log: publish the plugin JAR, fixes JENKINS-25007 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] [gradle-jpi-plugin] (JENKINS-25007) Publish Plugin JAR
Daniel Spilker closed JENKINS-25007 as Fixed Publish Plugin JAR Change By: Daniel Spilker (16/Feb/15 2:31 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] [jacoco-plugin] (JENKINS-26254) Jacoco plugin is too slow and occupies too much microprocessor time
Sean Flanigan commented on JENKINS-26254 Jacoco plugin is too slow and occupies too much microprocessor time This discussion might be relevant to the slow serialisation of .exec files: https://groups.google.com/d/topic/jacoco/4f0rf3zqYKY/discussion 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-plugin] (JENKINS-25391) Cannot delete project
Idan Bidani commented on JENKINS-25391 Cannot delete project Thanks Daniel, Sorry, I can't reproduce this issue. Morne do you know what's the steps to reproduce this? otherwise I'll close this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-26973) Manage ownership not working with the global security method Matrix based security
Oleg Nenashev commented on JENKINS-26973 Manage ownership not working with the global security method Matrix based security "Configure specific access rights" is designed to work with Role Strategy Plugin only. It's explicitly mentioned on its Wiki page, but it worth to mention it on Jenkins Web UI (or just hide controls) I'll convert the issue to the feature request 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-26973) Support project-specific security in Matrix based security plugin
vikas choudhary commented on JENKINS-26973 Support project-specific security in Matrix based security plugin If "Configure specific access rights" is designed to work with Role Strategy Plugin only then how one can manage the ownership in case of "Matrix based security" in the global security ?? Is it possible in this case?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-26973) Support project-specific security in Matrix based security plugin
Oleg Nenashev updated JENKINS-26973 Support project-specific security in Matrix based security plugin Change By: Oleg Nenashev (16/Feb/15 12:17 PM) Summary: Manageownershipnotworkingwiththeglobal Supportproject-specific security method in Matrixbasedsecurity plugin Issue Type: Bug NewFeature 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] [audit-trail-plugin] (JENKINS-23449) .lck files are not removed during a clean shutdown
Walter Kacynski commented on JENKINS-23449 .lck files are not removed during a clean shutdown Is there a way to update https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/main/java/hudson/plugins/audit_trail/LogFileAuditLogger.java to close the FileHandler on JVM termination? 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] [audit-trail-plugin] (JENKINS-23449) .lck files are not removed during a clean shutdown
Walter Kacynski assigned JENKINS-23449 to Nicolas De Loof .lck files are not removed during a clean shutdown Change By: Walter Kacynski (16/Feb/15 12:45 PM) Assignee: NicolasDeLoof 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-26973) Support project-specific security in Matrix based security plugin
vikas choudhary commented on JENKINS-26973 Support project-specific security in Matrix based security plugin When I try to add new user/group in Global configuration setttings in Jenkins, it displays the user as ERROR in the screenshot attached in this comment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-26973) Support project-specific security in Matrix based security plugin
vikas choudhary updated JENKINS-26973 Support project-specific security in Matrix based security plugin Change By: vikas choudhary (16/Feb/15 1:04 PM) Attachment: ownershipGlobalConfig.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Sarah Woodall updated JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Added XShell Plugin to components list, as it is mentioned in the stack trace. Change By: Sarah Woodall (16/Feb/15 1:34 PM) Component/s: xshell-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26982) On MacOSX, pkg installation doesn't set newsyslog permissions properly
lacostej commented on JENKINS-26982 On MacOSX, pkg installation doesnt set newsyslog permissions properly Can probably be solved by https://github.com/lacostej/jenkins/commit/69d9bff59c2e4e7908a3490f9e154af4490d7298 I haven't tested it yet. 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] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
SCM/JIRA link daemon resolved JENKINS-26975 as Fixed Performance of the performance plugin Change By: SCM/JIRA link daemon (17/Feb/15 6:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
SCM/JIRA link daemon commented on JENKINS-26975 Performance of the performance plugin Code changed in jenkins User: Manuel Carrasco Moñino Path: src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/HttpSample.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/PerformancePublisher.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/PerformanceReportMap.java src/main/java/hudson/plugins/performance/TestSuiteReportDetail.java src/main/java/hudson/plugins/performance/ThroughputUriReport.java src/main/java/hudson/plugins/performance/TrendReportGraphs.java src/main/java/hudson/plugins/performance/UriReport.java src/test/java/hudson/plugins/performance/IagoParserTest.java src/test/java/hudson/plugins/performance/PerformanceReportTest.java src/test/java/hudson/plugins/performance/ThroughputReportTest.java src/test/java/hudson/plugins/performance/ThroughputUriReportTest.java src/test/java/hudson/plugins/performance/UriReportTest.java http://jenkins-ci.org/commit/performance-plugin/fa8d4a648b8b53a6728ba144333a631e16caadc1 Log: Merge pull request #44 from guusdk/master FIXED JENKINS-26975 Significant performance boost for Performance Plugin Compare: https://github.com/jenkinsci/performance-plugin/compare/2a3cac7672c6...fa8d4a648b8b 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] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
SCM/JIRA link daemon commented on JENKINS-26975 Performance of the performance plugin Code changed in jenkins User: Guus der Kinderen Path: .gitignore src/main/java/hudson/plugins/performance/AbstractReport.java src/main/java/hudson/plugins/performance/HttpSample.java src/main/java/hudson/plugins/performance/IagoParser.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/PerformancePublisher.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/PerformanceReportMap.java src/main/java/hudson/plugins/performance/TestSuiteReportDetail.java src/main/java/hudson/plugins/performance/ThroughputUriReport.java src/main/java/hudson/plugins/performance/TrendReportGraphs.java src/main/java/hudson/plugins/performance/UriReport.java src/test/java/hudson/plugins/performance/IagoParserTest.java src/test/java/hudson/plugins/performance/PerformanceReportTest.java src/test/java/hudson/plugins/performance/ThroughputReportTest.java src/test/java/hudson/plugins/performance/ThroughputUriReportTest.java src/test/java/hudson/plugins/performance/UriReportTest.java http://jenkins-ci.org/commit/performance-plugin/498799f3717fe9cbd8ad855f370f053c5b3d2b22 Log: FIXED JENKINS-26975 Three issues in the Jenkins performance plugin are fixed, resulting an significantly better performance (Disc, CPU and memory wise) of that plugin). An elaborate description of the changes can be found on https://issues.jenkins-ci.org/browse/JENKINS-26975 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] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
Guus der Kinderen created JENKINS-26975 Performance of the performance plugin Issue Type: Improvement Assignee: Manuel Carrasco Components: performance-plugin Created: 16/Feb/15 2:44 PM Description: The performance of the performance plugin is very poor when working with larger data-sets. The plugin effectively becomes unusable with data sets that are any bigger than very small. In this issue, I'm presenting my findings, as well as a description of the fixes that I've applied. I'm putting together a GitHub pull request for all of the code-changes to be merged with the official repository. After analysis, I've identified the following problems area's: Disc IO is off the charts CPU load is off the charts (well ok, under 100%, but way to high) Memory consumption is off the charts For illustration purposes: one of our jobs generates 16650 HTTP samples per iteration. The build history currently has a little under 200 builds. To generate Graphs, more than a gigabyte of memory is needed in the Jenkins JVM. Graph generation takes very, very long (so long for each graph that typically, either OOM occurred, or users gave up and aborted the page load). What is particularly problematic is that not only do our graphs not display, but the build-server itself becomes unworkable for quite some time. Project: Jenkins Priority: Major Reporter: Guus der Kinderen 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-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
SCM/JIRA link daemon commented on JENKINS-23152 builds getting lost due to GerritTrigger Code changed in jenkins User: Scott Hebert Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/ssh/BuildCompletedCommandJob.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/ssh/BuildStartedCommandJob.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/LockedDownGerritEventTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/a03c0d5da9cc4d275e4984ca1c8e035f1d6056d2 Log: Gerrit notifier threads should impersonate SYSTEM The BuildCompletedCommandJob was not impersonating SYSTEM and was therefore throwing permission-related exceptions. For completeness, BuildStartedCommandJob was updated too. Related to JENKINS-23152 Change-Id: I3eb6036d8186478a615c15036b4b7f98035dd54c 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] [clearcase-ucm-plugin] (JENKINS-26593) Performance issues with large changesets
Mads Nielsen resolved JENKINS-26593 as Fixed Performance issues with large changesets Change By: Mads Nielsen (16/Feb/15 2:47 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] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)
Mads Nielsen resolved JENKINS-26484 as Fixed Poll sibling from named stream (case 12577) Change By: Mads Nielsen (16/Feb/15 2:46 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] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
Guus der Kinderen
commented on JENKINS-26975
Performance of the performance plugin
After code analysis, I've found the following issues:
Issue with data structures
The first thing that I looked at was the structure of UriReport and PerformanceReport. Both work in a similar manner: they first build up a collection of items, and then iterate over that collection of items each time that data is needed. This is a simplified example of what is happening:
class UriReport {
private MapString, HttpSample samples = // ... ;
public void addSample(HttpSample sample) {
samples.add(sample.getUri(), sample);
}
public countErrors() {
int result = 0;
for (HttpSample sample : samples.values()) {
if ( !sample.isSuccessful() ) {
result +=1;
}
}
return result;
}
// Many more methods that do iterations like this.
}
This style has two drawbacks:
this is very cpu inefficient, as for every method invocation, the entire collection needs to be iterated. (as an added bonus: various methods call each-other, causing recursive iterations to occur);
this is very memory ineffecient as all of the raw data needs to be kept in memory (as computations need to iterate over everything).
I have applied code changes that change the above pattern to the following (again, simplified):
class UriReport {
int errors = 0;
public void addSample(HttpSample sample) {
if ( !sample.isSuccessful() ) {
errors +=1;
}
}
public countErrors() {
return errors;
}
// etcetera.
}
Note that there is no longer a need for the samples Map in the simplified example above, it's entire content is replaced by one primitive type. In the actual refactored code, it remains needed to keep some data (the date and duration of each sample), but all of the other data was removed from memory and replaced by just a few small primitives. As a result, memory consumption improved a lot, and the CPU does not need to be bothered with iterating over all map entries all the time. The .serialized files where significantly reduced in size as well (which is a good indication of JVM memory consumption, as those files contain raw object data).
In our setup, this fix caused graph generation to take a few minutes. Not (yet) to a workable degree, but at least one that eventually resulted in a graph.
Issue with file cache
The cache that is used to keep serialized files in memory (in JMeterParser) is not used properly. Notably: when there is no hit in the cache, the .serialized file is read from disc but not added to that cache. Only new files (files for which no .serialized data exists are added to the cache, but after a JVM restart, even that data will remain uncached.
By adding the file content to the cache, disc IO is reduced dramatically, as most invocations of graph generation will no longer need to do disc-IO.
The snippet below illustrates the required change to JMeterParser:
PerformanceReport r = cache.getIfPresent(fser);
if (r == null) {
in = new ObjectInputStream(new FileInputStream(fser));
r = (PerformanceReport) in.readObject();
cache.put(fser, r); // -- This line needs to be added.
}
Additionally, the cache size was pretty small (100 elements). Given the memory improvements that were made (as described below), the size of the cache can safely be enlarged from 100 to 1000 entities. A future improvement should make this number configurable instead of hard-coded.
In our setup, this fix (combined with the previous fix) caused graph generation to take slightly over one minute, instead of a few minutes. Additionally, this fix made any subsequent generation (after the first one) a lot faster (roughly half a second).
Issue with non-buffered disc IO
Disc IO happens without buffering. By wrapping all input and output streams in buffered streams, the operation is much faster.
The snippet below illustrates one of the required changes (but this needs to be applied in more than one place)
in = new ObjectInputStream(new BufferedInputStream(new FileInputStream(fser)));
In our setup, this fix (combined with the previous fixes) caused graph generation to take slightly over 10 seconds, instead of slightly over one minute.
For us, all of the above pretty much removed all issues regarding working with the performance plugin. I'd be grateful if my changes could be considered for merging back into the original source code.
[JIRA] [claim-plugin] (JENKINS-26976) Sticky Claim on failed build should persist only if build remains failed (not if it becomes unstable)
Denis Blanchette created JENKINS-26976 Sticky Claim on failed build should persist only if build remains failed (not if it becomes unstable) Issue Type: Bug Assignee: Christian Bremer Components: claim-plugin Created: 16/Feb/15 3:07 PM Description: When a developer claims a failed build and checks "Sticky", it means that he will fix the build failure, but not necessarily unit tests failures. Claiming a failed build wth "Sticky" option should only persists if the build remains failed and not if it becomes unstable. Environment: Jenkins ver. 1.580.3 Claim Plugin 2.5 Project: Jenkins Labels: claim Priority: Minor Reporter: Denis Blanchette This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Stephan Grimm commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. We have the same problem. Sometimes it works, sometimes it fails. Does anybody know if there is any action here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
recampbell commented on JENKINS-21466 Impossible to connect to the VSphere Cloud Anymore There is an active fork of vijava called yavijava. 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] [performance-plugin] (JENKINS-26975) Performance of the performance plugin
Guus der Kinderen commented on JENKINS-26975 Performance of the performance plugin This is the pull request that includes my fixes: https://github.com/jenkinsci/performance-plugin/pull/44 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-26571) Job page becomes un responsive when there are a lot of builds in the queue
Tom FENNELLY commented on JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue @Arpit: would you be able to test this issue against the 1.598 release and let me know if you're still having issues please? If the problem persists, please create a screen recording that allows us to see the issue for real. Another option might be for us to do a screenshare over skype (or other), allowing me to see it for real. 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] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Sebastian Bathke commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server We have loging working for a certain time period after startup of jenkins. But it gets broken some hours later. A restart solves login problems for another period. Other tools work well with the same ldap host (gerrit, sonar). 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] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Sebastian Bathke edited a comment on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server We have loging working for a certain time period after startup of jenkins. But it gets broken some hours later. A restart solves login problems for another period. Other tools work well with the same ldap host (gerrit, sonar). Jenkins v1.598, LDAP-Plugin v1.11 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-26970) Jenkins website: Community ratings in changelog no longer working
Daniel Beck resolved JENKINS-26970 as Duplicate Jenkins website: Community ratings in changelog no longer working Duplicates INFRA-234. Change By: Daniel Beck (16/Feb/15 10:42 AM) 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-26970) Jenkins website: Community ratings in changelog no longer working
Daniel Beck commented on JENKINS-26970 Jenkins website: Community ratings in changelog no longer working I wasn't sure where to report this error, since it's an issue with the site rather than with Jenkins itself. I hope this is the right place. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue section "Creating the issue" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-26968) No Reports with Maven 3.1.1 or Maven 3.2.5
Ulli Hafner commented on JENKINS-26968 No Reports with Maven 3.1.1 or Maven 3.2.5 Please switch to the freestyle project. 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] [analysis-core-plugin] (JENKINS-26968) No Reports with Maven 3.1.1 or Maven 3.2.5
Ulli Hafner resolved JENKINS-26968 as Duplicate No Reports with Maven 3.1.1 or Maven 3.2.5 Change By: Ulli Hafner (16/Feb/15 11:08 AM) 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] [subversion-plugin] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch commented on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Hello, Thanks again. I am back from holiday. Here is the version information: Jenkins ver. 1.598 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED
Torben Knerr commented on JENKINS-10406 Maven Jobs with build modules in parallel always ABORTED Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10540) Maven build aborted without cause
Torben Knerr commented on JENKINS-10540 Maven build aborted without cause Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-26968) No Reports with Maven 3.1.1 or Maven 3.2.5
podskalsky commented on JENKINS-26968 No Reports with Maven 3.1.1 or Maven 3.2.5 Only workaround (with Maven 3.2.5): downgrade to ... Static Code Analysis Plug-ins 1.65 Checkstyle Plug-in 3.40 FindBugs Plug-in 4.57 PMD Plug-in 3.39 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-failure-analyzer-plugin] (JENKINS-26969) I like it is possible to select that BFA set failed build status as ABORTED
Kari Sivonen created JENKINS-26969 I like it is possible to select that BFA set failed build status as ABORTED Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 16/Feb/15 8:13 AM Description: In our system we have time to time environment caused failures and we are using BFA plugin to recognize them. It would be nice if in rule is possible to set that BFS will change failed build status to ABORTED. That would help designers to see there is not normal failure, but environment issue. I have already modified plugin version in my system, but it is made from version 1.5.1, and there is only that whole plugin can be select to mark ABORTED or not. That causes that only those environment problems can be used here as code based failures is not wanted to change ABORTED. Better will be that ABORTED is changed only in wanted rules. Project: Jenkins Priority: Minor Reporter: Kari Sivonen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Orgad Shaneh commented on JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Happens to me with a freestyle project with 1.598, Windows master, Linux slave (debian wheezy). When I abort a job, it appears as aborted in Jenkins, but keeps running. The following exception appears in the log. Project #362 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:751) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy47.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:984) at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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] [analysis-core-plugin] (JENKINS-26968) No Reports with Maven 3.1.1 or Maven 3.2.5
podskalsky updated JENKINS-26968 No Reports with Maven 3.1.1 or Maven 3.2.5 Change By: podskalsky (16/Feb/15 8:25 AM) Environment: Jenkinsver.1.597LatestMaven-PluginLatestAnalysis-Core-Plugin 1.69 Maven3.1.1orMaven3.2.5LatestArtifactory-Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26970) Jenkins website: Community ratings in changelog no longer working
Simon C created JENKINS-26970 Jenkins website: Community ratings in changelog no longer working Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Feb/15 9:46 AM Description: In the Jenkins website, go to the changelog page (or the LTS changelog), and click the "Community Ratings" link: It not longer works. With browser dev tools open, we can see that clicking the link generates two JS errors. I wasn't sure where to report this error, since it's an issue with the site rather than with Jenkins itself. I hope this is the right place. Project: Jenkins Labels: website changelog Priority: Minor Reporter: Simon C This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-19576) Build cause is not resetted after failure
Sven Appenrodt resolved JENKINS-19576 as Wont Fix Build cause is not resetted after failure Version 1.14 does not contain the line BUILD_CAUSE_NAGINATORCAUSE=true and the automatically added badges introcuced in 1.14 (or former) does not require the groovy script. Big problem for us: because of the missing NAGINATORCAUSE information we cannot determine if a job has been failed before. Waiting for the unreleased version (according to RN there will be some variables again) so if you like you can close this ticket. Change By: Sven Appenrodt (16/Feb/15 9:37 AM) 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] [p4-plugin] (JENKINS-26787) Upgrade p4java to 2014.1
Paul Allen commented on JENKINS-26787 Upgrade p4java to 2014.1 The 1.2.0 release as some major changes to support the new Jenkins 'Workflow' plugin. Some of my changes may have broken support for the Matrix plugin around polling, still trying to get to the route cause. If you use the Matrix plugin and are able to help with testing that would be a great help. I hope to get something out on Friday, but I have a lot on at the moment. 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] [testng-plugin] (JENKINS-26971) looking at failed TestNG result causes an exception
Nikolay Metchev created JENKINS-26971 looking at failed TestNG result causes an exception Issue Type: Bug Assignee: Nalin Makar Components: testng-plugin Created: 16/Feb/15 10:02 AM Description: Clicking on a failed TestNG unit test causes the following exception to be shown in the browser: java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.598.jar!/lib/layout/layout.jelly:245:28: d:invokeBody org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.598.jar!/lib/layout/main-panel.jelly:36:21: d:invokeBody org.apache.commons.jelly.JellyTagException: Cannot get property 'escapeExceptionMsg' on null object at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy44.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at hudson.plugins.testng.results.MethodResult.index.run(index.groovy:8) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
[JIRA] [build-failure-analyzer-plugin] (JENKINS-26969) I like it is possible to select that BFA set failed build status as ABORTED
Tomas Westling commented on JENKINS-26969 I like it is possible to select that BFA set failed build status as ABORTED I feel that if the build fails due to an environment error, I would want precisely this information. To mark the build as ABORTED when it hasn't been aborted feels wrong in my opinion. 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] [chef-plugin] (JENKINS-26972) Chef Plugin | run chef-client remotely under Jenkins CI not working
Amandeep Singh created JENKINS-26972 Chef Plugin | run chef-client remotely under Jenkins CI not working Issue Type: Bug Assignee: Unassigned Attachments: chef-client.jpg, configure.jpg, no_previous_configurations.jpg Components: chef-plugin Created: 16/Feb/15 11:38 AM Description: Hi All, I am trying to integrate Jenkins with chef where Jenkins will automatically trigger chef-client command on multiple nodes. I figured out the Chef Plugin and installed it on my Jenkins server. It is showing me while creating job under build options to run chef-client on remote machines. Once I provided all the SSH details and save the job, I come to know that the all the details provided in job for Chef plugin are not getting saved and it is wiping out. So every time , I click on configure button for my job , the previous details are not present there and I have to provide details again. Please suggest, if something is missing or what is the desired behavior for this plugin. Attaching screenshots for reference. Thanks in Advance Regards Amandeep Singh Environment: Jenkins version 1.598 Windows 7 OS Chef-Plugin 1.0.3 Project: Jenkins Labels: plugin Priority: Major Reporter: Amandeep Singh 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] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
Christoph Beckmann assigned JENKINS-26797 to Francis Upton Zombie instance created by the EC2 plugins Change By: Christoph Beckmann (16/Feb/15 11:42 AM) Assignee: ChristophBeckmann FrancisUpton 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.
