[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title E D commented on JENKINS-53743 Re: Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse. hi Jie Shen, its 0.2.7. Hope it helps Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53702) Groovy script build error
Title: Message Title Minu Kumari commented on JENKINS-53702 Re: Groovy script build error Hi, I havent heard back did you need more details for this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Kostiantyn Shchepanovskyi commented on JENKINS-26257 Re: java.lang.ClassCastException/NPE in Remoting while executing Maven Builder I had same issue, it disappeared after removing fingerprints. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52239) being able to select which severity level to display in the graphical on job status page
Title: Message Title Ulli Hafner updated JENKINS-52239 Will be part of next beta. (Note that the selection is not saved so you need to click every time) Jenkins / JENKINS-52239 being able to select which severity level to display in the graphical on job status page Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53684) Provide links for all tabs in details page
Title: Message Title Ulli Hafner commented on JENKINS-53684 Re: Provide links for all tabs in details page I see, seems that you are using the wrong post build action for the Clang warnings. You should use the same post build action as for CheckStyle. When you click on the arrow, you will see a chart for new warnings as well. Does it make sense to see the new warnings as first chart in the carousel? Or should I save the selected chart so you get the same selection if you open the page again? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53703) Unable to see Online Results During the load runner test
Title: Message Title Daniel Gront assigned an issue to Rolando-Mihai Vlad Jenkins / JENKINS-53703 Unable to see Online Results During the load runner test Change By: Daniel Gront Assignee: Daniel Gront Rolando-Mihai Vlad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title Jie Shen started work on JENKINS-53743 Change By: Jie Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title Jie Shen commented on JENKINS-53743 Re: Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse. Hi E D, could you please provide your azure-commons-plugin's version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53756) Azure VM agents disconnected and deprovisioned mid-build
Title: Message Title Jie Shen started work on JENKINS-53756 Change By: Jie Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53747) cron schedule not parsed correctly
Title: Message Title Daniel Beck closed an issue as Not A Defect Mark is right. Jenkins / JENKINS-53747 cron schedule not parsed correctly Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53743 Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse. Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53756) Azure VM agents disconnected and deprovisioned mid-build
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53756 Azure VM agents disconnected and deprovisioned mid-build Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53759) jiraGetIssueRemoteLinks does not work
Title: Message Title Naresh Rayapati commented on JENKINS-53759 Re: jiraGetIssueRemoteLinks does not work Look at the JIRA documentation, it varies based the JIRA instance configuration, the error is from the JIRA server itself, so please look at the JIRA API and docs based on the JIRA version you are using. https://docs.atlassian.com/software/jira/docs/api/REST/7.12.2/#api/2/issue-getRemoteIssueLinks https://developer.atlassian.com/server/jira/platform/using-fields-in-remote-issue-links/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43607) Jenkins pipeline not aborted when the machine running docker container goes offline
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-43607 Jenkins pipeline not aborted when the machine running docker container goes offline Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53759) jiraGetIssueRemoteLinks does not work
Title: Message Title Frederic Rousseau commented on JENKINS-53759 Re: jiraGetIssueRemoteLinks does not work Or maybe I did not understand the documentation? https://jenkinsci.github.io/jira-steps-plugin/steps/issuelink/jira_get_remote_issuelinks/ it says globalId is optional Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46170) Capability to add notes to stages (regardless of the actual result)
Title: Message Title Jesse Glick commented on JENKINS-46170 Re: Capability to add notes to stages (regardless of the actual result) @sam I think you are thinking not of this issue, but of JENKINS-37324. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Jesse Glick commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) The sshagent step is more convenient, but it boils down to more or less the same thing. withCredentials does not write files to the workspace per se, but to an @tmp sibling directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53759) jiraGetIssueRemoteLinks does not work
Title: Message Title
Frederic Rousseau updated an issue
Jenkins / JENKINS-53759
jiraGetIssueRemoteLinks does not work
Change By:
Frederic Rousseau
jiraGetIssueRemoteLinks does not work if I do not provide the argument globalId. {code:java}WorkflowScript: 6: Missing required parameter: "globalId" @ line 6, column 17. {code}I don't know what globalId to provide, I just want to list the remote links (name and url would be nice). I tested with version 1.4.4 of the plugin
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53759) jiraGetIssueRemoteLinks does not work
Title: Message Title Frederic Rousseau updated an issue Jenkins / JENKINS-53759 jiraGetIssueRemoteLinks does not work Change By: Frederic Rousseau jiraGetIssueRemoteLinks does not work if I do not provide the argument globalId. WorkflowScript: 6: Missing required parameter: "globalId" @ line 6, column 17. I don't know what globalId to provide, I just want to list the remote links (name and url would be nice). I tested with version 1.4.4 of the plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43012) manager.setBuildNumber() does not seem to do anything
Title: Message Title
James Chuong commented on JENKINS-43012
Re: manager.setBuildNumber() does not seem to do anything
Issue exists in Jenkins 2.121.3 LTS with groovy-postbuild-plugin 2.4.2 Workaround I have done is to just rewrite the parts I actually want as a Jenkins global shared library. I just avoid using manager and directly interact with the build. Since it is a globally loaded library, it also avoids the security sandboxing.
vars/foo.groovy
import com.jenkinsci.plugins.badge.action.BadgeAction;
@NonCPS
def addBadge(jobName, buildNumber) {
def project = manager.hudson.getItemByFullName(jobName)
def build = project.getBuildByNumber(buildNumber as Integer)
build.addAction(BadgeAction.createBadge(icon, text, link));
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53759) jiraGetIssueRemoteLinks does not work
Title: Message Title Frederic Rousseau created an issue Jenkins / JENKINS-53759 jiraGetIssueRemoteLinks does not work Issue Type: Bug Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2018-09-25 00:20 Priority: Minor Reporter: Frederic Rousseau jiraGetIssueRemoteLinks does not work if I do not provide the argument globalId. WorkflowScript: 6: Missing required parameter: "globalId" @ line 6, column 17. I don't know what globalId to provide, I just want to list the remote links (name and url would be nice). I tested with version 1.4.4 of the plugin Add Comment
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title leemeador commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once One solution is to have sh() return the output in the case of returnStdout: true as usual and, in the case of failure, throw an exception that could be a subclass of the current failure exception from which you could extract the error return code if you catch it and the console output is present in the exception as well (so you could extract it too). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53758) Permit notifyBitbucket without workspace present
Title: Message Title John Myers created an issue Jenkins / JENKINS-53758 Permit notifyBitbucket without workspace present Issue Type: Improvement Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2018-09-24 22:56 Priority: Minor Reporter: John Myers Attempting to do a notifyBitbucket from a step with "agent none" or from the post/always block on a pipeline with "agent none" results in: Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node While this can be worked around by wrapping in a node block, it doesn't appear that the plugin would really need the contents of the workspace in order to send a notification. It would be a great simplification if the step could be performed without a workspace. Add Comment
[JIRA] (JENKINS-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Jeff Thompson commented on JENKINS-26257 Re: java.lang.ClassCastException/NPE in Remoting while executing Maven Builder This issue doesn't seem to occur consistently or repeatedly in all Maven projects. There seem to be some conditions that cause it in some presumably small subset of situations. Further, we have at least one report, from Peter Taucher, of the issue being resolved by cleaning up fingerprints. The connection to fingerprints is not obvious. Even with that case, it is hard to know if that is a repeatable resolution. If anyone who sees this can provide more information, particularly about how it can be isolated and reproduced, I'll see if I can get a chance to look into it further. Do you see it consistently? For all jobs / builds / agents / configurations? Besides Peter's observations regarding fingerprints, have you observed any candidate causes? Has anyone else tried pursuing that path of removing fingerprints? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53330) Repositories not found without project in bitbucket cloud
Title: Message Title Gael Colin commented on JENKINS-53330 Re: Repositories not found without project in bitbucket cloud The report-info-plugin does not deals with Bitbucket cloud. It parses some xml and display them above the jobs list (ListView). When you use the List View instead of the Report Info, do you have the issue? (see https://plugins.jenkins.io/report-info Create a new ReportInfo view) If it is the case, the plugin may need an upgrade to a more recent vesion of Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53757) Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Title: Message Title
Brett Cashman created an issue
Jenkins / JENKINS-53757
Exec Failure: Expected HTTP 101 response but was '403 Forbidden'
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-09-24 21:40
Priority:
Major
Reporter:
Brett Cashman
I have a bare-metal Jenkins master (v2.141, running kubernetes-plugin v1.12.6) and a bare-metal Kubernetes cluster (v1.11.0). I'm trying to run a simplified version of the multi-container example described in the "Container Group Support" section of the README. My Jenkinsfile is as follows:
def label = "pod-${env.JOB_NAME}-${env.BUILD_NUMBER}".replace('_', '-').replace('/', '-')
podTemplate(label: label, cloud: 'kubernetes2', namespace: 'default',
containers: [
containerTemplate(name: 'maven', image: 'maven:3.5-jdk-8-alpine', ttyEnabled: true, command: 'cat')
])
{
node(label) {
echo "#1"
stage('Fetch Maven') {
git 'https://github.com/jenkinsci/kubernetes-plugin.git'
echo "#2"
container('maven') {
stage ('Build Maven') {
echo "#3"
sh 'mvn -B clean install'
}
}
}
}
}
Everything seems copacetic until the `sh` command in the final stage. Log fragment:
[Pipeline] stage
[Pipeline] { (Build Maven)
[Pipeline] echo
#3
[Pipeline] sh
[experimental_pipeline_k8s] Running shell script
java.net.ProtocolException: Expected HTTP 101 response but was '403 Forbidden'
at
[JIRA] (JENKINS-44231) Safely pass args to sh step
Title: Message Title
Jesse Glick commented on JENKINS-44231
Re: Safely pass args to sh step
Yes for sh that would be the workaround, until the Jenkins step does something similar as a standard function. For bat it is a little trickier; as per this and this it might suffice to use something like the following (untested):
bat args.collect {it.replaceAll('[^a-zA-Z0-9_.\r\n-]', '^$0').replaceAll('\r?\n', '^\r\n\r\n')}.join(' ')
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title Stuart Rowe assigned an issue to Paul Allen Jenkins / JENKINS-53723 [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync Change By: Stuart Rowe Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I do not foresee anyone spending much effort on this issue, as that would distract from the goal of moving Pipeline execution out of process, rendering this moot. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53503) More test coverage for Snapshotter.git()
Title: Message Title R. Tyler Croy assigned an issue to Baptiste Mathus Jenkins / JENKINS-53503 More test coverage for Snapshotter.git() Change By: R. Tyler Croy Issue Type: Task Improvement Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53542) Update Levels have duplicate commits in production
Title: Message Title R. Tyler Croy resolved as Cannot Reproduce I haven't yet seen this crops up Jenkins / JENKINS-53542 Update Levels have duplicate commits in production Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53542) Update Levels have duplicate commits in production
Title: Message Title R. Tyler Croy started work on JENKINS-53542 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51059) Ensure that seeds are idempotent
Title: Message Title R. Tyler Croy updated JENKINS-51059 Jenkins / JENKINS-51059 Ensure that seeds are idempotent Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53756) Azure VM agents disconnected and deprovisioned mid-build
Title: Message Title Emanuel Birge created an issue Jenkins / JENKINS-53756 Azure VM agents disconnected and deprovisioned mid-build Issue Type: Bug Assignee: Azure DevOps Attachments: azure-vm-agents.log, cloud_statistics.PNG, offline_agents.PNG Components: azure-vm-agents-plugin Created: 2018-09-24 20:58 Environment: Jenkins master OS: Ubuntu 16.04 running in a docker container on Ubuntu 16.04 Affected slaves: Ubuntu 16.04 VMs from custom Azure image (basically vanilla except docker installation) Plugins: org.jenkins-ci.main:jenkins-war:2.107.1 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 org.jenkins-ci.main:cli:2.107.1 aopalliance:aopalliance:1.0 org.kohsuke.stapler:stapler-jelly:1.254 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2 commons-digester:commons-digester:2.1 commons-io:commons-io:2.4 org.kohsuke:trilead-putty-extension:1.2 commons-codec:commons-codec:1.9 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.ui:jquery-detached:1.2 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 net.java.sezpoz:sezpoz:1.12 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.jenkins-ci:winstone:4.1 org.slf4j:log4j-over-slf4j:1.7.25 org.jenkins-ci:version-number:1.4 org.codehaus.groovy:groovy-all:2.4.11 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 org.jenkins-ci:jmdns:3.4.0-jenkins-3 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.jenkins-ci:bytecode-compatibility-transformer:1.8 org.jenkins-ci.main:remoting:3.17 org.apache.ant:ant:1.9.2 com.sun.solaris:embedded_su4j:1.1 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.apache.commons:commons-compress:1.10 commons-beanutils:commons-beanutils:1.8.3 org.jvnet.localizer:localizer:1.24
[JIRA] (JENKINS-51059) Ensure that seeds are idempotent
Title: Message Title R. Tyler Croy started work on JENKINS-51059 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53342) agent went offline after jenkins instance restart
Title: Message Title Jeff Thompson commented on JENKINS-53342 Re: agent went offline after jenkins instance restart Are you seeing this on multiple agents or just a single one? If it is a single one, you should investigate the configuration and network connectivity from that one machine to the master. There is likely something that changed in its configuration or networking. You could try manually verifying connectivity. If you see it on multiple agents, then you could investigate the settings on the master. Consider common configurations or behaviors among the agents that experience the problem. There isn't enough information provided for anyone else to be able to diagnose or reproduce this issue. This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite commented on JENKINS-53754 Re: svn, git plugin have different interfaces, and not good pipeline documentation The Jenkins Minute video shows how to use the GIT_COMMIT environment variable. Other environment variables are available with a similar technique. Scripted Pipeline can use the return value of the checkout step as a map which contains the environment variables for that checkout. Other variables are included in the JENKINS-45489 test case. A simpler example is in the JENKINS-50401 test case. A different example is in the JENKINS-51218 test case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52125) jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue
Title: Message Title Jeff Thompson commented on JENKINS-52125 Re: jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue Unfortunately, there is not enough information provided to be able to diagnose or reproduce this problem. If you can determine more information about how to isolate or characterize it, we could look into it in more detail. This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53755) Detect and publish Jacoco reports
Title: Message Title
Cyrille Le Clerc created an issue
Jenkins / JENKINS-53755
Detect and publish Jacoco reports
Issue Type:
New Feature
Assignee:
Cyrille Le Clerc
Components:
pipeline-maven-plugin
Created:
2018-09-24 20:34
Priority:
Major
Reporter:
Cyrille Le Clerc
Detect Jacoco reports
"MojoStarted" class="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="2018-09-24 18:00:21.408">
"/path/to/my-webapp" file="/path/to/my-webapp/pom.xml" groupId="com.mycompany.compliance" name="my-webapp" artifactId="my-webapp" packaging="jar" version="0.0.1-SNAPSHOT">
"/path/to/my-webapp/src/main/java" directory="/path/to/my-webapp/target"/>
"default-prepare-agent" goal="prepare-agent" lifecyclePhase="initialize" groupId="org.jacoco" artifactId="jacoco-maven-plugin" version="0.8.2">
${jacoco.address}
${jacoco.append}
${jacoco.classDumpDir}
${jacoco.destFile}
${jacoco.dumpOnExit}
${jacoco.exclClassLoaders}
${jacoco.inclBootstrapClasses}
${jacoco.inclNoLocationClasses}
${jacoco.jmx}
${jacoco.output}
${plugin.artifactMap}
${jacoco.port}
${project}
${jacoco.propertyName}
${jacoco.sessionId}
${jacoco.skip}
"MojoSucceeded" class="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="2018-09-24 18:00:22.635">
"/path/to/my-webapp" file="/path/to/my-webapp/pom.xml" groupId="com.mycompany.compliance" name="my-webapp" artifactId="my-webapp" packaging="jar" version="0.0.1-SNAPSHOT">
"/path/to/my-webapp/src/main/java" directory="/path/to/my-webapp/target"/>
"default-prepare-agent" goal="prepare-agent"
[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Since the original reporter no longer observes this issue and no one has provided additional information to describe, diagnose, or reproduce this issue in quite some time I am going to close this report down as Cannot Reproduce. If anyone can provide further reports and information that could move this forward we can re-open it at that time. Jenkins / JENKINS-50730 NoClassDefFound errors in Cloud Slaves Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53628) Evergreen UI messages should wrap on the screen
Title: Message Title R. Tyler Croy updated JENKINS-53628 Jenkins / JENKINS-53628 Evergreen UI messages should wrap on the screen Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52787) SEVERE: Failed to launch NIO hub java.io.IOException: Unable to establish loopback connection
Title: Message Title Jeff Thompson commented on JENKINS-52787 Re: SEVERE: Failed to launch NIO hub java.io.IOException: Unable to establish loopback connection This is probably caused by a problem relating to your network configuration on your Windows machine. Or other processes that get involved in networking, such as anti-virus and firewall. There are various discussions around the internet regarding "java.io.IOException: Unable to establish loopback connection", which may have useful information for you to try. Here is one: https://stackoverflow.com/questions/15651644/jetty-server-not-starting-unable-to-establish-loopback-connection and another https://stackoverflow.com/questions/32796856/unable-to-build-project-in-idea . This problem isn't specific to Jenkins Remoting, as demonstrated by the latter portion of the provided log. Jetty also demonstrates the same error, similar to the first link I shared. As there are no indications this is a Jenkins-specific problem I will close this issue. If you find other information that relates this specifically to Jenkins, you may re-open it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52787) SEVERE: Failed to launch NIO hub java.io.IOException: Unable to establish loopback connection
Title: Message Title Jeff Thompson closed an issue as Not A Defect Jenkins / JENKINS-52787 SEVERE: Failed to launch NIO hub java.io.IOException: Unable to establish loopback connection Change By: Jeff Thompson Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title rupert je thurner commented on JENKINS-53754 Re: svn, git plugin have different interfaces, and not good pipeline documentation ah, that is really interesting and seems powerful. i saw : https://stackoverflow.com/questions/37395860/jenkinsfile-with-two-git-repositories https://stackoverflow.com/questions/40224272/using-a-jenkins-pipeline-to-checkout-multiple-git-repos-into-same-job https://qa.nuxeo.org/jenkins/pipeline-syntax/globals https://jenkins.io/doc/pipeline/steps/workflow-scm-step/ i saw that one has "scm", "currentBuild". how would you get the author, and commit-id ? how would you put an example of such a deploy snipped if you have another jenkinsfile which is loaded, containing e.g. deploy scripts? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53628) Evergreen UI messages should wrap on the screen
Title: Message Title R. Tyler Croy started work on JENKINS-53628 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Roger Wooley commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing I'm seeing the same issue going from 1.7.2 to 1.8.3. I've lost the triggered builds section on parallel steps. If I rollback to 1.7.2 they come back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus commented on JENKINS-53286 Re: Enable Sentry user capturing We did. We now definitely have that feature enabled in Sentry UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus updated JENKINS-53286 Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Sprint: Evergreen - Milestone 1 , Evergreen - Milestone 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53725 git-plugin cannot operate on a git-worktree Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52710) ECS build nodes disconnect from Master
Title: Message Title Jeff Thompson commented on JENKINS-52710 Re: ECS build nodes disconnect from Master These sort of log messages just indicate that the channel was closed but don't give information about what caused the closure. When there isn't any additional information in the log frequently the closure was initiated by something outside of the Jenkins Remoting library. (Otherwise, there are commonly other log messages from other portions of the Remoting library.) Unfortunately, there can be lots of reasons why something closes a connection and it can be difficult to track it down. Often it has something to with the environment, the system, the OS, the hosting environment, or the network. Cloud environments provide more opportunities to make things complicated or to create transient behaviors. This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues On JENKINS-52922, Nush Ahmd reported that they were able to resolve something similar by configuring the Jenkins ping interval. This might be worth trying. If you figure anything out, please report back so that we can learn more about what areas to investigate or improve. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53747) cron schedule not parsed correctly
Title: Message Title
Mark Waite edited a comment on JENKINS-53747
Re: cron schedule not parsed correctly
I think you may have misunderstood the meaning of the "H" in the second item. I believe it means "choose a single value from within the specified range". For the execution that you specify, I think you want:{noformat}H/30 6-20 * * 1-5{noformat}If you can confirm that works as expected, could you close this bug as a user misunderstanding?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53747) cron schedule not parsed correctly
Title: Message Title Mark Waite commented on JENKINS-53747 Re: cron schedule not parsed correctly I think you may have misunderstood the meaning of the "H" in the second item. I believe it means "choose a single value from within the specified range". For the execution that you specify, I think you want: H/30 6-20 * * 1-5 If you can confirm that works as expected, could you close this bug as a user misunderstanding? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Jo Shields commented on JENKINS-53752 Re: Block PRs from forks from untrusted users No. That's the point. That setting determines whether pull requests should use Jenkinsfile from origin/ or from the fork - it has no functionality to block pull requests from users under any circumstance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Mark Waite commented on JENKINS-53752 Re: Block PRs from forks from untrusted users Isn't the option to "Discover pull requests from forks" what you are seeking, with the setting "From Users with Admin or Write permission"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53752 Block PRs from forks from untrusted users Change By: Mark Waite Attachment: github-branch-source-discover-pull-requests.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Doug Whitfield commented on JENKINS-48525 Re: Perforce plugin doesn't sync What versions of P4Jenkins is everybody here running? Some versions of P4Java do not support parallel sync, so that's possibly an issue for some of you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite commented on JENKINS-53754 Re: svn, git plugin have different interfaces, and not good pipeline documentation There is nothing on how to checkout two git URLs and use the variables. If two different Git URL's are being used from within a single Pipeline job then each checkout must be performed in a separate subdirectory with a separate checkout command performed for each repository. The git plugin does not support mixing checkouts from two unrelated repositories in the same working directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50498) Invalid Object ID in remoting module related to Proxy methods
Title: Message Title Jeff Thompson resolved as Duplicate Jenkins / JENKINS-50498 Invalid Object ID in remoting module related to Proxy methods Change By: Jeff Thompson Status: Open Resolved Resolution: Duplicate Released As: Remoting 3.26 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title rupert je thurner commented on JENKINS-53754 Re: svn, git plugin have different interfaces, and not good pipeline documentation thank you so much for the documentation. there is nothing on how to check out 2 git urls and use the variables? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title rupert je thurner assigned an issue to Mark Waite Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Change By: rupert je thurner Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite commented on JENKINS-53754 Re: svn, git plugin have different interfaces, and not good pipeline documentation Refer to the following resources for additional information on the results of a checkout: Jenkins Minute video that describes how to use git environment variables Pipeline SCM Step for checkout How to customize checkout for Multibranch Pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation
Title: Message Title rupert je thurner created an issue Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Issue Type: Improvement Assignee: Mark Waite Components: git-plugin, subversion-plugin Created: 2018-09-24 18:57 Priority: Minor Reporter: rupert je thurner the subversion plugin supports multiple roots and sets variables like SVN_REVISION_1. the git-plugin does the same and sets GIT_COMMIT. the suversiom-plugin sets SVN_URL_1, the git plugin sets GIT_URL, or GIT_URL_1 for the first one, depending how many there are. there is a request JENKINS-34271 to add GIT_COMMIT_n to the git plugin, which was closed with "use pipeline plugin", without referring to more details. it would be great to make this consistent. and document it so it can be found easily. Add Comment
[JIRA] (JENKINS-34271) Cannot Retrieve Commit Hashes when Using Multiple Get Repositories
Title: Message Title rupert jenkins thurner commented on JENKINS-34271 Re: Cannot Retrieve Commit Hashes when Using Multiple Get Repositories can you elaborate where this is documented in the pipeline plugin? i saw: https://stackoverflow.com/questions/40224272/using-a-jenkins-pipeline-to-checkout-multiple-git-repos-into-same-job Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42440) Job directory is empty when using pipeline multi-branch
Title: Message Title Mark Waite commented on JENKINS-42440 Re: Job directory is empty when using pipeline multi-branch Omar Malik it won't help to ask a question as a comment on an unrelated bug report. Please refer to the documentation, mailing lists, chat channels, and other locations. The bug database is intentionally used for bug reports rather than answering technical questions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42440) Job directory is empty when using pipeline multi-branch
Title: Message Title Omar Malik commented on JENKINS-42440 Re: Job directory is empty when using pipeline multi-branch This is my first Jenkins post. I have an issue, when I am trying to read a Jenkins file (from RTC) i get Access denied. I am really not sure how to continue or why my Jenkinsfile cannot be read from RTC. The Jenkinsfile is placed in the workspace@scripts directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53529) Evergreen client should be able to automatically update itself
Title: Message Title R. Tyler Croy stopped work on JENKINS-53529 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53748) SAML plugin skips Jenkins Proxy Configuration
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-53748 SAML plugin skips Jenkins Proxy Configuration Change By: Ivan Fernandez Calvo Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53748) SAML plugin skips Jenkins Proxy Configuration
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53748 Re: SAML plugin skips Jenkins Proxy Configuration I strongly recommend to not have a proxy between Jenkins and the Idp, to avoid issues with certificates, Man-in-the-middle, caches, and other kind of potential issues. You have to keep in mind that connection is an authentication connection type, it is not a web page, put something in the middle decrease the security and make thinks complex where should be as simplex as possible. As workaround you can configure the java proxy settings https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html . Not long time ago (I think that was Jesse) I have a conversation about which would be the right setting on the plugins proxy configuration or with the JVM properties. The JVM properties win because you do not have to make anything on code. However I am going to implemented support to the plugins proxy configuration in the next release. There is no ETA for this release 2-4 weeks (or more it depends of my spare time) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48848) Discover permissions check doesn't work
Title: Message Title John Zila commented on JENKINS-48848 Re: Discover permissions check doesn't work Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48848) Discover permissions check doesn't work
Title: Message Title Sam Schwarz commented on JENKINS-48848 Re: Discover permissions check doesn't work I made Jira issues to request this to be a feature and to change the documentation to be more clear about the actual functionality. https://issues.jenkins-ci.org/browse/JENKINS-53753 and https://issues.jenkins-ci.org/browse/JENKINS-53752 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48848) Discover permissions check doesn't work
Title: Message Title John Zila commented on JENKINS-48848 Re: Discover permissions check doesn't work Yeah that makes sense. It has several problems, however: 1. It's difficult to discover what is happening. It seems like it shouldn't build, but instead it builds? And it's not easy to determine whether it's building from the merge target's Jenkinsfile or the branch one. 2. Jenkinsfiles are hardly the only security risk for forked builds. Just echoing an environment variable from a modified source file can be hugely damaging, potentially revealing secrets. Not to mention the ability to curl out and/or execute arbitrary code as the jenkins user on a build machine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53753) Misleading documentation for permissions
Title: Message Title Sam Schwarz created an issue Jenkins / JENKINS-53753 Misleading documentation for permissions Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-09-24 17:42 Labels: security Priority: Major Reporter: Sam Schwarz The plugin has an option to discover PRs from forks and only trust those with admin or write access. The documentation is misleading and makes it sound as thought this will block PRs from untrusted users from being built. Instead this causes the original Jenkinsfile to be used instead of the Jenkinsfile from the fork. Not only is the phrasing of the documentation misleading, it still allows for many vectors of attack such as changing a file that the original Jenkinsfile calls. Add Comment
[JIRA] (JENKINS-53741) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable
Title: Message Title Oleg Nenashev commented on JENKINS-53741 Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable The root cause s incorrect generic handling, https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/DescribableList.java#L126 should be OK on its own. Most likely there is a bogus NodeProperty being submitted. Please provide current config.xml for global node properties (make sure to remove secrets if any) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48848) Discover permissions check doesn't work
Title: Message Title Andrew Bayer commented on JENKINS-48848 Re: Discover permissions check doesn't work This is an interesting one - the implementation is actually intended to block running any changes in the Jenkinsfile from an untrusted fork, instead using the merge target's Jenkinsfile unchanged, rather than blocking building of an untrusted fork's PR entirely. But that does seem to be a worthwhile feature to consider adding. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Sam Schwarz created an issue Jenkins / JENKINS-53752 Block PRs from forks from untrusted users Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-09-24 17:15 Labels: security configuration Priority: Major Reporter: Sam Schwarz The plugin currently has no way to block untrusted users from making a PR from a fork and having this PR built by Jenkins. The GitHub Pull Request Builder does have this feature which is very useful for open source projects to protect the build system from malicious changes. The documentation on the GitHub Pull Request Builder wiki page says to move from the GHPRB plugin to the GitHub Branch source plugin which causes the user to lose this extremely useful functionality. Add Comment
[JIRA] (JENKINS-51491) Remoting Thread Terminated Randomly
Title: Message Title Jeff Thompson commented on JENKINS-51491 Re: Remoting Thread Terminated Randomly Possibly related and worth trying. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51491) Remoting Thread Terminated Randomly
Title: Message Title Jeff Thompson commented on JENKINS-51491 Re: Remoting Thread Terminated Randomly On JENKINS-52922, Nush Ahmd reported that they were able to resolve something similar by configuring the Jenkins ping interval. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title Jeff Thompson commented on JENKINS-52922 Re: slave is getting disconnected in the middle of the job Nush Ahmd, thanks for sharing that information. I'm glad it resolved your issue and maybe it will also help others. Just a note: hudson.slaves.ChannelPinger.pingInterval was deprecated in Jenkins 2.37. It was replaced by hudson.slaves.ChannelPinger.pingIntervalSeconds. Instead of assigning it a value of 2 in your case, you would want to assign it a value of 120 (seconds). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53751) The same parallel scripted and declarative pipelines rendered differently
Title: Message Title
Taras Postument created an issue
Jenkins / JENKINS-53751
The same parallel scripted and declarative pipelines rendered differently
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
declarative.log, declarative.png, scripted.log, scripted.png
Components:
blueocean-plugin
Created:
2018-09-24 17:02
Labels:
blueocean
Priority:
Major
Reporter:
Taras Postument
Hello, I'm trying to migrate my Declarative pipelines to scripted ones and cannot reproduce behavior completely. In order to visualize issue I created 2 identical pipelines defined in a scripted way and in a declarative way. Scripted:
node {
stage("Build") {
parallel([
"Android":{ stage("Android"){ stage("a"){ echo "x" }; stage("a1"){ echo "x" }}},
"iOS":{ stage("iOS"){stage("b"){ echo "x" }; stage("a2"){ echo "x" }}}
])
}
}
Declarative:
pipeline {
agent any
stages {
stage('Build') {
failFast true
parallel {
stage('Android') {
stages {
stage('a') { steps { echo
[JIRA] (JENKINS-53750) Shell scripts keep the working directory locked on Windows
Title: Message Title
Roman Donchenko created an issue
Jenkins / JENKINS-53750
Shell scripts keep the working directory locked on Windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2018-09-24 16:58
Environment:
Jenkins 2.138.1 Durable Task plugin 1.22
Labels:
windows sh
Priority:
Major
Reporter:
Roman Donchenko
Try to run the following pipeline on a Windows node (you'll need a Unix shell port; I am using bash from Git for Windows):
node('mynode') {
stage('Test') {
dir('foo/bar') { sh 'sleep 1' }
bat 'rename foo baz'
}
}
The bat step will fail with an "Access is denied" message. It seems that the reason for this is that when the Durable Task plugin runs its wrapper script (in BourneShellScript.launchWithCookie), it doesn't wait for the wrapper process to finish before it allows pipeline execution to proceed to the next step. It only waits until the result file gets created. This means that for a fraction of time, the bat step will be running concurrently with these three processes created for the sh step:
The wrapper script.
The nohup
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Sam Van Oort commented on JENKINS-50993 Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Apurv Raj Have you tried the Stage View 2.10 upgrade? This looks like it may be a URL generation quirk somehow triggered by something the Splunk Plugin does – the 2.10 update includes at least some fixes to URL generation logic in Stage View. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53397) ChannelClosedException when using kafka nodes
Title: Message Title Jeff Thompson commented on JENKINS-53397 Re: ChannelClosedException when using kafka nodes That's good news, Federico Naum. Pham Vu Tuan, I would be surprised at Remoting 3.26 causing a new exception. Let me know if you continue to see issues there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46158) Add support for Kotlin static analysis using detekt tool
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-46158 Add support for Kotlin static analysis using detekt tool Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: 5.0.0-beta1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48529) NPE when clicking define value for trend graph for warnings plugin in pipeline snippet generator
Title: Message Title Ulli Hafner updated JENKINS-48529 I removed that part in the upcoming 5.0 release. Jenkins / JENKINS-48529 NPE when clicking define value for trend graph for warnings plugin in pipeline snippet generator Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51992) All warnings are "fixed" and "new" every build when used with pipeline
Title: Message Title Ulli Hafner commented on JENKINS-51992 Re: All warnings are "fixed" and "new" every build when used with pipeline I think a simple workaround would be to pipe the output to a file and remove the prefixes using a shell command. In the upcoming 5.x release it is possible to provide a preprocessor for the text that is scanned. However, it is not configurable in the UI in the moment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53749) Ensure that Sentry errors are being sent from the backend service properly
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53749 Ensure that Sentry errors are being sent from the backend service properly Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-24 16:33 Priority: Minor Reporter: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51894) Use UncheckedIOException where possible
Title: Message Title Ulli Hafner updated JENKINS-51894 Jenkins / JENKINS-51894 Use UncheckedIOException where possible Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52236) Being able to configure some parameters after choosing a parser
Title: Message Title Ulli Hafner updated JENKINS-52236 See documentation. Jenkins / JENKINS-52236 Being able to configure some parameters after choosing a parser Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Ulli Hafner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration It is in the admin section due to security reasons: the script can basically do anything on your system so it is only safe to be checked by an admin. I think we found a secure workaround for this: I will prohibit Groovy parsers to scan the console log. They are permitted only to scan files on the agent. Then only an agent might be compromised by a not well behaving script. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53684) Provide links for all tabs in details page
Title: Message Title Flash Sheridan commented on JENKINS-53684 Re: Provide links for all tabs in details page I really like the beginning of the Clang Warnings page (below, deliberately truncated), with New and Fixed Warnings prominently displayed: The beginning of the CheckStyle (in our case actually Scala Style) page is less informative: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53684) Provide links for all tabs in details page
Title: Message Title Flash Sheridan updated an issue Jenkins / JENKINS-53684 Provide links for all tabs in details page Change By: Flash Sheridan Attachment: Warnings trend.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53684) Provide links for all tabs in details page
Title: Message Title Flash Sheridan updated an issue Jenkins / JENKINS-53684 Provide links for all tabs in details page Change By: Flash Sheridan Attachment: Checkstyle warnings top.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52238) is it possible to save in one file all parser created in jenkins ?
Title: Message Title Ulli Hafner updated JENKINS-52238 See documentation. Jenkins / JENKINS-52238 is it possible to save in one file all parser created in jenkins ? Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52574) Provided author and commit ID for Git jobs
Title: Message Title Ulli Hafner updated JENKINS-52574 Jenkins / JENKINS-52574 Provided author and commit ID for Git jobs Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53567) Create tools for all of the violations parsers (alias to other parser)
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-53567 Create tools for all of the violations parsers (alias to other parser) Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: R. Tyler Croy Epic Status: To Do Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53748) SAML plugin skips Jenkins Proxy Configuration
Title: Message Title Carlos Lopez created an issue Jenkins / JENKINS-53748 SAML plugin skips Jenkins Proxy Configuration Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: Jenkins-ProxyConf.png, SAML_skipProxy.png Components: saml-plugin Created: 2018-09-24 16:05 Environment: Jenkins LTS 2.121.x saml:1.0.7 Priority: Major Reporter: Carlos Lopez Using a fake proxy like 999.999.999.999:8080 for Running Jenkins Behind a Proxy Configuration, and then testing a URL (https://federation.basf.com/nidp/saml2/metadata) and results are expected, the URL is not reachable.What is not expected is that for SAML plugin configuration > Idp Metadata Test URL, it succeeded to connect. As result, we can determinate that the saml plugin is skipping the proxy configuration. Add Comment
[JIRA] (JENKINS-50255) Tickets describing the onboarding experience for Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50255 Tickets describing the onboarding experience for Jenkins Essentials Change By: R. Tyler Croy Epic Status: To Do Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
