[JIRA] (JENKINS-47022) DropDown is loosing focus on selection of an option
Title: Message Title Alvaro Lobato commented on JENKINS-47022 Re: DropDown is loosing focus on selection of an option Vivek Pandey can we backport this to 1.4.x ? 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-47022) DropDown is loosing focus on selection of an option
Title: Message Title Alvaro Lobato assigned an issue to Nicolae Pascu Jenkins / JENKINS-47022 DropDown is loosing focus on selection of an option Change By: Alvaro Lobato Assignee: Alvaro Lobato Nicolae Pascu 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-47022) DropDown is loosing focus on selection of an option
Title: Message Title Alvaro Lobato assigned an issue to Alvaro Lobato Jenkins / JENKINS-47022 DropDown is loosing focus on selection of an option Change By: Alvaro Lobato Assignee: Nicolae Pascu Alvaro Lobato 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-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato updated JENKINS-42800 Jenkins / JENKINS-42800 Update plugin parent pom to be compatible with JaCoCo jenkins plugin Change By: Alvaro Lobato Status: In Progress Review 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-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato started work on JENKINS-42800 Change By: Alvaro Lobato Status: Open In Progress 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-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42800 Update plugin parent pom to be compatible with JaCoCo jenkins plugin Issue Type: Task Assignee: Alvaro Lobato Components: plugin-pom Created: 2017/Mar/15 10:36 AM Priority: Minor Reporter: Alvaro Lobato The JaCoCo plugin is displaying empty coverage reports with the current plugin parent pom. According to this issue JENKINS-28652 maven plugin should be updated to >0.7.5 to fix the issue. Add Comment This message was
[JIRA] (JENKINS-39679) Use maven-plugin interceptor for maven project integration
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-39679 Use maven-plugin interceptor for maven project integration Change By: Alvaro Lobato Issue Type: Bug Improvement 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-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Alvaro Lobato started work on JENKINS-39407 Change By: Alvaro Lobato Status: Open In Progress 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-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Alvaro Lobato assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-39407 Use system default Maven, Maven Settings if not specified Change By: Alvaro Lobato Assignee: Alvaro Lobato Cyrille Le Clerc 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-40484) Unable to use withMaven step inside docker container
Title: Message Title Alvaro Lobato commented on JENKINS-40484 Re: Unable to use withMaven step inside docker container I've done multiple tests and I can't reproduce this issue. Can you give me the exact versions of the pipeline plugins you are running? The easiest way to help me reproduce this is to install the Support Plugin and generate a support bundle which will contain all the envirornment information. Did you check if this is related to JENKINS-41339? 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-40792) Pipeline Maven fails when configured to use settings.xml from config file provider
Title: Message Title Alvaro Lobato closed an issue as Cannot Reproduce Please reopen if it is still happening, and provide the requested information. Thanks. Jenkins / JENKINS-40792 Pipeline Maven fails when configured to use settings.xml from config file provider Change By: Alvaro Lobato Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-41889) Environment variables available in the Jenkinsfile are not propagated to Maven
Title: Message Title Alvaro Lobato commented on JENKINS-41889 Re: Environment variables available in the Jenkinsfile are not propagated to Maven Konrad Windszus can you give more details? I've done some tests and seems to work. 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-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Alvaro Lobato commented on JENKINS-42484 Re: JAVA_TOOL_OPTIONS message displayed when using with maven I had a look at the changes made to fix JENKINS-42179 and you had it as arguments to the command line before using JAVA_TOOL_OPTIONS, did you try MAVEN_OPT? If not I can give it a shot. We could also try the new extension mechanism or the jvm.config but only for mvn +3.3, but we could fallback for old versions http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/ 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-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Alvaro Lobato commented on JENKINS-42484 Re: JAVA_TOOL_OPTIONS message displayed when using with maven Ok, I missed that original issue. Feel free to close this or leave it as a reminder. 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-42484) ToolOption message displayed when using with maven
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42484 ToolOption message displayed when using with maven Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/04 8:48 AM Priority: Minor Reporter: Alvaro Lobato ToolOption message displayed when using with maven, and it certain cases picked up as a Java doc warning: 08:38:00 - withMaven Wrapper script - 08:38:00 Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0cc64df6/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0cc64df6" 08:38:00 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) 08:39:44 [INFO] <<< maven-javadoc-plugin:2.10.1:javadoc (default) < generate-sources @ operations-center-client <<< 08:39:44 [INFO] 08:39:44 [INFO] --- maven-javadoc-plugin:2.10.1:javadoc (default) @ operations-center-client --- 08:39:47 [INFO] 08:39:47 2 warnings 08:39:47 [WARNING] Javadoc Warnings 08:39:47 [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0ba4a79a/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0ba4a79a" 08:39:47 [WARNING]
[JIRA] (JENKINS-42481) NPE when cancelling a on a withMaven step
Title: Message Title
Alvaro Lobato commented on JENKINS-42481
Re: NPE when cancelling a on a withMaven step
When canceled this error is always displayed:
[Pipeline] }
08:37:23 ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven2f9f6307/maven-spy-20170304-083657-567.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
Maybe a cancel should be detected and logs not processed. From global logs
Mar 04, 2017 8:38:55 AM WARNING org.jenkinsci.plugins.pipeline.maven.reporters.GeneratedArtifactsReporter listArtifacts
listArtifacts: Project MavenArtifact{com.cloudbees.operations-center.client:operations-center-client::2.32.0.4-SNAPSHOT}: no associated file found for MavenArtifact{com.cloudbees.operations-center.client:operations-center-client:hpi:2.32.0.4-SNAPSHOT} in "1.0" encoding="UTF-8"?>"operations-center-client" extension="hpi" groupId="com.cloudbees.operations-center.client" id="com.cloudbees.operations-center.client:operations-center-client:hpi:2.32.0.4-SNAPSHOT" type="hpi" version="2.32.0.4-SNAPSHOT">
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42481) NPE when cancelling a on a withMaven step
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42481 NPE when cancelling a on a withMaven step Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/04 12:43 AM Priority: Minor Reporter: Alvaro Lobato Version 2.0-beta-4 00:27:19 Running com.cloudbees.opscenter.client.plugin.BasicHeaderApiTokenAuthenticatorTest Resuming build at Sat Mar 04 00:28:05 UTC 2017 after Jenkins restart 00:27:35 Cannot contact 43d180aa: java.lang.InterruptedException Waiting to resume Unknown Pipeline node step: 43d180aa is offline Waiting to resume Unknown Pipeline node step: 43d180aa is offline Waiting to resume Unknown Pipeline node step: 43d180aa is offline Ready to run at Sat Mar 04 00:28:21 UTC 2017 Timeout set to expire in 11 hr Aborted by Alvaro Lobato 00:33:42 Sending interrupt signal to process Aborted by Alvaro Lobato 00:33:50 Sending interrupt signal to process 00:33:52 After 10s process did not stop [Pipeline] } 00:33:52 ERROR: [withMaven] WARNING Exception processing the logs generated by the Jenkins Maven Event Spy /home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven14b4a14e/maven-spy-20170304-002549-490.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org 00:33:52 java.lang.NullPointerException 00:33:52 at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:95) 00:33:52 at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$Callback.finished(WithMavenStepExecution.java:780) 00:33:52 at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onFailure(BodyExecutionCallback.java:124) 00:33:52 at
[JIRA] (JENKINS-42169) AsyncPeriodicWork listener logs don't get included on the support bundles
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42169 AsyncPeriodicWork listener logs don't get included on the support bundles Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 2017/Feb/18 4:14 PM Priority: Minor Reporter: Alvaro Lobato Previously AsyncPeriodicWork listener logs went to JENKINS_HOME and where included in other-logs folder, now that they are going to logs/tasks they don't come in the support bundle which makes it hard to diagnose some kinds of issues. https://github.com/jenkinsci/jenkins/commit/b8584f5047be33fe1477d55ea2a53edc4a3d7b2d Add Comment
[JIRA] (JENKINS-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-41978 NPE on Bouncy castle when the PEM cannot be read Change By: Alvaro Lobato Status: Resolved Closed 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-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato updated JENKINS-41978 Jenkins / JENKINS-41978 NPE on Bouncy castle when the PEM cannot be read Change By: Alvaro Lobato Status: In Review Resolved Resolution: Fixed 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-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato commented on JENKINS-41978 Re: NPE on Bouncy castle when the PEM cannot be read Cyrille Le Clerc yes that should be fixed, in any case this NPE shouldn't happend. Thanks for the report. 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-42013) Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Title: Message Title
Alvaro Lobato updated an issue
Jenkins / JENKINS-42013
Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Change By:
Alvaro Lobato
Attachment:
traceback (1).txt
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-42013) Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Title: Message Title
Alvaro Lobato updated an issue
Jenkins / JENKINS-42013
Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Change By:
Alvaro Lobato
If there is a blocked remote channel to an agent the /threadDump page won't be generated as it will block trying to get the threadDump from that agent.See attached stacktrace with an example.We should add a timeout to each remote operation we perform on the threadDump page or start printing the local results right away, so if a remote thread dump fails we still have the local one.This happened on 2.32Steps to reproduce:1. Somehow hang a remoting channel. In this case also was the backup plugin transferring data + maybe a connectivity issue.2. Wait some some time for the monitoring threads to launch again, the monitoring threads will be locked on the channel and they will should begin to multiply in a period equal to the check time
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42013) Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Title: Message Title
Alvaro Lobato created an issue
Jenkins / JENKINS-42013
Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2017/Feb/14 11:36 AM
Priority:
Minor
Reporter:
Alvaro Lobato
If there is a blocked remote channel to an agent the /threadDump page won't be generated as it will block trying to get the threadDump from that agent. See attached stacktrace with an example. We should add a timeout to each remote operation we perform on the threadDump page or start printing the local results right away, so if a remote thread dump fails we still have the local one. This happened on 2.32 Steps to reproduce: 1. Somehow hang a remoting channel. In this case also was the backup plugin transferring data + maybe a connectivity issue. 2. Wait some some time for the monitoring threads to launch again, the monitoring threads will be locked on the channel and they will begin to multiply in a period equal to the check time
Add Comment
[JIRA] (JENKINS-42012) ThreadDump generation blocked when an agent remote channel is blocked
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42012 ThreadDump generation blocked when an agent remote channel is blocked Issue Type: Bug Assignee: Steven Christou Attachments: traceback (1).txt Components: support-core-plugin Created: 2017/Feb/14 11:32 AM Priority: Major Reporter: Alvaro Lobato If there is a blocked remote channel to an agent the /threadDump page won't be generated as it will block trying to get the threadDump from that agent. See attached stacktrace with an example. We should add a timeout to each remote operation we perform on the threadDump page or start printing the local results right away, so if a remote thread dump fails we still have the local one. This happened on 2.32 Steps to reproduce: 1. Somehow hang a remoting channel. In this case also was the backup plugin transferring data + maybe a connectivity issue. 2. Take a support bundle. Add Comment
[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding Change By: Alvaro Lobato There are situations where a Jenkins instance is not responding properly and before restarting it we request a support bundle to have the maximum diagnosis information possible.ie. If there is a blocked remote channel to an agent the support bundle will not be generated, as it will block trying to get information from that agent, and the user will be forced to restart without a support bundle.See attached stacktrace with an example.We should add a timeout to each operation we perform on the support bundled to make sure we get at least some information when Jenkins is not responding.This happened on 2.32Steps to reproduce:1. Somehow hang a remoting channel ? . In this case it was a plugin transferring huge amounts of data + maybe some connectivity issues. 2. Take a support bundle. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding Issue Type: Bug Assignee: Steven Christou Attachments: traceback (1).txt Components: support-core-plugin Created: 2017/Feb/14 11:27 AM Priority: Major Reporter: Alvaro Lobato There are situations where a Jenkins instance is not responding properly and before restarting it we request a support bundle to have the maximum diagnosis information possible. ie. If there is a blocked remote channel to an agent the support bundle will not be generated, as it will block trying to get information from that agent, and the user will be forced to restart without a support bundle. See attached stacktrace with an example. We should add a timeout to each operation we perform on the support bundled to make sure we get at least some information when Jenkins is not responding. This happened on 2.32 Steps to reproduce: 1. Somehow hang a remoting channel? 2. Take a support bundle.
[JIRA] (JENKINS-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato updated JENKINS-41978 Jenkins / JENKINS-41978 NPE on Bouncy castle when the PEM cannot be read Change By: Alvaro Lobato Status: In Progress Review 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-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato started work on JENKINS-41978 Change By: Alvaro Lobato Status: Open In Progress 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-41978) NPE on Bouncy castle when the PEM cannot be read
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-41978 NPE on Bouncy castle when the PEM cannot be read Issue Type: Improvement Assignee: Alvaro Lobato Components: bouncycastle-api-plugin Created: 2017/Feb/13 12:18 PM Priority: Minor Reporter: Alvaro Lobato NPE on Bouncy castle when the PEM cannot be read BC-plugin 2.16.0 SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@2f47a11d failed java.lang.NullPointerException at jenkins.bouncycastle.api.PEMEncodable.decode(PEMEncodable.java:197) at jenkins.bouncycastle.api.PEMEncodable.decode(PEMEncodable.java:133) at hudson.plugins.ec2.EC2PrivateKey.getFingerprint(EC2PrivateKey.java:65) at hudson.plugins.ec2.EC2PrivateKey.find(EC2PrivateKey.java:96) at hudson.plugins.ec2.SlaveTemplate.getKeyPair(SlaveTemplate.java:863) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:450) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:377) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:530) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:547) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:307) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:60) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:796) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-39301) During test executions optional transitive plugin dependencies don't get correctly loaded
Title: Message Title Alvaro Lobato commented on JENKINS-39301 Re: During test executions optional transitive plugin dependencies don't get correctly loaded Jesse Glick if there is an issue already for that rewrite, I'm ok with closing this issue. 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Alvaro Lobato commented on JENKINS-41757 Re: BUILD_NOW_TEXT is not being applied when the job is parameterized PR created: https://github.com/jenkinsci/jenkins/pull/2735 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Alvaro Lobato started work on JENKINS-41757 Change By: Alvaro Lobato Status: Open In Progress 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-41757 BUILD_NOW_TEXT is not being applied when the job is parameterized Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Feb/06 12:05 PM Priority: Minor Reporter: Alvaro Lobato When a Job has parameters, the BUILD_NOW_TEXT is not being applied and the default text is being displayed. https://github.com/jenkinsci/jenkins/blob/2311ae8a5e7afd550b13909b4b1c4ae3338274dd/core/src/main/java/jenkins/model/ParameterizedJobMixIn.java#L281 Add Comment
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/09 11:47 AM Priority: Minor Reporter: Alvaro Lobato When you use SNAPSHOTs the transitive dependency versions of the plugins are not being checked correctly, indicating the the -SNAPSHOT version is older than the actual version, which in this case is the same resolved to timestamped snapshot version Dec 13, 2016 5:22:09 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin Operations Center Client Plugin v2.19.2.1-SNAPSHOT (private-e20a1be3-alobato) (operations-center-client) java.io.IOException: Operations Center Client Plugin v2.19.2.1-SNAPSHOT (private-e20a1be3-alobato) failed to load. - Operations Center Context v2.19.2.4-SNAPSHOT (private-6f16fea4-alobato) is older than required. To fix, install v2.19.2.4-20161201.084526-6 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621) at hudson.PluginManager$2$1$1.run(PluginManager.java:516) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1038) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
Alvaro Lobato commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
Does this work for you?
node('master') {
docker.image('maven').inside {
sh 'mvn -version'
}
}
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-40792) Pipeline Maven fails when configured to use settings.xml from config file provider
Title: Message Title Alvaro Lobato commented on JENKINS-40792 Re: Pipeline Maven fails when configured to use settings.xml from config file provider What version of config-file-provider do you have installed? 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-40712 Exception when using mavenSettingsConfig Change By: Alvaro Lobato Status: Open Closed Resolution: Fixed 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-39134) com.google.inject.CreationException after resuming build in script {} or withMaven {}
Title: Message Title
Alvaro Lobato updated JENKINS-39134
Jenkins / JENKINS-39134
com.google.inject.CreationException after resuming build in script {} or withMaven {}
Change By:
Alvaro Lobato
Status:
In Review Resolved
Resolution:
Fixed
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-40142) Snippet generator creates parameters even if they are left empty
Title: Message Title Alvaro Lobato started work on JENKINS-40142 Change By: Alvaro Lobato Status: Open In Progress 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-40142) Snippet generator creates parameters even if they are left empty
Title: Message Title
Alvaro Lobato created an issue
Jenkins / JENKINS-40142
Snippet generator creates parameters even if they are left empty
Issue Type:
Improvement
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2016/Dec/01 9:20 AM
Priority:
Minor
Reporter:
Alvaro Lobato
Snippet generator creates parameters even if they are left empty
withMaven( mavenSettingsFilePath = '', globalMavenSettingsFilePath = '', mavenLocalRepo = '' ){
}
Add Comment
[JIRA] (JENKINS-40142) Snippet generator creates parameters even if they are left empty
Title: Message Title
Alvaro Lobato updated an issue
Jenkins / JENKINS-40142
Snippet generator creates parameters even if they are left empty
Change By:
Alvaro Lobato
Snippet generator creates parameters even if they are left empty{code}withMaven( mavenSettingsFilePath = '', globalMavenSettingsFilePath = '', mavenLocalRepo = '' , mavenOpts = '' ){}{code}
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-39741) Setup wizard does not correctly handle authentication when checking connectivity
Title: Message Title Alvaro Lobato started work on JENKINS-39741 Change By: Alvaro Lobato Status: Open In Progress 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-39741) Setup wizard does not correctly handle authentication when checking connectivity
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-39741 Setup wizard does not correctly handle authentication when checking connectivity Change By: Alvaro Lobato Attachment: Screen Shot 2016-11-15 at 08.34.23.png 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-39741) Setup wizard does not correctly handle authentication when checking connectivity
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-39741 Setup wizard does not correctly handle authentication when checking connectivity Issue Type: Improvement Assignee: Alvaro Lobato Components: core Created: 2016/Nov/15 11:57 AM Priority: Minor Reporter: Alvaro Lobato The setup wizard is no checking authentication when checking updateCenter connectivity and the user can be presented with a white screen. The workaround is to go to /login and login. Add Comment This
[JIRA] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Alvaro Lobato assigned an issue to Alvaro Lobato Jenkins / JENKINS-34007 Jenkins 2.0 - wizard 'X' button Change By: Alvaro Lobato Assignee: Keith Zantow Alvaro Lobato 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-26057) Workflow build step for Maven
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-26057 Workflow build step for Maven Change By: Alvaro Lobato Status: In Progress Closed Resolution: Fixed 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-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Alvaro Lobato commented on JENKINS-38027 Re: withMaven disabled AnsiColorBuildWrapper Release 0.3 was created with a fix to this bug. 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-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Alvaro Lobato commented on JENKINS-38027 Re: withMaven disabled AnsiColorBuildWrapper Release 0.3 was created with a fix to this bug. 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-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-38027 withMaven disabled AnsiColorBuildWrapper Change By: Alvaro Lobato Comment: Release 0.3 was created with a fix to this bug. 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-38709) withMaven Disables Containing MaskPasswordsBuildWrapper
Title: Message Title Alvaro Lobato commented on JENKINS-38709 Re: withMaven Disables Containing MaskPasswordsBuildWrapper Release 0.3 was created with a fix to this bug. 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-38709) withMaven Disables Containing MaskPasswordsBuildWrapper
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-38709 withMaven Disables Containing MaskPasswordsBuildWrapper Change By: Alvaro Lobato Status: In Progress Closed Resolution: Fixed 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-39301) During test executions optional transitive plugin dependencies don't get correctly loaded
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-39301 During test executions optional transitive plugin dependencies don't get correctly loaded Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Oct/27 10:34 AM Priority: Minor Reporter: Alvaro Lobato When you are testing a plugin with Jenkins for test by using the Jenkins rule, if you have an optional transitive dependency and the Jenkins for test war already has that dependency but in an older version, it will fail to load the plugin: SEVERE: Failed Loading plugin Operations Center Context v2.19.0.2-SNAPSHOT (private-263c8f8a-alobato) (operations-center-context) java.io.IOException: Operations Center Context v2.19.0.2-SNAPSHOT (private-263c8f8a-alobato) failed to load. - Maven Integration plugin v2.7.1 is older than required. To fix, install v2.11 or later. - Matrix Project Plugin v1.4.1 is older than required. To fix, install v1.7.1 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621) at hudson.PluginManager$2$1$1.run(PluginManager.java:516) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1026) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Alvaro Lobato commented on JENKINS-38027 Re: withMaven disabled AnsiColorBuildWrapper Actually it was the other way round, sorry. There is a PR in review with a fix. 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-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Alvaro Lobato closed an issue as Duplicate This is a duplicate of JENKINS-38709 Jenkins / JENKINS-38027 withMaven disabled AnsiColorBuildWrapper Change By: Alvaro Lobato Status: Open Closed Resolution: Duplicate 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-38709) withMaven Disables Containing MaskPasswordsBuildWrapper
Title: Message Title Alvaro Lobato started work on JENKINS-38709 Change By: Alvaro Lobato Status: Open In Progress 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-38709) withMaven Disables Containing MaskPasswordsBuildWrapper
Title: Message Title Alvaro Lobato commented on JENKINS-38709 Re: withMaven Disables Containing MaskPasswordsBuildWrapper A PR with a fix has been submitted. 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-38078) Pipeline with Maven fail build parameters and profile
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-38078 Pipeline with Maven fail build parameters and profile Change By: Alvaro Lobato Component/s: pipeline-maven-plugin 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-38078) Pipeline with Maven fail build parameters and profile
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-38078 Pipeline with Maven fail build parameters and profile Change By: Alvaro Lobato Summary: Pipeline withMaven with Maven fail build parameters and profile 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-38078) Pipeline withMaven fail build parameters and profile
Title: Message Title Alvaro Lobato commented on JENKINS-38078 Re: Pipeline withMaven fail build parameters and profile David Beer You are not using withMaven on that snipped. I'm removing the component, as it is not related to withMaven. 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-38445) Pipeline withMaven Failed to serialize on agent
Title: Message Title Alvaro Lobato commented on JENKINS-38445 Re: Pipeline withMaven Failed to serialize on agent Are you sure this is related to withMaven?, see: https://issues.jenkins-ci.org/browse/JENKINS-38122 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-38395) Can't start Jenkins
Title: Message Title Alvaro Lobato commented on JENKINS-38395 Re: Can't start Jenkins Oleg Nenashev Yes it looks like a BC issue, but it may be related to Java 9. I've seen similar errors on Java 8 when putting the bc library on the JDK lib folder which should be done. Please try Java 8 and post the logs if the problem persists. 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-38395) Can't start Jenkins
Title: Message Title Alvaro Lobato edited a comment on JENKINS-38395 Re: Can't start Jenkins [~oleg_nenashev] Yes it looks like a BC issue, but it may be related to Java 9. I've seen similar errors on Java 8 when putting the bc library on the JDK lib folder which should be done. [~nitro2016] Please try Java 8 and post the logs if the problem persists. 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-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato stopped work on JENKINS-37317 Change By: Alvaro Lobato Status: In Progress Open 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-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-37317 Variant plugin not working when requiredClasses don't exist Change By: Alvaro Lobato Status: Open Closed Resolution: Fixed 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-38723) Stash failed with IOException during scalability testing
Title: Message Title
Alvaro Lobato created an issue
Jenkins / JENKINS-38723
Stash failed with IOException during scalability testing
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2016/Oct/05 8:22 AM
Priority:
Minor
Reporter:
Alvaro Lobato
During an scalability test, one of the executions failed on stash while executing this pipeline script in a high concurrency environment (15 nodes and 4 executors and a start queue of about 700 jobs)
def branch(name) {
return {
node {
sh "sleep 30 && head -c 52428800 /dev/urandom > ${name}.bin"
stash includes: "${name}.bin", name: "${name}"
}
}
}
stage "Thinking"
for (i = 0; i < 5; i++) {
sleep time: 250, unit: 'MILLISECONDS'
echo "Thinking $i"
}
stage "Working"
def branches = [:]
branches["b1"] = branch("b1")
branches["b2"] = branch("b2")
branches["b3"] = branch("b3")
parallel branches
stage "Resting"
for (i = 0; i < 5; i++) {
sleep time: 150, unit: 'MILLISECONDS'
echo "Resting $i"
}
This was the result of the execution:
Started
[Pipeline] stage (Thinking)
Entering stage Thinking
Proceeding
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 0
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 1
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 2
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 3
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 4
[Pipeline] stage (Working)
Entering stage Working
Proceeding
[Pipeline]
[JIRA] (JENKINS-37613) Unify naming convention for tool installation on withMaven step
Title: Message Title Alvaro Lobato updated JENKINS-37613 Released as 0.2 Jenkins / JENKINS-37613 Unify naming convention for tool installation on withMaven step Change By: Alvaro Lobato Status: In Review Closed Resolution: Fixed 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-37613) Unify naming convention for tool installation on withMaven step
Title: Message Title Alvaro Lobato updated JENKINS-37613 Jenkins / JENKINS-37613 Unify naming convention for tool installation on withMaven step Change By: Alvaro Lobato Status: In Progress Review 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-37613) Unify naming convention for tool installation on withMaven step
Title: Message Title Alvaro Lobato started work on JENKINS-37613 Change By: Alvaro Lobato Status: Open In Progress 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-37613) Unify naming convention for tool installation on withMaven step
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-37613 Unify naming convention for tool installation on withMaven step Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2016/Aug/23 7:16 AM Priority: Minor Reporter: Alvaro Lobato Currently we are using mavenInstallation and jdk to name two tool installation. There should be a single criteria for both of them. mavenInstallation should be renamed to just maven, also reducing verbosity. Add Comment
[JIRA] (JENKINS-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato commented on JENKINS-37317 Re: Variant plugin not working when requiredClasses don't exist Filed PR with a proposed fix https://github.com/jenkinsci/variant-plugin/pull/1 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-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato started work on JENKINS-37317 Change By: Alvaro Lobato Status: Open In Progress 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-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-37317 Variant plugin not working when requiredClasses don't exist Change By: Alvaro Lobato Summary: Variant plugin not workin working when requiredClasses don't exist 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-37317) Variant plugin not workin when requiredClasses don't exist
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-37317 Variant plugin not workin when requiredClasses don't exist Issue Type: Bug Assignee: Alvaro Lobato Components: other Created: 2016/Aug/10 5:08 PM Priority: Minor Reporter: Alvaro Lobato The Variant Plugin (https://github.com/jenkinsci/variant-plugin/) is not working properly when you specify `requiredClasses` and one of them do not exists. There are two observed situations. If the annotated class extends the non existent class this exception is thrown: WARNING: Failed to load org.jenkinsci.plugins.variant.Negative4 java.lang.InstantiationException: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/Beer at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230) at com.google.inject.spi.Elements.getElements(Elements.java:103) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:282) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at
[JIRA] (JENKINS-37255) hpi:run not honoring systemProperties jetty:port and hudson.udp
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-37255 hpi:run not honoring systemProperties jetty:port and hudson.udp Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Aug/08 9:34 AM Priority: Minor Reporter: Alvaro Lobato If you configure http and udp port by specifying the following configuration for the hpi plugin, the ports will not be honored if you set the same config by using -D it will work correctly. jetty.port 8083 hudson.udp 33852 Add Comment
[JIRA] (JENKINS-36908) "All" view not being created when there are already other views
Title: Message Title Alvaro Lobato started work on JENKINS-36908 Change By: Alvaro Lobato Status: Open In Progress 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-36908) "All" view not being created when there are already other views
Title: Message Title Alvaro Lobato assigned an issue to Alvaro Lobato Jenkins / JENKINS-36908 "All" view not being created when there are already other views Change By: Alvaro Lobato Assignee: Alvaro Lobato 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-36908) "All" view not being created when there are already other views
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-36908 "All" view not being created when there are already other views Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/25 7:32 AM Priority: Minor Reporter: Alvaro Lobato If there is already a view or a plugin creates one at start, the "All" views is not created and the first view will be the default one. This is the change that caused it: https://github.com/jenkinsci/jenkins/commit/a95ac5ea48366dada228c1f55acec1fa8018a071 Add Comment
[JIRA] (JENKINS-26462) Extract Maven builder to a separate plugin
Title: Message Title Alvaro Lobato commented on JENKINS-26462 Re: Extract Maven builder to a separate plugin Submitted changes with the extension point to allow MavenInstallation selection and created downstream PR-72 for Maven Plugin. 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-35489) Remove Bouncy Castle dependency from instance identity module
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-35489 Remove Bouncy Castle dependency from instance identity module Change By: Alvaro Lobato Status: In Progress Closed Resolution: Fixed 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-20187) TarArchiver.visit produces corrupt archive when file size changes during write
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-20187 TarArchiver.visit produces corrupt archive when file size changes during write Change By: Alvaro Lobato Status: In Progress Closed Resolution: Fixed 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Alvaro Lobato commented on JENKINS-36197 Re: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Francis, I've created PR-208 with the fix. Let me know if you find any problem. 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Alvaro Lobato commented on JENKINS-36197 Re: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Let me have a look, I'll tell you something shortly. 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Alvaro Lobato closed an issue as Not A Defect Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Alvaro Lobato Status: Open Closed Resolution: Not A Defect 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Alvaro Lobato commented on JENKINS-36197 Re: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Yes, it was for @Ryan, sorry. @Francis yes it can be fixed if raising the minimum core version. Right know EC2 plugin is depending on plugin version 1, just to support cores prior to 1.648, but if you raise the core version to 1.648, you can also depend on BC API 1.648 (actually 1.648.3) and no manual action will have to be taken. 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Alvaro Lobato commented on JENKINS-36197 Re: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Francis, which version of jenkins are you using?, for the error I suppose you are using >1.648, if this is the case, after updating EC2 plugin, you will have to update Bouncy Castle API plugin to a version >= than 1.648 which come with the API compatible with the included BC library in jenkins cores > 1.648. Let me know how it goes. More information here: Bouncy Castle API Plugin 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-35458) Adapt azure-slave-plugin to the new bouncycastle-api
Title: Message Title Alvaro Lobato commented on JENKINS-35458 Re: Adapt azure-slave-plugin to the new bouncycastle-api Created PR-29 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-35458) Adapt azure-slave-plugin to the new bouncycastle-api
Title: Message Title Alvaro Lobato started work on JENKINS-35458 Change By: Alvaro Lobato Status: Open In Progress 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-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Alvaro Lobato resolved as Fixed Jenkins / JENKINS-32120 With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Change By: Alvaro Lobato Status: In Progress Resolved Resolution: Fixed 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-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Alvaro Lobato commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Released ssh-agent-1.12 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-20187) TarArchiver.visit produces corrupt archive when file size changes during write
Title: Message Title Alvaro Lobato commented on JENKINS-20187 Re: TarArchiver.visit produces corrupt archive when file size changes during write Created PR-2419 with a proposed fix. 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-20187) TarArchiver.visit produces corrupt archive when file size changes during write
Title: Message Title Alvaro Lobato started work on JENKINS-20187 Change By: Alvaro Lobato Status: Open In Progress 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-20187) TarArchiver.visit produces corrupt archive when file size changes during write
Title: Message Title Alvaro Lobato assigned an issue to Alvaro Lobato Jenkins / JENKINS-20187 TarArchiver.visit produces corrupt archive when file size changes during write Change By: Alvaro Lobato Assignee: Alvaro Lobato 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-36035) Bouncycastle stacktrace at jenkins start after an upgrade
Title: Message Title Alvaro Lobato closed an issue as Fixed Released as 1.648.3 / 1.0.3 Jenkins / JENKINS-36035 Bouncycastle stacktrace at jenkins start after an upgrade Change By: Alvaro Lobato Status: In Progress Closed Resolution: Fixed 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-36035) Bouncycastle stacktrace at jenkins start after an upgrade
Title: Message Title
Alvaro Lobato created an issue
Jenkins / JENKINS-36035
Bouncycastle stacktrace at jenkins start after an upgrade
Issue Type:
Improvement
Assignee:
Alvaro Lobato
Components:
bouncycastle-api-plugin
Created:
2016/Jun/17 10:33 AM
Priority:
Major
Reporter:
Alvaro Lobato
In some occasions this exception appears in the jenkins logs during the start
INFO] java -Djava.security.egd=file:/dev/./urandom -Xdebug -Xrunjdwp:transport=dt_socket,suspend=n,server=y,address=127.0.0.1:8000 -XX:MaxPermSize=512m -Xms256m -Dhudson.DNSMultiCast.disabled=true -jar /Users/dvilladiego/.m2/repository/com/cloudbees/jenkins/main/jenkins-enterprise-war/1.651.3.1-beta-2/jenkins-enterprise-war-1.651.3.1-beta-2.war --httpPort=8080 --httpListenAddress=127.0.0.1
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Running from: /Users/dvilladiego/.m2/repository/com/cloudbees/jenkins/main/jenkins-enterprise-war/1.651.3.1-beta-2/jenkins-enterprise-war-1.651.3.1-beta-2.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
jun 16, 2016 3:58:07 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
jun 16, 2016 3:58:09 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-winstone-2.9
jun 16, 2016 3:58:11 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
jun 16, 2016 3:58:11 PM com.cloudbees.jenkins.ha.AbstractJenkinsSingleton contextInitialized
INFO: Jenkins home directory: /Users/dvilladiego/workspaces/test/CJE_1.651.3.1-beta-2/T3304/jenkins-home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
jun 16, 2016 3:58:11 PM com.cloudbees.jenkins.ha.singleton.HASingleton createChannel
INFO: Loading default
[JIRA] (JENKINS-36035) Bouncycastle stacktrace at jenkins start after an upgrade
Title: Message Title Alvaro Lobato started work on JENKINS-36035 Change By: Alvaro Lobato Status: Open In Progress 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-36035) Bouncycastle stacktrace at jenkins start after an upgrade
Title: Message Title Alvaro Lobato commented on JENKINS-36035 Re: Bouncycastle stacktrace at jenkins start after an upgrade Created PR-12 to solve the issue 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-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Alvaro Lobato commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" This means that the code for the fix has been submitted. It has to be reviewed and after that a released can be cut so you have it available on the Update Center. 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-35914) BouncyCastle Plugin when registering BC on an agent should re-throw the exceptions when checking the returned future
Title: Message Title Alvaro Lobato resolved as Fixed https://github.com/jenkinsci/bouncycastle-api-plugin/pull/10 Jenkins / JENKINS-35914 BouncyCastle Plugin when registering BC on an agent should re-throw the exceptions when checking the returned future Change By: Alvaro Lobato Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Alvaro Lobato commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" The problems are related with the Bouncy Castle version conflicts, the solution is to use Bouncy Castle API plugin to do all the Bouncy Castle related stuff. See Bouncy Castle API Plugin. Some of the problems are related with BC not being correctly registered on build agents, I've submitted a PR hopefully fixing those cases: PR-14 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.
