[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 The / in the job name is because BitBucket leverages the Folders plugin, creating a folder for the project/repository, and then creating jobs inside that. As I mentioned above, it's the Folder part that does it, not the BitBucket part - I can reproduce it with a manual job placed in a manually created folder. I suspect the Github Organisation Folder has the same issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title kpop commented on JENKINS-41867 Re: Scanning MultiBranchProject fails with IllegalStateException The attached plugin also fixes the issue for me. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Michael Neale commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 It is quite normal to use foo/bar style branch names. Git and github branch source have no troubles with this (they encode it I guess before creating the job). Job names (which branches are) aren't meant to have '/' in them, but as showin in the PR above it is possible via the api, which bitbucket seems to be doing. This may be a case of "accidentally works"... in any case I am sure there is a solution somewhere, possibly even on the bitbucket plugin side. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title James Dumay commented on JENKINS-42200 Re: No valid crumb was included in the request in kubernetes Glad you were able to get a resolution! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title Jesse Haka closed an issue as Fixed Jenkins / JENKINS-42200 No valid crumb was included in the request in kubernetes Change By: Jesse Haka Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title Jesse Haka commented on JENKINS-42200 Re: No valid crumb was included in the request in kubernetes Hi Thanks, now it works. I enabled also "Enable proxy compatibility" which was needed in order to work properly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30382) TFS plug-in 4.0.0 NumberFormatExceptions
Title: Message Title ahmed daniel commented on JENKINS-30382 Re: TFS plug-in 4.0.0 NumberFormatExceptions I think I have seen this same issue on tfs-plugin 4.0 and upgrading it to newer version changes the issue to something like below. The slave machine is windows 7 64 bit and tfs plugin version 5.3.1. Both issues occurr randomly for me. Building remotely on BuildMachine (VisualStudio) in workspace c:\Jenkins\InteractiveLibraries FATAL: java.lang.NumberFormatException: For input string: "" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "" at hudson.plugins.tfs.model.Server.execute(Server.java:226) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:275) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:271) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:287) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:359) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:308) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.NumberFormatException: For input string: "" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-21460) TFS plugin throws NumberFormatException
Title: Message Title ahmed daniel commented on JENKINS-21460 Re: TFS plugin throws NumberFormatException I have a samilar issue but mine comes randomly on builds which were working fine before and disappears the next time I run the same job without making any changes. I have the collections appended in TFS server URL in Jenkins. Building remotely on BuildMachine (VisualStudio) in workspace c:\Jenkins\InteractiveLibraries FATAL: java.lang.NumberFormatException: For input string: "" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "" at hudson.plugins.tfs.model.Server.execute(Server.java:226) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:275) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:271) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:287) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:359) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:308) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Long.parseLong(Unknown Source) at java.lang.Long.parseLong(Unknown Source) at java.text.DigitList.getLong(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:285) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:365) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.(DateVersionSpec.java:51) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:197) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:59) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:85) at java.lang.Thread.run(Unknown Source) at ..remote call to BuildMachine(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:781) at hudson.plugins.tfs.model.Server.execute(Server.java:222) ... 13 more
[JIRA] (JENKINS-42214) Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static
Title: Message Title Reinhold Füreder commented on JENKINS-42214 Re: Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static Well, I claim that the current entries are just wrong then. And since I am actually needing and actively using such static field whitelist entries in other contexts (e.g. "staticField hudson.model.Result FAILURE", cf. JENKINS-35352) with success, I was pretty confident that this would help here as well... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42197) Job import plugin refreshes the page after clicking on "Query" button
Title: Message Title Darshan Deshmukh assigned an issue to Valentin Marin Jenkins / JENKINS-42197 Job import plugin refreshes the page after clicking on "Query" button Change By: Darshan Deshmukh Assignee: Darshan Deshmukh Valentin Marin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42197) Job import plugin refreshes the page after clicking on "Query" button
Title: Message Title Darshan Deshmukh assigned an issue to Darshan Deshmukh Jenkins / JENKINS-42197 Job import plugin refreshes the page after clicking on "Query" button Change By: Darshan Deshmukh Assignee: Darshan Deshmukh Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42197) Job import plugin refreshes the page after clicking on "Query" button
Title: Message Title Darshan Deshmukh commented on JENKINS-42197 Re: Job import plugin refreshes the page after clicking on "Query" button @ Valentin Marin - It takes some time to import the jobs from the destination Jenkins instance. When I refreshed the page again I started seeing those jobs. To be very specific you need to wait for approx. 5-7 mins after clicking "Query" button, if still you are not seeing the jobs then try to refresh the page by clicking on "Job Import Plugin' link. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42242) SauceLabs results not displayed on Blue Ocean
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-42242 SauceLabs results not displayed on Blue Ocean Issue Type: Improvement Assignee: Gavin Mogan Components: blueocean-plugin, sauce-ondemand-plugin Created: 2017/Feb/22 5:16 AM Priority: Minor Reporter: Liam Newman Similar to JENKINS-40616. See the Jenkinsfile in https://github.com/bitwiseman/JS-Nightwatch.js/tree/issue/declarative/sauceConnectPublish The saucelabs results are recorded and viewable in stage view but not in Blue Ocean. Add Comment
[JIRA] (JENKINS-42001) Blue Ocean logo should be Jenkins
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-42001 Blue Ocean logo should be Jenkins Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41823) SMTP server showing unknown host name
Title: Message Title mani sirasapalli commented on JENKINS-41823 Re: SMTP server showing unknown host name Stephen Connolly i am using jenkins version 1.581 and also having same issue. Can you help us please Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42001) Blue Ocean logo should be Jenkins
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-42001 Blue Ocean logo should be Jenkins Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42001) Blue Ocean logo should be Jenkins
Title: Message Title Brody Maclean commented on JENKINS-42001 Re: Blue Ocean logo should be Jenkins Zeplin link with exportable svg https://zpl.io/Z1BVpq3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42001) Blue Ocean logo should be Jenkins
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-42001 Blue Ocean logo should be Jenkins Change By: Brody Maclean Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42204) Scan of git pipeline fails with NPE due to recent GitSCMSource change
Title: Message Title Mark Waite commented on JENKINS-42204 Re: Scan of git pipeline fails with NPE due to recent GitSCMSource change I was able to run your change in a later version of that docker instance tonight. It passed the check described in this bug report, bug fails with a null pointer exception when scanning the "jenkins-bugs-bitbucket" repository. The stack trace is: Started by user anonymous [Tue Feb 21 21:36:19 MST 2017] Starting branch indexing... > git rev-parse --is-inside-work-tree # timeout=11 Setting origin to https://bitbucket.org/markewaite/jenkins-bugs.git > git config remote.origin.url https://bitbucket.org/markewaite/jenkins-bugs.git # timeout=11 Fetching & pruning origin... Fetching upstream changes from origin > git --version # timeout=11 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune Getting remote branches... Seen branch in repository origin/JENKINS-39905 Seen 1 remote branch Checking branch JENKINS-39905 ERROR: [Tue Feb 21 21:36:20 MST 2017] Could not fetch branches from source 542506ca-b4e4-4721-a50f-e301e193846e java.lang.NullPointerException at jenkins.plugins.git.AbstractGitSCMSource.getPattern(AbstractGitSCMSource.java:458) at jenkins.plugins.git.AbstractGitSCMSource.isExcluded(AbstractGitSCMSource.java:447) at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:256) at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:242) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:212) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:242) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:300) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:210) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:219) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:141) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:973) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) [Tue Feb 21 21:36:20 MST 2017] Finished branch indexing. Indexing took 0.58 sec FATAL: Failed to recompute children of Bugs - Pipeline Checks » jenkins-bugs bitbucket java.lang.NullPointerException at jenkins.plugins.git.AbstractGitSCMSource.getPattern(AbstractGitSCMSource.java:458) at jenkins.plugins.git.AbstractGitSCMSource.isExcluded(AbstractGitSCMSource.java:447) at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:256) at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:242) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:212) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:242) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:300) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:210) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:219) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:141) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:973) at
[JIRA] (JENKINS-41242) Blue Ocean views should include versions in footer
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41242 Blue Ocean views should include versions in footer Change By: James Dumay Summary: Blue Ocean views should include core version versions in footer Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42241) duplicate Ids in table
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-42241
duplicate Ids in table
Change By:
Michael Neale
If you setup a multibranch project with at least 2 branches, run them, you will see items in the activity table that have the same element id (use chrome inspector). The element id seems to be of the form: {pipelinename}-{run id}When it should include branch in there. As you can have multiple runs for different branches, but they wil have same pipeline and run id: !Screen Shot 2017-02-22 at 3.13.10 pm.png|thumbnail! This could upset some tools or browsers. The id may not be needed.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42241) duplicate Ids in table
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-42241
duplicate Ids in table
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2017-02-22 at 3.13.10 pm.png
Components:
blueocean-plugin
Created:
2017/Feb/22 4:22 AM
Priority:
Minor
Reporter:
Michael Neale
If you setup a multibranch project with at least 2 branches, run them, you will see items in the activity table that have the same element id (use chrome inspector). The element id seems to be of the form: {pipelinename} - {run id} When it should include branch in there. As you can have multiple runs for different branches, but they wil have same pipeline and run id.
Add Comment
[JIRA] (JENKINS-42241) duplicate Ids in table
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42241 duplicate Ids in table Change By: Michael Neale Attachment: Screen Shot 2017-02-22 at 3.13.10 pm.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42241) duplicate Ids in table
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-42241
duplicate Ids in table
Change By:
Michael Neale
If you setup a multibranch project with at least 2 branches, run them, you will see items in the activity table that have the same element id (use chrome inspector). The element id seems to be of the form: {pipelinename}-{run id}When it should include branch in there. As you can have multiple runs for different branches, but they wil have same pipeline and run id : !Screen Shot 2017-02-22 at 3 . 13.10 pm.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41619) NPE in Pipeline Step after update
Title: Message Title Suresh Kumar commented on JENKINS-41619 Re: NPE in Pipeline Step after update From v2.8 included capability of adding multiple artifacts and there is change in the configuration, we have to reconfigure the build step after upgrading. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41611) Update pipeline node designs
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-41611 Update pipeline node designs Change By: James Dumay Assignee: James Dumay Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41611) Update pipeline node designs
Title: Message Title James Dumay commented on JENKINS-41611 Re: Update pipeline node designs Brody Maclean any hover states or anything like that we should know about? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41611) Update pipeline node designs
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-41611 Update pipeline node designs Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41611) Update pipeline node designs
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41611 Update pipeline node designs Change By: Brody Maclean Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41611) Update pipeline node designs
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41611 Update pipeline node designs Change By: Brody Maclean *Scope** UI & interaction design for nodes* We want this variant ! Pipeline Editor 2017 screenshot - 02-06 10-26-24 1 .png |thumbnail ! http://codepen.io/brody/pen/JEMGWz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Xiaoming Wang commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I get this more and more recently either during git submodule or cmake build. I tried 2.32, 2,38, 2.45 and 2.46. All the same. Redirect stdout/stderror of console may help a little. For the same Windows slave it run OK with old Jenkins, such as Jenkins 1.6.x Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42240) Modify Build Environment Order execution
Title: Message Title
Eyzen Medina commented on JENKINS-42240
Re: Modify Build Environment Order execution
In the screen shoot you can see, the JIRA Release notes action will be executed before that the environment variable is created, I'm creating the environment variable $ {JiraBuild} from the build.property file and should be loaded from the repository. I need to run first "Inject environment variables" and then the other plugins actions. I believe JENKIINS run actions ordered by name in this section; Instead of set the name of the action to "Inject environment variables to the build process" could be changed to a name starting with the letter "A" could be "Add/Inject environment variables to the build process". Don't know if this could make this action to be placed on top of the list.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title Nikolas Falco commented on JENKINS-42232 Re: Node executable is not begin initialised on slave node ASAP I will release the 1.1.2 and I will update the workaround branch accordingly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-42232 Node executable is not begin initialised on slave node Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42232 Re: Node executable is not begin initialised on slave node Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java src/test/java/jenkins/plugins/nodejs/tools/NodeJSInstallationTest.java http://jenkins-ci.org/commit/nodejs-plugin/dc4e2946d34cd2a0a773aaf80688c8df42d7e4bf Log: [FIX JENKINS-42232] Fix node executable not initialised on slave node where Computer.currentComputer was null. In case current computer is null platform is calculated on the current system properties, that it is also the case of MasterToSlave callable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title Nikolas Falco started work on JENKINS-42232 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-42232 Node executable is not begin initialised on slave node Change By: Nikolas Falco Summary: Node executable is not begin initialised on branch workaround-26583 slave node Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable is not begin initialised on slave node
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-42232 Node executable is not begin initialised on slave node Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41941) Add credentials data to API for "permissions"
Title: Message Title Vivek Pandey updated JENKINS-41941 Jenkins / JENKINS-41941 Add credentials data to API for "permissions" Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dan Russell commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Reverted to: github-branch-source 2.0.3 branch-api 2.0.6 github-api 1.84 cloudbees-folder 5.17 And all my folders are displaying as expected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dan Russell edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Reverted to and all my folders are displaying as expected :* github-branch-source 2.0.3* branch-api 2.0.6* github-api 1.84* cloudbees-folder 5.17 And all my folders are displaying as expected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title
Dan Russell commented on JENKINS-36121
Re: Github Branch Source plugin trips api rate limit
I have setup my Jenkins instance with 11 GitHub Organization folders and 2 "normal" Folders. My company is divided into 11 sub-teams ("verticals"), and I use a regex to identify which GitHub repos in our company are mapped to each "vertical". After installing these plugins, my 2 "normal" folders load, one of my GitHub Organization Folders loads, and the remaining 10 GitHub Organization Folders fail to load. `jenkins.log` has this for each of the 10 failed-to-load folders: ``` (lots of these, one for each repo + branch which exists on the filesystem. Inspection by hand confirms config.xml is not there) Feb 22, 2017 1:18:57 AM com.cloudbees.hudson.plugins.folder.AbstractFolder loadChildren WARNING: could not find file /var/lib/jenkins/jobs/operations_vertical/jobs/chef-repo/branches/typography-nerd/config.xml Feb 22, 2017 1:18:57 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading item analytics_vertical java.lang.NullPointerException at jenkins.branch.OrganizationFolder.onLoad(OrganizationFolder.java:185) at hudson.model.Items.load(Items.java:372) at jenkins.model.Jenkins$17.run(Jenkins.java:3060) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1064) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ``` I just updated to the SCM 2.x series yesterday; everything had seemed to be working OK before I tried these attached plugins, but it's possible the 1.x to 2.x update left things in a fragile or broken state, and I didn't noticed until now. I'm going to try to uninstall these experimental plugins and get back to a working Jenkins instance. I've preserved all my logs if you'd like more details.
Add Comment
[JIRA] (JENKINS-38751) run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38751 run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job Change By: James Dumay *Do not start this work if the new headers are not on master**Scope** Add the "exit to classic" link to both the header of application and to the run modal* App header* !AJAX Fail.png|thumbnail! *Run header* !screenshot-1.png|thumbnail! * Original request*If I navigate to a Pipeline, deep within a GitHub Organization Folder, it's impossible to quickly get to the "classic" UI with my current browsing context.If I want to get from a detail page for a pull request run, I need to open a new window, click the folder, click the repository, click pull requests, click the appropriate pull request job, then click the build number.It would be nicer if there was a little link in the header of the detail page which allowed me to "view in classic" or something like that. That way I could easily go from [this detail view|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-2577/2] to [this classic page|https://ci.jenkins.io/job/Core/job/jenkins/view/Pull%20Requests/job/PR-2577/2/] without wanting to flip my desk. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly In the nginx access logs, I see the following when I reload a project page: 172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/a4338d24-8ef6-4b36-a45e-dba6f4b8139f/render HTTP/1.1" 403 305 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806" 172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/ab8ee004-37cc-4e2b-8d49-3802040cdf60/render HTTP/1.1" 403 304 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806" Those are the only 403s I see on the page load, everything else is 200. There are no entries in the nginx error.log. In the jenkins.log, I get these messages: Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a. Will check remaining parameters for a valid one... Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /$stapler/bound/d29a127d-6455-4b93-80b3-653dc55aeaa7/render. Returning 403. Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a. Will check remaining parameters for a valid one... Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /$stapler/bound/8ff58aec-9694-4c5f-b3a3-4906160a9176/render. Returning 403. I can capture the full HTTP request/response cycle with Charles if that'd be helpful. Add Comment
[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly I can get things working again properly if I turn "Prevent Cross Site Request Forgery exploits" OFF on the "Configure Global Security" page. If I turn it on, the only option I have for "Crumb Algorithm" is "Default Crumb Issuer". So I select that and then it doesn't matter if I have "Enable proxy compatibility" checked or not, I see the same failure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38751) run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38751 run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job Change By: Brody Maclean Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38751) run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Brody Maclean commented on JENKINS-38751 Re: run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job Run screen https://invis.io/Q2A110KM9#/194503320_Success https://zpl.io/1MtiWN Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly No, I'm using the same URL that's set in Configure System. I am using nginx in front of Jenkins running as a stand-alone application (i.e. not as a war in Tomcat), but I don't have the broken reverse proxy message. I just updated to 2.47, cleared my cookies and cache, and am still seeing the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Vivek Pandey assigned an issue to Vivek Pandey Jenkins / JENKINS-41425 Refreshing page with / in job name results in 404 Change By: Vivek Pandey Assignee: Tom FENNELLY Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/LastBuildNodeColumn.java http://jenkins-ci.org/commit/extra-columns-plugin/550a45648f5688ffd20b3ca55ffe4314a2e02557 Log: JENKINS-40477 - get rid of ClassCastException Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41870) Update duration format
Title: Message Title Ivan Meredith started work on JENKINS-41870 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41870) Update duration format
Title: Message Title Ivan Meredith updated JENKINS-41870 Jenkins / JENKINS-41870 Update duration format Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G closed an issue as Won't Fix Jenkins / JENKINS-40477 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Change By: Fred G Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Thanks Jesse for the feedback. I will fix the ClassCastException, but since I currently don't see a nice way to show (potentially) more than one build node in a column, I won't implement this. If someone has an idea how this can be done in a reasonable way, I'm looking forward to their pull request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning
Title: Message Title Daniel Beck commented on JENKINS-42235 Re: Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning Should probably just discard root loggers with ALL/FINEST/FINER/FINE level, or force their level to a higher (i.e. less verbose) one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36632) Pipeline support
Title: Message Title Fred G commented on JENKINS-36632 Re: Pipeline support Thanks for the feedback Jesse. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Cliff Meyers commented on JENKINS-40206 Re: Eliminate shrinkwrap pain To add to the prior point, my recollection is that since shrinkwrap holds fully-qualified URL's to each artifact, the registry being used at the time of shrinkwrapping in what npm will use. We had experimented with doing a search/replace for the main registry path in shrinkwrap.json which I believe did work - perhaps Yoann Dubreuil can confirm. However it's not great since a CI build would behave differently from the user's local machine, unless each developer configured their npmrc file to use the same registry. My recollection is that Yarn wouldn't have this problem, as the Lockfiles do not specify URL's and I know it supports registries (see: https://github.com/yarnpkg/yarn/issues/606 ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Jesse Glick commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Found it—I was just missing anon-access = none, as noted here and elsewhere. With that the test passes, including changelog of externals using additionalCredentials. As an aside, if you get the password wrong for the main checkout, you get a cryptic “authentication cancelled” message, whereas a wrong password in additional credentials causes the externals to just quietly be omitted. Not sure if this is all just poor behavior in SVNKit or what. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42238) API for listing repositories in creation should include the default branch
Title: Message Title Michael Neale resolved as Fixed Jenkins / JENKINS-42238 API for listing repositories in creation should include the default branch Change By: Michael Neale Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Jesse Glick commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Hmm, a have a test which is now producing a different error (but only from changelog calculation, not the actual update): hudson.util.IOException2: revision check failed on svn://…/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at … Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E220001: Item is not readable at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:68) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:269) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:276) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1311) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:843) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1038) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194) ... 12 more Still trying to figure out what that might mean. JENKINS-27231? Add Comment
[JIRA] (JENKINS-41870) Update duration format
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41870 Update duration format Change By: James Dumay Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41434) Restrict access to Creation Flow for users with insufficient permissions
Title: Message Title Cliff Meyers commented on JENKINS-41434 Re: Restrict access to Creation Flow for users with insufficient permissions The permissions data is already being written into the page via the preloader stuff, so it's available without a separate REST fetch. However, in core-js, the User object is wrapping this data, and explicitly exposing a known list of properties. This is probably bad for extensibility and probably a maintenance headache. We probably just want to Object.assign(this, blueUser) and call it a day Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41597) Git Creation flow eager validation in UI
Title: Message Title Michael Neale started work on JENKINS-41597 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41434) Restrict access to Creation Flow for users with insufficient permissions
Title: Message Title Ivan Meredith started work on JENKINS-41434 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41597) Git Creation flow eager validation in UI
Title: Message Title Ivan Meredith stopped work on JENKINS-41597 Change By: Ivan Meredith Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title Reece Casey commented on JENKINS-33182 Re: Checking "This build is parameterized" but having no parameters throws a NullPointerException This is happening because you have not setup any params. You do not need to tick this to use the env vars that come from git. This issue is not related to the plugin, Jenkins doesn't deal with no params correctly when this is ticked, its a global Jenkins issue. However, it wont happen if you don't tick the box. Reece Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41096) Only show admin link in header if the user has privileges
Title: Message Title Ivan Meredith stopped work on JENKINS-41096 Change By: Ivan Meredith Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42206) No selection state for "where do you store your code"
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42206 No selection state for "where do you store your code" Change By: James Dumay Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42179 Re: withMaven doesn't discover the released artifacts when executing "mvn release" Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/pom.xml jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/3952f7fb1071a4dd5025dab853ac54de56dc7166 Log: JENKINS-42179 use the JAVA_TOOL_OPTIONS environment variable to pass `-Dmaven.ext.class.path` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42221) MSBuild parser takes unreasonable amount of time
Title: Message Title Ulli Hafner commented on JENKINS-42221 Re: MSBuild parser takes unreasonable amount of time After fixing several issues the MS build parser regular _expression_ seems to be overly complex now. I think this is the problem. You can try to pipe the output of the compile steps into files and use the parser only on the corresponding files too speed up things... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42179 Re: withMaven doesn't discover the released artifacts when executing "mvn release" Code changed in jenkins User: Alvaro Lobato Path: jenkins-plugin/pom.xml jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/50291c9c7878f5899065731c14d446f7e1d7546c Log: Merge pull request #19 from cyrille-leclerc/JENKINS-42179 JENKINS-42179 use the JAVA_TOOL_OPTIONS environment variable to pass `-Dmaven.ext.class.path` Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/fa0f35294292...50291c9c7878 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42240) Modify Build Environment Order execution
Title: Message Title Eyzen Medina created an issue Jenkins / JENKINS-42240 Modify Build Environment Order execution Issue Type: Bug Assignee: Oleg Nenashev Attachments: action_order.PNG Components: envinject-plugin Created: 2017/Feb/21 9:57 PM Environment: JENKINS Linux Master with slaves Labels: order execution Priority: Minor Reporter: Eyzen Medina Hi I really don't know if this was fixed or exist a way to set the execution order of the different plugins in JENKINS. I wan to set multiple environment variables using a property file from my repository, i have set the property file to load in Build Environment section, but one of the action i want to tdo is generate JIRA release notes based in one of the env variable. The issue i'm having is that the JIRA plugins runs before than the "Inject environment variables to the build process". Exists any way to move the execution of "Inject environment variables to the build process" as a first action of the "Build Environment" section of JENKINS. The nature of this plugins is to execute before any other plugin to set the environment, now is useless with other actions. I'm providing a screen shoot in order to visualize my problem. Will be great to run this plugin action at the beginning of the "Build Environment" JENKINS section. Regards
[JIRA] (JENKINS-42239) When there is a conflict from saving a Jenkinsfile we should include the new sha
Title: Message Title James Dumay resolved as Won't Do Jenkins / JENKINS-42239 When there is a conflict from saving a Jenkinsfile we should include the new sha Change By: James Dumay Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42239) When there is a conflict from saving a Jenkinsfile we should include the new sha
Title: Message Title James Dumay created an issue Jenkins / JENKINS-42239 When there is a conflict from saving a Jenkinsfile we should include the new sha Issue Type: Task Assignee: Vivek Pandey Components: blueocean-pipeline-editor-plugin Created: 2017/Feb/21 9:53 PM Priority: Critical Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-41597) Git Creation flow eager validation in UI
Title: Message Title Ivan Meredith started work on JENKINS-41597 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41597) Git Creation flow eager validation in UI
Title: Message Title Ivan Meredith assigned an issue to Ivan Meredith Jenkins / JENKINS-41597 Git Creation flow eager validation in UI Change By: Ivan Meredith Assignee: Cliff Meyers Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42238) API for listing repositories in creation should include the default branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42238 API for listing repositories in creation should include the default branch Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42238) API for listing repositories in creation should include the default branch
Title: Message Title James Dumay created an issue Jenkins / JENKINS-42238 API for listing repositories in creation should include the default branch Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Feb/21 9:45 PM Priority: Minor Reporter: James Dumay When returning the list of repositories from Github the response should include the name of the default branch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42237) Add a label per indicator
Title: Message Title Adam L created an issue Jenkins / JENKINS-42237 Add a label per indicator Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2017/Feb/21 9:41 PM Environment: jenkins 1.658 BFA 1.17.2 Priority: Minor Reporter: Adam L When reporting the build failure reasons, currently all that is shown is the cause group name, and "Indication 1". It would be useful to have a label for each indication added to a cause and display that instead. This would provide a much more useful analysis to the end user. Thank you. Add Comment
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Nadav Goldin commented on JENKINS-38268
Re: Parallel step and closure scope
Jesse Glick, thanks! I changed the code to simple for loops without iterators , and without '@NonCPS' and it seems to work . A small gotcha I encountered is that the looping variable needs to be aliased, otherwise only the last variable will be sent to all closures(unlike when using iterators, I think). For reference, here is the code that does work:
def get_dummy_params(val)
{
return [string(name: 'dummy', value: "$val")]
}
def create_jobs()
{
def jobs = [:]
for (int i=1; i <= 3; i++) {
def x = i
jobs["job-$x"] = { -> build([job: "job-$x", parameters: get_dummy_params(x) ]) }
}
return jobs
}
stage ('triggering') {
parallel(create_jobs())
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title James Dumay updated JENKINS-35768 Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23284) Get value of all parameters in the database
Title: Message Title Adam L commented on JENKINS-23284 Re: Get value of all parameters in the database This request was made almost 3 yrs ago. Check out: https://wiki.jenkins-ci.org/display/JENKINS/Audit+To+Database+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42236) SCMEventImpl should check isMatch() conditions in heads() method
Title: Message Title Stephen Connolly started work on JENKINS-42236 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title James Dumay edited a comment on JENKINS-42200 Re: No valid crumb was included in the request in kubernetes I believe this is because you have not [generated a CSRF token and used that in your API requests|https://support.cloudbees.com/hc/en-us/articles/219257077-CSRF-Protection-Explained]. CSRF was enabled by default in Jenkins 2.0. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title James Dumay commented on JENKINS-42200 Re: No valid crumb was included in the request in kubernetes I believe this is because you have not generated a CSRF token and used that in your API requests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-42235 Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Feb/21 9:17 PM Priority: Major Reporter: Owen Mehegan As I learned the hard way, the Jenkins log recorder UI makes it easy for you to accidentally create an unfiltered recorder with a log level of 'ALL' (because that is the default level), and this will easily overwhelm and take down Jenkins if it is under normal load. In my case the only way to recover was to find the log recorder config XML file on the filesystem, move it aside, and restart Jenkins. This caused an unpleasant 25 minute production outage for us. I would propose that if the user attempts to create an empty recorder at level ALL we should throw a warning dialog, explaining that this configuration can be dangerous, and give them the option to back out. Alternatively, maybe the default level should be SEVERE rather than ALL, so that if you accidentally create an unfiltered recorder it won't log much. Daniel Beck you want to comment on this? I can make an attempt at implementation if you think the logic is sound. Add
[JIRA] (JENKINS-42234) Missing guard call to isMatch when processing update events
Title: Message Title Stephen Connolly updated JENKINS-42234 Jenkins / JENKINS-42234 Missing guard call to isMatch when processing update events Change By: Stephen Connolly Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41942) Show loading animation
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41942 Show loading animation Change By: James Dumay Sprint: up next 1.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42236) SCMEventImpl should check isMatch() conditions in heads() method
Title: Message Title Stephen Connolly updated JENKINS-42236 Jenkins / JENKINS-42236 SCMEventImpl should check isMatch() conditions in heads() method Change By: Stephen Connolly Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42200 No valid crumb was included in the request in kubernetes Change By: James Dumay Component/s: core Component/s: blueocean-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42236) SCMEventImpl should check isMatch() conditions in heads() method
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-42236 SCMEventImpl should check isMatch() conditions in heads() method Issue Type: Bug Assignee: Stephen Connolly Components: git-plugin Created: 2017/Feb/21 9:20 PM Priority: Minor Reporter: Stephen Connolly Related to JENKINS-42234 as it was causing the triggering Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-42235 Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning Change By: Owen Mehegan As I learned the hard way, the Jenkins log recorder UI makes it easy for you to accidentally create an unfiltered recorder with a log level of 'ALL' (because that is the default level), and this will easily overwhelm and take down Jenkins if it is under normal load. In my case the only way to recover was to find the log recorder config XML file on the filesystem, move it aside, and restart Jenkins. This caused an unpleasant 25 minute production outage for us.I would propose that if the user attempts to create an empty recorder at level ALL we should throw a warning dialog, explaining that this configuration can be dangerous, and give them the option to back out.Alternatively, maybe the default level should be SEVERE rather than ALL, so that if you accidentally create an unfiltered recorder it won't log much.[~danielbeck] do you want to comment on this? I can make an attempt at implementation if you think the logic is sound. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42234) Missing guard call to isMatch when processing update events
Title: Message Title Stephen Connolly started work on JENKINS-42234 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42234) Missing guard call to isMatch when processing update events
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-42234 Missing guard call to isMatch when processing update events Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Feb/21 9:16 PM Priority: Minor Reporter: Stephen Connolly https://github.com/jenkinsci/branch-api-plugin/blob/81e9fe59aef2329e0613c58fb4d66166c7406edd/src/main/java/jenkins/branch/MultiBranchProject.java#L1321-L1329 is missing a guard on SCMEvent.isMatch(SCMSource) so implementations that have overridden the default behaviour can end up with false triggers. Add Comment
[JIRA] (JENKINS-42233) Missing "Scriptler Script" step
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-42233 Missing "Scriptler Script" step Change By: Rick Liu Attachment: Selection_011.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42233) Missing "Scriptler Script" step
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-42233 Missing "Scriptler Script" step Change By: Rick Liu Attachment: Selection_010.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42233) Missing "Scriptler Script" step
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-42233 Missing "Scriptler Script" step Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin, run-condition-plugin Created: 2017/Feb/21 9:11 PM Environment: Jenkins v2.32.1 Conditional BuildStep v1.3.5 Run Condition Plugin v1.0 Priority: Major Reporter: Rick Liu Under drop-down menu for "Add step to condition", it doesn't have "Scriptler Script" Step. Add Comment
[JIRA] (JENKINS-42217) Post-build-email directs to all-changes page instead of detailed build ID page
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42217 Post-build-email directs to all-changes page instead of detailed build ID page Moving into sprint for investigation Change By: James Dumay Sprint: 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42217) Post-build-email directs to all-changes page instead of detailed build ID page
Title: Message Title James Dumay commented on JENKINS-42217 Re: Post-build-email directs to all-changes page instead of detailed build ID page Hi Ben Ruopp, Are we linking to the wrong page or are you asking about the ?changes query parameter? Depending on your preference (classic or Blue Ocean) sometimes plugins want to link to the page that shows all the changes for a run. On classic this is at the job level and on Blue Ocean this is at the run level in the UI. Thanks James Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42232) Node executable not initialised on branch workaround-26583
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-42232
Node executable not initialised on branch workaround-26583
Change By:
Alexander Komarov
I followed the workaround recommendation in JENKINS-41848 since I have env-inject plugin (and rely heaviliy on it) and "Provide npm to $PATH" did not work.With the workaround-26583 branch, $PATH issue has been addressed, but now the node build steps don't work. I have no global npm modules configured in tool config (and no spaces in the field either). !Screenshot_2017-02-21_13-57-04.png|thumbnail! If I add an invalid value to global npm modules (ie comma-delimited: phantomjs,pnpm,gulp), I get an error running npm. Otherwise, I get the stacktrace below (even when I have valid global npm modules specified){quote}FATAL: command execution failedjenkins.plugins.nodejs.tools.DetectionFailedException: Cannot get installation for node, since it is not online at jenkins.plugins.nodejs.tools.NodeJSInstallation.getPlatform(NodeJSInstallation.java:178) at jenkins.plugins.nodejs.tools.NodeJSInstallation.access$000(NodeJSInstallation.java:64) at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:128) at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:123) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Channel to /10.130.221.2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1435) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:795) at jenkins.plugins.nodejs.tools.NodeJSInstallation.getExecutable(NodeJSInstallation.java:123) at jenkins.plugins.nodejs.NodeJSCommandInterpreter.perform(NodeJSCommandInterpreter.java:106) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:65) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)ERROR: Build step failed with exceptionjava.lang.IllegalStateException: Node executable not
