[JIRA] (JENKINS-44292) Jcloud GCP network error
Title: Message Title Ignasi Barrera commented on JENKINS-44292 Re: Jcloud GCP network error jcouds 2.1.0 is now released! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44292) Jcloud GCP network error
Title: Message Title Ignasi Barrera edited a comment on JENKINS-44292 Re: Jcloud GCP network error jcouds jclouds 2.1.0 is now released! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44292) Jcloud GCP network error
Title: Message Title Ignasi Barrera commented on JENKINS-44292 Re: Jcloud GCP network error We are just validating jclouds 2.1.0 RC3. You can expect a new jclouds version this week. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26639) JClouds failing after upgrade to 1.598
Title: Message Title Ignasi Barrera commented on JENKINS-26639 Re: JClouds failing after upgrade to 1.598 Just for the record, jclouds 2.0 will support Guice 4.0. Here is the compatibility build to keep an eye on: https://jclouds.ci.cloudbees.com/job/jclouds-guava-guice-compat/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI
Ignasi Barrera created JENKINS-25971 Job list and console output are not properly aligned in the new UI Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Dec/14 4:36 PM Description: When a view that is not the "All" one is selected as the default view, the job list appears at the bottom of the page, just after the executors box, instead of being near the task menu. This also happens to the Console Output view; it is always displayed at the bottom, after the menu. The job list appears OK after resizing the window, or if the "All" view is configured as the default one, but the Console Output view always appears in the wrong place. I've installed the Simple Theme plugin to see if the components are aligned properly in other themes and they work, so it seems something wrong in the default CSS. I've provided my screen resolution and other details in the environment details of the issue. Environment: Jenkins v1.593 Ubuntu 14.04.1 LTS Screen resolution: 1680x1050 Chrome version 40.0.2214.28 beta (64-bit) Project: Jenkins Labels: gui Priority: Major Reporter: Ignasi Barrera This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25971) Job list and console output are not properly aligned in the new UI
Ignasi Barrera edited a comment on JENKINS-25971 Job list and console output are not properly aligned in the new UI Although the environment description says it happens in Chrome, the console alignment also is wrong in Firefox (version 34.0). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25971) Job list and console output are not properly aligned in the new UI
Ignasi Barrera commented on JENKINS-25971 Job list and console output are not properly aligned in the new UI Although The environment description says it happens in Chrome, the console alignment also is wrong in Firefox (version 34.0). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera resolved JENKINS-22963 as Fixed Unable to connect to digitalocean cloud Fixed. See https://github.com/jenkinsci/jclouds-plugin/pull/69 Change By: Ignasi Barrera (03/Jun/14 9:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
Ignasi Barrera resolved JENKINS-23168 as Fixed Allow to specify a Location where to deploy the slaves in the jclouds-plugin Change By: Ignasi Barrera (29/May/14 10:29 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud Yes, the plugin still does not have an option to specify the location where the node will be created, but that would be a nice addition. Mind opening a ticket to track it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud I've just opened it: https://issues.jenkins-ci.org/browse/JENKINS-23168 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
Ignasi Barrera created JENKINS-23168 Allow to specify a Location where to deploy the slaves in the jclouds-plugin Issue Type: Improvement Assignee: Ignasi Barrera Components: jclouds, jclouds-jenkins Created: 23/May/14 1:56 PM Description: Currently the jclouds plugin does not provide a way to specify a location. If the image being deployed and the hardware profile can be used in more than one location, then jclouds picks an available location. The plugin should also allow to manually specify a location, so users can force slaves to be deployed in the desired one. Project: Jenkins Priority: Major Reporter: Ignasi Barrera This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
Ignasi Barrera started work on JENKINS-23168 Allow to specify a Location where to deploy the slaves in the jclouds-plugin Change By: Ignasi Barrera (23/May/14 2:02 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] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
Ignasi Barrera commented on JENKINS-23168 Allow to specify a Location where to deploy the slaves in the jclouds-plugin Patch here: https://github.com/jenkinsci/jclouds-plugin/pull/68 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install hpi:run (have a lok at the README for further details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera edited a comment on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install hpi:run (have a lok at the README for further details. After that you should be able to manually install the plugin in Jenkins from the plugin management page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera stopped work on JENKINS-22963 Unable to connect to digitalocean cloud Change By: Ignasi Barrera (21/May/14 1:53 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera edited a comment on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install (have a look at the README for further details. After that you should be able to manually install the plugin in Jenkins from the plugin management page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud I've just compiled it as shown in my previous comment and uploaded it to my Jenkins instance to verify that the slugs can be used instead of the ids, and that old images are not causing trouble. Let's keep this open until jclouds 1.7.3 is released and we can upgrade the plugin to that 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] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera started work on JENKINS-22963 Unable to connect to digitalocean cloud Change By: Ignasi Barrera (19/May/14 9:05 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud Opened JCLOUDS-572 to address this by also adding support to use the slugs as the IDs. If you want to give it a try, the pull request is linked in the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera assigned JENKINS-22963 to Ignasi Barrera Unable to connect to digitalocean cloud Change By: Ignasi Barrera (18/May/14 8:37 PM) Assignee: abayer IgnasiBarrera This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud This error is raised if the connection fails. To check the connection, the plugin will attempt to use the provided credentials to list the existing nodes. Are you providing the right client ID and api key? Make sure to leave the "endpoint URL" field blank. Jclouds will already set the appropriate one. Also check that the OpenStack zones field is blank. If the error persists, you can enable the jclouds wire logging as follows In the Jenkins Administration System logs, create a new logger. Add the "jclouds.wire", "jclouds.compute" and "jclouds.headers" loggers to it. Edit the jclouds plugin configuration that is having issues and add the following in the "Cloud Instance Tempaltes Advanced Custom JVM Options": -Djenkins.plugins.jclouds.compute.ComputeLogger.wireLogging=true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud There is an ongoing patch for that here: https://github.com/jclouds/jclouds-labs/pull/58 But seeing your comment (many thanks for the investigation!) I think the right fix is to use the slugs instead of the ids everywhere. The change should be easy: we just need to change the classes in the compute.functions package to set the slug in the id field and change the DigitalOceanComputeServiceAdapter accordingly. I'll try to have a patch ASAP for this (if you don't beat me with a PR https://wiki.apache.org/jclouds/How%20to%20Contribute). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud BTW, the plugin will fail as long as the droplet that uses the old image exists. To workaround this, you can take a snapshot of that droplet, destroy it, and create it again from the snapshot. The snapshot will have a new image id and the plugin shouldn't find old ids. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
