[JIRA] (JENKINS-32118) Document Jenkins security settings so Robot Framework log/report can be opened
Title: Message Title Andrew Grimberg commented on JENKINS-32118 Re: Document Jenkins security settings so Robot Framework log/report can be opened My team gave up on doing the work around. We just shuffle the robot logs off to a different storage static web host, along with a lot of logs that Jenkins doesn't capture for us anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167087.1450344294000.2319.1568325421906%40Atlassian.JIRA.
[JIRA] (JENKINS-47301) JClouds aws-ec2 always tries to use default subnet
Title: Message Title Andrew Grimberg commented on JENKINS-47301 Re: JClouds aws-ec2 always tries to use default subnet I would really like to see this get fixed at some point. My team and I have been having to use the EC2 plugin to get around the failure of this one to operate as expected. That plugin is a lot less robust than JClouds and has required us to put a lot of brittle cron jobs in place to take care of things that this one natively supports. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39121) Needs help text for configuration
Title: Message Title Andrew Grimberg created an issue Jenkins / JENKINS-39121 Needs help text for configuration Issue Type: Improvement Assignee: Thanh Ha Components: msginject-plugin Created: 2016/Oct/19 7:05 PM Priority: Minor Reporter: Andrew Grimberg The configuration for the Message Injector doesn't have nay help / examples. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Andrew Grimberg commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Joshua Harlow it works pretty well actually. The one I linked is one of our simpler setups. Our most complex one is at: https://github.com/opendaylight/releng-builder/tree/master/jenkins-scripts Though I think the README is a little outdated since we're using the jenkins-init-script.sh pattern that was mentioned in the previous one I linked. It gives us some extra flexibility in our instance management so we don't have have to be regularly respinning packer builds for small configuration tweaks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Andrew Grimberg commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Donald Morton Here's how we do it in our various environments. We pass a user-data script that does what is explained in the README in the following location. https://github.com/zephyrproject-rtos/ci-management/tree/master/jenkins-scripts I'll note we do this for several different Jenkins systems that we support < /td> Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-28339) Allow skip-vote to also skip vote for "Started"
Title: Message Title Andrew Grimberg commented on JENKINS-28339 Re: Allow skip-vote to also skip vote for "Started" Khai Do Yes the silent start is an option but our customers like to get feedback that the job has started. Which means that with the current options Jenkins will reset its votes if a job is retriggered. I'll also note that as of Gerrit 2.13 a retriggering on an already merged change will cause any, and all messaging that has votes in it to fail and not even post the message if the votes don't match what Gerrit already has for the voting user. This makes it even more difficult for merge based jobs to work correctly without doing an override of the vote values in the job to be what they would "normally" be. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-36406) Ability to utilize HEAT orchestration templates
Title: Message Title Andrew Grimberg created an issue Jenkins / JENKINS-36406 Ability to utilize HEAT orchestration templates Issue Type: New Feature Assignee: Oliver Gondža Components: openstack-cloud-plugin Created: 2016/Jul/04 2:52 AM Priority: Minor Reporter: Andrew Grimberg Our environment makes extensive use of additional instance creation in jobs (aka multi-node labs). However, we have to share the resources between our build instances and these multi-node labs. Given that we can easily starve one or the other for resources if we don't balance things carefully, we can regularly have a job start on a lead multi-node instance and then fail because it can't allocate the needed additional instances. It would be really handy if we could instead of encoding all the instance setup logic in our jobs, instead utilize HEAT orchestration templates that have a lead node identified with a label attached to it. These could then be spun up and wait for Jenkins to attach to the lead node until the entire HEAT stack is online. I've added the HEAT orchestration developer docs link Add Comment
[JIRA] (JENKINS-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Andrew Grimberg commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes What we do is have our Jenkins user created as the very last step of the user data scripts. That keeps Jenkins from connecting into the node until it's actually ready. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
Title: Message Title Andrew Grimberg commented on JENKINS-25962 Re: Using Jenkins Job Builder to create triggers based on comment regex fails to trigger This actually seems to be even worse with the newer versions of the trigger plugin. I haven't worked backwards to figure out which one made it worse but 2.18 doesn't even pick up standard triggers when created / modified in this fashion. It's painful when a job that was working fine (after having either restarted jenkins or doing the save tango) gets an update and stops responding to any trigger events. 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] [jclouds-jenkins] (JENKINS-23454) JClouds plugin needs a way to enable configDrives
Andrew Grimberg created JENKINS-23454 JClouds plugin needs a way to enable configDrives Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 16/Jun/14 11:13 PM Description: Rackspace does not support the cloud-init metadata configuration option and only via a config drive. As such, I need a way to enable the configDrive flag when spawning instances otherwise the instance fails to spin up correctly for custom instances that are using cloud-init. I have found no option in any of the advanced settings for setting this flag. The logs during Jenkins driven instance spin up all state that configDrive=false. Environment: CentOS 6.5 OpenJDK 1.7.0 Jenkins 1.568 JClouds plugin 2.8 Rackspace (OpenStack) Project: Jenkins Labels: jclouds jenkins configuration Priority: Major Reporter: Andrew Grimberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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] (JENKINS-22587) JClouds does not honor security group against OpenStack
Andrew Grimberg created JENKINS-22587 JClouds does not honor security group against OpenStack Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 11/Apr/14 7:50 PM Description: Version 2.5.1 of the JClouds plugin added the ability to define Security Groups that VMs should launch under. I've seen in the logs that it is setting something related to it but VMs are still being forcibly created in the jclouds-instance_name security group which eventually gets deleted when no more slaves are in it and not recreated on the next slave creation. Environment: CentOS 6.5 OpenJDK 1.7.0 Jenkins 1.558 JClouds plugin 2.5.1 OpenStack (Havanna) Project: Jenkins Labels: jclouds Priority: Major Reporter: Andrew Grimberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
