[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate edited a comment on JENKINS-57749 Re: Latest terraform version (0.12.0) not available for download via global tool installation from bintray Thanks [~dpires]. Any clues on how to "invalidate" the cache , or who might be better placed to know ? Things i have already tried: * restart jenkins * reload config from disk * uninstall and reinstall the plugin from scratch * manually edit the file /var/lib/jenkins/org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml to change the version string and reload jenkins config from disk * restart the serverin all cases above I have not been able to get the plugin to show the desired 0.12.0 build as an option, even when hardcoding that into the org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml file. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.16574.1559216280364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate commented on JENKINS-57749 Re: Latest terraform version (0.12.0) not available for download via global tool installation from bintray Thanks David Pires. Any clues on how to "invalidate" the cache? Things i have already tried: restart jenkins reload config from disk uninstall and reinstall the plugin from scratch manually edit the file /var/lib/jenkins/org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml to change the version string and reload jenkins config from disk restart the server in all cases above I have not been able to get the plugin to show the desired 0.12.0 build as an option, even when hardcoding that into the org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml file. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.16571.1559216280319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate updated an issue Jenkins / JENKINS-57749 Latest terraform version (0.12.0) not available for download via global tool installation from bintray Change By: David Goate Priority: Critical Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.15637.1559152440152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate created an issue Jenkins / JENKINS-57749 Latest terraform version (0.12.0) not available for download via global tool installation from bintray Issue Type: New Feature Assignee: David Pires Attachments: Screenshot 2019-05-29 at 18.45.59.png, Screenshot 2019-05-29 at 18.46.06.png Components: terraform-plugin Created: 2019-05-29 17:52 Priority: Critical Reporter: David Goate We want to upgrade terraform to 0.12.0, but we are unable to do so via the terraform tool as the latest available is 0.11.13. I'm not sure if this is an issue with the bintray craweler rather than this plugin, but the end result is that we cannot use our terraform files with this plugin (to provide the binary tool at least). We approximately judge from https://github.com/jenkins-infra/crawler/blob/master/terraform.groovy that the crawler should use https://releases.hashicorp.com/terraform/ which does appear to have the relevant version. Could it be that we have some cache or is there an issue here in the crawler or plugin?
[JIRA] (JENKINS-55492) Plugin is not reusing stopped AWS EC2 instances
Title: Message Title David Goate created an issue Jenkins / JENKINS-55492 Plugin is not reusing stopped AWS EC2 instances Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-09 17:01 Environment: Plugin version 1.42 Priority: Major Reporter: David Goate Using 1.39 of the plugin, the behaviour I observed was that when the instance cap was set to 2 and 2 slaves were already provisioned (e.g. in the stopped EC2 state rather than terminated), when a slave is required for a pending queued build, the plugin used to simply start one of the 2 stopped instances as required. Now, on 1.42, the plugin appears to leave the previous 2 EC2 instances in the stopped state on AWS and provision a brand new slave, leading to it exceeding the instance cap of 2 and there now being 3 EC2 instances (albeit 2 stopped and only 1 running). For now, my workaround was to go back to 1.39. Add Comment
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title David Goate commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free I'm actually not sure about the title of this issue, specifically "Oracle JDK 11 is not free". I thought that it was not free for use in production, but that it can be used to produce development builds? If that is the case, as long as the Oracle JRE is not actually being used to run the code in production (rather than just build the JAR file that will ultimately be used), is there an issue with using Oracle JDK 11? It's a little academic in my specific case anyway, as we've started using OpenJDK java 11 build now (via the custom tool plugin rather than the JDK tool one). But I am interested on whether my interpretation of this is right. 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title David Goate edited a comment on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free I'm actually not sure about the title of this issue, specifically "Oracle JDK 11 is not free". I thought that it was not free for use in production, but that it can be used to produce development builds? If that is the case, as long as the Oracle JRE is not actually being used to run the code in production (rather than just build the JAR file that will ultimately be used), is there an issue with using Oracle JDK 11? It's a little academic in my specific case anyway, as we've started using OpenJDK java 11 build now (via the custom tool plugin rather than the JDK tool one - see JENKINS-55482 ). But I am interested on whether my interpretation of this is right. 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-55482) JDK 10 no longer working
Title: Message Title
David Goate commented on JENKINS-55482
Re: JDK 10 no longer working
Perhaps, it could be that one of our slaves got re-provisioned as we use the EC2 plugin to start and stop slaves - perhaps one today got re-provisioned. We have for now stopped using the tool and migrated to using JDK 11 with a custom tool installer. Our pipelines now look like this:
pipeline {
agent {label 'cloud-slave'}
environment {
JDK_11 = tool name: 'JDK11', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool'
JAVA_HOME = "${env.JDK_11}"
}
...
}
Which seems to be working. All it required was the set up of a customer tool (see attached image)
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-55482) JDK 10 no longer working
Title: Message Title David Goate updated an issue Jenkins / JENKINS-55482 JDK 10 no longer working Change By: David Goate Attachment: Screenshot 2019-01-09 at 14.32.58.png 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-55482) JDK 10 no longer working
Title: Message Title
David Goate created an issue
Jenkins / JENKINS-55482
JDK 10 no longer working
Issue Type:
Bug
Assignee:
Devin Nusbaum
Attachments:
Screenshot 2019-01-09 at 13.41.56.png
Components:
jdk-tool-plugin
Created:
2019-01-09 13:57
Environment:
All
Priority:
Blocker
Reporter:
David Goate
As of today, all of our java 10 builds no longer work (they did yesterday). In our pipeline we have:
stage('Build') {
tools {
jdk 'JDK10'
}
}
And at runtime Java version: 9.0.4, vendor: Oracle Corporation, runtime: is ultimately being used. I noticed in the JDK tools provided config in the jenkins admin pane that jdk 10 is no longer an option. Latest is now 9.0.4, which I presume is the root cause. Is there anything that can be done at the plugin provider level, or is this something Oracle related or licensing?
[JIRA] (JENKINS-54399) Configuration page no longer loads
Title: Message Title
David Goate updated an issue
Jenkins / JENKINS-54399
Configuration page no longer loads
Change By:
David Goate
Every Since version 3.4 every time I click the configure system link (manage -> configure system) I get an error page. The error is: {code:java}org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.138.2.jar!/jenkins/model/Jenkins/configure.jelly:51:84: No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at {code} currently I can't access any configuration page. I think today two plugins were updated but I can't find a way Downgrading to list which ones 3 . 3 fixes the issue.
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-54399) Configuration page no longer loads
Title: Message Title David Goate updated an issue Jenkins / JENKINS-54399 Configuration page no longer loads Change By: David Goate Component/s: config-file-provider-plugin Component/s: core 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-54399) Configuration page no longer loads
Title: Message Title David Goate updated an issue Jenkins / JENKINS-54399 Configuration page no longer loads Change By: David Goate Environment: jenkins 2.138.2 config fiel provider 3.4 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-54399) Configuration page no longer loads
Title: Message Title David Goate created an issue Jenkins / JENKINS-54399 Configuration page no longer loads Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-01 15:34 Environment: jenkins 2.138.2 Priority: Blocker Reporter: David Goate Every time I click the configure system link I get an error page. The error is: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.138.2.jar!/jenkins/model/Jenkins/configure.jelly:51:84: No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at currently I can't access any configuration page. I think today two plugins were updated but I can't find a way to list which ones.
[JIRA] (JENKINS-54392) EC2 Plugin Does Not Start Stopped Nodes
Title: Message Title
David Goate created an issue
Jenkins / JENKINS-54392
EC2 Plugin Does Not Start Stopped Nodes
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2018-11-01 09:43
Environment:
Jenkins 2.138.2 EC2-plugin: 1.41
Priority:
Blocker
Reporter:
David Goate
The last working version for me was 1.39, but it's no longer possible to downgrade (the jenkins UI let's me - but it doesn't work - since upgrading from 1.40 to 1.41 the plugin manager warned that the configuration had changed and downgrading may not be possible). After jenkins starts slaves and the idle time expires and they stop, the ec2 plugin does not start them again. They are in the stopped state in AWS and the jenkins logs show over and over again:
SlaveTemplate{ami='ami-xxx', labels='cloud-slave'}. Cannot provision - no capacity for instances: 0
Nov 01, 2018 9:40:19 AM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-xxx', labels='cloud-slave'}
I can manually fix the issue by starting the EC2 instances via the AWS console and then manually connecting the slaves by launching the agents on the jenkins nodes screen, but after the idle period they'll go back to sleep and the problem will reoccur. I've extended the idle timeout now to 8 hours so it's less of an issue throughout the day but each morning I need to start the slaves again and the instances we picked are pretty powerful as we intended to use them in short bursts
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title
David Goate edited a comment on JENKINS-54041
Re: EC2 Plugin no longer able to start build slaves
On latest version (1.41) I still get the warning: {code:java}WARNING: Failed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpljava.lang.NoClassDefFoundError: org/jenkinsci/plugins/blockqueuedjob/condition/BlockQueueCondition$BlockQueueConditionDescriptor{code} Reverting back to 1.39 now also gives: {code:java}Connecting to 10.1.1.90 on port 22, with timeout 1.Oct 29, 2018 11:19:39 AM WARNING org.jvnet.hudson.annotation_indexer.Index$2$1 fetchFailed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpljava.lang.ClassNotFoundException: org.jenkinsci.plugins.blockqueuedjob.condition.BlockQueueCondition$BlockQueueConditionDescriptor at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357){code} Currently none of So my Jenkins builds will run previous "fix" for this (downgrading) no longer fixes the problem . Do you I think this is related after upgrading to this 1.41 some configuration files might have changed as the plugin or manager in Jenkins displayed a different issue red warning saying that it might not be possible to downgrade . Currently none of my Jenkins builds will run automatically.
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-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate commented on JENKINS-54041 Re: EC2 Plugin no longer able to start build slaves Is there any other enhanced log level/appender I could enable or settings I could export which might help with this. I found a way to get builds running (manually log into the EC2 console and start the slaves which are in the stopped state and then once they are running go into the jenkins nodes section and start the agent) When I manually start the agent, I do get a few warnings/errors, but ultimately it does attach and run and builds work. @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! >ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.IllegalStateException: Already connected Agent successfully connected and online Oct 30, 2018 8:48:13 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ 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-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title
David Goate commented on JENKINS-54041
Re: EC2 Plugin no longer able to start build slaves
Further note on something I see in the logs which may be related/help debug the issue:
Oct 30, 2018 8:34:38 AM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-xxx', labels='cloud-slave'}. Attempting to provision slave needed by excess workload of 2 units
Oct 30, 2018 8:34:38 AM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-xxx', labels='cloud-slave'}. Cannot provision - no capacity for instances: 0
Oct 30, 2018 8:34:38 AM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-xxx', labels='cloud-slave'}
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-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate reopened an issue On latest version (1.41) I still get the warning: WARNING: Failed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpl java.lang.NoClassDefFoundError: org/jenkinsci/plugins/blockqueuedjob/condition/BlockQueueCondition$BlockQueueConditionDescriptor Reverting back to 1.39 now also gives: Connecting to 10.1.1.90 on port 22, with timeout 1. Oct 29, 2018 11:19:39 AM WARNING org.jvnet.hudson.annotation_indexer.Index$2$1 fetchFailed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpl java.lang.ClassNotFoundException: org.jenkinsci.plugins.blockqueuedjob.condition.BlockQueueCondition$BlockQueueConditionDescriptor at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) Currently none of my Jenkins builds will run. Do you think this is related to this plugin or a different issue. Jenkins / JENKINS-54041 EC2 Plugin no longer able to start build slaves Change By: David Goate Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate commented on JENKINS-54041 Re: EC2 Plugin no longer able to start build slaves Excellent, thanks for that. Looking forward to the new release 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-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate created an issue Jenkins / JENKINS-54041 EC2 Plugin no longer able to start build slaves Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-12 07:57 Environment: Jenkins 2.138.2 EC2 Plugin 1.40.1 Priority: Blocker Reporter: David Goate When using the EC2-plugin 1.40.1 all of my builds stop working. They are configured to only run on cloud slaves and the master node has no executors. They all queue up waiting for an executor, however all of the executors are offline and never start. Downgrading to EC2 plugin 1.39 fixes the issue. Log files: Failed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpl java.lang.ClassNotFoundException: org.jenkinsci.plugins.blockqueuedjob.condition.BlockQueueCondition$BlockQueueConditionDescriptor at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) Caused: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/blockqueuedjob/condition/BlockQueueCondition$BlockQueueConditionDescriptor at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1140) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:858) at jenkins.util.AntClassLoader.getClass
