[JIRA] [docker-plugin] (JENKINS-23401) docker plugin requires ssh key pair credentials
Kanstantsin Shautsou commented on JENKINS-23401 docker plugin requires ssh key pair credentials docker image contains EXPOSE 22 as expected port that will be forwarded from docker-proxy (in case of nat network) or directly with bridge. Page that lists docker images is broken at all. Also after failures docker node has not removed nodes and etc. +1 for @jglick comments. Fighting and patching 3 days and still don't understand what is happening and why it fails without obvious reasons. 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-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
hugo fonseca commented on JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Thank you @Francis and sorry the delay. Great job BTW. 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-26508) Upgrade to 1.597 breaks Job page
josh mac commented on JENKINS-26508 Upgrade to 1.597 breaks Job page I had the exact same issue you stated in this ticket. Reverting takes away the problem. All plugins are fully updated. 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-26508) Upgrade to 1.597 breaks Job page
josh mac edited a comment on JENKINS-26508 Upgrade to 1.597 breaks Job page I had the exact same issue you stated in this ticket. Reverting takes away the problem. (Though you can't see old builds when reverting, so I'm stuck with the new one) All plugins are fully updated. 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-26496) Trying to get the DateFormat as build ID
Grigoriy Milman commented on JENKINS-26496 Trying to get the DateFormat as build ID On the system where Jenkins is installed, the URL of the Jenkins is http://localhost:8080 I have tried http://localhost:8080/JENKINS-24380 I have tried http://localhost:8080/jenkins/JENKINS-24380 Result the same! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/RunIdMigrator.java http://jenkins-ci.org/commit/jenkins/fccc34987f03a2716f3744a998cfe7d9127abafc Log: JENKINS-26519 Unreproducible NPE from unmigrateJobsDir. 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-26508) Upgrade to 1.597 breaks Job page
josh mac edited a comment on JENKINS-26508 Upgrade to 1.597 breaks Job page I had the exact same issue you stated in this ticket, though I updated Jenkins on a mac mini server manually to 1.597. Reverting to 1.596 takes away the problem. (Though you can't see old builds when reverting, so I'm stuck with the new one) All plugins are fully updated. Plenty of disk space on the machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23134) Mixed separators fail for Linux paths
Christopher Orr commented on JENKINS-23134 Mixed separators fail for Linux paths So I did a terrible job of reviewing the code that caused this bug, and a terrible job of fixing it so far. I've been working on some other fixes and will do a release soon. So I will merge and test this pull request which should fix this issue: https://github.com/jenkinsci/android-emulator-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] [disk-usage-plugin] (JENKINS-26508) Upgrade to 1.597 breaks Job page
josh mac edited a comment on JENKINS-26508 Upgrade to 1.597 breaks Job page I had the exact same issue you stated in this ticket, though I updated manually to 1.597 Reverting to 1.596 takes away the problem. (Though you can't see old builds when reverting, so I'm stuck with the new one) All plugins are fully updated. Plenty of disk space on the machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Christopher Orr resolved JENKINS-22555 as Fixed android.util.AndroidException: Cant connect to activity manager; is the system running? Change By: Christopher Orr (21/Jan/15 5:48 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] [ssh-slaves-plugin] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
nel pontejos commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Kohsuke, I downgraded to .23 but still doesn't 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] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Node dem (i-cc)(i-cc) is still pending/launching, waiting 5s Node dem (i-cc)(i-) is ready Connecting to ec2.compute-1.amazonaws.com on port 22, with timeout 1. Waiting for SSH to come up. Sleeping 5. Connected via SSH. bootstrap() Getting keypair... Using key: dom Authenticating as dam take over connection Creating tmp directory () if it does not exist mkdir: missing operand Try `mkdir --help' for more information. Executing init script bash: /init.sh: No such file or directory init script failed: exit code=127 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-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Jenkins 1.580.2 Amazon EC2 plugin 1.25 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-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update Ubuntu slave No fancy configurations. Almost default. 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-26519) Build records not migrated due to “failed to rename
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename I suspect that the problem is that on some Windows systems, build number “symlinks” are really text files pointing to the target, and that these are not handled. 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-26496) Trying to get the DateFormat as build ID
Jesse Glick commented on JENKINS-26496 Trying to get the DateFormat as build ID Grigoriy Milman Working for me. You can use curl -i to see HTTP headers which may explain something. You may need to be logged in as an administrator for this URL 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] [core] (JENKINS-24380) Use build numbers as IDs
Jesse Glick resolved JENKINS-24380 as Fixed Use build numbers as IDs Please file blocking issues as needed rather than reopening this one. The “failed to rename” is already filed as JENKINS-26519 and will be fixed in 1.598; you need to delete legacyId files and rerun the migration, as described in that issue. Change By: Jesse Glick (21/Jan/15 6:49 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update No stacktrace at Jenkins log. 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-24380) Use build numbers as IDs
Jesse Glick commented on JENKINS-24380 Use build numbers as IDs The Disk Usage plugin issue is already filed in JENKINS-26496; disable that plugin until its maintainer merges my PR, unless you want to run a snapshot build. The NPE from unmigrateJobsDir I have not seen. Apparently there is a file f for which f.isDirectory() f.listFiles() == null, which seems anomalous (usually null from listFiles means the directory does not really exist), but prior to Java 7 there is no way to get a detailed exception from a file listing so I can only speculate about what that might have been. Anyway I can make that code more robust in 1.599. 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-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update @Hugo, yes, it should probably handle the empty temp dir better. Thanks for looking more deeply. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26338) Entering Emulator Executable value does not work
SCM/JIRA link daemon resolved JENKINS-26338 as Fixed Entering Emulator Executable value does not work Change By: SCM/JIRA link daemon (21/Jan/15 5: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] [android-emulator-plugin] (JENKINS-26338) Entering Emulator Executable value does not work
SCM/JIRA link daemon commented on JENKINS-26338 Entering Emulator Executable value does not work Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java src/test/java/hudson/plugins/android_emulator/EmulatorConfigTest.java http://jenkins-ci.org/commit/android-emulator-plugin/53fbfdf677e41dad1246a892f18a715e1abca9dd Log: Merge pull request #43 from eBay-European-Product-Development/master FIXED JENKINS-26338 Also use configured executable when using named emulators. Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/9bfa98a0b1fb...53fbfdf677e4 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-26519) Build records not migrated due to “failed to rename
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename In the interest of expediency I pushed what I think is a fix to the rc branch for 1.598 (which will I guess come out on Monday as usual), and am validating a merge to master. It would not be a bad idea to grab the jenkins.war from https://jenkins.ci.cloudbees.com/job/core/job/jenkins_rc_branch/317/ once it completes and try running it. In order to force a rerun of migration when using the patched version of Jenkins: Shut down Jenkins. Delete all %JENKINS_HOME%\jobs\builds\legacyId files. (They are just caches and will be recreated as needed.) Start Jenkins again. Check the log file. You should see the Migrating build records messages again, but should not see the warnings. 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-26531) Weird Could not find /init.sh after update
hugo fonseca commented on JENKINS-26531 Weird Could not find /init.sh after update If I set temp dir it works. Maybe some "null - empty string" 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] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton updated JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Change By: Francis Upton (21/Jan/15 7:17 PM) Summary: WeirdCould Slavedoes not find/init.sh startifthetempdirisnotsettoanything after update upgradeto1.25 Priority: Blocker 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
SCM/JIRA link daemon resolved JENKINS-26519 as Fixed Build records not migrated due to “failed to rename Change By: SCM/JIRA link daemon (21/Jan/15 6:19 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/056b446480d9f24619c2c30ebdf9df6122a9b653 Log: FIXED JENKINS-26519 Accept Windows text file quasi-symlinks for build numbers. 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-26519) Build records not migrated due to “failed to rename
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename Code changed in jenkins User: Jesse Glick Path: core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/c997ac0c865ca4866ffda0e9ae93fe818c311cba Log: JENKINS-26519 Confirming that it is safe to rerun migration by just deleting legacyId files. 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] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Jesse Glick created JENKINS-26535 DescribableHelper does not handle wildcards well Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 21/Jan/15 7:31 PM Description: org.jenkinsci.plugins.credentialsbinding.impl.BindingStep notes that while ListMultiBinding bindings works fine, List? extends MultiBinding? does not, nor does ListMultiBinding?. Project: Jenkins Priority: Minor Reporter: Jesse Glick 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-26519) Build records not migrated due to “failed to rename
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename Integrated in jenkins_main_trunk #3940 JENKINS-26519 Confirming that it is safe to rerun migration by just deleting legacyId files. (Revision c997ac0c865ca4866ffda0e9ae93fe818c311cba) FIXED JENKINS-26519 Accept Windows text file quasi-symlinks for build numbers. (Revision 056b446480d9f24619c2c30ebdf9df6122a9b653) Result = SUCCESS jesse glick : c997ac0c865ca4866ffda0e9ae93fe818c311cba Files : core/src/test/java/jenkins/model/RunIdMigratorTest.java jesse glick : 056b446480d9f24619c2c30ebdf9df6122a9b653 Files : changelog.html core/src/test/java/jenkins/model/RunIdMigratorTest.java core/src/main/java/jenkins/model/RunIdMigrator.java 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] [rich-text-publisher-plugin] (JENKINS-26533) get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher
Rick Patterson
created JENKINS-26533
get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher
Issue Type:
Bug
Assignee:
Unassigned
Components:
rich-text-publisher-plugin
Created:
21/Jan/15 4:37 PM
Description:
Hi.
I use the rich-text-publisher from a Jenkins job, to create HTML text on the build results page. Putting plain text there works very nicely. But, then I update this builds results text to contain a link to another Jenkins job that has parameters, that the user may wish to call after the first job is done, passing parameters used during the first job to the second job as URL parameters. Rich text publisher creates the link okay.
Here is the gist of it:
Text that is in "Rich Text Message" box, in Post build Step:
a href=""Promote this build ${ENV:FullVersion}./a
Generated link that appears on Build Results page:
https://jenkins_server.company.com:8442//job/_publish_promote_module_test/buildWithParameters?FullVersion=1.2.3.4Component=sample_componentlocation=//builds/daily/sample_location
When I click the link, I get new browser Window, with following message and a Proceed button:
You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.
I can click the proceed button, but despite the parameters all appearing to be processed by the Jenkins job, the job is failing with what may be authentication errors, as hinted to by the above message.
Environment:
Windows 2008 Server, Jenkins 1.592, rich-text-plublisher-plugin 1.3
Project:
Jenkins
Priority:
Minor
Reporter:
Rick Patterson
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-26519) Build records not migrated due to “failed to rename
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename The build number symlinks are deleted in one pass, then the build.xml modifications and directory renames happen in a second pass. There are no could not delete build number symlink warnings so it does not seem that this is the problem. Can you show me a long directory listing (IIRC dir suffices in a command shell) of one of the affected builds directories? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
SCM/JIRA link daemon commented on JENKINS-22555 android.util.AndroidException: Cant connect to activity manager; is the system running? Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java http://jenkins-ci.org/commit/android-emulator-plugin/9bfa98a0b1fb90ee811f9f029c041112f520ec14 Log: JENKINS-22555 Switched to using "init.svc.bootanim" to detect boot completion. I saw an Android TV system image that did not use "dev.bootcomplete", even although it had (apparently) booted correctly. Other tools seem to be using the bootanim variant, and it seems to be working in every case I tested. Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/3ddf4b3259db...9bfa98a0b1fb 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-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update Is there a stack trace? Can you attach the complete log? 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-26532) Stack trace when querying node API
Daniel Beck resolved JENKINS-26532 as Duplicate Stack trace when querying node API Duplicates JENKINS-24452. Change By: Daniel Beck (21/Jan/15 3:56 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-24618) Absolute priority not working
pedro reis commented on JENKINS-24618 Absolute priority not working Markus, to set via "Job Priorities" (aka http://jenkins:8080/advanced-build-queue/) you have to have all the jobs with the same priority in the same view? Did you use regular _expression_ to filter them? Before using "Job Priorities" do you have to clean up the priority of each job? Do you have to unset " Allow priorities directly on Jobs" at "Configure System" (http://jenkins:8080/configure)? Thanks in advance. 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-24380) Use build numbers as IDs
Cameron Horn commented on JENKINS-24380 Use build numbers as IDs Got a ton of messages like this: Jan 20, 2015 1:24:00 PM jenkins.model.RunIdMigrator doMigrate WARNING: failed to rename 2014-12-05_14-18-42 to 1 Ended up with every job timestamp set to 1970. Was able to downgrade. 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-24380) Use build numbers as IDs
Hans Baer reopened JENKINS-24380 Use build numbers as IDs After update to 1.597 my jobs fail with an Opss exception. Executing the unmigrate job will cause Exception in thread "main" java.lang.NullPointerException at jenkins.model.RunIdMigrator.unmigrateJobsDir(RunIdMigrator.java:310) at jenkins.model.RunIdMigrator.unmigrateJobsDir(RunIdMigrator.java:323) at jenkins.model.RunIdMigrator.main(RunIdMigrator.java:307) Now I stuck with not being able to downgrade nor being able to use 1.597 Change By: Hans Baer (21/Jan/15 4:00 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] [xcode-plugin] (JENKINS-26534) Cannot run tests and set custom arguments
James Howe created JENKINS-26534 Cannot run tests and set custom arguments Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 21/Jan/15 4:42 PM Description: All guides say to put "test" under "Custom xcodebuild arguments" to run tests for the selected scheme. However, if there's anything else in there (like -destination, CACHE_ROOT, etc.) then it still adds "build" to the command line and it will fail. sdk $ /usr/bin/xcodebuild -scheme MyTests -sdk iphonesimulator8.1 -configuration Release build test -destination "name=iPhone 5" ... xcodebuild: error: The scheme 'AurasmaSDKTests' is not configured for Running. The scheme 'AurasmaSDKTests' has nothing configured to build for Running and has no executable specified to Run. Edit the scheme to configure the Run action. Build step 'Xcode' marked build as failure Project: Jenkins Priority: Critical Reporter: James Howe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26524) Null Pointer Exception on github payload push to Jenkins
sunil madhu commented on JENKINS-26524 Null Pointer Exception on github payload push to Jenkins I have confirmed that the same issue now exists for Polling Github as well: Started on Jan 21, 2015 4:42:00 PM Using strategy: Default poll Last Built Revision: Revision 4fe2eefaf2beca036a8a9e05cf040b270405e39e (refs/remotes/origin/stage) ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@2324ada3stage-service java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.EnvironmentContributorImpl.buildEnvironmentFor(EnvironmentContributorImpl.java:23) at hudson.model.Run.getEnvironment(Run.java:2224) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:905) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:563) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:525) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1441) at hudson.model.AbstractProject.poll(AbstractProject.java:1344) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 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-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update Which version are you running? 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] [prioritysorter-plugin] (JENKINS-24618) Absolute priority not working
pedro reis commented on JENKINS-24618 Absolute priority not working Hi, We are also having this issue. Jenkins 1.565.3 ; priority sorter 2.9 . We're using "Absolute", and "Allow priorities directly on Jobs" so we set the priorities in each job. (each job has sub-jobs with different configurations, aka matrix) We have a python script that starts several jobs. Priority isn't always being respected. What is the threshold time that the jobs delay before starting? (I image there is such a delay, to allow other jobs with bigger priority to start before them) 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] [sonargraph-plugin] (JENKINS-26360) User should be able to define the metrics to be displayed as charts
SCM/JIRA link daemon commented on JENKINS-26360 User should be able to define the metrics to be displayed as charts Code changed in jenkins User: Ingmar Kellner Path: pom.xml.releaseBackup release.properties http://jenkins-ci.org/commit/sonargraph-plugin/2b8c72e984e8b201195c80fc8fcd48c380d57ab3 Log: JENKINS-26360: Sonargraph Plugin. Finish release 1.6.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26524) Null Pointer Exception on github payload push AND polling to/from Jenkins
sunil madhu updated JENKINS-26524 Null Pointer Exception on github payload push AND polling to/from Jenkins Change By: sunil madhu (21/Jan/15 5:07 PM) Summary: NullPointerExceptionongithubpayloadpush ANDpolling to /from Jenkins Component/s: github-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-26519) Build records not migrated due to “failed to rename
Jesse Glick updated JENKINS-26519 Build records not migrated due to “failed to rename I glanced at one of the build.xml files and it was in the old format, which is clearly the problem. I do recall testing migration on Windows but there are a thousand and one things that can go wrong on a Windows filesystem and it looks like you hit one of them. Will see if I can find a cause. Change By: Jesse Glick (21/Jan/15 5:32 PM) Summary: Wrong(lastsuccess)dateaftermigration Buildrecordsnotmigrateddue to 1.597 “failedtorename 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-20577) Add support for buildaction like test
James Howe commented on JENKINS-20577 Add support for buildaction like test Doesn't work if you also want to set other options 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-24380) Use build numbers as IDs
John Miller commented on JENKINS-24380 Use build numbers as IDs I am having this issue also.. I get the oops page when I upgrade to 1.597 but can not downgrade javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/export/jenkins/.jenkins/war/WEB-INF/lib/jenkins-core-1.597.jar!/lib/hudson/project/projectActionFloatingBox.jelly:38:74: st:include hudson.model.Run.getIDFormatter()Ljava/text/DateFormat; at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) 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$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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename Integrated in jenkins_main_trunk #3941 JENKINS-26519 Unreproducible NPE from unmigrateJobsDir. (Revision fccc34987f03a2716f3744a998cfe7d9127abafc) Result = SUCCESS jesse glick : fccc34987f03a2716f3744a998cfe7d9127abafc Files : core/src/main/java/jenkins/model/RunIdMigrator.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26540) notifyCommit pushes with a sha1 trigger builds where scm polling is not enabled
Bradley Baetz created JENKINS-26540 notifyCommit pushes with a sha1 trigger builds where scm polling is not enabled Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 21/Jan/15 10:27 PM Description: Not sure if this is a bug or expected behaviour, but its a bit confusing. If I call the notifyCommit URL without a sha1, then the build only triggers if 'scm polling' is enabled. However, if a sha1 is provided then the build triggers regardless. I realise that when the sha1 is provided, strictly speaking this isn't 'polling' happening. However this means that the only way to disable triggering (eg for a nightly sonar build) is to enable the scm trigger, set no time and then select the "Ignore post-commit hooks" option. ie: polling disabled - triggers if and only if a sha1 was provided polling enabled - triggers polling enabled but skipped - doesn't trigger this is a but unintuitive and confusing. The git plugin should require that polling is enabled (even with an empty time), just like it does if a sha1 isn't provided. Project: Jenkins Priority: Minor Reporter: Bradley Baetz 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-15736) Viewing performance report changes jvm locale
Daryl Spartz commented on JENKINS-15736 Viewing performance report changes jvm locale Submitted pull request, https://github.com/jenkinsci/performance-plugin/pull/42 for this fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26488) Add support for Bitbucket Pull Request Builder plugin
Daniel Spilker commented on JENKINS-26488 Add support for Bitbucket Pull Request Builder plugin I'm not going to add DSL support where the password can be stored in plain text in the DSL script. JENKINS-24707 must be fixed before adding DSL support. 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas
edited a comment on JENKINS-21605
Logging all UpstreamCauses floods Jenkins in large setups
I will describe two concrete cases to have a baseline for the further discussion.
Case (A) ( https://gist.github.com/dirk-thomas/9bbd47397e48ef3ceef8 ):
A job "leaf" has only a single upstream dependency on "before_leaf".
And "before leaf" has many (in this example 40: "01" to "40") upstream dependencies.
Each upstream dependency "N" has "N-1" as its upstream dependency.
The "before_leaf" job will list all 40 upstream causes.
Each upstream cause on its own is limited to a recursive depth of 10 (according to `MAX_DEPTH`).
The "leaf" job has a single upstream cause ("before_leaf").
The `SetString traversed` in the `UpstreamClause` prevents listing repeated upstream causes of the single upstream cause.
Case (B) ( https://gist.github.com/dirk-thomas/37febb42abeb8631f946 ):
A job "leaf" has only a single upstream dependency on "before_leaf".
And "before leaf" has several (in this example 5: "a15" to "e15") upstream dependencies.
Each upstream dependency "xN" has "xN-1" as its upstream dependency.
Recursive upstream causes are usually "terminated" by a `DeeplyNestedUpstreamCause` when `MAX_DEPTH` is reached.
`MAX_LEAF` prevents adding a `DeeplyNestedUpstreamCause` at the end of the recursion once the number of different causes has reached 25 addresses (`MAX_LEAF`).
This can be seen in the "leaf" of of case (B).
(I don't understand why skipping the `DeeplyNestedUpstreamCause` when aborting the recursion makes a big different though - it does not affect the log size significantly and contains valuable information (that the recursion has been aborted)).
Based on these I identified two problems.
Problem (A): limitation of performing the thresholds in the `UpstreamCause`:
The "before_leaf" job of case (A) has 40 upstream causes.
While each on its own does some logic for limiting the information each separate `UpstreamCause` instance does not know about its siblings.
Therefore it can not adjust the level of information shown in the case that there are many siblings.
This is not "fixable" in the `UpstreamCause` class itself.
This would require some changes in the code handling the upstream causes to pass in information e.g. the number of siblings (which arguably a `UpstreamCause` should not need to know about).
(The problem is the same for the "before_leaf" job of case (B).)
Problem (B): the depth threshold is independent from the number of upstream causes:
The "leaf" job of case (B) has only a single upstream cause.
But this upstream cause outputs every upstream cause up to the recursion limit.
This results in N x 10 upstream causes where N is the number of upstream causes of the single upstream cause of the job.
I "combined" limit would probably make much more sense in this case.
E.g. limit each recursion to not 10 but potentially less if the number of sibling upstream causes on the first level increases.
(I am unable to provide a Java unit test since I lack the experience programming in Java but the Groovy examples should be verify specific and hopefully easy to transfer into a unit test by an experienced Jenkins/Java programmer.)
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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Jesse Glick commented on JENKINS-21605 Logging all UpstreamCauses floods Jenkins in large setups Thank you for the analysis. I do not personally expect to have time to work on a fix, but perhaps someone else will. 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] [virtualbox-plugin] (JENKINS-16231) Stop slave options should list all possible options, not just save and poweroff
p r commented on JENKINS-16231 Stop slave options should list all possible options, not just save and poweroff But with the option to actually have an acpipowerbutton option the end user can set what action is taken when that acpi button is pressed. End users have to setup what action is taken when that signal is received it does not just automatically send the OS the proper shutdown command for a clean and safe shutdown. Using the poweroff is essentially the same as pulling the power cord from a box. That is not a good choice at all. Also once you send the poweroff you could easily poll to make sure it is not running anymore through checking what is left running or just checking the state of said machine that just got the acpi button press signal. Just my opinion and the biggest downfall I see to this plugin. Not everyone wants or needs to save state and really no one should use the poweroff command unless you want to corrupt your file system VERY quickly. 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-26539) Build descriptions in sidebar ignores HTML breaks (br)
Brian Clark created JENKINS-26539 Build descriptions in sidebar ignores HTML breaks (br) Issue Type: Bug Assignee: Unassigned Attachments: pluginVersions.xml Components: core Created: 21/Jan/15 10:23 PM Description: 1). Create a new freestyle job and run it once. 2). Edit the build description for the first run of the job to contain the following (excluding the quotes): "Line1brLine2br" 3). The build description in the sidebar will look like "Line1Line2" when it should look like: Line1 Line2 Environment: Jenkins version: 1.593 Operating System: Windows and Ubuntu 14.04 (possibly others) Browsers: IE, Firefox, Chrome Project: Jenkins Priority: Minor Reporter: Brian Clark 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] [teamconcert-plugin] (JENKINS-26536) Team Concert Plugin - does not recognize load rules when determining changesets
Anthony Ferrari created JENKINS-26536 Team Concert Plugin - does not recognize load rules when determining changesets Issue Type: Bug Assignee: Unassigned Components: teamconcert-plugin Created: 21/Jan/15 8:08 PM Description: The Jenkins RTC Team Concert plugin (written by IBM) does not seem to recognize (consider) load rules when determining changesets (and therefore developers and culprits) for Jenkins jobs. It seems to use all components defined in the RTC repository workspace instead. The result is that code changes in areas OUTSIDE the Jenkins job are being identified incorrectly as changes. This would include any changes for all components in the RTC workspace. The result is that the Jenkins job triggers emails for changes not related to the Jenkins job source code. Environment: Jenkins ver. 1.532.2, any web browser, Project: Jenkins Labels: team-concert changeset Priority: Minor Reporter: Anthony Ferrari 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] [workflow-plugin] (JENKINS-26101) Load Script from SCM (wave #2)
Jesse Glick started work on JENKINS-26101 Load Script from SCM (wave #2) Change By: Jesse Glick (21/Jan/15 8:08 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] [workflow-plugin] (JENKINS-26101) Load entire script from SCM
SCM/JIRA link daemon commented on JENKINS-26101 Load entire script from SCM Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction2.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly http://jenkins-ci.org/commit/workflow-plugin/50be69d7db0fff857f044bf725bcb0f1d8d0e7a2 Log: JENKINS-26101 Proof of concept of flow definition loaded entirely from a local SCM checkout. Compare: https://github.com/jenkinsci/workflow-plugin/compare/0d2226288236^...50be69d7db0f 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-26508) Upgrade to 1.597 breaks Job page
josh mac commented on JENKINS-26508 Upgrade to 1.597 breaks Job page So, I finally figured out my issue. For me, it was a plugin. Downgraded the "Disk Usage Plugin" from 0.24 to 0.23. Issue solved. 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas
commented on JENKINS-21605
Logging all UpstreamCauses floods Jenkins in large setups
I will describe two concrete cases to have a baseline for the further discussion.
Case (A) (https://gist.github.com/dirk-thomas/9bbd47397e48ef3ceef8):
A job "leaf" has only a single upstream dependency on "before_leaf".
And "before leaf" has many (in this example 40: "01" to "40") upstream dependencies.
Each upstream dependency "N" has "N-1" as its upstream dependency.
The "before_leaf" job will list all 40 upstream causes.
Each upstream cause on its own is limited to a recursive depth of 10 (according to `MAX_DEPTH`).
The "leaf" job has a single upstream cause ("before_leaf").
The `SetString traversed` in the `UpstreamClause` prevents listing repeated upstream causes of the single upstream cause.
Case (B) (https://gist.github.com/dirk-thomas/37febb42abeb8631f946):
A job "leaf" has only a single upstream dependency on "before_leaf".
And "before leaf" has several (in this example 5: "a15" to "e15") upstream dependencies.
Each upstream dependency "xN" has "xN-1" as its upstream dependency.
Recursive upstream causes are usually "terminated" by a `DeeplyNestedUpstreamCause` when `MAX_DEPTH` is reached.
`MAX_LEAF` prevents adding a `DeeplyNestedUpstreamCause` at the end of the recursion once the number of different causes has reached 25 addresses (`MAX_LEAF`).
This can be seen in the "leaf" of of case (B).
(I don't understand why skipping the `DeeplyNestedUpstreamCause` when aborting the recursion makes a big different though - it does not affect the log size significantly and contains valuable information (that the recursion has been aborted)).
Based on these I identified two problems.
Problem (A): limitation of performing the thresholds in the `UpstreamCause`:
The "before_leaf" job of case (A) has 40 upstream causes.
While each on its own does some logic for limiting the information each separate `UpstreamCause` instance does not know about its siblings.
Therefore it can not adjust the level of information shown in the case that there are many siblings.
This is not "fixable" in the `UpstreamCause` class itself.
This would require some changes in the code handling the upstream causes to pass in information e.g. the number of siblings (which arguably a `UpstreamCause` should not need to know about).
(The problem is the same for the "before_leaf" job of case (B).)
Problem (B): the depth threshold is independent from the number of upstream causes:
The "leaf" job of case (B) has only a single upstream cause.
But this upstream cause outputs every upstream cause up to the recursion limit.
This results in N x 10 upstream causes where N is the number of upstream causes of the single upstream cause of the job.
I "combined" limit would probably make much more sense in this case.
E.g. limit each recursion to not 10 but potentially less if the number of sibling upstream causes on the first level increases.
(I am unable to provide a Java unit test since I lack the experience programming in Java but the Groovy examples should be verify specific and hopefully easy to transfer into a unit test by an experienced Jenkins/Java programmer.)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu commented on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Yw. And thanks for fixing it . I will try the new version. 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] [workflow-plugin] (JENKINS-26537) workflow-cps-global-lib inaccessible over authenticated HTTP(S)
Jesse Glick created JENKINS-26537 workflow-cps-global-lib inaccessible over authenticated HTTP(S) Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 21/Jan/15 9:16 PM Description: It seems that workflowLibs.git is not available over HTTP(S) protocol if you need to authenticate, possibly because the Git client does not send BASIC authentication in a form that the Jenkins embedded Git server acknowledges. Related to Jenkins Enterprise bug 2021; serverfault discussion. Project: Jenkins Priority: Major Reporter: Jesse Glick 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] [virtualbox-plugin] (JENKINS-16231) Stop slave options should list all possible options, not just save and poweroff
p r edited a comment on JENKINS-16231 Stop slave options should list all possible options, not just save and poweroff But with the option to actually have an acpipowerbutton option the end user can set what action is taken when that acpi button is pressed. End users have to setup what action is taken when that signal is received it does not just automatically send the OS the proper shutdown command for a clean and safe shutdown. Using the poweroff is essentially the same as pulling the power cord from a box. That is not a good choice at all. Also once you send the acpipoweroff you could easily poll to make sure it is not running anymore through checking what is left running or just checking the state of said machine that just got the acpi button press signal. Just my opinion and the biggest downfall I see to this plugin. Not everyone wants or needs to save state and really no one should use the poweroff command unless you want to corrupt your file system VERY quickly. 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-25869) Jenkins is getting crashed and shutting down once in a while
Daniel Beck commented on JENKINS-25869 Jenkins is getting crashed and shutting down once in a while This appears to be a bug in your JDK, and has nothing to do with Jenkins (except that it runs code that causes the JDK code to run). See: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7188755 https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/885195 http://mail.openjdk.java.net/pipermail/jdk7u-dev/2012-August/003911.html 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] [workflow-plugin] (JENKINS-26538) Less-trusted workflow-cps-global-lib
Jesse Glick created JENKINS-26538 Less-trusted workflow-cps-global-lib Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 21/Jan/15 9:19 PM Description: Currently in order to push to workflow-cps-global-lib you need to have Jenkins.RUN_SCRIPTS. It would be useful to be able to let users with lesser permissions push here, so long as the result is only loaded inside scripts run inside the sandbox anyway. Project: Jenkins Labels: permissions Priority: Minor Reporter: Jesse Glick 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Daniel Weber assigned JENKINS-9104 to Daniel Weber Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Change By: Daniel Weber (21/Jan/15 10:23 PM) Assignee: DanielWeber 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-26508) Upgrade to 1.597 breaks Job page
josh mac commented on JENKINS-26508 Upgrade to 1.597 breaks Job page Odd that the upgrade seemed to cause the conflict. Again, downgrading to Jenkins 1.596 resolves the issue and allows use for the 0.24 version of Disk Usage 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods not being recorded for approval
Jesse Glick created JENKINS-26541 Rejected sandbox methods not being recorded for approval Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 21/Jan/15 11:27 PM Description: I tried to run the CD demo in the sandbox and got org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod java.util.UUID randomUUID at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:100) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:81) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.runWithServer(WorkflowScript:47) at WorkflowScript.run(WorkflowScript:16) at Unknown.Unknown(Unknown) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69) Fine, but then http://localhost:8081/scriptApproval/ did not list the rejected method. Is SandboxContinuable not calling ScriptApproval.accessRejected? Project: Jenkins Priority: Major Reporter: Jesse Glick 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-26441) GoogleTest failure interpreted as compiler error on VC10_64
Ulli Hafner commented on JENKINS-26441 GoogleTest failure interpreted as compiler error on VC10_64 Which parser are you using? 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] [workflow-plugin] (JENKINS-26101) Load entire script from SCM
SCM/JIRA link daemon commented on JENKINS-26101 Load entire script from SCM Code changed in jenkins User: Jesse Glick Path: flow.groovy http://jenkins-ci.org/commit/workflow-plugin-pipeline-demo/485c0ec6837c82795b0d438809ba286718c7784d Log: JENKINS-26101 Should be able to load complete script from SCM now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Thomas Shewmake commented on JENKINS-25435 Embedded Sauce Report does not show up when session ID present in xunit file Hi Ross, I was still able to reproduce the issue after some thorough investigation. I have also ensured that the "Run Sauce Labs Test Publisher" Post Build Action is enabled. 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-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Jackey Cheung updated JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy Change By: Jackey Cheung (22/Jan/15 12:34 AM) Environment: CentOS6,Jenkins1. 595 596 ,subversion-plugin2.5,Java1.7.0_71,visualsvnserver2.7.3 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-25906) Incremental builds are not represented in Warnings plugin
Ulli Hafner commented on JENKINS-25906 Incremental builds are not represented in Warnings plugin How would one detect that the build is incremental? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Ross Rowe commented on JENKINS-25435 Embedded Sauce Report does not show up when session ID present in xunit file Okay, thanks for letting me know, I'll try setup my environment to replicate the issue. As a workaround, can you try set the 'build' capability, using the value of the 'JENKINS_BUILD_NUMBER' environment variable? This should cause the Sauce job to be updated to include the Jenkins build number, which should in turn cause the Sauce jobs to appear within the build/test results. 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-26365) Animated ball in job's build history widget won't open Console Output
Samuel Gabriel commented on JENKINS-26365 Animated ball in jobs build history widget wont open Console Output Is there is any progress on this case. Is this part of 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] [google-play-android-publisher-plugin] (JENKINS-26542) Cannot change Google Service Account
Alex V created JENKINS-26542 Cannot change Google Service Account Issue Type: Bug Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 22/Jan/15 1:07 AM Description: I configured and used a google service account in a job. Now I want to change that google service account to a new one. The two accounts appear in the drop down list in "Google Play Account" I can change it to the new one and hit Save. Everything seems to work fine, but when I open the configuration again, it still is on the previous account Project: Jenkins Priority: Minor Reporter: Alex V 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-26496) Trying to get the DateFormat as build ID
Andrey Regentov commented on JENKINS-26496 Trying to get the DateFormat as build ID Daniel's suggestion to install unmerged 0.25-snapshot https://jenkins.ci.cloudbees.com/job/plugins/job/disk-usage-plugin/75/org.jenkins-ci.plugins$disk-usage/ works for me. 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] [vmware-plugin] (JENKINS-26543) VM abruptly gets restarted through Jenkins.
manohar joshi created JENKINS-26543 VM abruptly gets restarted through Jenkins. Issue Type: Bug Assignee: stephenconnolly Attachments: Jenkins_VM.jpg Components: vmware-plugin, vsphere-cloud-plugin Created: 22/Jan/15 5:05 AM Description: Hello Team, We have connected Slave windows 2008 R2 machine to jenkins using vmrun command. "C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe" -T server -h Vcenter_IP -u domain\username -p password -gu administrator -gp password runProgramInGuest "DATASTORE build_vm/build_vm.vmx" -noWait "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar C:\jenkins\slave.jar -jnlpUrl "http://JENKINS_IP/jenkins/computer/BUild_VM/slave-agent.jnlp" We observed that build VM gets restarted randomly eventhough the build job is running on that VM. Please check the attachment for details. Environment: Jenkins 1.580.2 , Tomcat7 , JRE 7 , Windows 2008 R2 , Vsphere Plugin 1.1.12 Project: Jenkins Labels: Vsphere Priority: Major Reporter: manohar joshi 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-26544) Select All icon in configuration page looks image not found icon
Naoki Ishihara created JENKINS-26544 Select All icon in configuration page looks image not found icon Issue Type: Bug Assignee: Unassigned Attachments: Screen_Shot_2015-01-21_at_9_47_58_PM.png Components: core Created: 22/Jan/15 5:54 AM Description: Current icon for "select all" in configuration page looks like "image not found" icon. See the screenshot attached. Typical Image Not Found icon: http://th01.deviantart.net/fs71/200H/i/2012/324/c/0/image_not_found_icon_by_oldskull-d5llmx5.jpg I would suggest to use an icon that clearly shows "select" like this: http://icons.iconarchive.com/icons/kyo-tux/phuzion/256/Sign-Select-icon.png Environment: Google Chrome Project: Jenkins Labels: gui www Priority: Trivial Reporter: Naoki Ishihara 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-24673) Build wrappers in Workflow plugin
Jesse Glick updated JENKINS-24673 Build wrappers in Workflow plugin Change By: Jesse Glick (22/Jan/15 2:22 AM) Labels: apiworkflow 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-24673) SimpleBuildWrapper
Jesse Glick updated JENKINS-24673 SimpleBuildWrapper Change By: Jesse Glick (22/Jan/15 2:22 AM) Summary: BuildwrappersinWorkflowplugin SimpleBuildWrapper Component/s: core Component/s: workflow-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] [subversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Christian Grobauer commented on JENKINS-26318 Subversion Plug in 2.5 causes sporadic problems Wiping out the workspace and setting svn workspace to 1.8 works. But this makes the update to subversion plug in 2.5 a bit complex, because I had to wipe out all workspaces at once (or modify all jobs to do that). When the Plug in would work stable with svn workspaces 1.7, I can do this step by step. 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-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli updated JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Change By: Libero Scarcelli (22/Jan/15 7:49 AM) Description: Persistingbuild(s)log(s)inMySQL(orsimilar)willmakeJenkinsupdatesmucheasiertomanage.Infact,whenbuildlogschangetheirformatwe sometimes endupwithabrokensystemwhichitisoftenunabletoreadlogsofoldbuilds. Sometimessoftware Software changesevenbreakstoredbuildsinfo fromtimetotime 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-26496) Trying to get the DateFormat as build ID
Daniel Beck commented on JENKINS-26496 Trying to get the DateFormat as build ID Another user reports that downgrading to Disk Usage 0.23 works as well. (I haven't tried it though.) 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-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli created JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Issue Type: New Feature Assignee: Praqma Support Components: core, logging-plugin Created: 22/Jan/15 7:45 AM Description: Persisting build(s) log(s) in MySQL (or similar) will make Jenkins updates much easier to manage. In fact, when build logs change their format we end up with a broken system which it is often unable to read logs of old builds. Sometimes software changes even break stored builds info Project: Jenkins Labels: jenkins build database logs format persistence Priority: Critical Reporter: Libero Scarcelli 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-26519) Build records not migrated due to “failed to rename
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename Switched to Jenkins ver. 1.598-SNAPSHOT (rc-01/21/2015 18:23 GMT-jenkins) after having deleted the legacyIds files. But still: ... ... 22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate INFO: Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.02-dev\builds 22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate WARNUNG: failed to rename 2014-08-30_00-58-41 to 79 22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate INFO: Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 12.01.02-patched\builds 22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate WARNUNG: found no build.xml in 2012-12-07_00-13-31 22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate WARNUNG: failed to rename 2013-03-01_00-22-07 to 271 22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate WARNUNG: failed to rename 2015-01-20_01-45-40 to 82 22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate ... ... 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-26519) Build records not migrated due to “failed to rename
tdtappe updated JENKINS-26519 Build records not migrated due to “failed to rename Listings of job and job/builds directories. Change By: tdtappe (22/Jan/15 7:27 AM) Attachment: job.dir.txt Attachment: job-builds.dir.txt 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] [cloudfoundry-plugin] (JENKINS-26546) Deploy all applications defined in manifest.yml file
Andreas Buchen created JENKINS-26546 Deploy all applications defined in manifest.yml file Issue Type: Improvement Assignee: William Gautier Components: cloudfoundry-plugin Created: 22/Jan/15 7:54 AM Description: One can define multiple applications in a manifest.yml file. Quickly glancing over the ManfestReader, that class also understands that. However, only the first application is deployed because there seems to be only one DeploymentInfo. Yesterday, I posted it here https://github.com/ActiveState/cloudfoundry-jenkins/issues/1 Project: Jenkins Priority: Minor Reporter: Andreas Buchen 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] [workflow-plugin] (JENKINS-26101) Load entire script from SCM
Jesse Glick
updated JENKINS-26101
Load entire script from SCM
Change By:
Jesse Glick
(21/Jan/15 9:02 PM)
Summary:
Load
Script
entirescript
fromSCM
(wave#2)
Description:
h3.Addingclasspath
Allowtheworkflowto(visually)configurean{{SCM}},checkitoutintoaworkspaceontheJenkinsmaster,andloadasandboxedGroovyscript
from
adefinedlocationinthat
workspace
?
.
Byconstructing
_Perhaps_allowtheworkspacetobetreatedasasourcepathsolibrariescanbeimported.OptionallyincludetheflowSCMinpollingand/orchangeloggeneration.Abandonedideas:#Construct
{{URL}}withaninstanceof{{URLStreamHandler}}wecancreateaURLspacethatcanaccessfilesover{{FilePath}}
.Thiswouldenableprimitiveslikethis:{code}node{giturl:my-shared-script.git
,
credentialId:1234-5678-deadbeefdeadbeefaddClassPath}{code}Theressomedetailsthatneedtobefiguredouthowto
andsomehow
prevent
classloader
theclassloader
fromcontinuingtouse
workspaceafter
theworkspace
afterit
goesoutofscope.
h3.AddclasspathfromSCMSourceprimitiveTheideaissimilarhereexcept
#Similarbut
the
custom
{{URLStreamHandler}}uses{{SCMSource}}toaccessfileswithoutevercheckingoutanything.
{code}librarytype:git,remote:my-shared-script.git,credentialId:1234-5678-deadbeefdeadbeef...{code}h3.Primitivethatuses{{SCM}}tocheckoutstuffintothemasterInsteadofmessingaroundwith{{URLStreamHandler}},justuseordinary{{SCM}}andcheckoutcodeintosomehiddenlocationsonthemasterandaddsthatlocaldirectoryasclasspath.Needstobeseenif{{SCM}}checkouthaveanyunwantedside-effecttotheprojectortothemaster.h3.SecurityConsiderationsInallthecases,donotallowclassfiles,jarfilestobeaddeddirectlytotheclasspathasitdbypassthesandbox.
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] [virtualbox-plugin] (JENKINS-16231) Stop slave options should list all possible options, not just save and poweroff
p r edited a comment on JENKINS-16231 Stop slave options should list all possible options, not just save and poweroff But with the option to actually have an acpipowerbutton option the end user can set what action is taken when that acpi button is pressed. End users have to setup what action is taken when that signal is received it does not just automatically send the OS the proper shutdown command for a clean and safe shutdown in every OS. Using the poweroff is essentially the same as pulling the power cord from a box. That is not a good choice at all. Also once you send the acpipoweroff you could easily poll to make sure it is not running anymore through checking what is left running or just checking the state of said machine that just got the acpi button press signal. Just my opinion and the biggest downfall I see to this plugin. Not everyone wants or needs to save state and really no one should use the poweroff command unless you want to corrupt your file system VERY quickly. 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-5125) Projects building at the same time despite Block build when upstream is building option
Marko Macek commented on JENKINS-5125 Projects building at the same time despite Block build when upstream is building option I just encountered it now in jenkins 1.574... not sure if that's recent (it was on above date). I will upgrade it now to the latest. 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer edited a comment on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. I have solved this using a trigger job and a BuildParameterFactory as described on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin It would be nice if this could be solved by only using one single jenkins job without any downstream triggering. 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Christian Bremer commented on JENKINS-22185 Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. I have solved this using a trigger job and a BuildParameterFactory as described on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin Although it would be nice if this could be solved by only using one single jenkins job without any downstream triggering. 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-26526) Test results link only works from all tab
David Rubio created JENKINS-26526 Test results link only works from all tab Issue Type: Bug Assignee: Unassigned Attachments: testresults.png Components: core Created: 21/Jan/15 11:37 AM Description: I am observing the following behaviours when trying accessing the test results from the All tab and from any other tab. The link I'm talking about can be seen in the attached image: The link Jenkins redirects the user when clicking the link from the All tab is: https://jenkins.seebyte.com/view/tab_Name/job/job_Name/lastCompletedBuild/testReport/ The link Jenkins redirects the user when clicking the link from the other tab is: https://jenkins.seebyte.com/view/tab_Name/view/tab_Name/job/job_Name/lastCompletedBuild/testReport/ The problem is that the link has view/tab_Name/ duplicated. I've tried with different view plugins with the same results. For example: Dashboard List view My view Environment: Jenkins 1.596 Project: Jenkins Labels: test-results Priority: Minor Reporter: David Rubio 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] [workflow-plugin] (JENKINS-26522) Annotated block results
Jesse Glick updated JENKINS-26522 Annotated block results Change By: Jesse Glick (21/Jan/15 11:39 AM) Issue Type: Bug NewFeature 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-26526) Test results link only works from all tab
David Rubio
updated JENKINS-26526
Test results link only works from all tab
Change By:
David Rubio
(21/Jan/15 11:38 AM)
Description:
IamobservingthefollowingbehaviourswhentryingaccessingthetestresultsfromtheAlltabandfromanyothertab.ThelinkImtalkingaboutcanbeseenintheattachedimage:!testresults.png!-ThelinkJenkinsredirectstheuserwhenclickingthelinkfromtheAlltabis:https://
jenkins.seebyte.com
server
/view/tab_Name/job/job_Name/lastCompletedBuild/testReport/-ThelinkJenkinsredirectstheuserwhenclickingthelinkfromtheothertabis:https://
jenkins.seebyte.com
server
/view/tab_Name/view/tab_Name/job/job_Name/lastCompletedBuild/testReport/Theproblemisthatthelinkhas{{view/tab_Name/}}duplicated.Ivetriedwithdifferentviewpluginswiththesameresults.Forexample:*Dashboard*Listview*Myview
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-24589) Build History - name and links overlap if build names are long
Steve Haworth commented on JENKINS-24589 Build History - name and links overlap if build names are long I would check the conclusions Daniel has come to carefully, I think I have both the issues he indicates. However, they only seemed to be present for me when upgrading to 1.586. This change may not have introduced these issues. The improvement with non-overlapping, I would not like to see regressed. 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-26519) Wrong (last success) date after migration to 1.597
tdtappe commented on JENKINS-26519 Wrong (last success) date after migration to 1.597 Old builds' dates are incorrect (01.01.1970), new builds (after having updated to 1.597) are correct. Same for viewing a single 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] [core] (JENKINS-25869) Jenkins is getting crashed and shutting down once in a while
Vamsi Hari updated JENKINS-25869 Jenkins is getting crashed and shutting down once in a while Hey Daniel - We had tried by commenting the proxy related env variables in the host. we had only specified the proxy settings in the Jenkins UI, but the Jenkins crashes still persists. I am attaching the most recent crash log. Please verify, We truly appreciate your help, Thanks and Regards, Vamsi Hari Change By: Vamsi Hari (21/Jan/15 10:47 AM) Attachment: hs_err_pid13387.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26524) Null Pointer Exception on github payload push to Jenkins
sunil madhu created JENKINS-26524 Null Pointer Exception on github payload push to Jenkins Issue Type: Bug Assignee: Unassigned Components: git-plugin Created: 21/Jan/15 11:06 AM Description: we recently upgraded Jenkins and It's plugins and we are experiencing an issue with failure to build on git commit events, which prior to the update was working properly. We have confirmed that the issue is this NPE in Jenkins: Poked SocureService-Dev-Static-Checks Jan 21, 2015 7:29:18 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked SocureService-Dev-with-tests Jan 21, 2015 7:29:18 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked SocureService-Production-Patches Jan 21, 2015 7:29:18 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked stage-service Jan 21, 2015 7:29:18 AM SEVERE com.cloudbees.jenkins.GitHubPushTrigger$1 runPolling Failed to record SCM polling java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.EnvironmentContributorImpl.buildEnvironmentFor(EnvironmentContributorImpl.java:23) at hudson.model.Run.getEnvironment(Run.java:2224) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:905) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:563) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:525) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1441) at hudson.model.AbstractProject.poll(AbstractProject.java:1344) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Environment: jenkins 1.597 on Centos Linux Open jdk Java 7 Project: Jenkins Labels: build-on-commit Priority: Critical Reporter: sunil madhu 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.
