[JIRA] (JENKINS-57808) FileNotFoundException Downloading x86 NodeJS packages
Title: Message Title Carlos Antonio created an issue Jenkins / JENKINS-57808 FileNotFoundException Downloading x86 NodeJS packages Issue Type: Bug Assignee: Nikolas Falco Attachments: image-2019-05-31-21-37-29-078.png Components: nodejs-plugin Created: 2019-06-01 01:41 Environment: Jenkins ver. 2.121.3 Linux jenkins-4-xmgl2 3.10.0-957.1.3.el7.x86_64 #1 x86_64 x86_64 x86_64 GNU/Linux Deployed in Openshift 3.11 Labels: jenkins plugin nodejs Priority: Minor Reporter: Carlos Antonio Hi, I'm reporting an issue that I'm facing when I run a Job and trying to download the NodeJS package using the Plugin from nodejs.org; after installed the NodeJS Plugin in Jenkins and set the version of nodeJS in Configuration tools; when I run the build in my Job, it's thrown an error reference to FileNotFoundException. where it's looking for the architecture of a package that doesn't exist in the nodejs.org host: node-v11.0.0-linux-x86.tar.gz java.io.FileNotFoundException: https://nodejs.org/dist/v11.0.0/node-v11.0.0-linux-x86.tar.gz at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890) at
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Ulli Hafner commented on JENKINS-57789 Re: Warning-ng plugin doesn't capture 'Hint' output from msBuild I wonder if it would make sense to write a new parser here, as the first part of such a log message actually can be totally ignored. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199737.1559308621000.17842.1559341620160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57807) Stapler JS proxy not correctly created for classes implementing StaplerProxy
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-57807
Stapler JS proxy not correctly created for classes implementing StaplerProxy
Change By:
Ulli Hafner
If a method of a Stapler model object *S* is annotated with {{@_javascript_Method}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object *P* of a different class then the invocation of the {{@_javascript_Method}} (that is now part of the class *P*) does not work anymore. In order to get this working again, one needs to add an additional empty method In with the same name in the class *S* that is also marked with {{@_javascript_Method}}.See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199758.155934133.17839.1559341440089%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57807) Stapler JS proxy not correctly created for classes implementing StaplerProxy
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-57807
Stapler JS proxy not correctly created for classes implementing StaplerProxy
Change By:
Ulli Hafner
If a method of a Stapler model object *S* is annotated with {{@_javascript_Method}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object *P* of a different class then the invocation of the {{@_javascript_Method}} (that is now part of the class *P*) does not work anymore. In order to get this working again, one needs to add an additional empty method with the same name in the class *S* that is also marked with {{@_javascript_Method}}.See [ChangeLog of warnings plugin 5.1.0 ]( | https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0 ) ] for details.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199758.155934133.17840.1559341440121%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57807) Stapler JS proxy not correctly created for classes implementing StaplerProxy
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-57807
Stapler JS proxy not correctly created for classes implementing StaplerProxy
Change By:
Ulli Hafner
If a method of a Stapler model object * * S* * is annotated with {{@_javascript_Method}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object * * P* * of a different class then the invocation of the {{@_javascript_Method}} (that is now part of the class * * P* * ) does not work anymore. In order to get this working again, one needs to add an additional empty method In the class * * S* * that is also marked with {{@_javascript_Method}}.See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199758.155934133.17838.1559341380161%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57807) Stapler JS proxy not correctly created for classes implementing StaplerProxy
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-31 22:22 Priority: Minor Reporter: Ulli Hafner If a method of a Stapler model object *S* is annotated with @_javascript_Method then code to access this method using an Ajax call is automatically generated. If the model object implement StaplerProxy and thus delegates all UI logic to a new object *P* of a different class then the invocation of the @_javascript_Method (that is now part of the class *P) does not work anymore. In order to get this working again, one needs to add an additional empty method In the class **S* that is also marked with @_javascript_Method. See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details. Add Comment
[JIRA] (JENKINS-57799) IndexOutOfBoundsException
Title: Message Title Ulli Hafner commented on JENKINS-57799 Re: IndexOutOfBoundsException Can you narrow down the part of the log that causes the exception? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199750.1559324204000.17836.1559337960102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum started work on JENKINS-57805 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.17834.1559336640224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Opened a PR against core to fix the symptoms, but I'm still not sure about the best way to fix the error on Pipeline's side. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.17833.1559336580040%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57806) Jenkins Checkpoints display order
Title: Message Title Steve Sanders created an issue Jenkins / JENKINS-57806 Jenkins Checkpoints display order Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-05-31 20:42 Environment: CloudBees Jenkins Enterprise 2.138.4.3-rolling Priority: Minor Reporter: Steve Sanders We use the workflow-cps-checkpoint plugin (https://release-notes.cloudbees.com/product/110) to handle groovy checkpoints so we can restart pipelines from failed stages. When i click on the checkpoints link of a failed build, it displays the checkpoints in a very random order. I'm wondering if we can display these in the order that was actually ran? Add Comment
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title
Steven Gardner edited a comment on JENKINS-52646
Re: KV v2 changes the API path to secrets & the response format
Latest build from master of the plugin caused my Jenkins builds to fail when the job tries logging in via AppRole to get the client token:{code:java}FATAL: could not log in into vaultcom.bettercloud.vault.VaultException: Vault responded with HTTP status code: 400 at com.bettercloud.vault.api.Auth.loginByAppRole(Auth.java:409) at com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential.getToken(VaultAppRoleCredential.java:50){code}Line 50 in VaultAppRoleCredential.java was updated to use the path string variable from the path field specified for the AppRole credentials instead being hardcoded as "approle", there seems to be a formatting error with the path string causing it to fail. Here's the change:[https://github.com/jenkinsci/hashicorp-vault-plugin/commit/c2c141cbf24b548c266a9134bd0f8df5a4800339]{code:java}-token = vault.auth().loginByAppRole("approle", roleId, Secret.toString(secretId)).getAuthClientToken();+token = vault.auth().loginByAppRole(path, roleId, Secret.toString(secretId)).getAuthClientToken(); {code}As a workaround I updated the file to format the path string:{code:java}public String getPath() {- return path;+ return String.format("%s", path);} {code}Jobs are now able to successfully login via AppRole and get the client token. Am able to pull secrets from both KV v1 and v2 engines. KV v2 no longer needs "data" in the path. Here's my personal repo with the changes:[https://github.com/stewcee/hashicorp-vault-plugin ] ] I'm not well-versed in Java and couldn't figure out the proper format for the string when the path field is null, so the path field cannot be null for the AppRole credentials.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title
Steven Gardner edited a comment on JENKINS-52646
Re: KV v2 changes the API path to secrets & the response format
Latest build from master of the plugin caused my Jenkins builds to fail when the job tries logging in via AppRole to get the client token:{code:java}FATAL: could not log in into vaultcom.bettercloud.vault.VaultException: Vault responded with HTTP status code: 400 at com.bettercloud.vault.api.Auth.loginByAppRole(Auth.java:409) at com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential.getToken(VaultAppRoleCredential.java:50){code}Line 50 in VaultAppRoleCredential.java was updated to use the path string variable from the path field specified for the AppRole credentials instead being hardcoded as "approle", there seems to be a formatting error with the path string causing it to fail. Here's the change:[https://github.com/jenkinsci/hashicorp-vault-plugin/commit/c2c141cbf24b548c266a9134bd0f8df5a4800339 ]{code:java}-token = vault.auth().loginByAppRole("approle", roleId, Secret.toString(secretId)).getAuthClientToken();+token = vault.auth().loginByAppRole(path, roleId, Secret.toString(secretId)).getAuthClientToken(); {code} [ |https://github.com/jenkinsci/hashicorp-vault-plugin/commit/c2c141cbf24b548c266a9134bd0f8df5a4800339] As a workaround I updated the file to format the path string:{code:java}public String getPath() {- return path;+ return String.format("%s", path);} {code}Jobs are now able to successfully login via AppRole and get the client token. Am able to pull secrets from both KV v1 and v2 engines. KV v2 no longer needs "data" in the path. Here's my personal repo with the changes:[https://github.com/stewcee/hashicorp-vault-plugin]I'm not well-versed in Java and couldn't figure out the proper format for the string when the path field is null, so the path field cannot be null for the AppRole credentials.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-57805 Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Issue Type: Bug Assignee: Devin Nusbaum Components: core, workflow-durable-task-step-plugin Created: 2019-05-31 20:38 Environment: workflow-durable-task-step 2.29+ Priority: Minor Reporter: Devin Nusbaum I have seen the following exception break Queue maintenance and make it impossible for new jobs to be scheduled: 2019-04-29 14:24:14.748+ [id=118] SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@7edb0f64 failed java.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:4454) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.bruteForceScanForEnclosingBlock(StandardGraphLookupView.java:150) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findEnclosingBlockStart(StandardGraphLookupView.java:197) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findAllEnclosingBlockStarts(StandardGraphLookupView.java:217) at org.jenkinsci.plugins.workflow.flow.FlowExecution.findAllEnclosingBlockStarts(FlowExecution.java:299) at org.jenkinsci.plugins.workflow.graph.FlowNode.getEnclosingBlocks(FlowNode.java:195) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.concatenateAllEnclosingLabels(ExecutorStepExecution.java:527) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getAffinityKey(ExecutorStepExecution.java:545) at
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title
Steven Gardner commented on JENKINS-52646
Re: KV v2 changes the API path to secrets & the response format
Latest build from master of the plugin caused my Jenkins builds to fail when the job tries logging in via AppRole to get the client token:
FATAL: could not log in into vault
com.bettercloud.vault.VaultException: Vault responded with HTTP status code: 400
at com.bettercloud.vault.api.Auth.loginByAppRole(Auth.java:409)
at com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential.getToken(VaultAppRoleCredential.java:50)
Line 50 in VaultAppRoleCredential.java was updated to use the path string variable from the path field specified for the AppRole credentials instead being hardcoded as "approle", there seems to be a formatting error with the path string causing it to fail. Here's the change: [https://github.com/jenkinsci/hashicorp-vault-plugin/commit/c2c141cbf24b548c266a9134bd0f8df5a4800339 ]
-token = vault.auth().loginByAppRole("approle", roleId, Secret.toString(secretId)).getAuthClientToken();
+token = vault.auth().loginByAppRole(path, roleId, Secret.toString(secretId)).getAuthClientToken();
[
https://github.com/jenkinsci/hashicorp-vault-plugin/commit/c2c141cbf24b548c266a9134bd0f8df5a4800339]As a workaround I updated the file to format the path string:
public String getPath() {
- return path;
+ return String.format("%s", path);
}
Jobs are now able to successfully login via AppRole and get the client token. Am able to pull secrets from both KV v1 and v2 engines. KV v2 no longer needs "data" in the path. Here's my personal repo with the changes: [https://github.com/stewcee/hashicorp-vault-plugin ]I'm not well-versed in Java and couldn't figure out the proper format for the string when the path field is null, so the path field cannot be null for the AppRole credentials.
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-57804
Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Change By:
mike cirioli
The page object that can be used to configure the {{JenkinsDatabaseSecurityRealm}} in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named " {{allowsSignup}} " but the pageobject references it using the name "{{allowSignup}}". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception.[This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution).|https://github.com/jenkinsci/jenkins/pull/3954/files#diff-aec8de1c6c772be0d3ecb3573c46ead8L29], which in turn caused some tests, which expected this to be enabled by default, to break.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-57804
Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Change By:
mike cirioli
The page object that can be used to configure the {{JenkinsDatabaseSecurityRealm}} in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named {{allowsSignup}} but the pageobject references it using the name " {{ allowSignup }} ". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception.[This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution).|https://github.com/jenkinsci/jenkins/pull/3954/files#diff-aec8de1c6c772be0d3ecb3573c46ead8L29], which in turn caused some tests, which expected this to be enabled by default, to break.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title mike cirioli created an issue Jenkins / JENKINS-57804 Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method Issue Type: Bug Assignee: mike cirioli Components: acceptance-test-harness Created: 2019-05-31 20:11 Priority: Minor Reporter: mike cirioli The page object that can be used to configure the JenkinsDatabaseSecurityRealm in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named allowsSignup but the pageobject references it using the name "allowSignup". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception. This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution)., which in turn caused some tests, which expected this to be enabled by default, to break. Add Comment
[JIRA] (JENKINS-57803) Add README to GitHub repository
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57803 Add README to GitHub repository Issue Type: Task Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-31 19:06 Labels: gsoc-2019 Priority: Major Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57785) Show only relevant credentials in the listbox
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57785 Show only relevant credentials in the listbox Change By: Parichay Barpanda Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199733.155929912.17790.1559329380062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57784) Add a `none` option when no credential is added to server configuration
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57784 Add a `none` option when no credential is added to server configuration Change By: Parichay Barpanda Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199732.1559298771000.17789.1559329320063%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57783) Make manage hooks independent of credentials
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57783 Make manage hooks independent of credentials Change By: Parichay Barpanda Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199731.155929854.17788.1559329260133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57802) Add support for GitLab API Plguin
Title: Message Title Parichay Barpanda started work on JENKINS-57802 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199753.1559328589000.17786.1559328660109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57802) Add support for GitLab API Plguin
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-57802 Add support for GitLab API Plguin Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199753.1559328589000.17787.1559328660134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57802) Add support for GitLab API Plguin
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57802 Add support for GitLab API Plguin Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-31 18:49 Labels: gsoc-2019 Priority: Major Reporter: Parichay Barpanda A GitLab API Plugin has been created that wraps a GitLab API for Java inside a plugin. GitLab Plugin depend on this plugin to abstract away the GitLab API functions from the plugin functionality. Add Comment
[JIRA] (JENKINS-57800) Convert Docker Plugin Bash Script to Java
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-57800 Convert Docker Plugin Bash Script to Java Change By: Natasha Stopa Labels: gsoc plugin-manager Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199751.1559326912000.17783.1559328180076%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57800) Convert Docker Plugin Bash Script to Java
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-57800 Convert Docker Plugin Bash Script to Java Change By: Natasha Stopa The start of the plugin manager will be created by convering the docker install-plugins.sh bash script ([https://github.com/jenkinsci/docker/blob/master/install-plugins.sh]) to a java Java implementation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199751.1559326912000.17784.1559328180117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57787) Bitbucket Plugin unable to parse Bitbucket webhook json
Title: Message Title kevin belter commented on JENKINS-57787 Re: Bitbucket Plugin unable to parse Bitbucket webhook json It's happening the same to me, i'm using a mac mini and this started to happen since yesterday :/ ''' net.sf.json.JSONException: JSONObject["username"] not found.net.sf.json.JSONException: JSONObject["username"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processWebhookPayload(BitbucketPayloadProcessor.java:46) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:28) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:27) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at com.cloudbees.jenkins.plugins.BitbucketCrumbExclusion.process(BitbucketCrumbExclusion.java:21) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:73) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:140) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:82) at
[JIRA] (JENKINS-50050) junit realtime plugin does not support test result sets
Title: Message Title Daniel Beland updated JENKINS-50050 My PR with the fix has been merged and is included in the latest release of the plugin. Jenkins / JENKINS-50050 junit realtime plugin does not support test result sets Change By: Daniel Beland Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189058.1520618366000.17773.1559327760278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50050) junit realtime plugin does not support test result sets
Title: Message Title Daniel Beland closed an issue as Fixed Jenkins / JENKINS-50050 junit realtime plugin does not support test result sets Change By: Daniel Beland Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189058.1520618366000.17774.1559327760290%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57801) Execution of the wrong post stage block
Title: Message Title
Daniel Beland created an issue
Jenkins / JENKINS-57801
Execution of the wrong post stage block
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2019-05-31-14-26-08-781.png
Components:
pipeline
Created:
2019-05-31 18:28
Priority:
Major
Reporter:
Daniel Beland
The declarative pipeline documentation on "post" says the following: "These condition blocks allow the execution of steps inside each condition depending on the completion status of the Pipeline or stage" Currently, the post execution of a stage seems to refer to the whole pipeline status at that point and not the completion status of the stage as documented. Given the following pipeline:
pipeline {
agent any
stages {
stage('First') {
steps { echo 'Hello' }
post { success { echo 'First stage is success' } }
}
stage('Second') {
steps { sh """ echo '" failures="0" name="test" skipped="0" tests="1" time="1">" file="file.txt" name="name" time="0.000">">' > test-results.xml """ }
post {
always { junit 'test-results.xml' }
unstable { echo 'Second stage is unstable' }
}
}
stage('Third') {
steps { echo 'Hello' }
post {
success { echo 'Third stage is success' }
unstable { echo 'Third stage is unstable! really???' }
}
}
}
post { unstable { echo 'Job is unstable' } }
}
I get the following output:
[JIRA] (JENKINS-57800) Convert Docker Plugin Bash Script to Java
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-57800 Convert Docker Plugin Bash Script to Java Issue Type: Task Assignee: Natasha Stopa Components: core, docker Created: 2019-05-31 18:21 Priority: Major Reporter: Natasha Stopa The start of the plugin manager will be created by convering the docker install-plugins.sh bash script (https://github.com/jenkinsci/docker/blob/master/install-plugins.sh) to a java implementation. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Connor Tumbleson commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found Took awhile to find this report. All webhooks now broken from Bitbucket due to this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17760.1559325900338%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57799) IndexOutOfBoundsException
Title: Message Title Jason MCDev created an issue Jenkins / JENKINS-57799 IndexOutOfBoundsException Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-31 17:36 Environment: Linux - Ubuntu Jenkins ver. 2.164.2 Warnings Next Generation Plugin 5.0.0 Priority: Blocker Reporter: Jason MCDev Given the following pipeline code: recordIssues aggregatingResults: true, enabledForFailure: true, minimumSeverity: 'HIGH', tools: [clangTidy(), clang(), gcc(), myPy(), pep8(), pyDocStyle()] I get this exception: Could not parse build causes edu.hm.hafner.analysis.ParsingException: Exception occurred during parsing IndexOutOfBoundsException: Index: 0, Size: 0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:657) at java.util.ArrayList.get(ArrayList.java:433) at se.bjurr.violations.lib.parsers.PyDocStyleParser.parseReportOutput(PyDocStyleParser.java:26) at edu.hm.hafner.analysis.parser.violations.AbstractViolationAdapter.parse(AbstractViolationAdapter.java:33) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInConsoleLog(ReportScanningTool.java:173) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:122) at
[JIRA] (JENKINS-57798) PagerDuty Plugin - NullPointerException if you update after a failure
Title: Message Title Curtis Foon updated an issue Jenkins / JENKINS-57798 PagerDuty Plugin - NullPointerException if you update after a failure Change By: Curtis Foon Summary: PagerDuty Plugin - NullPointerException if you update after a failure Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199749.1559322964000.17753.1559323500175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57798) NullPointerException if you update after a failure
Title: Message Title Daniel Richardson commented on JENKINS-57798 Re: NullPointerException if you update after a failure plugin version: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199749.1559322964000.17750.1559323080087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57798) NullPointerException if you update after a failure
Title: Message Title Daniel Richardson created an issue Jenkins / JENKINS-57798 NullPointerException if you update after a failure Issue Type: Bug Assignee: Alexander Leibzon Components: pagerduty-plugin Created: 2019-05-31 17:16 Environment: jenkins 2.150 Priority: Minor Reporter: Daniel Richardson configure job with pagerduty plugin with no incident key fail the job edit the job setting incident key to empty string fix the job job fails due to NPR. proposed pull request is https://github.com/jenkinsci/pagerduty-plugin/pull/6 Add Comment
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title bala k commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found Same problem in our installation as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17740.1559322720157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title eugene riabchuk commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found The same problem occurred in our organization Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17733.1559321640192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky updated JENKINS-38819 Jenkins / JENKINS-38819 Build history not visible for user who copied jobs Change By: Ilya Dobrovolsky Status: Open Fixed but Unreleased Assignee: max lehmann Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17728.1559320620402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title Radek Antoniuk commented on JENKINS-53780 Re: jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Can you check if this still occurs with the current plugin version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194290.1537948123000.17726.1559320440073%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=198519 Jenkins / JENKINS-56577 Unable to add Jira Site Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198192.1552639896000.17724.1559320320412%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=198519 Jenkins / JENKINS-56677 Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198314.1553248627000.17722.1559320320304%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. Jenkins / JENKINS-56857 Unable to validate JIRA site Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198519.1554240962000.17720.1559320260448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky edited a comment on JENKINS-38819 Re: Build history not visible for user who copied jobs Hello all.I had the same issue. I was quite confused, because I haven't noticed, when time it was "broken".In fact it is not a bug. Please pay attention to the plus sign near "trend" at the screenshot:!Screen Shot 2016-10-07 at 14.38.12.png|thumbnail!If you click on it, then you will see the build log. For ex:!image-2019-05-31-18-25-45-979.png! !image-2019-05-31-18-27-08-792.png!So one can show build history by pressing plus sign or hide it by pressing minus sign. Best Regards,Ilya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17718.1559320260415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky edited a comment on JENKINS-38819 Re: Build history not visible for user who copied jobs Hello all.I had the same issue. I was quite confused, because I haven't noticed, when time it was "broken".In fact it is not a bug. Please pay attention to the plus sign near "trend" at the screenshot:!Screen Shot 2016-10-07 at 14.38.12.png|thumbnail!If you click on it, then you will see the build log. For ex:!image-2019-05-31-18-25-45-979.png! !image-2019-05-31-18-27-08-792.png! So one can show build history by pressing plus sign or hide it by pressing minus sign. Best Regards,Ilya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17710.1559320200204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57797) Validate and/or fix support for CasC on ssh-slaves plugin
Title: Message Title Adrien Lecharpentier updated JENKINS-57797 Jenkins / JENKINS-57797 Validate and/or fix support for CasC on ssh-slaves plugin Change By: Adrien Lecharpentier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199747.155931868.17708.1559320080187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57797) Validate and/or fix support for CasC on ssh-slaves plugin
Title: Message Title Adrien Lecharpentier commented on JENKINS-57797 Re: Validate and/or fix support for CasC on ssh-slaves plugin I opened the PR-126 to track this work. We could validate all fields from the SSHLaucher but with the 3 already included in the PR, we have no problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199747.155931868.17706.1559320080162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky edited a comment on JENKINS-38819 Re: Build history not visible for user who copied jobs Hello all.I had the same issue. I was quite confused, because I haven't noticed, when time it was "broken".In fact it is not a bug. Please pay attention to the plus sign near trends "trend" at the screenshot:!Screen Shot 2016-10-07 at 14.38.12.png|thumbnail!If you click on it, then you will see the build log. For ex:!image-2019-05-31-18-25-45-979.png! Best Regards,Ilya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17701.1559320020160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky commented on JENKINS-38819 Re: Build history not visible for user who copied jobs Hello all. I had the same issue. I was quite confused, because I haven't noticed, when time it was "broken". In fact it is not a bug. Please pay attention to the plus sign near trends at the screenshot: If you click on it, then you will see the build log. For ex: Best Regards, Ilya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17696.1559319960460%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Ilya Dobrovolsky updated an issue Jenkins / JENKINS-38819 Build history not visible for user who copied jobs Change By: Ilya Dobrovolsky Attachment: image-2019-05-31-18-25-45-979.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175223.1475847671000.17694.1559319960395%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Labels: build jenkins jira plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17688.1559319840758%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk stopped work on JENKINS-54486 Change By: Radek Antoniuk Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17681.1559319840629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk assigned an issue to Unassigned Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17685.1559319840703%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57797) Validate and/or fix support for CasC on ssh-slaves plugin
Title: Message Title Adrien Lecharpentier started work on JENKINS-57797 Change By: Adrien Lecharpentier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199747.155931868.17677.1559319300112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa commented on JENKINS-57672 Re: Determine Dependencies between PluginManager.java on Jenkins Core Jon Brohauge, I'd definitely like to do something that would be most beneficial to the Jenkins community, but I get kind of overwhelmed when I look at this and I'm not even really sure how to start. I'd still be open to going that route, but I'd probably need a lot of active help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.17675.1559319060176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57797) Validate and/or fix support for CasC on ssh-slaves plugin
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-57797 Validate and/or fix support for CasC on ssh-slaves plugin Issue Type: Improvement Assignee: Adrien Lecharpentier Components: ssh-slaves-plugin Created: 2019-05-31 16:04 Priority: Trivial Reporter: Adrien Lecharpentier Add the required code in ssh-slaves plugin to validate the support for configuration-as-code (test) and fix the plugin if any incompatibility is shown. Add Comment This message was sent by
[JIRA] (JENKINS-56683) Declarative Pipeline: set the build result when tests fail without a script block
Title: Message Title Jakub Bochenski resolved as Duplicate That's great. I think we can resolve this issue now Jenkins / JENKINS-56683 Declarative Pipeline: set the build result when tests fail without a script block Change By: Jakub Bochenski Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198320.1553265541000.17669.1559318040323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk commented on JENKINS-54486 Re: Not created JIRA issue after build failed I don't think so as here we don't have any NPE. Interestingly the reporter mentions two plugins for JIRA, one is the open source one (v. 3.0.5) and the other one is (I'm assuming) the Marvellution plugin. So as a first shot, I'd propose disabling one of the plugins, configuring the other one and checking if you get the correct results as they might interfere with each other. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17666.1559317800176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Mark Haskins created an issue Jenkins / JENKINS-57796 Checkmarx affected by JEP-200 Issue Type: Bug Assignee: Sergey Kadaner Attachments: Jenkins.txt Components: checkmarx-plugin Created: 2019-05-31 15:44 Environment: OS : Centos Linux 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Java openjdk version "1.8.0_212" OpenJDK Runtime Environment (build 1.8.0_212-b04) OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode) More information in attached file Labels: JEP-200 Priority: Major Reporter: Mark Haskins CheckMarx stopped working this afternoon. It had been working in the morning. Some Plugins where updated during this time period by CheckMarx (8.90.1) was not. step([$class: 'CxScanBuilder', avoidDuplicateProjectScans: false, comment : "Pipeline Scan", credentialsId : 'checkmarx', excludeFolders: '', exclusionsSetting : 'global', failBuildOnNewResults : true, failBuildOnNewSeverity: 'HIGH', fullScanCycle : 10,
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title John James commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found Hi we are having the same problem that has affected a number of our Jenkins installs we are running behind nginx proxy with the error net.sf.json.JSONException: JSONObject["username"] not found. My workaround that I am currently trying to do is to hardcode a username in the plugin source and rebuild the plugin just so we can get builds working again Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17655.1559317080148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57781) Add support for generating personal access token via username/password credentials like GitHub Plugin
Title: Message Title Parichay Barpanda resolved as Fixed This has been fixed by adding a `GitLabPersonalAccessTokenCreator` class. Allows adding personal access token credential, either by username/password credentials stored in Jenkins or username/password form at runtime. Jenkins / JENKINS-57781 Add support for generating personal access token via username/password credentials like GitHub Plugin Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199729.1559298031000.17653.1559316240080%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-57795
Orphaned EC2 instances after Jenkins restart
Change By:
Jakub Bochenski
Sometimes after a Jenkins restart the plugin won't be able to spawn more agents.The plugin will just loop on this:{code}SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Attempting to provision slave needed by excess workload of 1 unitsMay 31, 2019 2:23:53 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Cannot provision - no capacity for instances: 0May 31, 2019 2:23:53 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}{code}If I go to the EC2 console and terminate the instance manually the plugin will spawn a new one and use it.It seems like there is some mismatch in the plugin logic. The part responsible for calculating the number of instances and checking the cap sees the EC2 instance. However the part responsible for picking up running EC2 instances doesn't seem to be able to find it.We use a single subnet, security group and vpc (I've seen some reports about this causing problems).It seems the problems do not occur when I do a ` {{ /safeRestart ` }} but they do if I use e.g. "restart Jenkins when no jobs are running" form the Update Center. We use instanceCap = 1 setting as we are testing the plugin, this might make this problem more visible than with a higher cap.
Add Comment
This message was
[JIRA] (JENKINS-54697) How to use 'p4 print' with P4Groovy?
Title: Message Title andre sreih updated an issue Jenkins / JENKINS-54697 How to use 'p4 print' with P4Groovy? Change By: andre sreih Comment: Hello,Is there any updates on this matter ? how can we resolve this issue ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195495.1542629343000.17650.1559315160362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54697) How to use 'p4 print' with P4Groovy?
Title: Message Title andre sreih updated an issue Jenkins / JENKINS-54697 How to use 'p4 print' with P4Groovy? Change By: andre sreih Comment: Hello,Putting the second argument as an array fixed the problem (-q and your path to the file) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195495.1542629343000.17647.1559315160235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-57795
Orphaned EC2 instances after Jenkins restart
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-05-31 15:04
Priority:
Critical
Reporter:
Jakub Bochenski
Sometimes after a Jenkins restart the plugin won't be able to spawn more agents. The plugin will just loop on this:
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Attempting to provision slave needed by excess workload of 1 units
May 31, 2019 2:23:53 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Cannot provision - no capacity for instances: 0
May 31, 2019 2:23:53 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}
If I go to the EC2 console and terminate the instance manually the plugin will spawn a new one and use it. It seems like there is some mismatch in the plugin logic. The part responsible for calculating the number of instances and checking the cap sees the EC2 instance. However the part responsible for picking up running EC2 instances doesn't seem to be able to find it. We use a single subnet, security group and vpc (I've seen some reports about this causing problems). It seems the problems do not occur when I do a `/safeRestart` but they do if I use e.g. "restart Jenkins when no jobs are running" form the Update Center. We use instanceCap = 1 setting as we are testing the plugin, this might make this problem more visible than with a higher cap.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Mario Nantes commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found I have the same problem, do you have any outline solution? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17641.1559315100259%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56683) Declarative Pipeline: set the build result when tests fail without a script block
Title: Message Title
Devin Nusbaum commented on JENKINS-56683
Re: Declarative Pipeline: set the build result when tests fail without a script block
Jakub Bochenski From a quick glance, you should be able to use warnError, which we added specifically so it could be used in Declarative without a script block: Change this code:
script {
try {
echo 'Running tests...'
sh 'exit 1'
}
catch (exc) {
echo 'Testing failed!'
currentBuild.result = 'UNSTABLE'
}
}
to this:
warnError('Testing Failed!') {
echo 'Running tests...'
sh 'exit 1'
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198320.1553265541000.17637.1559314920240%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53179) Direct link to tests page in Blue Ocean
Title: Message Title
Victor Martinez edited a comment on JENKINS-53179
Re: Direct link to tests page in Blue Ocean
I've just created [https://github.com/jenkinsci/blueocean-display-url-plugin/pull/22] which provides two more env variables: * {{RUN_ARTIFACTS_DISPLAY_URL}} * {{RUN_TESTS_DISPLAY_URL}} {{}}{{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193200.1534904839000.17629.1559314860698%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53179) Direct link to tests page in Blue Ocean
Title: Message Title
Victor Martinez commented on JENKINS-53179
Re: Direct link to tests page in Blue Ocean
I've just created https://github.com/jenkinsci/blueocean-display-url-plugin/pull/22 which provides two more env variables:
RUN_ARTIFACTS_DISPLAY_URL
RUN_TESTS_DISPLAY_URL
{{}} {{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193200.1534904839000.17621.1559314860542%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Alex Mace commented on JENKINS-57789 Re: Warning-ng plugin doesn't capture 'Hint' output from msBuild Attached example file with the two problem lines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199737.1559308621000.17618.1559314800230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Alex Mace updated an issue Jenkins / JENKINS-57789 Warning-ng plugin doesn't capture 'Hint' output from msBuild Change By: Alex Mace Attachment: issue57789.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199737.1559308621000.17614.1559314740285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56683) Declarative Pipeline: set the build result when tests fail without a script block
Title: Message Title Jakub Bochenski commented on JENKINS-56683 Re: Declarative Pipeline: set the build result when tests fail without a script block Devin Nusbaum does the new `unstable` step solve this? I think it still requires a `script` block, right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198320.1553265541000.17612.1559314680125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title
Martin Moore updated an issue
Jenkins / JENKINS-57789
Warning-ng plugin doesn't capture 'Hint' output from msBuild
Change By:
Martin Moore
When building Delphi projects with msBuild, the output can include Warnings and Hints. Currently Hints are ignored. It would be very useful if they were included and any increase in the number of hints treated as a fail in qualityGate.Additionally the parser misidentifies the affected files. Sample console log:{code:java}Embarcadero Delphi for Win32 compiler version 21.0 Copyright (c) 1983,2009 Embarcadero Technologies, Inc.C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never usedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands 269261 lines, 2.61 seconds, 2496188 bytes code, 595788 bytes data. Done building target "CoreCompile" in project "POSManagerTests.dproj".Done building project "POSManagerTests.dproj".Build succeeded. C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands 3 Warning(s) 0 Error(s){code}warnings-ng reports the affected file being C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets, rather than C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas I suspect it would report the hint correctly, but the ignores it entirely (I imagine because the parser isn't looking for "hints" in the output of msbuild. Example line with hint{code:java}C:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never used{code} I suspect it would report the hint correctly, but the ignores it entirely (I imagine because the parser isn't looking for "hints" in the output of msbuild.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Martin Moore commented on JENKINS-57789 Re: Warning-ng plugin doesn't capture 'Hint' output from msBuild Thanks, line added above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199737.1559308621000.17607.1559314440234%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title
Martin Moore updated an issue
Jenkins / JENKINS-57789
Warning-ng plugin doesn't capture 'Hint' output from msBuild
Change By:
Martin Moore
When building Delphi projects with msBuild, the output can include Warnings and Hints. Currently Hints are ignored. It would be very useful if they were included and any increase in the number of hints treated as a fail in qualityGate.Additionally the parser misidentifies the affected files. Sample console log:{code:java}Embarcadero Delphi for Win32 compiler version 21.0 Copyright (c) 1983,2009 Embarcadero Technologies, Inc.C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never usedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands 269261 lines, 2.61 seconds, 2496188 bytes code, 595788 bytes data. Done building target "CoreCompile" in project "POSManagerTests.dproj".Done building project "POSManagerTests.dproj".Build succeeded. C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands 3 Warning(s) 0 Error(s){code} warnings-ng reports the affected file being C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets, rather than C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas Example line with hint{code:java}C:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never used{code} I suspect it would report the hint correctly, but the ignores it entirely (I imagine because the parser isn't looking for "hints" in the output of msbuild.
[JIRA] (JENKINS-57794) Use MySQL API Plugin to load MySQL Connector
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-57794 Use MySQL API Plugin to load MySQL Connector Issue Type: Improvement Assignee: Cyrille Le Clerc Components: database-mysql-plugin, pipeline-maven-plugin Created: 2019-05-31 14:50 Priority: Minor Reporter: Cyrille Le Clerc To prevent classloading issues and prevent version mismatches on the MySQL Connector jar, use the MySQL API Plugin to load the MySQL Connector Jar. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-57794) Use MySQL API Plugin to load MySQL Connector
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-57794 Use MySQL API Plugin to load MySQL Connector Issue Type: Improvement Assignee: Cyrille Le Clerc Components: database-mysql-plugin, pipeline-maven-plugin Created: 2019-05-31 14:50 Priority: Minor Reporter: Cyrille Le Clerc To prevent classloading issues and prevent version mismatches on the MySQL Connector jar, use the MySQL API Plugin to load the MySQL Connector Jar. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Fauzan commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found same problem since yesterday am using Bitbucket Plugin version 1.1.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199726.1559290809000.17597.1559314280245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title
Alex Mace updated an issue
Jenkins / JENKINS-57789
Warning-ng plugin doesn't capture 'Hint' output from msBuild
Change By:
Alex Mace
When building Delphi projects with msBuild, the output can include Warnings and Hints. Currently Hints are ignored. It would be very useful if they were included and any increase in the number of hints treated as a fail in qualityGate.Additionally the parser misidentifies the affected files. Sample console log: {code:java} Embarcadero Delphi for Win32 compiler version 21.0Copyright (c) 1983,2009 Embarcadero Technologies, Inc. C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecated C:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never used C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands269261 lines, 2.61 seconds, 2496188 bytes code, 595788 bytes data.Done building target "CoreCompile" in project "POSManagerTests.dproj". Done building project "POSManagerTests.dproj". Build succeeded.C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands3 Warning(s)0 Error(s) {code} warnings-ng reports the affected file being C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets, rather than C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pasI suspect it would report the hint correctly, but the ignores it entirely (I imagine because the parser isn't looking for "hints" in the output of msbuild.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Alex Mace updated an issue Jenkins / JENKINS-57789 Warning-ng plugin doesn't capture 'Hint' output from msBuild Change By: Alex Mace The When building Delphi projects with msBuild , the output can include Warnings and Hints. Currently Hints are ignored. It would be very useful if they were included and any increase in the number of hints treated as a fail in qualityGate. Additionally the parser misidentifies the affected files. Sample console log:Embarcadero Delphi for Win32 compiler version 21.0Copyright (c) 1983,2009 Embarcadero Technologies, Inc.C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Delphi Projects\DCU 2010\Externals\Lib\Delphi\IBSQL.pas(205) hint: H2219 Private symbol 'GetCodePage' declared but never usedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands269261 lines, 2.61 seconds, 2496188 bytes code, 595788 bytes data.Done building target "CoreCompile" in project "POSManagerTests.dproj".Done building project "POSManagerTests.dproj".Build succeeded.C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(469) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pas(1221) Warning: W1000 Symbol 'GIdIPv6FuncsAvailable' is deprecatedC:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : C:\Program Files (x86)\Jenkins\workspace\POS_Manager_develop\Externals\Lib\Common\FBHStrUtils.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands3 Warning(s)0 Error(s)warnings-ng reports the affected file being C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets, rather than C:\Delphi Projects\DCU 2010\indy10\Lib\System\IdWship6.pasI suspect it would report the hint correctly, but the ignores it entirely (I imagine because the parser isn't looking for "hints" in the output of msbuild.
[JIRA] (JENKINS-57790) Incorrect source file reported
Title: Message Title Ulli Hafner commented on JENKINS-57790 Re: Incorrect source file reported Do all your warnings look like this? Seems that there are two logs interleaving: First part: C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\CodeGear.Delphi.Targets : warning : Second part: C:\Delphi Projects\Projects...\myfile.pas(349) Warning: W1024 Combining signed and unsigned types - widened both operands Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199738.1559308951000.17587.1559314020271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57559) Move JCasC support to the Credentials Plugin
Title: Message Title Oleg Nenashev updated JENKINS-57559 Jenkins / JENKINS-57559 Move JCasC support to the Credentials Plugin Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Credentials Plugin 2.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199470.1558355708000.17585.1559314020234%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't process hints and warnings correctly when building Delphi with msBuild
Title: Message Title Alex Mace updated an issue Jenkins / JENKINS-57789 Warning-ng plugin doesn't process hints and warnings correctly when building Delphi with msBuild Change By: Alex Mace Summary: Warning-ng plugin doesn't capture 'Hint' output from process hints and warnings correctly when building Delphi with msBuild Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199737.1559308621000.17579.1559313840279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Ulli Hafner assigned an issue to Unassigned Can you please add one whole console log line with an example that can be used in a test? Jenkins / JENKINS-57789 Warning-ng plugin doesn't capture 'Hint' output from msBuild Change By: Ulli Hafner Summary: Warning-ng plugin doesn't process hints and warnings correctly when building Delphi with capture 'Hint' output from msBuild Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Jakub Bochenski commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin Kinnaird McQuade thanks for sharing your workaround. I think you'll agree that having credentials plugin support would make be better than jumping all those hoops? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.17576.1559313000115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title Jesse Glick commented on JENKINS-57774 Re: JenkinsRule: Jetty leaves stray threads running after server.stop() Is there a concrete problem this behavior is causing? mvn test failures, etc.? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199721.1559274543000.17572.1559312700151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-57774
JenkinsRule: Jetty leaves stray threads running after server.stop()
Change By:
Jesse Glick
I was debugging through JenkinsRule from Jenkins Test Harness. After the Jetty server and Jenkins have both been terminated in JenkinsRule#after() ([line 488|https://github.com/jenkinsci/jenkins-test-harness/blob/2281a68194604c983e7a8d1e7822379b262f153d/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L488] and {color:#20}[line 502|https://github.com/jenkinsci/jenkins-test-harness/blob/2281a68194604c983e7a8d1e7822379b262f153d/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L502]{color}, respectively) stray threads keep running. Attached is the dump of the running threads. Is it possible to terminate these threads to allow the JVM to exit gracefully? This issue may already have been reported before in this Stack Overflow question: [https://stackoverflow.com/questions/13769007/jetty-server-leaves-behind-threads-after-stop] A minimal example would be following test code and setting a breakpoint at the System.gc() call on line 517: { color:#660066 code } {color:#004000} import org.junit.Rule; {color}{color}{color:#660066}{color:#004000} import org.junit.Test;import org.jvnet.hudson.test.JenkinsRule; {color}{color}{color:#660066}{color:#004000} public class RandomTest { @Rule public JenkinsRule jenkinsRule = new JenkinsRule(); {color}{color}{{{color:#660066}{color:#004000} @Test public void randomTest() { System.out.println("Hello world"); }} { color code } {color}}} I was able to confirm the behaviour with the latest Jetty on both Windows 10 and Linux. This issues was discussed on the developer mailing list: {color:#004000}https://groups.google.com/forum/#!topic/jenkinsci-dev/7yL0MKjxQwA{color}
Add Comment
[JIRA] (JENKINS-57793) Creates addition empty connection cfg. after applying JCasC
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-57793 Creates addition empty connection cfg. after applying JCasC Change By: Pavel Janoušek Attachment: gitlab.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199742.1559312157000.17526.1559312220144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57793) Creates addition empty connection cfg. after applying JCasC
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57793 Creates addition empty connection cfg. after applying JCasC Issue Type: Bug Assignee: Owen Mehegan Components: gitlab-plugin Created: 2019-05-31 14:15 Labels: jcasc-compatibility Priority: Major Reporter: Pavel Janoušek Simple YAML definition as: unclassified: gitLabConnectionConfig: connections: - apiTokenId: "token" clientBuilderId: "autodetect" name: "test" url: "https://test.foo.com" The result is 2 connections in UI as you can see in the attached screenshot. The second one shouldn't be there. Add Comment
[JIRA] (JENKINS-57792) BitBucket Cloud Webhook JSONException
Title: Message Title
Edcel Vista created an issue
Jenkins / JENKINS-57792
BitBucket Cloud Webhook JSONException
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-plugin
Created:
2019-05-31 14:08
Environment:
Jenkins ver. 2.179
Priority:
Critical
Reporter:
Edcel Vista
Upon further investigation, we have identified that while the Jenkins Plugin is expecting the "username" field in the JSON object of the payload, Bitbucket Cloud has removed the "username" field and replaced it with the Atlassian Account ID ("account_id") field as per Bitbucket Cloud REST APIs are changing to improve user privacy. Bitbucket Cloud has removed the "username" field as per the new GDPR regulation. To move forward with this issue, we'd like to suggest that you reach out to Jenkins to have the Plugin Updated.
Add Comment
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS I can't add screenshots to the ADFS configuration example, but the Jenkins side of it is not very clear. I am attaching screenshots that might improve those instructions here:[https://github.com/jenkinsci/saml-plugin/blob/master/doc/ADFS_CONFIG.md]*Add this to the Jenkins Side*I think some people like me, screw up the Redirect part and set it to post inadvertently, and I reached a blind conclusion that the logout was broken. It's not really. !image-2019-05-31- 09 10 - 57 05 - 23 18 - 911 462 .png! *Add this to the Windows Server side*It shows the logout url being mirrored in both the Jenkins and the ADFS configuration.!image-2019-05-31-10-01-54-291.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17519.1559311560124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS I can't add screenshots to the ADFS configuration example, but the Jenkins side of it is not very clear. I am attaching screenshots that might improve those instructions here:[https://github.com/jenkinsci/saml-plugin/blob/master/doc/ADFS_CONFIG.md]*Add this to the Jenkins Side*I think some people like me, screw up the Redirect part and set it to post inadvertently, and I reached a blind conclusion that the logout was broken. It's not really. !image-2019-05-31-09-57-23-911.png! *Add this , or maybe something even prettier, to the Windows Server side*It shows the logout url being mirrored in both the Endpoint Jenkins and the ADFS configuration section* . !image-2019-05-31-10-01-54-291.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17509.1559311500254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54832) Groovy Parser cannot access console log
Title: Message Title Norbert Lange commented on JENKINS-54832 Re: Groovy Parser cannot access console log Daniel Saier: No I did not knew about this yet, I proposed practically the same thing in JENKINS-44930. Thanks. That seems to be the proper solution for me now, as I prefer feeding just the output from the build command to the warnings-plugin (vs. using the whole log output) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195821.1542969482000.17511.1559311500275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS I can't add screenshots to the ADFS configuration example, but the Jenkins side of it is not very clear. I am attaching screenshots that might improve those instructions here:[https://github.com/jenkinsci/saml-plugin/blob/master/doc/ADFS_CONFIG.md]*Add this to the Jenkins Side , * I think some people like me, screw up the Redirect part and set it to post inadvertently * , and I reached a blind conclusion that the logout was broken. It's not really. !image-2019-05-31-09-57-23-911.png! *Add this, or maybe something even prettier, in the Endpoint configuration section*!image-2019-05-31-10-01-54-291.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17506.1559311440117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS I can't add screenshots to the ADFS configuration example, but the Jenkins side of it is not very clear. I am attaching screenshots that might improve those instructions here:[https://github.com/jenkinsci/saml-plugin/blob/master/doc/ADFS_CONFIG.md]*Add this to the Jenkins Side, I think some people like me, screw up the Redirect part and set it to post inadvertently* !image-2019-05-31-09-57-23-911.png! *Add this, or maybe something even prettier, in the Endpoint configuration section*!image-2019-05-31-10-01-54-291.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17503.1559311380411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS !image-2019-05-31-09-57-23-911.png! I can't add screenshots to the ADFS configuration example, but the Jenkins side of it is not very clear. I am attaching screenshots that might improve those instructions here:[https://github.com/jenkinsci/saml-plugin/blob/master/doc/ADFS_CONFIG.md] *Add this to the Jenkins Side, I think some people like me, screw up the Redirect part and set it to post inadvertently* !image-2019-05-31-09-57-23-911.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17493.1559311260142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Jesse Borden edited a comment on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS This would be a great fix to the almost perfect ADFS solution !image-2019-05-31-09-57-23-911 . Just so it's clear to me, we png! I can't use this plugin add screenshots to logout from the ADFS at all configuration example, but the Jenkins side of it is not very clear . .. yet? I am attaching screenshots that might improve those instructions here: *+When Logout button clicked, ADFS logs+*MSIS7000 [https : The sign in request is not compliant to the WS //github.com/jenkinsci/saml - Federation language for web browser clients or the SAML 2 plugin/blob/master/doc/ADFS_CONFIG . 0 protocol WebSSO profile. md] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197201.1548663867000.17490.1559311140262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57791) Database credentials in Build Step configuration
Title: Message Title José Lamas created an issue Jenkins / JENKINS-57791 Database credentials in Build Step configuration Issue Type: New Feature Assignee: José Lamas Components: genexus-plugin Created: 2019-05-31 13:54 Priority: Minor Reporter: José Lamas The MSBuild script invoked for the KB build step uses the OpenKnowledgeBase task, with no database credentials, so that they are taken from the knowledgebase.connection file. In some cases the build step may need to use custom database credentials but there is currently no way to specify them. Add Comment
[JIRA] (JENKINS-57787) Bitbucket Plugin unable to parse Bitbucket webhook json
Title: Message Title prog wml6 commented on JENKINS-57787 Re: Bitbucket Plugin unable to parse Bitbucket webhook json A PR was filed to fix this on the repo https://github.com/jenkinsci/bitbucket-plugin/pull/64 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199735.1559300884000.17482.1559310660227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54832) Groovy Parser cannot access console log
Title: Message Title Daniel Saier commented on JENKINS-54832 Re: Groovy Parser cannot access console log If you don't know it yet, you should take a look at the tee step. This does what it should and automatically propagates the return codes of any failed steps inside of the tee. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195821.1542969482000.17476.1559310420266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
