[JIRA] (JENKINS-47442) Parameterized Trigger hangs waiting for downstream job
Title: Message Title Travis Neal commented on JENKINS-47442 Re: Parameterized Trigger hangs waiting for downstream job Was this ever fixed for you guys? we're running into the same issues. We tried downgrading to 2.32 but this is lower than required for the Git plugin (which requires 2.33, which is the breaking version) downgrading the Git plugin to allow the parameterized trigger plugin to work correctly would mean removing core functionality from our Jenkins implementation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-46044) ec2 plugin doesn't work it has same label with other slaves
Title: Message Title Travis Neal commented on JENKINS-46044 Re: ec2 plugin doesn't work it has same label with other slaves I have this problem too, we created a single jenkins system to be used by our entire company, but because of this queue build up on common labels like "ubuntu" and "windows" there's an exponential queue time of waiting for executors and eventually creating a new instance. Was hoping the One-Shot Executor Plugin would fix this, however that only supplies an API to be used by other plugins and the Amazon EC2 plugin doesn't implement this API. Working on creating a custom plugin to tie these 2 community plugins together. 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-52499) All Descriptions throughout Jenkins, Change to AD_Login
Title: Message Title Travis Neal assigned an issue to Francis Upton Jenkins / JENKINS-52499 All Descriptions throughout Jenkins, Change to AD_Login Change By: Travis Neal Component/s: ec2-plugin Component/s: credentials-plugin Assignee: Francis Upton 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-52499) All Descriptions throughout Jenkins, Change to AD_Login
Title: Message Title Travis Neal commented on JENKINS-52499 Re: All Descriptions throughout Jenkins, Change to AD_Login Update: I duplicated our entire Jenkins stack and started deleting things. Deleted every single plugin except the Amazon EC2 Plugin and all of its dependencies, deleted all files related to deleted plugins and deleted all builds and jobs from the server. It was still happening. However, I decided to delete all but 1 AMI profile in the configuration and it stopped updating the field to say "AD_Login". I then deleted 1 by 1, restarted the server and checked. It stopped after deleting the last windows profile. I then put them all back copying that section from the "live" jenkins server we have and pasting it in. It started happening again. Removed all the windows profiles and only the windows profiles, and it no longer updates the field to say "AD_Login". I don't feel like this is a way to fix it, but it's a way to get around it for now and at least SOME lead to go on when trying to debug this. I'm going to update the components on this ticket to show the ec2 plugin and hope that this ticket hasn't been lost to the abyss. 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-52883) Single Use Slave Plugin Not Triggered In Pipelines
Title: Message Title Travis Neal updated an issue Jenkins / JENKINS-52883 Single Use Slave Plugin Not Triggered In Pipelines Change By: Travis Neal Attachment: ami_prof.png Attachment: sus_config.png 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-52883) Single Use Slave Plugin Not Triggered In Pipelines
Title: Message Title Travis Neal created an issue Jenkins / JENKINS-52883 Single Use Slave Plugin Not Triggered In Pipelines Issue Type: Bug Assignee: Clayton O'Neill Components: singleuseslave-plugin Created: 2018-08-03 22:48 Priority: Minor Reporter: Travis Neal We use the ec2 plugin to drive our version of "Nodepool", from this we use the Single Use Slave plugin to mark nodes offline after the job has completed. However, when running a pipeline job, the Single Use Slave plugin does not trigger on these nodes, thus allowing multiple jobs to build on a "dirty" node. I have triple checked that the label of the profile is marked under the Single Use Slave plugin's config and there is no other AMI profile being used when creating the node, Single Use Slave simply does not handle this. Add Comment
