[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title
Marlon Cenita created an issue
Jenkins / JENKINS-42428
Jenkins master throwing java.io.IOException when running pipeline in swarm client
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
pipeline, swarm-plugin
Created:
2017/Mar/02 3:49 AM
Environment:
Master: Jenkins Version : 2.32.2 Running on Windows Server 2012 R2 Client: Swarm Client 3.3 on AIX 7.1 / JDK 8
Labels:
jenkins pipeline swarm
Priority:
Minor
Reporter:
Marlon Cenita
Im trying to run a pipeline job in an agent which is using swarm client. The job runs fine but im getting a lot of error messages in the log like below:
Cannot contact tst_db2: java.io.IOException: Remote call on Channel to /XX.XX.XX.XXX failed
(actual IP address replaced with XX) In my observation the master is throwing this errors while waiting for the script that is running in the client. Again, the pipeline job run perfectly except that im getting this error on the pipeline logs. Below is my pipeline script:
pipeline {
agent none
stages {
stage('Recreate DB') {
agent { label 'tst_db2'}
[JIRA] (JENKINS-42427) Allow regular expressions in "included branches"
Title: Message Title Mike Cating created an issue Jenkins / JENKINS-42427 Allow regular expressions in "included branches" Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Mar/02 3:34 AM Labels: plugin git Priority: Minor Reporter: Mike Cating When configuring an Organization in Jenkins 2.0, the Projects section allows the user to specify Include Branches and Exclude Branches. Currently, these text fields are space-delimited matches that only allow asterisk wildcards. Add a new feature to allow regular expressions in these fields. AC: When I click on an Organization in Jenkins 2.0 When I click Configure When I specify a regular _expression_ in the Include Branch field of the Github Organization Then branches that match that regular _expression_ are included when scanning repos under that Organization Add Comment
[JIRA] (JENKINS-42352) incorrect message when viewing the "branches" of a vanilla pipeline.
Title: Message Title Michael Neale commented on JENKINS-42352 Re: incorrect message when viewing the "branches" of a vanilla pipeline. cc James Dumay this is a fair point. Perhaps some alternative wording and say "Jenkinsfile" instead? (as that implies multibranch) instead of "Jenkins Pipeline"? 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-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Fritz Elfert commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) Same advice as before: Ask at the jclouds user list, if this is actually supposed to work. 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-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title Michael Neale commented on JENKINS-42408 Re: HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found yes this is the same problem. The reason was a rather embarrassing _javascript_ error that happened in most recent beta. Will be fixed in next release shipped. 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 Michael Neale commented on JENKINS-41611 Re: Update pipeline node designs Keith Zantow do you want to offload this to say Ivan? as there is already a fair bit on your plate 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-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title Ivan Meredith resolved as Duplicate Jenkins / JENKINS-42408 HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found Change By: Ivan Meredith Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title Ivan Meredith started work on JENKINS-42408 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-42040) Rundetails duration counter is not reset on rerun
Title: Message Title Ivan Meredith started work on JENKINS-42040 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-42126) creation flow organization list should not be scrollable
Title: Message Title Ivan Meredith updated JENKINS-42126 Jenkins / JENKINS-42126 creation flow organization list should not be scrollable 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-37623) No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Should be included in 2.1 release Jenkins / JENKINS-37623 No tooltips / image map generated on a graph when one of the previous builds failed before publishing TAP data Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41096) Only show admin link in header if the user has privileges
Title: Message Title Ivan Meredith updated JENKINS-41096 Jenkins / JENKINS-41096 Only show admin link in header if the user has privileges 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-42126) creation flow organization list should not be scrollable
Title: Message Title Ivan Meredith started work on JENKINS-42126 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-32616) p4 plugin should support for multibranch pipelines
Title: Message Title Moe Hussein commented on JENKINS-32616 Re: p4 plugin should support for multibranch pipelines I can't wait for this Thank you so much Paul Allen 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 started work on JENKINS-41096 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-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov commented on JENKINS-40925 Re: "dir" context is not honored by "sh" step So, it looks like hudson.Launcher.ProcStarter#pwd() provides correct path including "dir" context. It is available in if I change org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator. Is there a reason not to use it? If not I can make PR with change and test. 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-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov edited a comment on JENKINS-40925 Re: "dir" context is not honored by "sh" step So, it looks like hudson.Launcher.ProcStarter#pwd() provides correct path including "dir" context.It is available in if I change org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.Is there a reason not to use it?If not I can make PR with change and test. 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-42426) Unable to find latest submitted changelist number when workspace sources are from a Perforce remote depot
Title: Message Title Jason Carlsen created an issue Jenkins / JENKINS-42426 Unable to find latest submitted changelist number when workspace sources are from a Perforce remote depot Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2017/Mar/02 1:09 AM Environment: Jenkins 1.642.2 P4 Plugin 1.4.14 Priority: Major Reporter: Jason Carlsen The plugin does not currently work with remote depots because it is unable to find the correct changelist to sync against since the metadata for remote depot source is not available. From the log, it looks the like the plugin is doing the following: First tries to determine the CL via "p4 changes -m1 -ssubmitted ///..." If it can't, defaults to the latest CL in the server. The server CLs aren't associated with the remote depot source CLs, hence the issue. I would like to request that the plugin be updated to support remote depots. Perhaps a more complicated CL discovery method can be added in-between the "p4 changes" and latest change methods? Whatever the implementation, the plugin should be smart enough to determine the CL regardless of what type of depot the sources are coming from.
[JIRA] (JENKINS-42423) Websphere Deployer Plugin fails to deploy due to ConfigServiceServerProxy - NotSerializableException
Title: Message Title Nick Hitcan commented on JENKINS-42423 Re: Websphere Deployer Plugin fails to deploy due to ConfigServiceServerProxy - NotSerializableException Upgraded Websphere to 8.5.5.10 and installed a JDK 1.8_64 fixpack 3 and the issue still remains. 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-42425) "configure" button incorrectly assumes a servlet context of "/jenkins"
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-42425 "configure" button incorrectly assumes a servlet context of "/jenkins" Change By: Ben Walding The "gear" icon / "configure" icon on a Job should take me to the Jenkins classic configuration page for the job.It currently takes me to a broken URL in Jenkins classic as it assumes a "/jenkins/" prefixh4. Steps1. I am viewing "/blue/organizations/jenkins/pumpkin/activity"2. I click on the "gear" icon (left hand side, next to favourite star) - check all gear icons - as they're "all" doing 3. I am taken to /jenkins/job/pumpkin/configureh4. Expected1. I should have been taken to /job/pumpkin/configure 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
[JIRA] (JENKINS-40526) Developer would like to get the logs for a stage or parallel
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40526 Developer would like to get the logs for a stage or parallel Change By: James Dumay *Scope** Log toolbar buttons should open or download the log for the selected stage or parallel** Freestyle behaviour remains the same as before this change - e.g. the buttons should show or download the full log for freestyle * Link to full Pipeline log appears on Artifact tab (looks like an artifact) ** name: "pipeline.log" * * size: "–" * Problem*There is no way to get the log for the whole stage or parallel. The full log is not useful as it intermingles logs from different parallel branches.*Design brief*What we'd like to do is change the download/view links for the log so that they only produce logs for the stage/parallel that has been selected. We should then have download/view links for the whole log somewhere else - I am thinking the same has to go above the graph? Need to think about what this looks like when the graph is present and not present.* Full log appears as an artifact *Original request*Will be nice to have "expand all" button to see all steps (view whole log doesn't help due multiple parallels) !image-2016-12-18-12-41-56-651.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov commented on JENKINS-40925 Re: "dir" context is not honored by "sh" step OK. It runs out of the box with minikube. 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-42425) "configure" button incorrectly assumes a servlet context of "/jenkins"
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-42425 "configure" button incorrectly assumes a servlet context of "/jenkins" Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/02 12:45 AM Environment: b24 Priority: Minor Reporter: Ben Walding The "gear" icon / "configure" icon on a Job should take me to the Jenkins classic configuration page for the job. It currently takes me to a broken URL in Jenkins classic as it assumes a "/jenkins/" prefix Steps 1. I am viewing "/blue/organizations/jenkins/pumpkin/activity" 2. I click on the "gear" icon (left hand side, next to favourite star) 3. I am taken to /jenkins/job/pumpkin/configure Expected 1. I should have been taken to /job/pumpkin/configure Add Comment
[JIRA] (JENKINS-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov edited a comment on JENKINS-40925 Re: "dir" context is not honored by "sh" step I'm looking at the code at of org.jenkinsci.plugins.workflow.steps.PushdStep.Execution#start and org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator#decorate and it look like context is just ignored by LauncherDecorator.I want to try to fix this issue. [~csanchez] can you please add at least basic steps on how to configure integration test environment for this 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-40925) "dir" context is not honored by "sh" step
Title: Message Title Roman Safronov commented on JENKINS-40925 Re: "dir" context is not honored by "sh" step I'm looking at the code at org.jenkinsci.plugins.workflow.steps.PushdStep.Execution#start and org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator#decorate and it look like context is just ignored by LauncherDecorator. I want to try to fix this issue. Carlos Sanchez can you please add at least basic steps on how to configure integration test environment for this 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-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Dhruv Parpia commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) Facing the same issue. Jenkins Version: 2.47 Plugin Version: 2.14 Verified that it works in a project without an instance created from a snapshot. 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-33846) Restart pipeline from specific stage, after failure
Title: Message Title eguess74 commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure For all who wants this feature - there is a workaround: Create a "configuration job" that is a parameterized job. Fill it with the parameters that are reflecting the names of stages in the pipeline. for example (STAGE1=run/skip, STAGE2=run/skip) Use post build action trigger parameterized build to pass all those stages as parameters to the pipeline job. Use conditional build step in pipeline to determine if the step needs to be executed or not. (https://jenkins.io/blog/2017/01/19/converting-conditional-to-pipeline/) If the pipeline fails at STAGE2 you can rerun it starting from config job and you can say STAGE1=skip, STAGE2=run there are additional benefits as you can always go back to every run and see which parameters were used and so on. I hope that helps. 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-42424) Ability to pass IAM role while creating stack using CFT
Title: Message Title Muktesh Mishra created an issue Jenkins / JENKINS-42424 Ability to pass IAM role while creating stack using CFT Issue Type: New Feature Assignee: Nathan Good Components: cloudformation-plugin Created: 2017/Mar/02 12:21 AM Priority: Major Reporter: Muktesh Mishra How to use IAM role while creating stack from CFT plugin. Currently it allows only by use of secret and access key. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42417) Inconsistent presentation for unstable builds
Title: Message Title Daniel Beck commented on JENKINS-42417 Re: Inconsistent presentation for unstable builds Yes. It was actually confusing to me trying to understand the icons here – the tests with the same icon as "the entire build" were basically irrelevant. Something grey would be better here, and perhaps even consider changing the failed "red x" icon to "orange !" to match the build step. 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-42417) Inconsistent presentation for unstable builds
Title: Message Title James Dumay commented on JENKINS-42417 Re: Inconsistent presentation for unstable builds Daniel Beck oh are you saying "skipped" tests shouldn't have the same state as "unstable"? I agree. Since skipped tests are not built, WDYT about using the "not built" status here Brody Maclean? 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-42417) Inconsistent presentation for unstable builds
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42417 Inconsistent presentation for unstable builds 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-42417) Inconsistent presentation for unstable builds
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-42417 Inconsistent presentation for unstable builds 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-42289) Not possible to see the full name on the branch filter
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-42289 Not possible to see the full name on the branch filter Change By: James Dumay 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-42289) Not possible to see the full name on the branch filter
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-42289 Not possible to see the full name on the branch filter Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41642) Handle when favouriting a pipeline fails
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41642
Handle when favouriting a pipeline fails
Change By:
James Dumay
*In Scope* * If favouriting fails for any reason we should show an error toast to the user to tell them the error has failed. * Usually there is a reason sent for the failed rest call and this is safe to send to the user as a toast message . * The toast should use the failure style *Reproduce*You can make favouriting fail by:# Create a multibranch pipeline with no branches# Go to the dashboard# Favourite the pipeline*REST data*REST call will fail with:{code}{ "message" : "no master branch to favorite", "code" : 400, "errors" : [ ]}{code} *Scope** Show the failure toast in this case
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus, release candidates 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-41642) Handle when favouriting a pipeline fails
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41642
Handle when favouriting a pipeline fails
Change By:
James Dumay
*In Scope*If favouriting fails for any reason we should show an error toast to the user to tell them the error has failed. Usually there is a reason sent for the failed rest call and this is safe to send to the user as a toast message*Reproduce*You can make favouriting fail by:# Create a multibranch pipeline with no branches# Go to the dashboard# Favourite the pipeline * REST data*REST call will fail with:{code}{ "message" : "no master branch to favorite", "code" : 400, "errors" : [ ]}{code}*Scope** Show the failure toast in this case
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
[JIRA] (JENKINS-41642) Handle when favouriting a pipeline fails
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41642
Handle when favouriting a pipeline fails
Change By:
James Dumay
*In Scope* If favouriting fails for any reason we should show an error toast to the user to tell them the error has failed. Usually there is a reason sent for the failed rest call and this is safe to send to the user as a toast message *Reproduce* You can make favouriting fail by:# Create a multibranch pipeline with no branches# Go to the dashboard# Favourite the pipelineREST call will fail with:{code}{ "message" : "no master branch to favorite", "code" : 400, "errors" : [ ]}{code}*Scope** Show the failure toast in this case
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
[JIRA] (JENKINS-41897) Karaoke: Steps are limited to 100 - need to use pagination to fetch more
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41897 Karaoke: Steps are limited to 100 - need to use pagination to fetch more Change By: James Dumay Priority: Major Minor 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-41885) Build log is scrolled down unconditionally on update
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41885 Build log is scrolled down unconditionally on update Change By: James Dumay Priority: Major Minor 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-42312) Can only select top node of parallel nodes while job is in progress.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42312 Can only select top node of parallel nodes while job is in progress. Change By: James Dumay Priority: Major Minor 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-32320) Ability to configure changelog message truncation and inclusion of merge commits
Title: Message Title Simon Hardman commented on JENKINS-32320 Re: Ability to configure changelog message truncation and inclusion of merge commits Hi Henrik Unfortunately we've moved to using Pipeline builds and our use case is easy enough to manage with groovy and shell scripts so we no longer have a use for the changes. If you want to run with them you are most welcome. 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-42357) Loading... in creation should be more descriptive
Title: Message Title James Dumay resolved as Won't Fix I think the loading message here is fine TBH Jenkins / JENKINS-42357 Loading... in creation should be more descriptive Change By: James Dumay Status: Open Resolved 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
[JIRA] (JENKINS-42357) Loading... in creation should be more descriptive
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42357 Loading... in creation should be more descriptive Change By: James Dumay *Scope** Change text from "Loading..." "Discovering organizations..."*Original request* When you click on "Github" in creation the next step says "Loading". It should probably be more descriptive of what it is loading.It also happens when loading repo listing. 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-42040) Rundetails duration counter is not reset on rerun
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42040 Rundetails duration counter is not reset on rerun Change By: James Dumay Priority: Major Minor 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-42126) creation flow organization list should not be scrollable
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-42126 creation flow organization list should not be scrollable Change By: James Dumay Assignee: 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-42206) No selection state for "where do you store your code"
Title: Message Title James Dumay updated JENKINS-42206 Jenkins / JENKINS-42206 No selection state for "where do you store your code" 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-40746) Tests failures on the test module of the core on Windows
Title: Message Title Daniel Beck commented on JENKINS-40746 Re: Tests failures on the test module of the core on Windows org.jvnet.hudson.test.BuildTriggerTest.testSomething WTF is this, and why is it marking https://ci.jenkins.io/job/Core/job/jenkins/job/master/272/ unstable? I can't find this anywhere, is this crap just written into a file to test JUnit or something? 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-42417) Inconsistent presentation for unstable builds
Title: Message Title Daniel Beck reopened an issue James Dumay Please see the screenshot for what this is about. Jenkins / JENKINS-42417 Inconsistent presentation for unstable builds Change By: Daniel Beck Resolution: Duplicate Status: Resolved Reopened 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
[JIRA] (JENKINS-42417) Inconsistent presentation for unstable builds
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-42417 Inconsistent presentation for unstable builds Change By: Daniel Beck Attachment: Screen Shot 2017-03-02 at 00.44.10.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-42423) Websphere Deployer Plugin fails to deploy due to ConfigServiceServerProxy - NotSerializableException
Title: Message Title Nick Hitcan created an issue Jenkins / JENKINS-42423 Websphere Deployer Plugin fails to deploy due to ConfigServiceServerProxy - NotSerializableException Issue Type: Bug Assignee: Unassigned Attachments: SystemErr.log Components: websphere-deployer-plugin Created: 2017/Mar/01 11:37 PM Environment: Jenkins 2.32.2 Websphere Deployer Plugin - 1.3.4 Websphere Server - 8.5.5.9 Websphere JDK 1.8_64 Labels: websphere-deployer-plugin websphere Priority: Blocker Reporter: Nick Hitcan I am currently facing an issue with the Websphere Deployer Plugin, Jenkins is running on a Websphere 8.5.5.9 server with the 1.8_64 JDK. [3/1/17 18:23:23:870 EST] 00c4 SystemErr R com.ibm.websphere.management.exception.AdminException: [3/1/17 18:23:23:871 EST] 00c4 SystemErr R at com.ibm.websphere.management.application.AppManagementProxy.proxyInvokeNoRet(AppManagementProxy.java:173) [3/1/17 18:23:23:871 EST] 00c4 SystemErr R at com.ibm.websphere.management.application.AppManagementProxy.installApplication(AppManagementProxy.java:510) [3/1/17 18:23:23:871 EST] 00c4 SystemErr R at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.installArtifact(WebSphereDeploymentService.java:237) [3/1/17 18:23:23:871 EST] 00c4 SystemErr R at
[JIRA] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title Daniel Beck commented on JENKINS-33358 Re: Groovy and PermGen memory leak We decided today that the next LTS will be based on 2.46 due to the risk of further regressions/incompatibilities caused by the upgrade to Groovy 2.4.8. So this will likely only be in LTS 16 weeks from today unless we think it's safe enough for a backport (and I would be surprised if we'd consider it safe enough). 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-42422) Add support for directory caching in pod jobs
Title: Message Title Roman Safronov created an issue Jenkins / JENKINS-42422 Add support for directory caching in pod jobs Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Mar/01 11:29 PM Priority: Minor Reporter: Roman Safronov It would be great to be able to "cache" directories between job executions. In some cases it helps to greatly speedup job execution. Similar to Travis: https://docs.travis-ci.com/user/caching/. Now I achieve it with persistent volume and pipeline function doing explicit (re)store steps. What can be added to kubernetes-plugin: -option to manage caches (specifically drop cache for specific job) -add DSL construct like podTemplate(... cachePaths: ["A", "B/C"]) -default strategy for cache management (shared NFS-backed volume or provisioned PVC per job) Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title James Dumay commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Thanks Sam Van Oort! I understand this one is a difficult one to implement and its going to take its time. Im just adjusting tickets that are important to Blue Oceans 12 month roadmap. 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-40084) PipelineRunImpl.replay assumes the task is still in the queue
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40084 PipelineRunImpl.replay assumes the task is still in the queue Change By: Michael Neale 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-40084) PipelineRunImpl.replay assumes the task is still in the queue
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40084 PipelineRunImpl.replay assumes the task is still in the queue Change By: Michael Neale Sprint: release candidates 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-42395) If the jenkins banner is customized the "open blue ocean" button gets covered on a narrow screen (< 1060)
Title: Message Title James Dumay assigned an issue to Brody Maclean Jenkins / JENKINS-42395 If the jenkins banner is customized the "open blue ocean" button gets covered on a narrow screen (< 1060) Change By: James Dumay Assignee: Brody Maclean 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-42395) If the jenkins banner is customized the "open blue ocean" button gets covered on a narrow screen (< 1060)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42395 If the jenkins banner is customized the "open blue ocean" button gets covered on a narrow screen (< 1060) Change By: James Dumay Sprint: 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Sorry for the updatespam – I had this confused with another similarly named bug/RFE that this appears to clone. In any case, James Dumay I would not expect this to be a trivial change since you need to rework the way statuses are tracked. Basically, you can increase priority as much as you like, but it needs a significant data model change to do it the right way. If you choose to do it the wrong way, that will have to be purely Blue Ocean side and supported, and we can make no guarantees it will remain functional in the face of future pipeline changes. If you do it the right way, it will take a while though. 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-42357) Loading... in creation should be more descriptive
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42357 Loading... in creation should be more descriptive 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-35282) Make Job DSL's ExecuteDslScripts Pipeline-compatible
Title: Message Title Chris Denneen commented on JENKINS-35282 Re: Make Job DSL's ExecuteDslScripts Pipeline-compatible http://stackoverflow.com/questions/37353963/how-can-i-reference-the-jenkinsfile-directory-with-pipeline 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title
Chris Denneen edited a comment on JENKINS-33273
Re: Optimize Jenkinsfile loading and branch detection
[~jglick] I have referenced this issue from https://issues.jenkins-ci.org/browse/JENKINS-35282I'm curious... it seems the problem stems from the Pipeline from SCM is checking out as JOB@script vs just JOB workspace.Since the files are already in the JOB@script workspace I'm not sure why a git checkout would be necessary.Is there anyway to have the Pipeline just do the checkout in correct workspace of JOB and not JOB@script?That should resolve the issues and allow for something like this to work:{code: groovy }node { jobDsl targets: ['jobs/*.groovy'].join('\n'),removedJobAction: 'DELETE',removedViewAction: 'DELETE',lookupStrategy: 'SEED_JOB'}{code}workspace for test is emptyworkspace of test@script has the checked out repo with Jenkinsfile and the jobs subfolder with the groovy scripts to load.{code}jenkins@50eeb9a40763:~/workspace$ ls -la *test:total 8drwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..test@script:total 20drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:19 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..drwxr-xr-x 8 jenkins jenkins 4096 Mar 1 18:19 .git-rw-r--r-- 1 jenkins jenkins 835 Mar 1 18:19 Jenkinsfiledrwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 jobs{code}test job runs and fails:{code}ERROR: no Job DSL script(s) found at jobs/*.groovy{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title Victor Martinez resolved as Fixed Jenkins / JENKINS-42383 Maven and javadoc Plugin dependencies are not required when using reflection Change By: Victor Martinez 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-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-42383 Maven and javadoc Plugin dependencies are not required when using reflection Change By: Victor Martinez Labels: 0.8.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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title
Chris Denneen commented on JENKINS-33273
Re: Optimize Jenkinsfile loading and branch detection
Jesse Glick I have referenced this issue from https://issues.jenkins-ci.org/browse/JENKINS-35282 I'm curious... it seems the problem stems from the Pipeline from SCM is checking out as JOB@script vs just JOB workspace. Since the files are already in the JOB@script workspace I'm not sure why a git checkout would be necessary. Is there anyway to have the Pipeline just do the checkout in correct workspace of JOB and not JOB@script? That should resolve the issues and allow for something like this to work:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
node {
jobDsl targets: ['jobs/*.groovy'].join('\n'),
removedJobAction: 'DELETE',
removedViewAction: 'DELETE',
lookupStrategy: 'SEED_JOB'
}
workspace for test is empty workspace of test@script has the checked out repo with Jenkinsfile and the jobs subfolder with the groovy scripts to load.
jenkins@50eeb9a40763:~/workspace$ ls -la *
test:
total 8
drwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 .
drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..
test@script:
total 20
drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:19 .
drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..
drwxr-xr-x 8 jenkins jenkins 4096 Mar 1 18:19 .git
-rw-r--r-- 1 jenkins jenkins 835 Mar 1 18:19 Jenkinsfile
drwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 jobs
test job runs and fails:
ERROR: no Job DSL script(s) found at jobs/*.groovy
Add Comment
[JIRA] (JENKINS-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42383 Re: Maven and javadoc Plugin dependencies are not required when using reflection Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/b29ceb66f297edb4ee6f53f5f3126ef0819faec9 Log: JENKINS-42383 Removed Javadoc plugin dependency 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Sam Van Oort 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-42419) "Show more" implementation on activity tab is weird
Title: Message Title James Dumay resolved as Duplicate Daniel Beck assuming you are using ci.jenkins.io we've fixed this problem in beta 22 (two releases ago). Please upgrade to a later version to get the fix Jenkins / JENKINS-42419 "Show more" implementation on activity tab is weird Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Sam Van Oort Priority: Critical Minor 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-42408) HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found
Title: Message Title Michael Neale commented on JENKINS-42408 Re: HTTP ERROR 404 Problem accessing /jenkins/job/myproject/configure. Reason: Not Found Is the problem due to it adding /jenkins in? If so - this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-42291 which has been fixed in master but not released yet. 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-42417) Inconsistent presentation for unstable builds
Title: Message Title James Dumay commented on JENKINS-42417 Re: Inconsistent presentation for unstable builds You are right - it does not make sense. Pipeline actually sets every node as unstable and Blue Ocean just reports on what pipeline tells it. I do have internal commitment from CloudBees OSS team that they will fix it this year for me. Need to narrow down when because it annoys me a lot. 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-42417) Inconsistent presentation for unstable builds
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-42417 Inconsistent presentation for unstable builds Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should 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-42418) There's no login link on a build detail page
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42418 There's no login link on a build detail page 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-33358) Groovy and PermGen memory leak
Title: Message Title Christer Engde commented on JENKINS-33358 Re: Groovy and PermGen memory leak When will this fix be available in LTS? 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-42418) There's no login link on a build detail page
Title: Message Title James Dumay assigned an issue to Brody Maclean Jenkins / JENKINS-42418 There's no login link on a build detail page Change By: James Dumay Assignee: Brody Maclean 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 Michael Neale updated JENKINS-41434 Jenkins / JENKINS-41434 Restrict access to Creation Flow for users with insufficient permissions Change By: Michael Neale 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-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-42383 Maven and javadoc Plugin dependencies are not required when using reflection Change By: Victor Martinez It's Maven plugin is the only optional dependency, but let's remove it 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-41160) java.lang.LinkageError :loading constraint violation:loader "hudson/PluginFirstClassLoader..."
Title: Message Title Nick Hitcan commented on JENKINS-41160 Re: java.lang.LinkageError :loading constraint violation:loader "hudson/PluginFirstClassLoader..." I am also experiencing this issue with Jenkins installed onto Websphere 8.5.5.9 running the IBM JDK 1.7 as well as 1.8. 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-42383) Maven and javadoc Plugin dependencies are not required when using reflection
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-42383 Maven and javadoc Plugin dependencies are not required when using reflection Change By: Victor Martinez Summary: Maven and javadoc Plugin dependency is dependencies are not required when using reflection 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I didn't explain it well. Sorry. Let me try again: On login, fetch the public ssh keys stored in github (under https://github.com/settings/keys ) and put them into the user's profile in Jenkins automaticall (https://jenkins.example.com/user/USERNAME/ ). That shouldn't require any caching or anything. This is to facilitate using the `jenkins-cli.jar` and other things that talk to Jenkins via ssh. 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje commented on JENKINS-42421 Re: BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' This may possibly be related to JENKINS-34835 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-42421 BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2017/Mar/01 9:49 PM Environment: github-oauth-plugin 0.25 Priority: Major Reporter: Christian Höltje Before, team names would show up. Now they show as `org.kohsuke.github.GHTeam@e004985`. Example: Given the github org 'foo' with the team 'bar', the Organization would show up in my /user/ page as foo*bar. Now, it shows up as foo*org.kohsuke.github.GHTeam@e004985. This is breaking permissions, since I cannot give permissions to teams! Add Comment
[JIRA] (JENKINS-35282) Make Job DSL's ExecuteDslScripts Pipeline-compatible
Title: Message Title
Chris Denneen edited a comment on JENKINS-35282
Re: Make Job DSL's ExecuteDslScripts Pipeline-compatible
This seems to be still happening: job-dsl 1.58 - Create test pipeline job named 'test' pointed to repo to read JenkinsfileRepo with the following Jenkinsfile{code}node { jobDsl scriptText: 'job("example-2")' jobDsl scriptText: """def project = 'Netflix/asgard'def branchApi = new URL(\"https://api.github.com/repos/\${project}/branches\")def branches = new groovy.json.JsonSlurper().parse(branchApi.newReader())branches.each { def branchName = it.name def jobName = \"\${project}-\${branchName}\".replaceAll('/','-') job(jobName) {scm { git(\"https://github.com/\${project}.git\", branchName)} }} """ jobDsl scriptText: """folder('shared') { displayName('Shared Jobs') description('Shared Jobs Folder')} """ jobDsl targets: ['jobs/*.groovy'].join('\n'),removedJobAction: 'DELETE',removedViewAction: 'DELETE',lookupStrategy: 'SEED_JOB'}{code}Repo has a jobs subfolder with any groovy scripts... workspace for test is emptyworkspace of test@script has the checked out repo{code}jenkins@50eeb9a40763:~/workspace$ ls -la *test:total 8drwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..test@script:total 20drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:19 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..drwxr-xr-x 8 jenkins jenkins 4096 Mar 1 18:19 .git-rw-r--r-- 1 jenkins jenkins 835 Mar 1 18:19 Jenkinsfiledrwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 jobs{code}test job runs and fails at last step:{code}ERROR: no Job DSL script(s) found at jobs/*.groovy{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-24806) Scoverage: iFrames blocked by many server setups
Title: Message Title Dan Ebert commented on JENKINS-24806 Re: Scoverage: iFrames blocked by many server setups You can work around the issue in my previous comment by adding this "-Dhudson.model.DirectoryBrowserSupport.CSP=" to the JAVA_ARGS in your /etc/default/jenkins file and restarting via the command line (restarting via the UI doesn't reload the args) 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-42367) NPE from IteratorHack.writeReplace via ParamsVariable.getValue
Title: Message Title Jesse Glick updated JENKINS-42367 Jenkins / JENKINS-42367 NPE from IteratorHack.writeReplace via ParamsVariable.getValue Change By: Jesse Glick 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-35282) Make Job DSL's ExecuteDslScripts Pipeline-compatible
Title: Message Title
Chris Denneen edited a comment on JENKINS-35282
Re: Make Job DSL's ExecuteDslScripts Pipeline-compatible
This seems to be still happening:- Create test pipeline job named 'test' pointed to repo to read JenkinsfileRepo with the following Jenkinsfile{code}node { jobDsl scriptText: 'job("example-2")' jobDsl scriptText: """def project = 'Netflix/asgard'def branchApi = new URL(\"https://api.github.com/repos/\${project}/branches\")def branches = new groovy.json.JsonSlurper().parse(branchApi.newReader())branches.each { def branchName = it.name def jobName = \"\${project}-\${branchName}\".replaceAll('/','-') job(jobName) {scm { git(\"https://github.com/\${project}.git\", branchName)} }} """ jobDsl scriptText: """folder('shared') { displayName('Shared Jobs') description('Shared Jobs Folder')} """ jobDsl targets: ['jobs/*.groovy'].join('\n'),removedJobAction: 'DELETE',removedViewAction: 'DELETE',lookupStrategy: 'SEED_JOB'}{code}Repo has a jobs subfolder with any groovy scripts... workspace for test is emptyworkspace of test@script has the checked out repo {code}jenkins@50eeb9a40763:~/workspace$ ls -la * test :total 8drwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..test@script:total 20drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:19 .drwxr-xr-x 4 jenkins jenkins 4096 Mar 1 18:03 ..drwxr-xr-x 8 jenkins jenkins 4096 Mar 1 18:19 .git-rw-r--r-- 1 jenkins jenkins 835 Mar 1 18:19 Jenkinsfiledrwxr-xr-x 2 jenkins jenkins 4096 Mar 1 18:03 jobs{code}test job runs and fails at last step:{code}ERROR: no Job DSL script(s) found at jobs/*.groovy{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42367) NPE from IteratorHack.writeReplace via ParamsVariable.getValue
Title: Message Title Jesse Glick started work on JENKINS-42367 Change By: Jesse Glick 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-35282) Make Job DSL's ExecuteDslScripts Pipeline-compatible
Title: Message Title
Chris Denneen reopened an issue
This seems to be still happening:
Create test pipeline job named 'test' pointed to repo to read Jenkinsfile
Repo with the following Jenkinsfile
node {
jobDsl scriptText: 'job("example-2")'
jobDsl scriptText: """
def project = 'Netflix/asgard'
def branchApi = new URL(\"https://api.github.com/repos/\${project}/branches\")
def branches = new groovy.json.JsonSlurper().parse(branchApi.newReader())
branches.each {
def branchName = it.name
def jobName = \"\${project}-\${branchName}\".replaceAll('/','-')
job(jobName) {
scm {
git(\"https://github.com/\${project}.git\", branchName)
}
}
}
"""
jobDsl scriptText: """
folder('shared') {
displayName('Shared Jobs')
description('Shared Jobs Folder')
}
"""
jobDsl targets: ['jobs/*.groovy'].join('\n'),
removedJobAction: 'DELETE',
removedViewAction: 'DELETE',
lookupStrategy: 'SEED_JOB'
}
Repo has a jobs subfolder with any groovy scripts... workspace for test is empty workspace of test@script has the checked out repo test job runs and fails at last step:
ERROR: no Job DSL script(s) found at jobs/*.groovy
Jenkins / JENKINS-35282
Make Job DSL's ExecuteDslScripts Pipeline-compatible
Change By:
Chris Denneen
Resolution:
Fixed
Status:
Closed Reopened
[JIRA] (JENKINS-42367) NPE from IteratorHack.writeReplace via ParamsVariable.getValue
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-42367 NPE from IteratorHack.writeReplace via ParamsVariable.getValue Change By: Jesse Glick Assignee: Jesse Glick 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-40100) Credentials config not initialized properly.
Title: Message Title Mark Adamcin resolved as Fixed Thanks for identifying the issue. It has been resolved in CRX plugin 1.6.3. Jenkins / JENKINS-40100 Credentials config not initialized properly. Change By: Mark Adamcin Status: In Progress Resolved Assignee: Peter Grape Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-40100) Credentials config not initialized properly.
Title: Message Title Mark Adamcin started work on JENKINS-40100 Change By: Mark Adamcin 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-41416) "Scan Organisation" is a verb - but this performs no action.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41416 Re: "Scan Organisation" is a verb - but this performs no action. Code changed in jenkins User: Stephen Connolly Path: src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/FolderComputation/events.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/3ed06e3a5030c7f70e75745ed99c23c7ea5a3d61 Log: [FIXED JENKINS-41416] Fold the submenu into the main menu 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-42146) Branch indexing log link not rendering properly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42146 Re: Branch indexing log link not rendering properly Code changed in jenkins User: Stephen Connolly Path: src/main/resources/com/cloudbees/hudson/plugins/folder/computed/FolderComputation/console.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/FolderComputation/console_ja.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/FolderComputation/events.properties http://jenkins-ci.org/commit/cloudbees-folder-plugin/6322f4699fefcb0e342f02eda3e4b3725acbbf2b Log: [FIXED JENKINS-42146] Added the missing i18n bundle keys 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-42420) Code Coverage Report Missing from Project view when using a Pipeline
Title: Message Title Kyle Campbell created an issue Jenkins / JENKINS-42420 Code Coverage Report Missing from Project view when using a Pipeline Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2017/Mar/01 9:27 PM Environment: Jenkins 2.32.2 Jacoco 2.1.0 CentOS Linux release 7.3.1611 (Core) Java 1.8.0_102-b14 Priority: Minor Reporter: Kyle Campbell The code coverage report is showing up correctly when using the JaCoco Coverage column in a view, and also at the Build level. However, when viewing a project, the CodeCoverage link in the sidebar and the corresponding trend graph is missing. Add Comment
[JIRA] (JENKINS-42367) NPE from IteratorHack.writeReplace via ParamsVariable.getValue
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42367 NPE from IteratorHack.writeReplace via ParamsVariable.getValue Change By: Jesse Glick Summary: Groovy params NPE from IteratorHack . containsKey() NullPointerException org.jenkinsci.plugins.workflow.cps. writeReplace via ParamsVariable.getValue 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-41712) NullPointerException when using parameter separator in a pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41712 NullPointerException when using parameter separator in a pipeline Change By: Jesse Glick Component/s: workflow-cps-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-42367) Groovy params.containsKey() NullPointerException org.jenkinsci.plugins.workflow.cps.ParamsVariable.getValue
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-42367 Groovy params.containsKey() NullPointerException org.jenkinsci.plugins.workflow.cps.ParamsVariable.getValue Change By: Jesse Glick Component/s: pipeline Assignee: Jesse Glick 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-42387) Ability to add or delete single repository by name
Title: Message Title Jesse Glick commented on JENKINS-42387 Re: Ability to add or delete single repository by name As soon as you create a branch (or PR) that includes a Jenkinsfile, the webhook event should cause Jenkins to add the repository automatically. So this is invalid AFAICT. Are you running up-to-date plugins, and do you have a webhook registered on the organization? 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-26137) Mysterious serialization errors
Title: Message Title Jesse Glick commented on JENKINS-26137 Re: Mysterious serialization errors I think the main issue here could be resolved if the field lines in the stack trace specified the class name too. There is also an issue that RiverWriter can apparently be missing the list of pickles under some conditions TBD, which is something I can take care of. 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.
