[JIRA] (JENKINS-36954) RobotFramework Plugin is not available in the "Add Post Build action"
Title: Message Title Aleksi Simell commented on JENKINS-36954 Re: RobotFramework Plugin is not available in the "Add Post Build action" phani kumar Which plugin version are you using? Is this still an issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173011.146953983.890.1579246560345%40Atlassian.JIRA.
[JIRA] (JENKINS-57187) Graphs issue with Robot Framework plugin version 1.6.5 in Jenkins ver. 2.164.2
Title: Message Title Aleksi Simell commented on JENKINS-57187 Re: Graphs issue with Robot Framework plugin version 1.6.5 in Jenkins ver. 2.164.2 Dmitry Smelansky Kamlesh Gupta Sorry for a long delay. Is the issue still relevant with version 2.0.1? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198940.1556206292000.887.1579240980196%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60009 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202826.1572566602000.880.1579240800465%40Atlassian.JIRA.
[JIRA] (JENKINS-50524) robotframework plugin throws exception on parsing output.xml
Title: Message Title Aleksi Simell closed an issue as Won't Fix Closing due to lack of input. Please re-open if still an issue. Jenkins / JENKINS-50524 robotframework plugin throws exception on parsing output.xml Change By: Aleksi Simell Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this
[JIRA] (JENKINS-35327) Robot Framework should show dates in the Test results Trend graph
Title: Message Title Aleksi Simell closed an issue as Done Jenkins / JENKINS-35327 Robot Framework should show dates in the Test results Trend graph Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171115.1464950761000.878.1579240740243%40Atlassian.JIRA.
[JIRA] (JENKINS-51026) REST API doesn't provide information on failed test-cases
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-51026 REST API doesn't provide information on failed test-cases Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190256.1524761236000.874.1579240680429%40Atlassian.JIRA.
[JIRA] (JENKINS-59241) Jenkins/Robot Plugin changes the build to Unstable when merged output xml file produced from Robot Framework Tests
Title: Message Title Aleksi Simell updated JENKINS-59241 Jenkins / JENKINS-59241 Jenkins/Robot Plugin changes the build to Unstable when merged output xml file produced from Robot Framework Tests Change By: Aleksi Simell Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201698.1567673166000.869.1579240620312%40Atlassian.JIRA.
[JIRA] (JENKINS-59288) Not able to connect to RobotFramework-SikuliLibrary
Title: Message Title Aleksi Simell updated JENKINS-59288 Jenkins / JENKINS-59288 Not able to connect to RobotFramework-SikuliLibrary Change By: Aleksi Simell Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201831.1568068192000.871.1579240620339%40Atlassian.JIRA.
[JIRA] (JENKINS-59884) Migrate documentation to GitHub
Title: Message Title Aleksi Simell updated JENKINS-59884 Jenkins / JENKINS-59884 Migrate documentation to GitHub Change By: Aleksi Simell Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202629.1571747058000.867.1579240560085%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder edited a comment on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Oh yes, Support Core Plugin was changed: https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66 or https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66#diff-79928e08589e1f90af352ccce49d8eb0L274-L275 https://github.com/jenkinsci/support-core-plugin/commit/4a3c12403766f8e28386df1d2bd9757e3ec2fae7 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.866.1579239960129%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Oh yes, Support Core Plugin was changed: https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66 or https://github.com/jenkinsci/support-core-plugin/compare/support-core-2.65...support-core-2.66#diff-79928e08589e1f90af352ccce49d8eb0L274-L275 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.864.1579239900128%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-60805
NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Change By:
Reinhold Füreder
First seen yesterday (and only once so far) after upgrading plugins:* cloudbees-jenkins-advisor:3.0.1 (from 3.0)* support-core:2.66 (from 2.65)A bit before there were other but IMHO potentially rather non-related plugin updates:* ant:1.11* cloudbees-folder:6.11* antisamy-markup-formatter:1.8* credentials:2.3.1* workflow-support:3.4* mailer:1.30* ssh-credentials:1.18.1* Office-365-Connector:4.12.2{noformat}2020-01-16 15:12:36.908+ [id=19]WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: it.components in /cloudbees-jenkins-advisor/. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.NoSuchMethodError: com.cloudbees.jenkins.support.SupportPlugin.getComponents()Lhudson/ExtensionList;at com.cloudbees.jenkins.plugins.advisor.AdvisorGlobalConfiguration.getComponents(AdvisorGlobalConfiguration.java:286)Caused: java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94)at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-60805 NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Issue Type: Bug Assignee: Emilio Escobar Components: cloudbees-jenkins-advisor-plugin, support-core-plugin Created: 2020-01-17 05:29 Environment: The latest and greatest ;-) E.g. Jenkins core 2.214 Priority: Minor Reporter: Reinhold Füreder First seen yesterday (and only once so far) after upgrading plugins: cloudbees-jenkins-advisor:3.0.1 (from 3.0) support-core:2.66 (from 2.65) A bit before there were other but IMHO potentially rather non-related plugin updates: ant:1.11 cloudbees-folder:6.11 antisamy-markup-formatter:1.8 credentials:2.3.1 workflow-support:3.4 mailer:1.30 ssh-credentials:1.18.1 Office-365-Connector:4.12.2
[JIRA] (JENKINS-60804) my first project
Title: Message Title raja Maddukuri created an issue Jenkins / JENKINS-60804 my first project Issue Type: Task Assignee: Anthony Dahanne Components: accelerated-build-now-plugin Created: 2020-01-17 05:09 Priority: Trivial Reporter: raja Maddukuri Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-52555) Declarative pipeline functions cannot access defined environment variables from environment block
Title: Message Title
Andrew Vaughan commented on JENKINS-52555
Re: Declarative pipeline functions cannot access defined environment variables from environment block
This sounds somewhat related to an issue i am seeing. Perhaps you can advise Andrew Bayer? I want to call some shell commands to set env vars based on other env vars, and when they are cross-referenced, they appear to get re-evaluated. Here is a basic example just using uuidgen - the use case is that the command setting SHARED_VALUE is not idempotent:
pipeline {
agent any
environment {
// SHARED_VALUE is re-evaluated each time it is referenced below
SHARED_VALUE = sh(returnStdout: true, script: """uuidgen""").trim()
TEST_ONE = sh(returnStdout: true, script: """echo '${SHARED_VALUE}' """).trim()
TEST_TWO = sh(returnStdout: true, script: """echo '${SHARED_VALUE}' """).trim()
TEST_THR = sh(returnStdout: true, script: """echo '${SHARED_VALUE}' """).trim()
}
stages {
stage('Test') {
steps {
echo "JUST TESTING"
// each of these are different UUIDs
sh '''
echo "_ONE_ = $TEST_ONE"
echo "TWO = $TEST_TWO"
echo "THR = $TEST_THR"
'''
}
}
}
}
Is this expected behaviour? i have not found a workaround, so have reverted to a bash script in the step instead.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Raihaan Shouhell commented on JENKINS-51316 Re: NullPointerException when clicking 'Generate Key' I think its reasonable. This is definitely much better. Users must already go into the AWS Console to get their security groups and misc settings set up. We should leave that bit to AWS. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.847.1579231260378%40Atlassian.JIRA.
[JIRA] (JENKINS-60657) EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Title: Message Title
Handi Gao updated an issue
Jenkins / JENKINS-60657
EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Change By:
Handi Gao
We have two templates for the ec2 plugin:{code:java}template1label: testinstance cap: 1{code}{code:java}template2label: reportinstance cap: 3{code} Jenkins doesn't create a new instance with template 2 when there are jobs in queue waiting for an available excutor on a running instance created with template 1, for example in our queue:1. test_job (waiting for _template1:test_ as all exectuors on _template1:test_ are taken and we only want 1 instance with _template1:test_)2. report_job (waiting for _template2:report_ as it does not exist)report_job will be blocked until test_job is scheduled as Jenkins keeps trying to schedule test_job and ignores the request of an instance with _template2_ from report_job Seems like this only happens when there are a lot jobs in the queue (I don't know a definite number.. but I don't experience this issue when there are only two jobs in the queue) And I believe the problem is from Jenkins core not the ec2 plugin as the NodeProvisioner doesn't not look for all the labels. Here is the log from hudson.slaves.NodeProvisioner class{code:java}Jan 16, 2020 9:38:08 PM FINER hudson.slaves.NodeProvisionerConsulting hudson.plugins.ec2.NoDelayProvisionerStrategy@1cfb55fa provisioning strategy with state StrategyState{label=null, snapshot=LoadStatisticsSnapshot{definedExecutors=6, _onlineExecutors_=6, connectingExecutors=0, busyExecutors=6, idleExecutors=0, availableExecutors=0, queueLength=127}, plannedCapacitySnapshot=0, additionalPlannedCapacity=0}Jan 16, 2020 9:38:09 PM FINER hudson.slaves.NodeProvisionerConsulting hudson.slaves.NodeProvisioner$StandardStrategyImpl@6a13a6e5 provisioning strategy with state StrategyState{label=null, snapshot=LoadStatisticsSnapshot{definedExecutors=6, _onlineExecutors_=6, connectingExecutors=0, busyExecutors=6, idleExecutors=0, availableExecutors=0, queueLength=127}, plannedCapacitySnapshot=0, additionalPlannedCapacity=0}Jan 16, 2020 9:38:09 PM FINE hudson.slaves.NodeProvisionerExcess workload 117.81 detected. (planned capacity=0,connecting capacity=0,Qlen=117.81,available=0&0,_online_=6,m=0.106)Jan 16, 2020 9:38:18 PM FINER hudson.slaves.NodeProvisionerConsulting hudson.plugins.ec2.NoDelayProvisionerStrategy@1cfb55fa provisioning strategy with state StrategyState{label=null, snapshot=LoadStatisticsSnapshot{definedExecutors=6, _onlineExecutors_=6, connectingExecutors=0, busyExecutors=6, idleExecutors=0, availableExecutors=0, queueLength=127}, plannedCapacitySnapshot=0, additionalPlannedCapacity=0}Jan 16, 2020 9:38:18 PM FINER hudson.slaves.NodeProvisionerConsulting hudson.slaves.NodeProvisioner$StandardStrategyImpl@6a13a6e5 provisioning strategy with state StrategyState{label=null, snapshot=LoadStatisticsSnapshot{definedExecutors=6, _onlineExecutors_=6, connectingExecutors=0, busyExecutors=6, idleExecutors=0, availableExecutors=0,
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ updated JENKINS-41591 Jenkins / JENKINS-41591 The Rebuild Last shortcut is missing for Pipeline jobs Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178408.1485858407000.822.1579227480854%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.818.1579226100254%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke closed an issue as Duplicate Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.814.1579225980768%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke updated JENKINS-60475 Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.810.1579225980699%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke updated JENKINS-60475 Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.806.1579225920444%40Atlassian.JIRA.
[JIRA] (JENKINS-5120) Support node-specific Perforce configuration
Title: Message Title Rob Petti closed an issue as Won't Do This ticket looks like it was made against the perforce-plugin before it was deprecated, and was erroneously moved to p4-plugin. Perforce-plugin is no longer being maintained and has been decommissioned. If you are having this issue with the p4-plugin, I recommend opening a new ticket with as much detail as possible so they can resolve the issue. Jenkins / JENKINS-5120 Support node-specific Perforce configuration Change By: Rob Petti Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick updated JENKINS-60694 Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: Jesse Glick Status: Fixed but Unreleased Resolved Released As: jenkins-test-harness 2.60 , plugin 3.56 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.791.1579222440242%40Atlassian.JIRA.
[JIRA] (JENKINS-33394) Generate support bundle before providing download
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-33394 Generate support bundle before providing download Change By: Allan BURDAJEWICZ Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168802.1457451818000.786.1579221540740%40Atlassian.JIRA.
[JIRA] (JENKINS-60803) Support custom status context messages
Title: Message Title Matt Nelson created an issue Jenkins / JENKINS-60803 Support custom status context messages Issue Type: New Feature Assignee: Steven Foster Components: github-scm-trait-notification-context-plugin Created: 2020-01-17 00:38 Priority: Minor Reporter: Matt Nelson The plugin[1] uses the default message[2]. I would like the option to dynamically set a custom message based on discovered during the build. Example of the default message This commit looks good Example custom messages. There are two customizations I would like to be able to add. The option to append the duration of the build. And an option to populate a build context variable that could be read by this plugin when creating the notification context. I am adding some short circuit logic to a pipeline to skip the build when the changeset doesn't match the when rule and would like to indicate that in the message. This commit looks good (44s) Build did not match when criteria (1s) [1] https://github.com/jenkinsci/github-scm-trait-notification-context-plugin/blob/1.1/src/main/java/org/jenkinsci/plugins/githubScmTraitNotificationContext/NotificationContextTrait.java#L106 [2] https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.8/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubNotificationContext.java#L183-L207
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke commented on JENKINS-60699 Re: Cannot add bitbucket server Hi Davis, Thanks for reporting this issue. We're aware of it, and it appears to be linked to the version of Jenkins (2.213), but it needs further investigation. As of right now, we're not aware of a workaround for this issue. We're looking into a fix and will keep this issue updated on our progress. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.764.1579220400269%40Atlassian.JIRA.
[JIRA] (JENKINS-5120) Support node-specific Perforce configuration
Title: Message Title Josh Clausen commented on JENKINS-5120 Re: Support node-specific Perforce configuration I have the same use case: multiple locations, each of which has its own p4 proxy (different IPs in every location). Right now, the plugin clobbers P4HOST and P4PORT, rather than first checking if there are any existing environment variables by those names. So, that would be my recommendation - use any already-set environment variables rather than clobbering those environment variables with whatever happens to be in the form for the credential. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135204.1261045204000.759.1579220340210%40Atlassian.JIRA.
[JIRA] (JENKINS-45794) Option to use "-I" (ignore p4ignore) on auto cleanup and sync
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-45794 Option to use "-I" (ignore p4ignore) on auto cleanup and sync Change By: Joel Brown Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184003.1501025177000.757.1579220100330%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick updated JENKINS-60694 Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: jenkins-test-harness 2.60 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.753.1579219620422%40Atlassian.JIRA.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title
Jesse Rittner commented on JENKINS-59971
Re: Unable to create folder credentials for plain-credentials-plugin
Thanks, but unfortunately that still gives those weird error messages I posted. Also, just FYI you should also set scope('GLOBAL') for your credentials. Otherwise, your config might be corrupted.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.751.1579219500246%40Atlassian.JIRA.
[JIRA] (JENKINS-60754) Jenkins test harness InjectedTest freezes on 8+ core machines
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-60754 Jenkins test harness InjectedTest freezes on 8+ core machines Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204013.1578980511000.747.1579219320602%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke started work on JENKINS-60642 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.742.1579218540829%40Atlassian.JIRA.
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-41591 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178408.1485858407000.724.1579216741359%40Atlassian.JIRA.
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-41591 The Rebuild Last shortcut is missing for Pipeline jobs Change By: Allan BURDAJEWICZ Assignee: ragesh_nair Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178408.1485858407000.710.1579216741160%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick started work on JENKINS-60694 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.704.1579214100429%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick updated JENKINS-60694 Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.706.1579214100456%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: Jesse Glick Assignee: James Nord Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.701.1579213920180%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title John Flynn resolved as Fixed Corrected in version 2.2.4 Jenkins / JENKINS-60780 support unlimited subfolder hierarchy Change By: John Flynn Status: Reopened Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/requests-plugin/blob/requests-2.2. 2 4 /CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title John Flynn commented on JENKINS-60780 Re: support unlimited subfolder hierarchy All requests should now be corrected in version 2.2.4. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204043.1579088195000.677.1579205040199%40Atlassian.JIRA.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title
Jason Swager edited a comment on JENKINS-59971
Re: Unable to create folder credentials for plain-credentials-plugin
[~rittneje] - perhaps this will help. Your original example helped me get much further; I couldn't have figured out the secret file stuff without your example.{code:java}properties { folderCredentialsProperty {domainCredentials { domainCredentials {domain { name('') description('')} }} }}configure { folder -> def configNode = folder / 'properties' / 'com.cloudbees.hudson.plugins.folder.properties.FolderCredentialsProvider_-FolderCredentialsProperty' / 'domainCredentialsMap' / 'entry' / 'java.util.concurrent.CopyOnWriteArrayList' configNode << 'org.jenkinsci.plugins.plaincredentials.impl.FileCredentialsImpl' {id('secret-file-id')description('secret file desc')fileName('test.txt')secretBytes(com.cloudbees.plugins.credentials.SecretBytes.fromBytes('''This is a multiline fileLine two finaly final line'''.getBytes()).toString()) }}{code}This example won't work with a binary file. If that was necessary, you could generate a BASE64 encode of the binary file, put that in place of the string and do a decodeBase64() on it to get the bytes.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title
Jason Swager commented on JENKINS-59971
Re: Unable to create folder credentials for plain-credentials-plugin
Jesse Rittner - perhaps this will help. Your original example helped me get much further; I couldn't have figured out the secret file stuff without your example.
properties {
folderCredentialsProperty {
domainCredentials {
domainCredentials {
domain {
name('')
description('')
}
}
}
}
}
configure { folder ->
def configNode = folder / 'properties' / 'com.cloudbees.hudson.plugins.folder.properties.FolderCredentialsProvider_-FolderCredentialsProperty' / 'domainCredentialsMap' / 'entry' / 'java.util.concurrent.CopyOnWriteArrayList'
configNode << 'org.jenkinsci.plugins.plaincredentials.impl.FileCredentialsImpl' {
id('secret-file-id')
description('secret file desc')
fileName('test.txt')
secretBytes(com.cloudbees.plugins.credentials.SecretBytes.fromBytes('''This is a multiline file
Line two
finaly line'''.getBytes()).toString())
}
}
This example won't work with a binary file. If that was necessary, you could generate a BASE64 encode of the binary file, put that in place of the string and do a decodeBase64() on it to get the bytes.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this
[JIRA] (JENKINS-53051) Check label consistency for the 'remember me' feature
Title: Message Title Elton Alves commented on JENKINS-53051 Re: Check label consistency for the 'remember me' feature Anyone could help me with this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193041.1534347954000.660.1579201260214%40Atlassian.JIRA.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Ramon Leon updated JENKINS-51316 Jenkins / JENKINS-51316 NullPointerException when clicking 'Generate Key' Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.652.1579200180813%40Atlassian.JIRA.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Ramon Leon commented on JENKINS-51316 Re: NullPointerException when clicking 'Generate Key' This would be the PR: https://github.com/jenkinsci/ec2-plugin/pull/426 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.650.1579200180746%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Ramon Leon commented on JENKINS-60678 Re: ComputerLauncher: Detection of AdoptOpenJDK 11 fails PR filed: https://github.com/jenkinsci/jenkins/pull/4434 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.642.1579199760134%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Ramon Leon updated JENKINS-60678 Jenkins / JENKINS-60678 ComputerLauncher: Detection of AdoptOpenJDK 11 fails Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.640.1579199700176%40Atlassian.JIRA.
[JIRA] (JENKINS-60802) JCasC EC2 Plugin private key not working
Title: Message Title Ard-Jan Barnas created an issue Jenkins / JENKINS-60802 JCasC EC2 Plugin private key not working Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, ec2-plugin Created: 2020-01-16 18:32 Priority: Critical Reporter: Ard-Jan Barnas The private key in configuration-as-code placed under referenceContent of EC2 cloud is successfully imported, however jobs fail to connect to EC2 slaves. Once the (SAME) private key is configured MANUALLY through the UI, it works fine. Steps to reproduce: Install Jenkins using Helm chart (codecentric) and configure private key in values.yaml for this chart. Run helm install Run a job that uses EC2 slave Job fails Manually import private key in Jenkins system config Run job again... success No
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-60678 ComputerLauncher: Detection of AdoptOpenJDK 11 fails Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.634.1579199160236%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Ramon Leon started work on JENKINS-60678 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.636.1579199160277%40Atlassian.JIRA.
[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.
Title: Message Title
Jakub Krysl updated an issue
Jenkins / JENKINS-60801
Variable changes are shared between matrix (parallel) stages.
Change By:
Jakub Krysl
New matrix step provides ability to run the same code in parallel cells. But if that code assigns ANY variable (not just env), it gets overwritten later by the next cell. This is huge deal, it basically prevents from assigning any variable withing in this kind of pipeline which makes it nearly useless.The condition is to set variable, have a piece of code that takes some time to execute and use the already set variable after. This can be simulated with sleep().I boiled down my code to easily reproduce it, here is the pipeline:{code:java}pipeline {parameters {booleanParam(name: 'RHEL5', defaultValue: true)booleanParam(name: 'RHEL6', defaultValue: true)booleanParam(name: 'RHEL7', defaultValue: true)}stages {stage('Matrix') {matrix {when {anyOf { _expression_ { params.RHEL5 && env.RHEL == '5' } _expression_ { params.RHEL6 && env.RHEL == '6' } _expression_ { params.RHEL7 && env.RHEL == '7' }}}axes {axis { name 'RHEL' values '5', '6', '7'}}stages {stage('Build single'){ steps { script { echo "RHEL version: " + env.RHEL myVar = "something.something.RHEL-${env.RHEL}" echo "myVar: " + myVar sleep(10) echo "AFTER RHEL version: " + env.RHEL echo "AFTER myVar: " + myVar } }}}}}}}{code}The result of this code: {code:java}RHEL version: 5myVar: something.something.RHEL-5Sleeping for 10 secRHEL version: 6myVar: something.something.RHEL-6Sleeping for 10 secRHEL version: 7myVar: something.something.RHEL-7Sleeping for 10 secNo need to sleep any longerRHEL version: 5myVar: something.something.RHEL-7No need to sleep any longerRHEL version: 6myVar: something.something.RHEL-7No need to sleep any longerRHEL version: 7myVar: something.something.RHEL-7{code}As you can see, myVar gets overwritten by the last run cell even for the other cells.
[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.
Title: Message Title
Jakub Krysl created an issue
Jenkins / JENKINS-60801
Variable changes are shared between matrix (parallel) stages.
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-01-16 18:05
Environment:
Jenkins ver. 2.190.2 Pipeline: API 2.83 Pipeline: Basic Steps 2.19 Pipeline: Declarative 1.5.0
Labels:
matrix pipeline
Priority:
Major
Reporter:
Jakub Krysl
New matrix step provides ability to run the same code in parallel cells. But if that code assigns ANY variable (not just env), it gets overwritten later by the next cell. This is huge deal, it basically prevents from assigning any variable withing this kind of pipeline which makes it nearly useless. The condition is to set variable, have a piece of code that takes some time to execute and use the already set variable after. This can be simulated with sleep(). I boiled down my code to easily reproduce it, here is the pipeline:
pipeline {
parameters {
booleanParam(name: 'RHEL5', defaultValue: true)
booleanParam(name: 'RHEL6', defaultValue: true)
booleanParam(name: 'RHEL7', defaultValue: true)
}
stages {
stage('Matrix') {
matrix {
when {
anyOf {
_expression_ { params.RHEL5 && env.RHEL == '5' }
_expression_ { params.RHEL6 && env.RHEL == '6' }
[JIRA] (JENKINS-60800) Support quiet output for azureUpload
Title: Message Title Mickey Kianovsky created an issue Jenkins / JENKINS-60800 Support quiet output for azureUpload Issue Type: New Feature Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2020-01-16 17:00 Priority: Major Reporter: Mickey Kianovsky When using azureUpload function, we get a lot of output for the files that are being uploaded. We upload huge amounts of files every build - this makes the output very large and even freezes the browser when opening "full log". Please add support for "quiet" output that will suppress this output. Thanks! // 17:42:27 MicrosoftAzureStorage - Container name: ContainerName 17:42:27 MicrosoftAzureStorage - share name: 17:42:27 MicrosoftAzureStorage - File path: 17:42:27 MicrosoftAzureStorage - Virtual path: 17:42:27 MicrosoftAzureStorage - Exclude path: 17:42:27 MicrosoftAzureStorage - Uploading files to Microsoft Azure17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/404.html in 00:00:00.108 (HH:mm:ss.S) 17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/500.html in 00:00:00.112 (HH:mm:ss.S) 17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/500_static.html in 00:00:00.113 (HH:mm:ss.S) 17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/admin.html in 00:00:00.105 (HH:mm:ss.S) 17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/api.zip in 00:00:00.106 (HH:mm:ss.S) 17:43:40 Uploaded to file storage with uri https://url_path.blob.core.windows.net/ContainerName/some_folder/auth.html in 00:00:00.111 (HH:mm:ss.S) 17:43:40 Uploaded to file storage
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke updated JENKINS-55202 released as 3.1.5 Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Raphael Pionke Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196272.154479528.625.1579193821278%40Atlassian.JIRA.
[JIRA] (JENKINS-60799) credentials-plugin:2.3.1 breaks Jenkins Docker image
Title: Message Title Sohail Mirza created an issue Jenkins / JENKINS-60799 credentials-plugin:2.3.1 breaks Jenkins Docker image Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-01-16 16:54 Environment: Jenkins LTS Docker image (2.214) Labels: dependencies Priority: Critical Reporter: Sohail Mirza Between credentials release 2.3.0 and 2.3.1, a dependency on configuration-as-code v1.35 was introduced. configuration-as-code:1.35 isn't included in the Jenkins LTS Docker image, and so this breaks deployments that are not explicitly specifying configuration-as-code:1.35 be installed. The version included with Jenkins LTS is 1.32. This is mainly an issue with Docker deployments since the plugins folder may not be on a persistent volume. In general it doesn't seem like a good practice to update dependencies in a patch release.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick updated JENKINS-57888 Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.616.1579193401089%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick started work on JENKINS-57888 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.610.1579193400940%40Atlassian.JIRA.
[JIRA] (TEST-197) TEST - 01 Automation
Title: Message Title Mamoudou Camara created an issue test / TEST-197 TEST - 01 Automation Issue Type: Task Assignee: Unassigned Components: foo Created: 2020-01-16 16:39 Labels: jenkins Priority: Minor Reporter: Mamoudou Camara Selenium with Java - Hydrid Framework Add Comment This
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title
João Salavessa created an issue
Jenkins / JENKINS-60798
Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2020-01-16 16:36
Environment:
Kubernetes 1.15.6 Kubernetes-plugin 1.23.0 Jenkins LTS 2.204.1
Priority:
Blocker
Reporter:
João Salavessa
In latest release (1.23.0) I'm getting the below error while trying to use the "Setup Kubernetes CLI (kubectl)" in a job where field "Certificate of authority" is empty and field "Credentials" is populated from type "Username and password": {{}}
[...]
Building in workspace /var/jenkins_home/workspace/backups
$ kubectl version
FATAL: Failed to run kubectl version 1
java.io.IOException: Failed to run kubectl version 1
at org.csanchez.jenkins.plugins.kubernetes.KubectlBuildWrapper.setUp(KubectlBuildWrapper.java:94)
at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146)
at hudson.model.Build$BuildExecution.doRun(Build.java:157)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1853)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)
Finished: FAILURE
The previous version (1.22.5) works fine and after downgrading all jobs started to work again. This happened in two independent Jenkins boxes running the
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Tiran Meltser created an issue Jenkins / JENKINS-60797 remote-file-plugin: enable selecting a fallback branch Issue Type: Improvement Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-01-16 16:28 Environment: Jenkins ver. 2.204.1 Remote File Plugin: 1.6 Labels: plugin configuration pipeline Priority: Major Reporter: Tiran Meltser The plugin is missing a very helpful ability - when working in Match Branches mode we have a problem with developers feature branches which are short lived and have unique names and thus can currently only be matched with the fallback branch - master. The requested enhancement would be to supply the ability to configure the fallback branch (e.g. in that case one can use a development branch), while having a default of the master branch. I think this small addition would benefit all those practicing a full cycle CI/CD process. I hope you will find this worth adding (we for sure will use it ASAP). 10x
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet assigned an issue to Louis-Rémi Paquet Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Louis-Rémi Paquet Assignee: Louis-Rémi Paquet Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.599.1579191600625%40Atlassian.JIRA.
[JIRA] (JENKINS-60715) Fleet plugin throws java.util.concurrent.CancellationException and overprovisions
Title: Message Title Alan Sparks commented on JENKINS-60715 Re: Fleet plugin throws java.util.concurrent.CancellationException and overprovisions Any comments on this? Have tried changing the timeout values for the init and SSH timeout, ,to no avail. We still frequently get, say, 2 instances launched when one job is queued to run. Is a significant resource waste. Please advise what else I can provide, logs or configuration, to help determine where the problem is. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203963.1578598441000.597.1579191540234%40Atlassian.JIRA.
[JIRA] (JENKINS-60715) Fleet plugin throws java.util.concurrent.CancellationException and overprovisions
Title: Message Title Alan Sparks updated an issue Jenkins / JENKINS-60715 Fleet plugin throws java.util.concurrent.CancellationException and overprovisions Change By: Alan Sparks Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203963.1578598441000.595.1579191420372%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Alexander Borsuk commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor This is a critical issue that makes parallel/matrix builds unusable. In my pipeline I need to build for Mac and Linux. Obviously, it can be done in parallel. There are two build nodes available (Linux and Mac). The bug reproduces when one build node waits until another build node finishes. And another one waits until the first one finishes. This is a deadlock. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142612.1325650778000.556.1579190041047%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Alexander Borsuk updated an issue Jenkins / JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Change By: Alexander Borsuk Issue Type: Improvement Bug Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142612.1325650778000.516.1579189804988%40Atlassian.JIRA.
[JIRA] (JENKINS-60796) ERROR: current transaction is aborted, commands ignored until end of transaction block
Title: Message Title
Dilip Mahadevappa updated an issue
Jenkins / JENKINS-60796
ERROR: current transaction is aborted, commands ignored until end of transaction block
Change By:
Dilip Mahadevappa
We have got 3 jobs configured to be triggered for the same project. When these jobs starts around the same time (with few ms difference) there is error from Gerrit plugin.*Job #1* {code:java} 2020-01-15 05:39:12.680 Triggered by Gerrit: https://gerrit.ericsson.se/67389792020-01-15 05:39:14.925 [EnvInject] - Loading node environment variables.{code}*Job #2*{code:java}2020-01-15 05:39:12.685 GMT-05:00 Triggered by Gerrit: https://gerrit.ericsson.se/67389792020-01-15 05:39:12.736 ERROR Gerrit response: Server Error{code}There is 5 ms difference between two jobs..Looks like this is happening due to concurrent [HTTP POST requests|https://github.com/sonyxperiadev/gerrit-events/blob/bfee4c4dfd1d6dd8a136ce8e349025e888f272c4/src/main/java/com/sonymobile/tools/gerrit/gerritevents/workers/rest/AbstractRestCommandJob2.java#L144] *Error at Gerrit Server side:*{code:java}[2020-01-15 05:39:12,733] [HTTP-13958483] ERROR com.google.gerrit.httpd.restapi.RestApiServlet : Error in POST /a/changes/gen2%2Fci-config~main~Ieb21ba65941b17e9d43cb82069f75c74b4bb636d/revisions/a7e7e5753887b44b63638e516b96b0b5b9d6aa60/reviewcom.google.gerrit.server.update.UpdateException: com.google.gwtorm.server.OrmException: fetch failure on patch_sets at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:798) at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:696) at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125) at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:670) at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57) at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78) at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:258) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) at com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:66) at com.google.gerrit.server.update.ReviewDbBatchUpdate.executeChangeOps(ReviewDbBatchUpdate.java:533) at com.google.gerrit.server.update.ReviewDbBatchUpdate.execute(ReviewDbBatchUpdate.java:299) at com.google.gerrit.server.update.ReviewDbBatchUpdate.execute(ReviewDbBatchUpdate.java:426) at com.google.gerrit.server.update.ReviewDbBatchUpdate.execute(ReviewDbBatchUpdate.java:421) at com.google.gerrit.server.change.PostReview.apply(PostReview.java:303) at com.google.gerrit.server.change.PostReview.apply(PostReview.java:183) at com.google.gerrit.server.change.PostReview.apply(PostReview.java:126) at
[JIRA] (JENKINS-60796) ERROR: current transaction is aborted, commands ignored until end of transaction block
Title: Message Title
Dilip Mahadevappa updated an issue
Jenkins / JENKINS-60796
ERROR: current transaction is aborted, commands ignored until end of transaction block
Change By:
Dilip Mahadevappa
We have got 3 jobs configured to be triggered for the same project. When these jobs starts around the same time (with few ms difference) there is error from Gerrit plugin. Ex *Job #1*2020-01-15 05 : 39:12.680 Triggered by Gerrit: https://gerrit.ericsson.se/6738979 2020-01-15 05:39:14.925 [EnvInject] - Loading node environment variables. {code }*Job #2*{code :java}2020-01-15 05:39:12.685 GMT-05:00 Triggered by Gerrit: https://gerrit.ericsson.se/67389792020-01-15 05:39:12.736 GMT-05:00 ERROR Gerrit response: Server Error{code} There is 5 ms difference between two jobs.. Looks like this is happening due to concurrent [HTTP POST requests|https://github.com/sonyxperiadev/gerrit-events/blob/bfee4c4dfd1d6dd8a136ce8e349025e888f272c4/src/main/java/com/sonymobile/tools/gerrit/gerritevents/workers/rest/AbstractRestCommandJob2.java#L144] * Error at Gerrit Server side: * {code:java}[2020-01-15 13 05 : 42 39 : 53 12 , 225 733 ] [HTTP- 14255808 13958483 ] ERROR com.google.gerrit.httpd.restapi.RestApiServlet : Error in POST /a/changes/gen2%2Fci-config~main~ Id9dd4c734f8f076158772f146dd904ef3f0e408b Ieb21ba65941b17e9d43cb82069f75c74b4bb636d /revisions/ a3e8ee8430931703189d8e13d2544fe715cbb03d a7e7e5753887b44b63638e516b96b0b5b9d6aa60 /reviewcom.google.gerrit.server.update.UpdateException: com.google.gwtorm.server.OrmException: fetch failure on patch_sets at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:798) at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:696) at com.google. gerrit common . server util . update concurrent . ReviewDbBatchUpdate TrustedListenableFutureTask $ ChangeTask TrustedFutureInterruptibleTask . call runInterruptibly ( ReviewDbBatchUpdate TrustedListenableFutureTask .java: 670 125 ) at com.google. common gerrit . util server . concurrent update . TrustedListenableFutureTask ReviewDbBatchUpdate $ TrustedFutureInterruptibleTask ChangeTask . runInterruptibly call ( TrustedListenableFutureTask ReviewDbBatchUpdate .java: 125 670 ) at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57) at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78) at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:258) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) at com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:66) at com.google.gerrit.server.update.ReviewDbBatchUpdate.executeChangeOps(ReviewDbBatchUpdate.java:533) at com.google.gerrit.server.update.ReviewDbBatchUpdate.execute(ReviewDbBatchUpdate.java:299) at
[JIRA] (JENKINS-60796) ERROR: current transaction is aborted, commands ignored until end of transaction block
Title: Message Title Dilip Mahadevappa created an issue Jenkins / JENKINS-60796 ERROR: current transaction is aborted, commands ignored until end of transaction block Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2020-01-16 15:30 Environment: Jenkins ver. 2.46.2 Gerrit trigger plugin: 2.27.5 Priority: Minor Reporter: Dilip Mahadevappa We have got 3 jobs configured to be triggered for the same project. When these jobs starts around the same time (with few ms difference) there is error from Gerrit plugin. Ex: 2020-01-15 05:39:12.685 GMT-05:00 Triggered by Gerrit: https://gerrit.ericsson.se/6738979 2020-01-15 05:39:12.736 GMT-05:00 ERROR Gerrit response: Server Error Looks like this is happening due to concurrent HTTP POST requests Error at Gerrit Server side: [2020-01-15 13:42:53,225] [HTTP-14255808] ERROR com.google.gerrit.httpd.restapi.RestApiServlet : Error in POST /a/changes/gen2%2Fci-config~main~Id9dd4c734f8f076158772f146dd904ef3f0e408b/revisions/a3e8ee8430931703189d8e13d2544fe715cbb03d/review com.google.gerrit.server.update.UpdateException: com.google.gwtorm.server.OrmException: fetch failure on patch_sets at com.google.gerrit.server.update.ReviewDbBatchUpdate$ChangeTask.call(ReviewDbBatchUpdate.java:798) at
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Francisco Fernández commented on JENKINS-51316 Re: NullPointerException when clicking 'Generate Key' I agree with Matt Sicker and Ramon Leon and my vote is for removing it. what's your thoughts here Raihaan Shouhell? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.497.1579188601453%40Atlassian.JIRA.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Matt Sicker commented on JENKINS-51316 Re: NullPointerException when clicking 'Generate Key' This feature sounds redundant, and if it's causing exceptions, I'd say go for removing it. FABRIZIO MANFREDI Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.490.1579188360281%40Atlassian.JIRA.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Ramon Leon commented on JENKINS-51316 Re: NullPointerException when clicking 'Generate Key' My proposal here is to remove this functionality because: It's not a must-have, you can get a key with a lot of tools, AWS console for example It may imply a security issue The implementation has some issues If you generate a private key and then you don't save the cloud, the private key keeps stored in AWS Key pairs without being used. The keys are generated with the name hudson-n, if you have several running instances you cannot control which one is used on each instance. The key is shown in the UI only once, before saving the form, you cannot see it anymore. And it's not advertised. It's not recommended to show the key in the UI, it's better to allow the user to download it once. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-60785) corrupt workspaces.txt file on agent, changes multibranch builds to use workspace directory with slash converted to %2F, causing errors
Title: Message Title Jeff Richards commented on JENKINS-60785 Re: corrupt workspaces.txt file on agent, changes multibranch builds to use workspace directory with slash converted to %2F, causing errors Yeah, from my perspective, I would have been totally satisfied if the node was just marked offline. The file is corrupt. There is a problem. The problem is rare (any defense against partial writing of a file in code is admirable, but going to be partial (what happens in case of power outages). So marking the node offline would avoid an unexpected workspace name, alert that the node needs attention and the confusion that that causes. Call in the humans and let them deal with it. Once I realized that my issue was related to a problem on a single node, it only took a few minutes to think to look at the log, which pointed me straight to the problem. And while I didn't know quite what to do to fix it, I think that would be handled by an FAQ/Troubleshooting entry on the web for people to find. Or better yet reference it in the log message that is displayed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204110.1579125476000.470.1579187340204%40Atlassian.JIRA.
[JIRA] (JENKINS-60257) Jenkins配置gitlab的API token时出现未知错误
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-60257 Jenkins配置gitlab的API token时出现未知错误 Change By: Mark Waite Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195977.1543547747000.468.1579186680978%40Atlassian.JIRA.
[JIRA] (JENKINS-60257) Jenkins配置gitlab的API token时出现未知错误
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60257 Jenkins配置gitlab的API token时出现未知错误 Change By: Mark Waite 配置gitlab的token时出错，导致无法构建项目。 Translated to English by Google Translate:An error occurred while configuring gitlab's token, which prevented the project from being built. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195977.1543547747000.465.1579186680917%40Atlassian.JIRA.
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Devin Nusbaum commented on JENKINS-59560 Re: NPE exception on pipeline checkout step (Pipeline multibranch) Artem Gryshyn I would like to add some automated tests before I merge the change, but I will try to get a release out with my fix in the next few weeks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202193.1569582707000.462.1579186620120%40Atlassian.JIRA.
[JIRA] (JENKINS-50907) customWorkspace setting of agent directive does not support EXECUTOR_NUMBER
Title: Message Title Avner Hartuv commented on JENKINS-50907 Re: customWorkspace setting of agent directive does not support EXECUTOR_NUMBER Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190037.1524217689000.458.1579185660646%40Atlassian.JIRA.
[JIRA] (JENKINS-52548) Bitbucket Authentication fails if using URI path Specification
Title: Message Title
SHIVAKUMAR B M commented on JENKINS-52548
Re: Bitbucket Authentication fails if using URI path Specification
Hi, I am facing issue in Notification plugin. Kindly support me. [Bitbucket] Notifying commit build result ERROR: Could not send notifications com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: . HttpResponseProxy{HTTP/1.1 401 [Date: Thu, 16 Jan 2020 12:57:10 GMT, Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips mod_auth_kerb/5.4, X-AREQUESTID: @11123MCx777x13015x0, X-ASEN: SEN-L14756884, Cache-Control: no-cache, no-transform, Vary: accept-encoding,x-auserid,cookie,x-ausername, WWW-Authenticate: OAuth realm="https%3A%2F%2Frb-bitbucket-test.bcds.bosch.com%2Fbitbucket", X-Content-Type-Options: nosniff, Content-Type: application/json;charset=UTF-8, Keep-Alive: timeout=5, max=100, Connection: Keep-Alive, Transfer-Encoding: chunked] org.apache.http.client.entity.DecompressingEntity@471ecae9}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192389.1531497965000.446.1579185600711%40Atlassian.JIRA.
[JIRA] (JENKINS-60789) Getting error while deploying via Deploy Weblogic Plugin
Title: Message Title Avinash Kumar commented on JENKINS-60789 Re: Getting error while deploying via Deploy Weblogic Plugin can someone please help with this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204117.1579167237000.444.1579185481040%40Atlassian.JIRA.
[JIRA] (JENKINS-50907) customWorkspace setting of agent directive does not support EXECUTOR_NUMBER
Title: Message Title Georgi Valkov commented on JENKINS-50907 Re: customWorkspace setting of agent directive does not support EXECUTOR_NUMBER You can set the hudson.slaves.WorkspaceList system property to the separator that you'd like to use. For more information: https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190037.1524217689000.440.1579185241540%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet commented on JENKINS-57888 Re: Custom log format broken by 2.177 Yes, that would be possible. I'm wondering, though, why the standard java behavior is overridden. It's not something one would expect. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.434.1579183740555%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Martin Karing commented on JENKINS-60678 Re: ComputerLauncher: Detection of AdoptOpenJDK 11 fails Ramon Leon: The issue appears when trying to start a windows slave that is supposed to run using the AdoptOpenJDK 11 version of java. When starting the slave the following messsage appears in the log: Couldn't figure out the Java version of java After that the slave does not launch. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.432.1579183140151%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title Christian Häussler reopened an issue I open the issue as long again... Jenkins / JENKINS-60780 support unlimited subfolder hierarchy Change By: Christian Häussler Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60794) Data Tables Plugins
Title: Message Title Ulli Hafner assigned an issue to Andreas Pabst Jenkins / JENKINS-60794 Data Tables Plugins Change By: Ulli Hafner Assignee: Ulli Hafner Andreas Pabst Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204122.1579179815000.425.1579181880199%40Atlassian.JIRA.
[JIRA] (JENKINS-60794) Data Tables Plugins
Title: Message Title Ulli Hafner commented on JENKINS-60794 Re: Data Tables Plugins Yes, please go ahead... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204122.1579179815000.427.1579181880241%40Atlassian.JIRA.
[JIRA] (JENKINS-60795) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title Damien Roche created an issue Jenkins / JENKINS-60795 Unable to provision slaves due to network interface and subnet ID both being set Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-01-16 13:08 Environment: Cloudbees-Core - MM v2.204.1.3 ec2-plugin v1.46.2 Priority: Major Reporter: Damien Roche Regression on https://issues.jenkins-ci.org/browse/JENKINS-59543 Provisioning of any Ec2 instance configured for cloud fails with com.amazonaws.services.ec2.model.AmazonEC2Exception: Network interfaces and an instance-level subnet ID may not be specified on the same request (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: ) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1712) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1367) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1113) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:770) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:744) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:726) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:686) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:668) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:532) at
[JIRA] (JENKINS-44411) Support throttling of blocks without node() in the throttle() step
Title: Message Title Joachim Hagege commented on JENKINS-44411 Re: Support throttling of blocks without node() in the throttle() step Hi, any update on support of declarative pipeline flows ? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182237.1495446957000.406.1579180200320%40Atlassian.JIRA.
[JIRA] (JENKINS-60794) Data Tables Plugins
Title: Message Title Andreas Pabst created an issue Jenkins / JENKINS-60794 Data Tables Plugins Issue Type: New Feature Assignee: Ulli Hafner Components: data-tables-api-plugin Created: 2020-01-16 13:03 Priority: Minor Reporter: Andreas Pabst DataTables provides different extensions, for example for reordering columns or making a table responsive. To use them, their JS- & CSS-Files have to be included and they have to be enabled in the configuration. I'd like to enhance this plugin to include a (optional) TableConfiguration in a TableModel, where such extensions of the configuration could be configured. I will file a PR for this, if that change is okay? Add Comment
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title John Flynn commented on JENKINS-60780 Re: support unlimited subfolder hierarchy Yes, that is correct. I will have that change released in version 2.2.4. Thank you for the reminder. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204043.1579088195000.397.1579179480126%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title Christian Häussler commented on JENKINS-60780 Re: support unlimited subfolder hierarchy John Flynn Your change was only made in DeleteJobRequest.java, not in RenameRequest.java. I suspect the issue is still available at rename. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204043.1579088195000.388.1579179180861%40Atlassian.JIRA.
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated JENKINS-60739 Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg Status: Reopened Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203993.1578734603000.385.1579179000254%40Atlassian.JIRA.
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated JENKINS-60739 Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203993.1578734603000.381.1579178941301%40Atlassian.JIRA.
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline)but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, it is still triggering the build.found some workaround, see linkIt is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426 , Can close this one Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated JENKINS-60739 Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203993.1578734603000.383.1579178941383%40Atlassian.JIRA.
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline)but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, it is still triggering the build.found some workaround, see [ link | It is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426 ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline)but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, it is still triggering the build.found some workaround, see [link| [ https:// stackoverflow issues . com jenkins-ci.org / questions browse / 33792633/using JENKINS - jenkins-job-dsl-to-set-polling-ignores-commits-in-certain-paths-for-git 44426 ] ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60739) Github hook and trigger created even if repo checkout configured "poll = false"
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60739 Github hook and trigger created even if repo checkout configured "poll = false" Change By: Avihay Tsayeg When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline)but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, it is still triggering the build. found some workaround, see [link|[https://stackoverflow.com/questions/33792633/using-jenkins-job-dsl-to-set-polling-ignores-commits-in-certain-paths-for-git]] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60738 Override github hook url is not being saved Change By: Avihay Tsayeg Trying to override the jenkins url at "override hook url" is failing. The adress is being not saved and the original jenkins url is showed instead.This happen manually at the ui. after further checking it is working using Jenkins configuration as code plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.371.1579178580181%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60738 Override github hook url is not being saved Change By: Avihay Tsayeg Trying to override the jenkins url at "override hook url" is failing. The adress is being not saved and the original jenkins url is showed instead.This happen manually at the ui and using the jenkins as configuration code plugin . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.367.1579178520640%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60738 Override github hook url is not being saved Change By: Avihay Tsayeg Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.369.1579178520965%40Atlassian.JIRA.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-51316 NullPointerException when clicking 'Generate Key' Change By: Ramon Leon Assignee: Francis Upton Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190653.1526359659000.355.1579177620749%40Atlassian.JIRA.
