[JIRA] [ec2] (JENKINS-17410) Unable to delete ec2 slave
Adam PAPAI resolved JENKINS-17410 as Fixed Unable to delete ec2 slave This works now as expected. Not sure which commit fixes it, but it's Ok now. INFO: job2 #3 main build action completed: SUCCESS Mar 25, 2014 9:09:00 AM hudson.model.AsyncPeriodicWork$1 run INFO: Started EC2 alive slaves monitor Mar 25, 2014 9:09:02 AM hudson.plugins.ec2.EC2SlaveMonitor execute INFO: EC2 instance is dead: i-e0fa86e9 Mar 25, 2014 9:09:02 AM hudson.plugins.ec2.EC2OndemandSlave terminate INFO: EC2 instance already terminated: i-e0fa86e9 Mar 25, 2014 9:09:02 AM hudson.plugins.ec2.EC2SlaveMonitor execute INFO: EC2 instance is dead: i-cbfb87c2 Mar 25, 2014 9:09:03 AM hudson.plugins.ec2.EC2OndemandSlave terminate INFO: EC2 instance already terminated: i-cbfb87c2 Mar 25, 2014 9:09:03 AM hudson.model.AsyncPeriodicWork$1 run INFO: Finished EC2 alive slaves monitor. 2387 ms Change By: Adam PAPAI (25/Mar/14 8:13 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI commented on JENKINS-14575 SCM checkout retry count not working Sent PR and this time I added a test as well. So I won't happen again hopefully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [www] (JENKINS-17636) http://jenkins-ci.org/image is broken (PgSQL errors)
Adam PAPAI created JENKINS-17636 http://jenkins-ci.org/image is broken (PgSQL errors) Issue Type: Bug Assignee: Unassigned Components: www Created: 16/Apr/13 2:06 PM Description: The /images url is broken, and filled with a lot's of PgSQL error: warning: pg_query() function.pg-query: Query failed: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky D... ^ in /usr/share/drupal6/includes/database.pgsql.inc on line 139. user warning: query: SELECT DISTINCT n.nid from node n INNER JOIN term_node tn ON n.nid = tn.nid INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view = 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'content_access_author') OR (na.gid = 1 AND na.realm = 'content_access_rid'))) AND ( tn.tid IN (21) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky DESC, n.created DESC LIMIT 1 OFFSET 0 in /etc/drupal/6/sites/default/modules/image/contrib/image_gallery/views/image_gallery_handler_field_gallery_cover.inc on line 164. warning: pg_query() function.pg-query: Query failed: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky D... ^ in /usr/share/drupal6/includes/database.pgsql.inc on line 139. user warning: query: SELECT DISTINCT n.nid from node n INNER JOIN term_node tn ON n.nid = tn.nid INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view = 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'content_access_author') OR (na.gid = 1 AND na.realm = 'content_access_rid'))) AND ( tn.tid IN (21) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky DESC, n.created DESC LIMIT 1 OFFSET 0 in /etc/drupal/6/sites/default/modules/image/contrib/image_gallery/views/image_gallery_handler_field_gallery_cover.inc on line 164. warning: pg_query() function.pg-query: Query failed: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky D... ^ in /usr/share/drupal6/includes/database.pgsql.inc on line 139. user warning: query: SELECT DISTINCT n.nid from node n INNER JOIN term_node tn ON n.nid = tn.nid INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view = 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'content_access_author') OR (na.gid = 1 AND na.realm = 'content_access_rid'))) AND ( tn.tid IN (22) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky DESC, n.created DESC LIMIT 1 OFFSET 0 in /etc/drupal/6/sites/default/modules/image/contrib/image_gallery/views/image_gallery_handler_field_gallery_cover.inc on line 164. warning: pg_query() function.pg-query: Query failed: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky D... ^ in /usr/share/drupal6/includes/database.pgsql.inc on line 139. user warning: query: SELECT DISTINCT n.nid from node n INNER JOIN term_node tn ON n.nid = tn.nid INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view = 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'content_access_author') OR (na.gid = 1 AND na.realm = 'content_access_rid'))) AND ( tn.tid IN (22) AND n.type = 'image' AND n.status = 1 )ORDER BY n.sticky DESC, n.created DESC LIMIT 1 OFFSET 0 in /etc/drupal/6/sites/default/modules/image/contrib/image_gallery/views/image_gallery_handler_field_gallery_cover.inc on line 164. Project: Jenkins Labels: www postgresql Priority: Minor Reporter: Adam PAPAI
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize I've tested it. It works now. It can check out on a remote slave, it can merge to another repo, and after the tests it can push the merged thing to another branch. So the commit above my previous commit did it. I reverted it. Created a pull request for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize I've started to find out where went it bad. The affected commits are: https://github.com/jenkinsci/git-plugin/compare/1349eaba9c5767e9bf52ab27b6c31681f0c13733...6336dc5595266b83c199710953c61351297b7bd8 so this was the last stable commit: https://github.com/jenkinsci/git-plugin/commit/1349eaba9c5767e9bf52ab27b6c31681f0c13733 The next few commits failed to compile. This one compiles, but throws "kind of error", which means it fails to merge: Could not checkout release with start point https://github.com/jenkinsci/git-plugin/commit/a60b03fab35e62547a058cc8b4eefd62ee6b05b6 So somewhere between: https://github.com/jenkinsci/git-plugin/compare/1349eaba9c5767e9bf52ab27b6c31681f0c13733...6336dc5595266b83c199710953c61351297b7bd8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Meanwhile I think I've found the problematic part. It now works for me locally. Trying to create a patch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI assigned JENKINS-16941 to Adam PAPAI Git publisher post build action fails on slave agent - unable to serialize Change By: Adam PAPAI (12/Apr/13 6:19 PM) Assignee: NicolasDeLoof AdamPAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI started work on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Change By: Adam PAPAI (12/Apr/13 6:19 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/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize This one breaks the feature. At last for us it breaks when it wants to merge the main with another branch. (so merge before build) https://github.com/cosmin/git-plugin/commit/a7a9e3d714adc80eab8a9271c79883b6cdf7bd93 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Adam PAPAI edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize This one breaks the feature. At last for us it breaks when it wants to merge the main with another branch. (so merge before build) https://github.com/cosmin/git-plugin/commit/a7a9e3d714adc80eab8a9271c79883b6cdf7bd93 Try to revert it and test it on your system. Let me know how it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI commented on JENKINS-14575 SCM checkout retry count not working This solves the issue: https://github.com/jenkinsci/git-plugin/pull/143 We're waiting for the merge. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17410) Unable to delete ec2 slave
Adam PAPAI commented on JENKINS-17410 Unable to delete ec2 slave Do you see this EC2 instance via the AWS console? It could be an AWS issue. Perhaps your instance has been terminated (sometimes when they're stuck, AWS kills them). You can remove it by manually stop jenkins edit the config.xml (the main jenkins xml) delete that node from the xml save the config.xml start up jenkins The node will be gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17410) Unable to delete ec2 slave
Adam PAPAI commented on JENKINS-17410 Unable to delete ec2 slave And what kind of plugin are you using exactly for the EC2 auto provisioning. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI commented on JENKINS-14575 SCM checkout retry count not working I've just fixing this. I got the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI assigned JENKINS-14575 to Adam PAPAI SCM checkout retry count not working Change By: Adam PAPAI (28/Mar/13 9:07 AM) Assignee: AdamPAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI started work on JENKINS-14575 SCM checkout retry count not working Change By: Adam PAPAI (28/Mar/13 9:22 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15239) Tags feature is broken
Adam PAPAI commented on JENKINS-15239 Tags feature is broken What's up with this issue? Can we release a newer version? As far as I can see the development is happening in the background. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Adam PAPAI commented on JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Do we have any improvements on this? We also need no throttle our matrix jobs. Is there something I can help? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Adam PAPAI edited a comment on JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Do we have any improvements on this? We also need to throttle our matrix jobs. Is there something I can help? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14306) Matrix jobs are failed to load
Adam PAPAI created JENKINS-14306 Matrix jobs are failed to load Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 04/Jul/12 7:43 AM Description: The matrix jobs created via 1.471 version are not working anymore. During jenkins boot-up the following error messages can be found in the jenkins.log SEVERE: Failed Loading job website-acceptance-test-suite java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:296) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Perhaps it's something with the new Matrix job feature? Environment: Debian LTS Lucid 64bit Project: Jenkins Labels: matrix jenkins Priority: Major Reporter: Adam PAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14194) Stack Trace when going to main configuration page (throttle concurrent build plugin)
Adam PAPAI updated JENKINS-14194 Stack Trace when going to main configuration page (throttle concurrent build plugin) Change By: Adam PAPAI (28/Jun/12 5:51 AM) Assignee: AdamPAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14194) Stack Trace when going to main configuration page (throttle concurrent build plugin)
Adam PAPAI assigned JENKINS-14194 to Adam PAPAI Stack Trace when going to main configuration page (throttle concurrent build plugin) Change By: Adam PAPAI (25/Jun/12 9:29 PM) Assignee: KohsukeKawaguchi AdamPAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14158) Change to build timeout job configuration not saved
Adam PAPAI edited a comment on JENKINS-14158 Change to build timeout job configuration not saved It is fixed in the HEAD. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14158) Change to build timeout job configuration not saved
Adam PAPAI edited a comment on JENKINS-14158 Change to build timeout job configuration not saved Hm right. Same here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14158) Change to build timeout job configuration not saved
Adam PAPAI commented on JENKINS-14158 Change to build timeout job configuration not saved It seems it's fixed in git, just not released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14158) Change to build timeout job configuration not saved
Adam PAPAI commented on JENKINS-14158 Change to build timeout job configuration not saved Fail the build is only available if you select the "Likely stuck". The UI is a little bit confusing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
