[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Reinhold Füreder commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Maybe JENKINS-38316 and in particular https://issues.jenkins-ci.org/browse/JENKINS-38316?focusedCommentId=332021&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332021 explains the current situation (in case it has changed over the past almost 2 years)... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47074) `SpecificBuildSelector` should accept build ids
Title: Message Title ikedam commented on JENKINS-47074 Re: `SpecificBuildSelector` should accept build ids https://github.com/jenkinsci/copyartifact-plugin/pull/101 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47074) `SpecificBuildSelector` should accept build ids
Title: Message Title ikedam started work on JENKINS-47074 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Patrick Ruckstuhl commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs Still seeing this as well, what I found interesting is that it seems to check for the current version on the SLAVE which doesn't make sense (our jobs pick slave depending on availability so they will not always run on the same node.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Saad Azam reopened an issue Please try to reproduce using Jenkins version 2.89.2 and PTC integrity plugin 2.1 Job Dsl plugin version 1.66 Let me know if there is missing info. Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Saad Azam Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-50160) Can't add credentials through https
Title: Message Title Anton Anonymous created an issue Jenkins / JENKINS-50160 Can't add credentials through https Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-03-14 08:07 Environment: Jenkins version 2.89.3 Credentials Plugin version 2.1.16 Priority: Major Reporter: Anton Anonymous When I try to add credentials for example login/password for docker registry, nothing happens and I get following error in console: Mixed Content: The page at 'https://example.com/job/dfo-pm-staging_backend_develop/configure' was loaded over HTTPS, but requested an insecure form action 'http://example.com/descriptor/com.cloudbees.plugins.credentials.Cred...ials.SystemCredentialsProvider$ProviderImpl/context/jenkins/addCredentials'. This request has been blocked; the content must be served over HTTPS. I can change form url to https instead of http using developer tools and then it submits correctly. How do I fix this issue?
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Update to the latest version of Job DSL and post a small script that reproduces the problem. Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Daniel Spilker Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, sen
[JIRA] (JENKINS-50160) Can't add credentials through https
Title: Message Title
Anton Anonymous updated an issue
Jenkins / JENKINS-50160
Can't add credentials through https
Change By:
Anton Anonymous
When I try to add credentials for example login/password for docker registry, nothing happens and I get following error in console (domain name changed to example.com) :{quote} Mixed Content: The page at 'https://example.com/job/dfo-pm-staging_backend_develop/configure' was loaded over HTTPS, but requested an insecure form action 'http://example.com/descriptor/com.cloudbees.plugins.credentials.Cred...ials.SystemCredentialsProvider$ProviderImpl/context/jenkins/addCredentials'. This request has been blocked; the content must be served over HTTPS.{quote}I can change form url to https instead of http using developer tools and then it submits correctly. How do I fix this issue?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from th
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Raphael Fraysse commented on JENKINS-48067 Re: workspace-volume should be optional Hello, We also have the same issue and while trying a lot of workarounds, we didn't manage to redirect the workspace to another directory while getting Jenkins to run in a non emptyDir volume. Persistent volume is not the solution to our problem as it adds more complexity to our clusters. Please make it so we can disable this workspace automated volume creation. Hardcoding this and not letting users to change it is a huge drawback to use Kubernetes pods slaves. Sincerely, Raphael Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title
Brandon Saunders commented on JENKINS-40997
Re: Add way to get locked resource name in pipeline
I'm appearing to hit an issue where a released resource does not get an update on the environment variable once the lock is released. See the following code node { parallel ( "p1": { lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) { echo "A $env.ACCOUNTS_VAR" sleep 4 {{ }}} }, "p2": { lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) { echo "B $env.ACCOUNTS_VAR" sleep 2 {{ }}} }, "p3": { lock(label: 'automation-accounts', variable: 'ACCOUNT_ME', quantity: 1) { echo "C $env.ACCOUNTS_ME" {{ }}} {{ }}} ) } In the log I get the following (note "C null"): [Pipeline] { [Pipeline] parallel [Pipeline] [p1] { (Branch: p1) [Pipeline] [p2] { (Branch: p2) [Pipeline] [p3] { (Branch: p3) [Pipeline] [p1] lock [p1] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p1] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] { [Pipeline] [p2] lock [p2] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p2] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] { [Pipeline] [p3] lock [p3] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p3] Found 0 available resource(s). Waiting for correct amount: 1. [p3] [Label: automation-accounts, Quantity: 1] is locked, waiting... [Pipeline] [p1] echo [p1] A [Pipeline] [p1] sleep [p1] Sleeping for 4 sec [Pipeline] [p2] echo [p2] B [Pipeline] [p2] sleep [p2] Sleeping for 2 sec [p3] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] } [p2] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] { [Pipeline] [p2] // lock [Pipeline] [p2] } [Pipeline] [p3] echo [p3] C null [Pipeline] [p3] } [p3] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] // lock [Pipeline] [p3] } [Pipeline] [p1] } [p1] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] // lock [Pipeline] [p1] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Expected Result: I should get "C Perhaps I'm calling it wrong though?
Add Comment
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title
Brandon Saunders edited a comment on JENKINS-40997
Re: Add way to get locked resource name in pipeline
I'm appearing to hit an issue where a released resource does not get an update on the environment variable once the lock is released. See the following code {{node \{}}{{ parallel (}}{{ "p1": \{}}{{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}}{{ echo "A $env.ACCOUNTS_VAR"}}{{ sleep 4}} {{ } }} {{ },}}{{ "p2": \{}}{{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}}{{ echo "B $env.ACCOUNTS_VAR"}}{{ sleep 2}} {{ } }} {{ },}}{{ "p3": \{}}{{ lock(label: 'automation-accounts', variable: 'ACCOUNT_ME', quantity: 1) \{}}{{ }}{{echo "C $env.ACCOUNTS_ME"}} {{ } }} {{ } }} {{ )}}{{}}} In the log I get the following (note "C null"):[Pipeline] \{[Pipeline] parallel[Pipeline] [p1] \{ (Branch: p1)[Pipeline] [p2] \{ (Branch: p2)[Pipeline] [p3] \{ (Branch: p3)[Pipeline] [p1] lock[p1] Trying to acquire lock on [Label: automation-accounts, Quantity: 1][p1] Lock acquired on [Label: automation-accounts, Quantity: 1][Pipeline] [p1] \{[Pipeline] [p2] lock[p2] Trying to acquire lock on [Label: automation-accounts, Quantity: 1][p2] Lock acquired on [Label: automation-accounts, Quantity: 1][Pipeline] [p2] \{[Pipeline] [p3] lock[p3] Trying to acquire lock on [Label: automation-accounts, Quantity: 1][p3] Found 0 available resource(s). Waiting for correct amount: 1.[p3] [Label: automation-accounts, Quantity: 1] is locked, waiting...[Pipeline] [p1] echo[p1] A [Pipeline] [p1] sleep[p1] Sleeping for 4 sec[Pipeline] [p2] echo[p2] B [Pipeline] [p2] sleep[p2] Sleeping for 2 sec[p3] Lock acquired on [Label: automation-accounts, Quantity: 1][Pipeline] [p2] }[p2] Lock released on resource [Label: automation-accounts, Quantity: 1][Pipeline] [p3] \{[Pipeline] [p2] // lock[Pipeline] [p2] }[Pipeline] [p3] echo[p3] C null[Pipeline] [p3] }[p3] Lock released on resource [Label: automation-accounts, Quantity: 1][Pipeline] [p3] // lock[Pipeline] [p3] }[Pipeline] [p1] }[p1] Lock released on resource [Label: automation-accounts, Quantity: 1][Pipeline] [p1] // lock[Pipeline] [p1] }[Pipeline] // parallel[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineExpected Result:I should get "C Perhaps I'm calling it wrong though?
Add Comment
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title
Brandon Saunders edited a comment on JENKINS-40997
Re: Add way to get locked resource name in pipeline
I'm appearing to hit an issue where a released resource does not get an update on the environment variable once the lock is released. See the following code {{node \{}} {{ parallel (}} {{ "p1": \{}} {{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}} {{ echo "A $env.ACCOUNTS_VAR"}} {{ sleep 4}} } {{ },}} {{ "p2": \{}} {{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}} {{ echo "B $env.ACCOUNTS_VAR"}} {{ sleep 2}} } {{ },}} {{ "p3": \{}} {{ lock(label: 'automation-accounts', variable: ' ACCOUNT_ME ACCOUNTS_VAR ', quantity: 1) \{}} {{ }}{{echo "C $env. ACCOUNTS_ME ACCOUNTS_VAR "}} } } {{ )}} {{}}} In the log I get the following (note "C null"): [Pipeline] \{ [Pipeline] parallel [Pipeline] [p1] \{ (Branch: p1) [Pipeline] [p2] \{ (Branch: p2) [Pipeline] [p3] \{ (Branch: p3) [Pipeline] [p1] lock [p1] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p1] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] \{ [Pipeline] [p2] lock [p2] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p2] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] \{ [Pipeline] [p3] lock [p3] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p3] Found 0 available resource(s). Waiting for correct amount: 1. [p3] [Label: automation-accounts, Quantity: 1] is locked, waiting... [Pipeline] [p1] echo [p1] A [Pipeline] [p1] sleep [p1] Sleeping for 4 sec [Pipeline] [p2] echo [p2] B [Pipeline] [p2] sleep [p2] Sleeping for 2 sec [p3] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] } [p2] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] \{ [Pipeline] [p2] // lock [Pipeline] [p2] } [Pipeline] [p3] echo [p3] C null [Pipeline] [p3] } [p3] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] // lock [Pipeline] [p3] } [Pipeline] [p1] } [p1] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] // lock [Pipeline] [p1] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Expected Result: I should get "C Perhaps I'm calling it wrong though?
Add Comment
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title
Brandon Saunders edited a comment on JENKINS-40997
Re: Add way to get locked resource name in pipeline
I'm appearing to hit an issue where a released resource does not get an update on the environment variable once the lock is released. See the following code {{node \{}} {{ parallel (}} {{ "p1": \{}} {{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}} {{ echo "A $env.ACCOUNTS_VAR"}} {{ sleep 4}} } {{ },}} {{ "p2": \{}} {{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}} {{ echo "B $env.ACCOUNTS_VAR"}} {{ sleep 2}} } {{ },}} {{ "p3": \{}} {{ lock(label: 'automation-accounts', variable: 'ACCOUNTS_VAR', quantity: 1) \{}} {{ }}{{echo "C $env.ACCOUNTS_VAR"}} } } {{ )}} {{}}} In the log I get the following (note "C null"): [Pipeline] \{ [Pipeline] parallel [Pipeline] [p1] \{ (Branch: p1) [Pipeline] [p2] \{ (Branch: p2) [Pipeline] [p3] \{ (Branch: p3) [Pipeline] [p1] lock [p1] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p1] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] \{ [Pipeline] [p2] lock [p2] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p2] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] \{ [Pipeline] [p3] lock [p3] Trying to acquire lock on [Label: automation-accounts, Quantity: 1] [p3] Found 0 available resource(s). Waiting for correct amount: 1. [p3] [Label: automation-accounts, Quantity: 1] is locked, waiting... [Pipeline] [p1] echo [p1] A [Pipeline] [p1] sleep [p1] Sleeping for 4 sec [Pipeline] [p2] echo [p2] B [Pipeline] [p2] sleep [p2] Sleeping for 2 sec [p3] Lock acquired on [Label: automation-accounts, Quantity: 1] [Pipeline] [p2] } [p2] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] \{ [Pipeline] [p2] // lock [Pipeline] [p2] } [Pipeline] [p3] echo {color:#ff} [p3] C null {color} [Pipeline] [p3] } [p3] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p3] // lock [Pipeline] [p3] } [Pipeline] [p1] } [p1] Lock released on resource [Label: automation-accounts, Quantity: 1] [Pipeline] [p1] // lock [Pipeline] [p1] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline * Expected Result * : I should get "C Perhaps I'm calling it wrong though?
Add Comment
[JIRA] (JENKINS-50001) Global PTC settings not saved to JEP-200 changes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50001 Re: Global PTC settings not saved to JEP-200 changes Code changed in jenkins User: Anurag Sen Path: src/main/java/hudson/scm/IntegritySCM.java http://jenkins-ci.org/commit/integrity-plugin/a4d8e61f0359af7a9f9b64b79bc7fca05a544814 Log: Merge pull request #30 from jglick/DataSource-field-JENKINS-50001 JENKINS-50001 Do not attempt to serialize a ConnectionPoolDataSource to hudson.scm.IntegritySCM.xml Compare: https://github.com/jenkinsci/integrity-plugin/compare/9909ebaa2fbe...a4d8e61f0359 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50001) Global PTC settings not saved to JEP-200 changes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50001 Re: Global PTC settings not saved to JEP-200 changes Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/scm/IntegritySCM.java http://jenkins-ci.org/commit/integrity-plugin/ce39c29edf05843f37ab99f4cf939461e621e043 Log: JENKINS-50001 Do not attempt to serialize a ConnectionPoolDataSource to hudson.scm.IntegritySCM.xml. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50161) jira rest client get user error cause: RestClientException{statusCode=Optional.of(404), errorCollections=[]}
Title: Message Title
Adrian Wyssmann created an issue
Jenkins / JENKINS-50161
jira rest client get user error cause: RestClientException{statusCode=Optional.of(404), errorCollections=[]}
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-plugin
Created:
2018-03-14 08:32
Environment:
jenkins 2.83.4 JIRA plugin 2.5
Labels:
jenkins plugin
Priority:
Minor
Reporter:
Adrian Wyssmann
I recently enabled the connection from Jenkins to JIRA in the server configuration. Since then I get regularly the following issue
Mar 14, 2018 9:03:16 AM hudson.plugins.jira.JiraRestService getUser
WARNING: jira rest client get user error. cause: RestClientException{statusCode=Optional.of(404), errorCollections=[]}
java.util.concurrent.ExecutionException: RestClientException{statusCode=Optional.of(404), errorCollections=[]}
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:262)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:107)
at hudson.plugins.jira.JiraRestService.getUser(JiraRestService.java:277)
at hudson.plugins.jira.JiraMailAddressResolver.findMailAddressFor(JiraMailAddr
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title
John Lonergan commented on JENKINS-50158
Re: Git plugin class LocalBranch needs to be serializable
Will try and provide logs. The problem only occured when I tried to move the code below from the jenkinsfile to Jenkins library. NoTe Code below is not literally what I have as I am not at a computer right now... def gitscm = new GitScm(... , extensions: [new LocalBranch('**')]) def scmvars = checkout gitscm While this code was in my jenkinsfile there wasn't a problem, but move it to a Jenkins library and it then fails. Curiously even though the build fails with serializable eror I found that when I hit replay then the build succeeds. Presumably during replay Jenkins doesn't try to serialise the Jenkins job state.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Boguslaw Klimas commented on JENKINS-50131 Re: git parameter Ok, I see you have git SCM in pipeline definition, https://issues.jenkins-ci.org/browse/JENKINS-49834 https://issues.jenkins-ci.org/browse/JENKINS-49758 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Boguslaw Klimas updated an issue Jenkins / JENKINS-50131 git parameter Change By: Boguslaw Klimas Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Boguslaw Klimas resolved as Duplicate Jenkins / JENKINS-50131 git parameter Change By: Boguslaw Klimas Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-34340 Don't rename job names in TRIGGERED_JOB_NAMES Change By: Baptiste Mathus Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title Baptiste Mathus commented on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES Stumbled into this by chance:Sigh. Just an advice: this is not how you want to report things, if you want to have a single chance that people spend their free time fixing your issue... *Because* of this phrasing, if I was the maintainer, I would fix everything else but this if I'm not hitting it too. Be polite, be respectful. You're talking to humans, and humans that helps for nothing else than pleasure, and can choose whatever they work on. My 2 cents. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49336) Plugin should be able to use SYSTEM scope credentials
Title: Message Title Johannes Müller commented on JENKINS-49336 Re: Plugin should be able to use SYSTEM scope credentials any comments on this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50162) NUnit test results don't encode characters correctly in unit test report
Title: Message Title
Kai Bublitz created an issue
Jenkins / JENKINS-50162
NUnit test results don't encode characters correctly in unit test report
Issue Type:
Bug
Assignee:
Alex Earl
Components:
nunit-plugin
Created:
2018-03-14 09:22
Environment:
Jenkins ver. 2.89.4 NUnit Plugin
Labels:
nunit test-results
Priority:
Major
Reporter:
Kai Bublitz
Test results contain wrongly encoded characters when evaluating NUnit test results. Some characters are turned into question marks. Specifically our test reports contain the following test case and similar ones: (test name simplified and anonymized) In the test report view of Jenkins this test case is displayed as: SaveAlphaNumericals("??") The special characters are turned to ??. This happens for all test cases containing special characters like Ä,Ö,Ü or °, so in the test result the cases can't be distinguished anymore.
[JIRA] (JENKINS-49768) GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49768 Re: GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server Code changed in jenkins User: Stephen Connolly Path: CHANGES.md src/main/java/org/jenkinsci/plugin/gitea/GiteaSCMBuilder.java http://jenkins-ci.org/commit/gitea-plugin/bddf7b2925dfd44aaecc53b2f3e20a6e6c395463 Log: [FIXED JENKINS-49768] Detect scp style urls and translate to ssh style Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42509) authenticated team members should have read/build permissions when using Github Committer Authorization Strategy
Title: Message Title Olivier Jacques commented on JENKINS-42509 Re: authenticated team members should have read/build permissions when using Github Committer Authorization Strategy Thanks Sam Gleske. Do we have an ETA on the next release? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49768) GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-49768 GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track
Title: Message Title Artem Fedorov commented on JENKINS-49022 Re: Performance plugin. Allow choosing percentiles to track Oleg Nenashev I reproduced it with Jenkins 2.111 and this PR fixed it. https://github.com/jenkinsci/performance-plugin/pull/162 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47919) Checking parameters of remote job build fails
Title: Message Title Himanshu Paliwal commented on JENKINS-47919 Re: Checking parameters of remote job build fails Impacting my work as well. Can we have fix for this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Himanshu Paliwal commented on JENKINS-32462 Re: Checking Status of remote job fail Any Update on above issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track
Title: Message Title Artem Fedorov commented on JENKINS-49022 Re: Performance plugin. Allow choosing percentiles to track Andrey Pokhilko FYI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title
Saad Azam reopened an issue
OK, thanks for the hint. I have updated JobDSL to 1.68 and still getting the same error. here is my test code which I am using to reproduce the error. Unable to render embedded object: File (image-2018-03-14-11-07-34-143.png) not found. def cfg_name = "example" def serv_cfg = "example:" def cfg_path = "example/project.pj" pipelineJob('test_pipeline_gen') { definition { cpsScm { scm{ integritySCM { configurationName(cfg_name) configPath(cfg_path) serverConfig(serv_cfg) } } } } } Latest console output: Processing provided DSL script java.lang.IllegalArgumentException: Could not instantiate {configurationName=example, configPath=example/project.pj, serverConfig=example:} for IntegritySCM(serverConfig: String, configPath: String, configurationName: String, CPBasedMode?: boolean, alternateWorkspace?: String, browser?: IntegrityRepositoryBrowser{IntegrityWebUI(url: String)}, checkoutThreadPoolSize?: int, checkoutThreadTimeout?: int, checkpointBeforeBuild?: boolean, checkpointLabel?: String, cleanCopy?: boolean, deleteNonMembers?: boolean, excludeList?: String, fetchChangedWorkspaceFiles?: boolean, includeList?: String, lineTerminator?: String, localClient?: boolean, password?: String, restoreTimestamp?: boolean, skipAuthorInfo?: boolean, userName?: String): java.lang.reflect.InvocationTargetException at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:286) at org.jenkinsci.plugins.structs.describable.DescribableModel$instantiate$1.call(Unknown Source) at javaposse.jobdsl.plugin.structs.DescribableContext.createInstance(DescribableContext.groovy:50) at javaposse.jobdsl.plugin.structs.DescribableContext$createInstance.call(Unknown Source) at javaposse.jobdsl.plugin.ExtensionPointHelper$DescribableExtension.call(ExtensionPointHelper.groovy:117) at javaposse.jobdsl.plugin.JenkinsJobManagement.callExtension(JenkinsJobManagement.java:385) at javaposse.jobdsl.dsl.JobManagement$callExtension$2.call(Unknown Source) at javaposse.jobdsl.plugin.InterruptibleJobManagement.callExtension(InterruptibleJobManagement.groovy:151) at javaposse.jobdsl.dsl.JobManagement$callExtension$2.call(Unknown Source) at javaposse.jobdsl.dsl.AbstractExtensibleContext.methodMissing(AbstractExtensibleContext.groovy:17) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaClassImpl.invokeMissingMethod(MetaClassImpl.java:939) at groovy.lang.MetaClassImpl.invokePropertyOrMissing(MetaClassImpl.java:1262) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1215) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at javaposse.jobdsl.dsl.AbstractContext.invokeMethod(AbstractContext.groovy) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeOnDelegationObjects(ClosureMetaClass.java:430) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:371) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:69) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:154) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:166) at script$_run_closure1$_closure2$_closure3$_closure4.doCall(script:8) at script$_run_closure1$_closure2$_closure3$_closure4.doCall(script) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Michael Drygola commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS For case #2 there is another issue reported, JENKINS-48551 Also happens to me, on Jenkins v2.89.3, Publish Over CIFS v0.6 and v0.5 (tried downgrading) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title
Saad Azam edited a comment on JENKINS-49797
Re: IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
OK, thanks for the hint. I have updated JobDSL to 1.68 and still getting the same error. here is my test code from the job where I am processing Job DSL, which I am using to reproduce the error. {color:#205081}Build:{color} {color:#205081}Process Job DSLs:{color} !image-2018-03-14-11-07-34-143.png! {color:#205081}DSL Script:{color} {color:#205081} def cfg_name = "example" {color} {color:#205081} def serv_cfg = "example:" {color} {color:#205081} def cfg_path = "example/project.pj" {color} {color:#205081} pipelineJob('test_pipeline_gen') \{ {color} {color:#205081} definition \{ {color} {color:#205081} cpsScm \{ {color} {color:#205081} scm\{ {color} {color:#205081} integritySCM \{ {color} {color:#205081} configurationName(cfg_name) {color} {color:#205081} configPath(cfg_path) {color} {color:#205081} serverConfig(serv_cfg) {color} {color:#205081 } }{color} {color:#205081 } }{color} {color:#205081 } }{color} {color:#205081 } }{color} {color:#205081 } }{color} Latest console output:Processing provided DSL scriptjava.lang.IllegalArgumentException: Could not instantiate \{configurationName=example, configPath=example/project.pj, serverConfig=example:} for IntegritySCM(serverConfig: String, configPath: String, configurationName: String, CPBasedMode?: boolean, alternateWorkspace?: String, browser?: IntegrityRepositoryBrowser\{IntegrityWebUI(url: String)}, checkoutThreadPoolSize?: int, checkoutThreadTimeout?: int, checkpointBeforeBuild?: boolean, checkpointLabel?: String, cleanCopy?: boolean, deleteNonMembers?: boolean, excludeList?: String, fetchChangedWorkspaceFiles?: boolean, includeList?: String, lineTerminator?: String, localClient?: boolean, password?: String, restoreTimestamp?: boolean, skipAuthorInfo?: boolean, userName?: String): java.lang.reflect.InvocationTargetException at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:286) at org.jenkinsci.plugins.structs.describable.DescribableModel$instantiate$1.call(Unknown Source) at javaposse.jobdsl.plugin.structs.DescribableContext.createInstance(DescribableContext.groovy:50) at javaposse.jobdsl.plugin.structs.DescribableContext$createInstance.call(Unknown Source) at javaposse.jobdsl.plugin.ExtensionPointHelper$DescribableExtension.call(ExtensionPointHelper.groovy:117) at javaposse.jobdsl.plugin.JenkinsJobManagement.callExtension(JenkinsJobManagement.java:385) at javaposse.jobdsl.dsl.JobManagement$callExtension$2.call(Unknown Source) at javaposse.jobdsl.plugin.InterruptibleJobManagement.callExtension(InterruptibleJobManagement.groovy:151) at javaposse.jobdsl.dsl.JobManagement$callExtension$2.call(Unknown Source) at javaposse.jobdsl.dsl.AbstractExtensibleContext.methodMissing(AbstractExtensibleContext.groovy:17) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaClassImpl.invokeMissingMethod(MetaClassImpl.java:939) at groovy.lang.MetaClassImpl.invokePropertyOrMissing(MetaClassImpl.java:1262) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1215) at groovy.lang.MetaC
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50164 Renaming a job with non default build record directory makes old builds disappear Change By: Baptiste Mathus Summary: Renaming a job with non default build record directory makes old build builds disappear Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50163) Match Text not working on BitBucket Project (possibly any multibranch project)
Title: Message Title Jakub Pawlinski created an issue Jenkins / JENKINS-50163 Match Text not working on BitBucket Project (possibly any multibranch project) Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-03-14 10:21 Priority: Major Reporter: Jakub Pawlinski When verifying my regex against pipeline, all works fine, but when doing same against multibranch pipeline (Bitbucket Project Type) it yields null pointer exception. I think issue maybe in URL path interpretation: http://jenkins.company.com:8080/job/SimplePipeline/1206/ - works http://jenkins. company .com:8080/view/MultibranchPipeline/job/MyTeam/job/MyProject/job/master/65/ - yields: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old build disappear
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-50164
Renaming a job with non default build record directory makes old build disappear
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-03-14 10:21
Priority:
Major
Reporter:
Baptiste Mathus
I think this was introduced by JENKINS-22936 How to reproduce
Start Jenkins 2.110
Create a job and run/create some builds
Change default "Build Record Root Directory" to {{$ {JENKINS_HOME} /var/$ {ITEM_FULL_NAME} /builds/}}
Rename the job
Open a build created before the rename, it will show No such file: /var/jenkins_home/var/new_name/builds/2/log
Stack trace There's the following stack trace when renaming:
Mar 14, 2018 9:29:03 AM hudson.model.Job$SubItemBuildsLocationImpl onLocationChanged
SEVERE: Failed to move /var/jenkins_home/var/current_name/builds/ to /var/jenkins_home/var/new_name/builds
java.io.FileNotFoundException: /var/jenkins_home/var/current_name/builds/lastFailedBuild (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
[JIRA] (JENKINS-50163) Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-50163
Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Change By:
Jakub Pawlinski
Summary:
Match Text not working on BitBucket Project (possibly any other multibranch project projects as well )
When verifying my regex against simple pipeline project , all works fine, but when doing same against multibranch pipeline (Bitbucket Project Type) it yields null pointer exception.I 'm using [Failure Cause Management|http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/failure-cause-management] / MyError / Advanced... / Match TextI think issue maybe in URL path interpretation:[http://jenkins.company.com:8080/job/SimplePipeline/1206/] - works[http://jenkins.|http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] [company|http://jenkins.aveva.com:8080/job/CAF-Generic/1206/] [.com:8080/view/MultibranchPipeline/job/MyTeam/job/MyProject/job/master/65/|http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] - yields:{code:java}A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejava.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.Na
[JIRA] (JENKINS-50163) Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-50163
Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Change By:
Jakub Pawlinski
When verifying my regex against simple pipeline project, all works fine, but when doing same against multibranch pipeline (Bitbucket Project Type) it yields null pointer exception.I'm using [ Failure Cause Management |http: / /jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/failure-cause-management] / MyError / Advanced... / Match TextI think issue maybe in URL path interpretation:[http://jenkins.company.com:8080/job/SimplePipeline/1206/] - works[http://jenkins.|http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] [company|http://jenkins.aveva.com:8080/job/CAF-Generic/1206/] [.com:8080/view/MultibranchPipeline/job/MyTeam/job/MyProject/job/master/65/|http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] - yields:{code:java}A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejava.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at or
[JIRA] (JENKINS-50163) Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-50163
Match Text not working on BitBucket Project (possibly other multibranch projects as well)
Change By:
Jakub Pawlinski
When verifying my regex against simple pipeline project, all works fine, but when doing same against multibranch pipeline (Bitbucket Project Type) it yields null pointer exception.I'm using Failure Cause Management / MyError / Advanced... / Match TextI think issue maybe in URL path interpretation: [ http://jenkins.company.com:8080/job/SimplePipeline/1206/ ] - works [ http://jenkins. |http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] [ company |http://jenkins . aveva. com:8080/ job/CAF-Generic/1206/] [.com:8080/ view/MultibranchPipeline/job/MyTeam/job/MyProject/job/master/65/ |http://jenkins.aveva.com:8080/view/CommonFramework/job/EDM%20Platform/job/caf/job/master/65/] - yields:{code:java}A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejava.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication$BuildLogIndicationDescriptor.doMatchText(BuildLogIndication.java:292) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:84
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50164 Renaming a job with non default build record directory makes old builds disappear Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48983) Artifactory Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Oleg Nenashev updated JENKINS-48983 The fix has been finally released in 2.15.0 Jenkins / JENKINS-48983 Artifactory Plugin is affected by JEP-200 in Jenkins 2.102+ Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.googl
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title Patrick Ruckstuhl commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository Having the same issue (with bitbucket branch source instead of github). I also tried to set it through one of the jobs with pipelineTriggers([[$class: 'PeriodicFolderTrigger', interval: '5m']]), But didn't work either. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Daniel Beck commented on JENKINS-50164 Re: Renaming a job with non default build record directory makes old builds disappear It was never a good idea to use the UI option while Jenkins was running. While the error could be new (which I doubt but whatever), just restarting Jenkins would have wiped all your previous build records. This should never have been a UI option, it's so insanely unsafe to use. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Daniel Beck commented on JENKINS-50164 Re: Renaming a job with non default build record directory makes old builds disappear Please try to confirm this actually worked in older releases before claiming regression. There's no indication here that this is new. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Daniel Beck edited a comment on JENKINS-50164 Re: Renaming a job with non default build record directory makes old builds disappear Please try to confirm this actually worked in older releases before claiming regression , or mention that you did so (and which release) . There's no indication here that this is new. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Oleg Nenashev commented on JENKINS-49715 Re: Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject We are still waiting for the release by Jeffrey Damick. Jenkins 2.107.1 will be released today, and there is a risk that the plugin will be broken after the release Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50151) Jenkins does not start if the content of the folder pointed by--webroot is deleted
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-50151 Jenkins does not start if the content of the folder pointed by--webroot is deleted Change By: Daniel Beck Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50135) Error while connecting from Slave to master
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, and not a support site. Please ask for help on the users mailing list or on IRC. Jenkins / JENKINS-50135 Error while connecting from Slave to master Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegro
[JIRA] (JENKINS-49589) Global Tools Config not opeing
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the reporter Jenkins / JENKINS-49589 Global Tools Config not opeing Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47734 Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Oleg Nenashev commented on JENKINS-47734 Re: Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 google.com is blocked in China at least IIRC. It seems to be a valid defect. CC Keith Zantow Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50164 Renaming a job with non default build record directory makes old builds disappear Change By: Baptiste Mathus Environment: Jenkins 2.110 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title
Patrick Ruckstuhl commented on JENKINS-48960
Re: Org folders repository folder never runs scans on repository
Found an easier workaround than to manually edit all the configs. Using the script console, this will change all the triggers to 5 minutes for the folders inside Organizations
for (f in Jenkins.instance.getAllItems(jenkins.branch.MultiBranchProject.class)) {
if (f.parent instanceof jenkins.branch.OrganizationFolder) {
f.addTrigger(new com.cloudbees.hudson.plugins.folder.computed.PeriodicFolderTrigger("5m"));
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47734 Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 Change By: Oleg Nenashev Labels: connection installationWizard Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50030) Job.getEstimatedDurationCandidates should not force loading of builds
Title: Message Title Daniel Beck commented on JENKINS-50030 Re: Job.getEstimatedDurationCandidates should not force loading of builds This is unreasonable—the UI should not be forcing build loading. Disagree. IIRC, estimated duration looks at the five newest builds, which isn't unreasonable. There'd just be useless unknown build duration estimates if this were implemented. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Oleg Nenashev edited a comment on JENKINS-47734 Re: Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 google.com is blocked in China at least IIRC. It seems to be a valid defect. We should be checking connectivity against Jenkins resources for sure. CC [~kzantow] [~danielbeck] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-47734 Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46534) Slave node connection fails Ubuntu server, windows slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-46534 Slave node connection fails Ubuntu server, windows slave Change By: Oleg Nenashev Component/s: remoting Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48358) Set cookies in Jenkins
Title: Message Title Oleg Nenashev resolved as Not A Defect This is not a helpdesk, sorry. Such questions should be asked in user mailing lists Jenkins / JENKINS-48358 Set cookies in Jenkins Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://group
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50164
Renaming a job with non default build record directory makes old builds disappear
Change By:
Baptiste Mathus
I think this was introduced by JENKINS-22936h3. How to reproduce* Start Jenkins 2.110* Create a job and run/create some builds* Change default "Build Record Root Directory" to {{ _ ${JENKINS_HOME}/var/${ITEM_FULL_NAME}/builds/ }} _ * Rename the job* Open a build created before the rename, it will show {{No such file: /var/jenkins_home/var/new_name/builds/2/log}}h3. Stack traceThere's the following stack trace when renaming:{noformat}Mar 14, 2018 9:29:03 AM hudson.model.Job$SubItemBuildsLocationImpl onLocationChanged SEVERE: Failed to move /var/jenkins_home/var/current_name/builds/ to /var/jenkins_home/var/new_name/builds java.io.FileNotFoundException: /var/jenkins_home/var/current_name/builds/lastFailedBuild (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138)at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230)at org.apache.commons.io.FileUtils.moveDirectory(FileUtils.java:2755)at hudson.model.Job$SubItemBuildsLocationImpl.onLocationChanged(Job.java:701)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:272)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:270)at hudson.model.listeners.ItemListener.forAll(ItemListener.java:180)at hudson.model.listeners.ItemListener.fireLocationChange(ItemListener.java:270)at hudson.model.AbstractItem.renameTo(AbstractItem.java:438)at hudson.model.Job.renameTo(Job.java:653)at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:261)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stap
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50164
Renaming a job with non default build record directory makes old builds disappear
Change By:
Baptiste Mathus
I think this was introduced by JENKINS-22936h3. How to reproduce* Start Jenkins 2.110* Create a job and run/create some builds* Change default "Build Record Root Directory" to _ " ${JENKINS_HOME}/var/${ITEM_FULL_NAME}/builds/ _ " * Rename the job* Open a build created before the rename, it will show {{No such file: /var/jenkins_home/var/new_name/builds/2/log}}h3. Stack traceThere's the following stack trace when renaming:{noformat}Mar 14, 2018 9:29:03 AM hudson.model.Job$SubItemBuildsLocationImpl onLocationChanged SEVERE: Failed to move /var/jenkins_home/var/current_name/builds/ to /var/jenkins_home/var/new_name/builds java.io.FileNotFoundException: /var/jenkins_home/var/current_name/builds/lastFailedBuild (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138)at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230)at org.apache.commons.io.FileUtils.moveDirectory(FileUtils.java:2755)at hudson.model.Job$SubItemBuildsLocationImpl.onLocationChanged(Job.java:701)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:272)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:270)at hudson.model.listeners.ItemListener.forAll(ItemListener.java:180)at hudson.model.listeners.ItemListener.fireLocationChange(ItemListener.java:270)at hudson.model.AbstractItem.renameTo(AbstractItem.java:438)at hudson.model.Job.renameTo(Job.java:653)at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:261)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Staple
[JIRA] (JENKINS-46534) Slave node connection fails Ubuntu server, windows slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-46534 Slave node connection fails Ubuntu server, windows slave Change By: Oleg Nenashev Labels: agents remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46534) Slave node connection fails Ubuntu server, windows slave
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-46534 Slave node connection fails Ubuntu server, windows slave Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48454) Simple jobs fails to complete
Title: Message Title Oleg Nenashev commented on JENKINS-48454 Re: Simple jobs fails to complete ping Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50058) while installing jenkins plugins are not coming jenkins apper offline
Title: Message Title Oleg Nenashev resolved as Incomplete Closing as incomplete.Please feel free to reopen if you are able to provide data for diagnostics Jenkins / JENKINS-50058 while installing jenkins plugins are not coming jenkins apper offline Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-50019 java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Change By: Daniel Beck Component/s: git-client-plugin Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49085) Request to JIRA webhook breaking pipeline
Title: Message Title Dmitriy Kagarlickij commented on JENKINS-49085 Re: Request to JIRA webhook breaking pipeline Wisen Tanasa I faced the same issue using Cloud version, but on-prem v7.2.12 works fine Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Ruud P updated an issue
Jenkins / JENKINS-37984
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Change By:
Ruud P
Comment:
I brake up the code but it did not help, so what i am doing wrong here? Anny solution available? oringinal:stages \{ stage('Test') \{ parallel \{ stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} . more as 200 change it into:stages \{ stage('Test') \{ maintest()}(in the same file i defined a function maintest with all the parallel stages)def maintest()parallel \{ stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} stage(bla1t') \{ when \{_expression_ bla}} steps \{node(label: 'bla') \{test('bla', '')}}} . more as 200
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49476) Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS)
Title: Message Title Oleg Nenashev commented on JENKINS-49476 Re: Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS) Iosif Bancioiu so, do you plan to provide the diagnostics info? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50164
Renaming a job with non default build record directory makes old builds disappear
Change By:
Baptiste Mathus
I think this was introduced by JENKINS-22936 h3. How to reproduce* Start Jenkins 2.110 * Create a job and run/create some builds* Change default "Build Record Root Directory" to "${JENKINS_HOME}/var/${ITEM_FULL_NAME}/builds/"* Rename the job* Open a build created before the rename, it will show {{No such file: /var/jenkins_home/var/new_name/builds/2/log}}h3. Stack traceThere's the following stack trace when renaming:{noformat}Mar 14, 2018 9:29:03 AM hudson.model.Job$SubItemBuildsLocationImpl onLocationChanged SEVERE: Failed to move /var/jenkins_home/var/current_name/builds/ to /var/jenkins_home/var/new_name/builds java.io.FileNotFoundException: /var/jenkins_home/var/current_name/builds/lastFailedBuild (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138)at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261)at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230)at org.apache.commons.io.FileUtils.moveDirectory(FileUtils.java:2755)at hudson.model.Job$SubItemBuildsLocationImpl.onLocationChanged(Job.java:701)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:272)at hudson.model.listeners.ItemListener$6.apply(ItemListener.java:270)at hudson.model.listeners.ItemListener.forAll(ItemListener.java:180)at hudson.model.listeners.ItemListener.fireLocationChange(ItemListener.java:270)at hudson.model.AbstractItem.renameTo(AbstractItem.java:438)at hudson.model.Job.renameTo(Job.java:653)at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:261)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invo
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Baptiste Mathus commented on JENKINS-50164 Re: Renaming a job with non default build record directory makes old builds disappear Good point. I (thought I) did, but wrongly it seems. Sigh. I can also reproduce this using 2.89.4... Lowering priority then. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) Renaming a job with non default build record directory makes old builds disappear
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50164 Renaming a job with non default build record directory makes old builds disappear Change By: Baptiste Mathus Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47734) Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2
Title: Message Title Daniel Beck closed an issue as Duplicate Jenkins / JENKINS-47734 Install Jenkins hangs indefinetly on Version 2.46.2 also in version 2.73.2 Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45997) BitBucket PRs failing to checkout on initial run after PR updated with new commits
Title: Message Title
Nicholas Brown commented on JENKINS-45997
Re: BitBucket PRs failing to checkout on initial run after PR updated with new commits
I think Justin Wojciechowski solution of having the Bitbucket Branch Source Plugin hit the CanMerge Rest API, to force the branch creations, is a good one. It need not even be a configuration option, Bitbucket Branch Source Plugin should simply do this every time it discovers PRs. In a some older Jenkins jobs I had, not making use of Bitbucket Branch Source Plugin, I had the same issue and used this horrid work around:
# Nasty hack to force Stash to generate the /merge branch for the PR
set +x
curl -u ${STASH_USER}:${STASH_PASSWORD} ${STASH_URL}/rest/api/1.0/projects/${destinationRepositoryOwner}/repos/${destinationRepositoryName}/pull-requests/${pullRequestId}/diff > /dev/null
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49699) Doktor plugin affected by JEP-200
Title: Message Title Siarhei Krukau commented on JENKINS-49699 Re: Doktor plugin affected by JEP-200 Sorry, not yet. I guess 44 installations are not very critical. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50165) NPE when trying to access several pages in the "Manage Jenkins" section
Title: Message Title Michael Stalker created an issue Jenkins / JENKINS-50165 NPE when trying to access several pages in the "Manage Jenkins" section Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-14 12:10 Environment: General Jenkins and OS Information == Jenkins ver. 2.73.1 OpenJDK Runtime Environment (build 1.8.0_151-b12) OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode) Scientific Linux release 7.1 (Nitrogen) Information from Jenkins's /systemInfo === * All plugins below are enabled. System Properties awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / guice.disable.misplaced.annotation.check true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_151-b12 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_151 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.151-b12 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna8873321459108692893.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-229.el7.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title Staffan Forsell commented on JENKINS-41488 Re: Pipeline view automatically scrolls down James Dumay I would also support a change to where the top of the page is the default. I typically find myself scrolling up even in a failed build, just to see which part of the build that failed and then scrolling down to get the step log. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46145) Groovy Traits are not supported
Title: Message Title
Piotr Paczyński commented on JENKINS-46145
Re: Groovy Traits are not supported
We're also affected by this issue. Because the error message was so weird, I've actually spent a lot of time figuring out why my pipeline shared library works fine under plain groovy, but not inside Jenkins. Is there any way to disable cps for my shared library or some other trick to make it work while keep using traits? A simple Jenkinsfile that can be used to reproduce the issue:
trait A {
def sayHello(script) {
script.echo "Hello"
}
}
class B implements A {}
new B().sayHello(this)
which results in:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
General error during canonicalization: [script]
java.lang.UnsupportedOperationException: [script]
at com.cloudbees.groovy.cps.CpsTransformer.visitArrayExpression(CpsTransformer.java:1179)
at org.codehaus.groovy.ast.expr.ArrayExpression.visit(ArrayExpression.java:88)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:341)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:347)
at com.cloudbees.groovy.cps.CpsTransformer$18.run(CpsTransformer.java:684)
at com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:430)
at com.cloudbees.groovy.cps.CpsTransformer.makeNode(CpsTransformer.java:393)
at com.cloudbees.groovy.cps.CpsTransformer.visitStaticMethodCallExpression(CpsTransformer.java:678)
at org.codehaus.groovy.ast.expr.StaticMethodCallExpression.visit(StaticMethodCallExpression.java:46)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:341)
at com.cloudbees.groovy.cps.CpsTransformer$48.run(CpsTransformer.java:1243)
at com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:430)
at com.cloudbees.groovy.cps.CpsTransformer.makeNode(CpsTransformer.java:393)
at com.cloudbees.groovy.cps.CpsTransformer.visitCastExpression(CpsTransformer.java:1239)
at com.cloudbees.groovy.cps.SandboxCpsTransformer.visitCastExpression(SandboxCpsTransformer.java:80)
at org.codehaus.groovy.ast.expr.CastExpression.visit(CastExpression.java:87)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:341)
at com.cloudbees.groovy.cps.CpsTransformer.visitExpressionStatement(CpsTransformer.java:572)
at org.codehaus.groovy.ast.stmt.ExpressionStatement.visit(ExpressionStatement.java:42)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:341)
at com.cloudbees.groovy.cps.CpsTransformer$10.run(CpsTransformer.java:564)
at com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:430)
at com.cloudbees.groovy.cps.CpsTransformer.makeNode(CpsTransformer.java:393)
at com.cloudbees.groovy.cps.CpsTransformer.visitIfElse(CpsTransformer.java:560)
at org.codehaus.groovy.ast.stmt.IfStatement.visit(IfStatement.java:43)
at com.cloudbees.groovy.cps.CpsTransformer.visit(CpsTransformer.java:341)
at com.cloudbees.groovy.cps.CpsTransformer$2.run(CpsTransformer.java:372)
at com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:430)
at com.cloudbees.groovy.cps.CpsTransformer.makeNode(CpsTransformer.java:393)
at com.cloudbees.groovy.cps.CpsTrans
[JIRA] (JENKINS-50166) Detect build interruption in plugin before the processes on the slave are killed
Title: Message Title Petres Andras created an issue Jenkins / JENKINS-50166 Detect build interruption in plugin before the processes on the slave are killed Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-03-14 12:26 Priority: Minor Reporter: Petres Andras Plugins may want to do custom action when the execution of a remote process is interrupted. Currently it is not possible, because the process started on a slave is killed on interruption. My actual use case: https://groups.google.com/forum/#!msg/jenkinsci-dev/s6IkynOzdqE/2eFNKN9lAAAJ A possible solution is to have a flag called dontKillWhenInterrupted which prevents process killing on the slave when set. Add Comment
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Daniel Spilker assigned an issue to PTC ALM Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Daniel Spilker Assignee: Daniel Spilker PTC ALM Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Daniel Spilker commented on JENKINS-49797 Re: IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM This is a problem in the integrity plugin. It doesn't handle a missing configuration gracefully. See https://github.com/jenkinsci/integrity-plugin/blob/integrity-plugin-2.1/src/main/java/hudson/scm/IntegritySCM.java#L166-L168. If serverConfig is set to a valid value, the problem should not occur. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Daniel Spilker Component/s: integrity-plugin Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37974) WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException
Title: Message Title Adrian Wyssmann commented on JENKINS-37974 Re: WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException The error is actually very annoying cause it fills the jenkins logfile extensively Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50167) Add support for environment variables
Title: Message Title David Sabin created an issue Jenkins / JENKINS-50167 Add support for environment variables Issue Type: Improvement Assignee: Aleksi Simell Components: influxdb-plugin Created: 2018-03-14 13:03 Priority: Minor Reporter: David Sabin Add the ability to use environment variables for the Custom Prefix and Custom Project Name. I'm trying to make a job that haves a parameter variable unique to a person using it, and I'd like that variable to be added as the prefix tag to the InfluxDB also, so the user can filter on their data in the database. This makes it more dynamic for having multiple users of the same Jenkins job. See https://stackoverflow.com/questions/30512887/variable-substitution-in-jenkins-plugin for some details. My thought is that adding the following lines to the beginning of InfluxDbPublisher.java:perform() final EnvVars env = build.getEnvironment(listener); String expandedCustomPrefix = env.expand(customPrefix); String expandedCustomProjectName = env.expand(customProjectName); Then use the new expanded variables for the rest of the function.I don't exactly know how to get the build and listener variables correct, but the link above should help. Add Comment
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Baptiste Mathus commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system As discussed yesterday, first draft submitted for review to the dev list: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/jenkinsci-dev/XdXuMFLXKPw (=> https://github.com/batmat/jep/pull/1) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title Mark Waite commented on JENKINS-50158 Re: Git plugin class LocalBranch needs to be serializable That syntax surprises me. It is quite different from the syntax provided by the "Pipeline Syntax" link that is available from PIpeline job pages. Steps I used: create a Pipeline library that performs a checkout with local branch Reference that Pipeline library from the Jenkinsfile in the JENKINS-50158 branch in my jenkins-bugs repository Watch that job run from the multi-branch Pipeline defined in my Docker image I'm not sure if the syntax you're using with the call to `new LocalBranch` is expected to run or not. I assume it is a surprise (to others) that it works in the Jenkinsfile and not in the library, but it is outside the expected use case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title
Mark Waite edited a comment on JENKINS-50158
Re: Git plugin class LocalBranch needs to be serializable
That syntax surprises me. It is quite different from the syntax provided by the "Pipeline Syntax" link that is available from PIpeline job pages.Steps I used to confirm that I can perform a checkout from inside a library:# create a [Pipeline library|https://github.com/MarkEWaite/jenkins-pipeline-utils/blob/branch-for-checkout-in-library/src/com/markwaite/Checkout.groovy] that performs a checkout with local branch# Reference that Pipeline library from the [Jenkinsfile in the JENKINS-50158 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-50158/Jenkinsfile] in my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/]# Watch that job run from the [multi-branch Pipeline|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/ref/jobs/Bugs-Pipeline-Checks/jobs/jenkins-bugs-multibranch-pipeline] defined in my [Docker image|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/Dockerfile]I'm not sure if the syntax you're using with the call to ` {{ new LocalBranch ` }} is expected to run or not. I assume it is a surprise (to others) that it works in the Jenkinsfile and not in the library, but it is outside the expected use case.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.c
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title Mark Waite edited a comment on JENKINS-50158 Re: Git plugin class LocalBranch needs to be serializable That syntax surprises me. It is quite different from the syntax provided by the "Pipeline Syntax" link that is available from PIpeline job pages.Steps I used to confirm that I can perform a checkout from inside a library :# create a [Pipeline library|https://github.com/MarkEWaite/jenkins-pipeline-utils/blob/branch-for-checkout-in-library/src/com/markwaite/Checkout.groovy] that performs a checkout with local branch# Reference that Pipeline library from the [Jenkinsfile in the JENKINS-50158 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-50158/Jenkinsfile] in my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/]# Watch that job run from the [multi-branch Pipeline|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/ref/jobs/Bugs-Pipeline-Checks/jobs/jenkins-bugs-multibranch-pipeline] defined in my [Docker image|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/Dockerfile]I'm not sure if the syntax you're using with the call to `new LocalBranch` is expected to run or not. I assume it is a surprise (to others) that it works in the Jenkinsfile and not in the library, but it is outside the expected use case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/opto
[JIRA] (JENKINS-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Ryan Campbell commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated Dave, do you have any log messages with the category org.jenkinsci.plugins.github.webhook? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50122) Incorrect permissions with non Multibranch based Pipeline jobs
Title: Message Title Brice Figureau commented on JENKINS-50122 Re: Incorrect permissions with non Multibranch based Pipeline jobs I've pushed a fix in PR#99 that happens to work for us. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50168) When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
Title: Message Title
Jeroen Smolenaers created an issue
Jenkins / JENKINS-50168
When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-client-plugin, git-plugin
Created:
2018-03-14 13:41
Environment:
jenkins version: 2.89.3 git plugin: 3.8.0 git client plugin version: 2.7.1
Labels:
regression pipeline scm git
Priority:
Minor
Reporter:
Jeroen Smolenaers
I have the following Jenkins Pipeline job:
Build Trigger: "Poll SCM"
Parametrized with String parameter "BRANCH", default value "master"
Definition is "Pipeline script from SCM" with Branch Specifier "$BRANCH", "Lightweight checkout" unchecked
Expected behaviour: The job polls SCM. When changes are detected in the branch specified in the default value of the BRANCH parameter ("master" in this case), the job is triggered. Actual behaviour: The job polls SCM, but it ONLY triggers the job when changes are detected in the branch that was last built. This causes the following issue: After I manually trigger the job with branch "develop", subsequent changes in branch "master" are ignored. This issue also manifests itself when Build Trigger: "Build when a change is pushed to BitBucket" is used. This seems to be a regre
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Jesse Glick assigned an issue to Daniel Spilker Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Jesse Glick Assignee: Daniel Spilker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Jesse Glick updated JENKINS-45860 Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50168) When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-50168 When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Jesse Glick started work on JENKINS-45860 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title Jesse Glick updated JENKINS-45860 Jenkins / JENKINS-45860 Support traits for ScmNavigators Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50168) When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
Title: Message Title Mark Waite commented on JENKINS-50168 Re: When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead As far as I can tell, JENKINS-27327 describes an issue in Freestyle jobs and this is an issue for polling in Pipeline jobs. They are quite different. Not a regression. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50168) When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-50168 When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead Change By: Mark Waite Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45928) Jenkins job crashes and dissapears when long running a checkmark security scan
Title: Message Title Colm O commented on JENKINS-45928 Re: Jenkins job crashes and dissapears when long running a checkmark security scan Slightly different context (different Jenkins instance), but this is still the same issue being manifested. We have a Jenkins pipeline submitting a Checkmarx task for the scannage of 3 related source code projects. The Checkmarx scan completes (within Checkmarx), but on the Jenkins side, the task locks up after the following output: [Checkmarx] - [info] - Scan Finished Successfully - RunID: 12650 ScanID:1001884 [Checkmarx] - [info] - Requesting XML Scan Report Generation [Checkmarx] - [info] - XML Report generation in progress [Checkmarx] - [info] - Scan report generated on Checkmarx server For comparison, in a different, but almost identically configured task, which is scans a different codebase, we see the following output: [Checkmarx] - [info] - XML Report generation in progress [Checkmarx] - [info] - Scan report generated on Checkmarx server [Checkmarx] - [info] - Scan report written to: /local/jenkins/jobs/<>/builds/40/checkmarx/ScanReport.xml [Checkmarx] - [info] - Requesting PDF Scan Report Generation [Checkmarx] - [info] - PDF Report generation in progress [Checkmarx] - [info] - Scan report generated on Checkmarx server [Checkmarx] - [info] - Scan report written to: /local/jenkins/jobs/<>/builds/40/checkmarx/ScanReport.pdf Note that in this example, the Jenkins instance does not fall over, but eventually all build executors are consumed by multiple instances of the same task, and subsequent tasks end up in the queue, instead of executing. Jenkins version: 2.109 Checkmarx plugin version: 8.60.0 Checkmarx version: 8.5.0 Add Comment
