[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-54064 Gradle plugin uses legacy plugin format Change By: René Scheibe Released As: gradle-jpi-plugin 0.36.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194683.1539463436000.14912.1577092981883%40Atlassian.JIRA.
[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-54064 Gradle plugin uses legacy plugin format Change By: René Scheibe Component/s: gradle-jpi-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194683.1539463436000.14909.1577092981716%40Atlassian.JIRA.
[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format
Title: Message Title René Scheibe reopened an issue Jenkins / JENKINS-54064 Gradle plugin uses legacy plugin format Change By: René Scheibe Resolution: Fixed Status: Resolved Reopened Assignee: Steve Hill René Scheibe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194683.1539463436000.14915.1577093040357%40Atlassian.JIRA.
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert Summary: Tech support analyst jobs iso certfication In Oman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198458.1553854779000.14919.1577093100706%40Atlassian.JIRA.
[JIRA] (JENKINS-56808) Tech support analyst jobs
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 Tech support analyst jobs Change By: iso cert Technical Support Analysts are trained IT support professionals, who resolve a variety of technical issues relating to their organization's computer systems, telecommunication network, LANs, WANs and desktop computers, whether these components are located onsite or in the field. Organizations are dependent on support analysts to actualize their organization's potential.Technical Support Analysts are experts who provide the foundation of an organization's digital infrastructure. Specifically, Technical Support Analysts are specialists who provide technical support, advice, and assistance to an organization and its customers. They help resolve hardware, software and other technical problems. They often provide front-line support for system issues, whether these issues be in the organization or at a customer's premise. Now the concept of freelancing has come into the picture. As a freelance technical support analyst, you can enjoy the benefits of flexibility.If you are looking for freelance opportunities in this field, register on FieldEngineer.com. Here you can find terrific job opportunities tailored to your needs. Currently, the site provides a one-stop solution, with more than 40,000+ freelancers from over 180 countries.Read More: *[Tech support analyst jobs|[https://www.fieldengineer.com/skills/technical-support-analyst]]* Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc44
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert URL: https http :// www factocert . fieldengineer. com/ skills/technical iso - support certification - analyst in-oman/ [Factocert |http://example.com]is an Epitome of consultation inculcating industry best practices. Our pragmatic approach delineates the requirements of ISO Standards, CE Mark, VAPT, Six Sigma, Process Audit and other International Standards. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on t
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert [ [ Factocert |http:// factocert.com] |http:// example.com / ]is an Epitome of consultation inculcating industry best practices. Our pragmatic approach delineates the requirements of ISO Standards, CE Mark, VAPT, Six Sigma, Process Audit and other International Standards. [ISO Certification in Oman|http://factocert.com/iso-certification-in-oman/] [|http://example.com/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198458.1553854779000.14923.1577093280925%40Atlassian.JIRA.
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert [[Factocert|http://factocert.com] |http: / /example.com/ ]is an Epitome of consultation inculcating industry best practices. Our pragmatic approach delineates the requirements of ISO Standards, CE Mark, VAPT, Six Sigma, Process Audit and other International Standards. Intellectual Curiosity of our Consulting team provides a better approach in understanding the unmet needs of the customers which leads the way in delivering sustainable solutions.Our consulting experts carry their domain experience in order to fulfill the customer requirements enabling us to be a one stop solution. Clients count on Factocert to help them transform uncertainty into possibility. [ISO Certification in Oman|http://factocert.com/iso-certification-in-oman/] [ http://example.com/ |http://example.com/] [ISO certification body in Oman|http://factocert.com/iso-certification-in-oman/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert [ [ Factocert |http://factocert.com]/]is an Epitome of consultation inculcating industry best practices. Our pragmatic approach delineates the requirements of ISO Standards, CE Mark, VAPT, Six Sigma, Process Audit and other International Standards.Intellectual Curiosity of our Consulting team provides a better approach in understanding the unmet needs of the customers which leads the way in delivering sustainable solutions.Our consulting experts carry their domain experience in order to fulfill the customer requirements enabling us to be a one stop solution. Clients count on Factocert to help them transform uncertainty into possibility.[ISO Certification in Oman|http://factocert.com/iso-certification-in-oman/] [http://example.com/ |http://example.com/][ISO certification body in Oman|http://factocert.com/iso-certification-in-oman/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56808) iso certfication In Oman
Title: Message Title iso cert updated an issue Jenkins / JENKINS-56808 iso certfication In Oman Change By: iso cert [Factocert |http://factocert.com / ]/]is an Epitome of consultation inculcating industry best practices. Our pragmatic approach delineates the requirements of ISO Standards, CE Mark, VAPT, Six Sigma, Process Audit and other International Standards.Intellectual Curiosity of our Consulting team provides a better approach in understanding the unmet needs of the customers which leads the way in delivering sustainable solutions.Our consulting experts carry their domain experience in order to fulfill the customer requirements enabling us to be a one stop solution. Clients count on Factocert to help them transform uncertainty into possibility.[ISO Certification in Oman|http://factocert.com/iso-certification-in-oman/] [http://example.com/ |http://example.com/] [ISO certification body in Oman|http://factocert.com/iso-certification-in-oman/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59501) ConcurrentModificationException during startup of Image.inside() step
Title: Message Title Oleg Nenashev updated JENKINS-59501 https://github.com/jenkinsci/docker-commons-plugin/releases/tag/docker-commons-1.16 Jenkins / JENKINS-59501 ConcurrentModificationException during startup of Image.inside() step Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Docker Commons 1.16 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-3666) Polling not working as intended
Title: Message Title Daire Kennedy assigned an issue to Praqma Support Jenkins / JENKINS-3666 Polling not working as intended Change By: Daire Kennedy Assignee: Daire Kennedy Praqma Support Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.133739.1242042897000.14994.1577098620446%40Atlassian.JIRA.
[JIRA] (JENKINS-3666) Polling not working as intended
Title: Message Title Daire Kennedy assigned an issue to Daire Kennedy Jenkins / JENKINS-3666 Polling not working as intended Change By: Daire Kennedy Assignee: Andrew Bayer Daire Kennedy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.133739.1242042897000.14991.1577098620381%40Atlassian.JIRA.
[JIRA] (JENKINS-60572) JEP for the CommunityBridge donations process
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-60572 JEP for the CommunityBridge donations process Issue Type: Task Assignee: Unassigned Components: other Created: 2019-12-23 10:57 Priority: Minor Reporter: Oleg Nenashev We can accept donations to Jenkins through Community Bridge. This process needs to be documented as JEP and discussed in the developer mailing list. Then it should be approved by the governance meeting Add Comment This message was sent by Atlassian Jira (
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title pjdarton commented on JENKINS-39636 Re: Could not initialize class org.jfree.chart.JFreeChart > I can confirm on Ubuntu using the openjdk-8-jdk solves this problem. ...so can I, although in my case (I had the headless jre installed initially), I had to reboot my server. Just stopping and restarting the Jenkins service didn't change anything. I remain "somewhat disgruntled" about installing the non-headless JRE on a headless server; IMO a headless server should not have any X11 code on it anywhere and installing the non-headless JRE pulled in numerous X11-related packages which offends my sense of neatness ... but my devs don't care as they're just happy they've got their pretty graphs back again, and it didn't take long either Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176200.1478758105000.15008.1577099340351%40Atlassian.JIRA.
[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 M McGrath 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 Hi Liam Newman I have been able to take your sample pipelines (Script_Splitting.groovy and Script_Splittingx10.groovy) I can reproduce the issue “Method Code too large” When I enable "SCRIPT_SPLITTING_TRANSFORMATION=true" the 2 pipelines you provided run successfully. When I add Script_Splitting.groovy to a shared Lib under /var, add shared library under jenkins config sys, Create a mock app with Jenkinsfile which consumes pipeline, and setup a Multibranch job I reproduce “Method Code too large” Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.15022.1577101681548%40Atlassian.JIRA.
[JIRA] (JENKINS-60573) global security security settings link in "project configuration" is not correct.
Title: Message Title João Pereira created an issue Jenkins / JENKINS-60573 global security security settings link in "project configuration" is not correct. Issue Type: Bug Assignee: Unassigned Attachments: Capture-1.PNG, Capture-2.PNG Components: core Created: 2019-12-23 12:07 Environment: Jenkins ver. 2.210 Plugins Nome ↓ Versão Activo ace-editor 1.1 true ant 1.10 true antisamy-markup-formatter 1.6 true apache-httpcomponents-client-4-api 4.5.10-2.0 true authentication-tokens 1.3 true authorize-project 1.3.0 true bouncycastle-api 2.17 true branch-api 2.5.5 true build-timeout 1.19 true cloudbees-folder 6.10.1 true command-launcher 1.4 true credentials 2.3.0 true credentials-binding 1.20 true display-url-api 2.3.2 true docker-commons 1.15 true docker-workflow 1.21 true durable-task 1.33 true email-ext 2.68 true git 4.0.0 true git-client 3.0.0 true git-server 1.8 true github 1.29.5 true github-api 1.95 true github-branch-source 2.5.8 true gradle 1.34 true handlebars 1.1.1 true jackson2-api 2.10.1 true jdk-tool 1.4 true jquery-detached 1.2.1 true jsch 0.1.55.1 true junit 1.28 true keycloak 2.3.0 true ldap 1.21 true lockable-resources 2.7 true mailer 1.29 true mapdb-api 1.0.9.0 true matrix-auth 2.5 true matrix-project 1.14 true momentjs 1.1.1 true pam-auth 1.6 true pipeline-build-step 2.10 true pipeline-github-lib 1.0 true pipeline-graph-analysis 1.10 true pipeline-input-step 2.11 true pipeline-milestone-step 1.3.1 true pipeline-model-api 1.5.0 true pipeline-model-declarative-agent 1.1.1 true pipeline-model-definition 1.5.0 true pipeline-model-extensions 1.5.0 true pipeline-rest-api 2.12 true pipeline-stage-step 2.3 true pipeline-stage-tags-metadata 1.5.0 true pipeline-stage-view 2.12 true plain-credentials 1.5 true resource-disposer 0.14 true scm-api 2.6.3 true script-security 1.68 true ssh-credentials 1.18 true ssh-slaves 1.31.0 true structs 1.20 true subversion 2.13.0 true timestamper 1.10 true token-macro 2.10 true trilead-api 1.0.5 true workflow-aggregator 2.6 true workflow-api 2.38 true workflow-basic-steps 2.18 true workflow-cps 2.78 true workflow-cps-global-lib 2.15 true workflow-durable-task-step 2.35 true workflow-job 2.36 true workflow-multibranch 2.21 true workflow-scm-step 2.9 true workflow-step-api 2.21 true workflow-support 3.3 true ws-cleanup 0.38 true
[JIRA] (JENKINS-60559) Job string parameters are unpredictably changed
Title: Message Title
Kornel Jankowski updated an issue
Jenkins / JENKINS-60559
Job string parameters are unpredictably changed
Change By:
Kornel Jankowski
I create a freestyle job, which runs a trivial shell script:{code:java}echo language $languageecho LANGUAGE $LANGUAGE{code}I create it as a freestyle job with two string parameters (`LANGUAGE` and `language`). When I set the parameters (using the GUI configurator) to:{code:java}LANGUAGE=zu-UOlanguage=sa-TN{code}The output is:{code:java}languageLANGUAGE sa-TN{code}While it should be{code:java}language sa-TNLANGUAGE zu-UO{code}And what's more: when i configure the same parameter values, but the order of parameters in the job configuration is reverse (yes, I just dragged one and moved it in the GUI), and so I set:{code:java}language=sa-TNLANGUAGE=zu-UO{code}The output is DIFFERENT! this time:{code:java}language sa-TNLANGUAGE{code}Which, anyway, is still wrong, though, as it still should be:{code:java}language sa-TNLANGUAGE zu-UO{code}This happens on a clean setup with default plugins prepared in a docker container from your dockerhub, both on current lts (2.204.1) and on latest (2.209).At this point, I simply do not now how to configure my jobs' parameters. Within my real setup (currently on 2.176.3) jobs that used to successfully work when configured with a parameter named `language` (*even if there is no uppercase parameter named* *`LANGUAGE`*** so there cannot be a upper-lower-case collision) now randomly start to misbehave - the parameter `language` isn't even set. Changing anything (even totally unrelated) in a job configuration results in blowing up a working configuration where the 'language' variable has been used for a long time without any problems.
Add Comment
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title
Erez Arbell commented on JENKINS-51552
Re: Cannot replay pipelines - files are read-only
problem 1: I need to check. problem 2: Thank you. problem 3: My Jenkinsfile:
def f5Lib, testsLib
timestamps{
try {
node ('master') {
f5Lib = loadLib('//depot/project/automation/fit/jenkins/pipeline')
testsLib = loadTestsLib('//test/maint/bigip14.1.0/automation/fit/TrafficShield/autotest/bvt-jenkins/src')
}
}
catch (e) {
throw e
}
}
def loadLib(mapping) {
def p4ClientFormat = "jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-lib"
return loadLibrary(
clientFormat: p4ClientFormat,
p4Mapping: "${mapping}"
)
}
def loadTestsLib(autotestMapping) {
def p4ClientFormat = "jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-tests"
return loadLibrary(
clientFormat: p4ClientFormat,
p4Mapping: "${autotestMapping}"
)
}
def loadLibrary(args) {
return lib = library( identifier: '@now', retriever: modernSCM(globalLib(charset: 'none', credential: env.P4_CREDENTIAL, id: args.clientFormat, path: args.p4Mapping)))
}
And I get the message:
Only using first definition of library
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59478) Automatically label Clear Linux agents
Title: Message Title Mark Waite updated JENKINS-59478 Jenkins / JENKINS-59478 Automatically label Clear Linux agents Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202093.1569240425000.15106.1577105880270%40Atlassian.JIRA.
[JIRA] (JENKINS-59478) Automatically label Clear Linux agents
Title: Message Title Mark Waite updated JENKINS-59478 Jenkins / JENKINS-59478 Automatically label Clear Linux agents Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202093.1569240425000.15111.1577105940713%40Atlassian.JIRA.
[JIRA] (JENKINS-59478) Automatically label Clear Linux agents
Title: Message Title Mark Waite updated JENKINS-59478 Jenkins / JENKINS-59478 Automatically label Clear Linux agents Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202093.1569240425000.15110.1577105940299%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated JENKINS-27975 Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.15113.1577108160325%40Atlassian.JIRA.
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Lance Swoboda commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError I was able to finally overcome this problem by taking these steps: Update the jenkins.xml file to use a 64bit JRE increase max heap size to 1024m for the JRE (in the jenkins.xml file) increase the stack size to 4m in the jenkins.xml as well (-Xss4m) hope this is helpful for someone else. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192947.1533846304000.15115.1577108940754%40Atlassian.JIRA.
[JIRA] (JENKINS-60574) Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin
Title: Message Title Konstantin Satunin created an issue Jenkins / JENKINS-60574 Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-12-23 13:50 Priority: Major Reporter: Konstantin Satunin After introduction of direct connection option in kubernetes plugin and remoting it's now possible to avoid http(s) requests to jenkins host. But if you want to connect agents which are tunneled, it's not possible to utilize direct connection because kubernetes plugin uses Jenkins host and port reported by TCP agent listener. https://github.com/jenkinsci/kubernetes-plugin/blob/33737fe0c96615e33b78205fe6e71aaffca2df49/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplateBuilder.java#L345 Currently there are no way to modify JENKINS_DIRECT_CONNECTION in the container using podTemplate because PodTemplateBuilder overrides any environment variables. Proposal Introduce one more property "Direct connection endpoint" in the cloud configuration under Direct Connection settings and allow to set it to be set to host:port string. If this direct connection endpoint was not set, use default values from TcpSlaveAgentListener like its done now.
[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host
Title: Message Title
Eric Schneider commented on JENKINS-60473
Re: Docker pipeline: 'absolute path' error when running linux container under windows host
I looked further into the indefinite freezing that I mentioned in a previous comment. My changes to the volume and working directory paths do result in the docker container starting successfully. The freeze is happening during the 'sh' command since the withDockerContainer block. The 'sh' command generates a really complex inline script to track the progress of the command and capture its output. The script's command also gets written to a file and is referenced. There are multiple absolute path references which use Windows's format. These fail on the Linux side and, because no output is written to the proper location, the 'sh' command waits indefinitely for it to finish. (It will eventually time out, but would otherwise wait forever.) If I capture the command in the Jenkins logs and rework all of the paths to be Linux-friendly, the command runs in docker successfully and Jenkins immediately moves to the next pipeline command/step. I tried to leverage the 'ws' command to force a Linux-friendly path inside the withDockerContainer block, but this causes new problems. Namely it causes the host-side of the 'sh' command to work in the wrong place - causing the same end result. You MIGHT be able to mostly work around this problem by using a Linux-friend path (like "/Jenkins") for the workspace root for the Windows node... but some of the commands may still use backslashes for path separators and cause failures. It's also not a user-friendly solution. At minimum, it seems like the Decorator class used by withDockerContainer needs to comb through the launcher's commands list ("cmds") and replace all of the Windows paths with Linux-friendly paths. A regular _expression_ might be able to do it, but I haven't tried yet. It's tricky with the amount of text being added to the command list. Maybe someone with more knowledge of Jenkins has a more elegant solution.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Pierre Beitz commented on JENKINS-49499 Re: Jenkins admin logs through Logger List not getting captured Anand Shekhar could you please clarify what those events are? Which plugin are you using generates those events? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188390.1518428802000.15150.1577109120189%40Atlassian.JIRA.
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-49499 Jenkins admin logs through Logger List not getting captured Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188390.1518428802000.15152.1577109120220%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.15163.1577109240934%40Atlassian.JIRA.
[JIRA] (JENKINS-53430) Capture logged in username and IP Address Audit Trail Plugin
Title: Message Title Pierre Beitz closed an issue as Incomplete Jenkins / JENKINS-53430 Capture logged in username and IP Address Audit Trail Plugin Change By: Pierre Beitz Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193623.153616120.15159.1577109240801%40Atlassian.JIRA.
[JIRA] (JENKINS-53430) Capture logged in username and IP Address Audit Trail Plugin
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-53430 Capture logged in username and IP Address Audit Trail Plugin Change By: Pierre Beitz Assignee: Tomasz Sęk Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193623.153616120.15155.1577109240711%40Atlassian.JIRA.
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-49499 Jenkins admin logs through Logger List not getting captured Change By: Pierre Beitz Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188390.1518428802000.15161.1577109240858%40Atlassian.JIRA.
[JIRA] (JENKINS-53430) Capture logged in username and IP Address Audit Trail Plugin
Title: Message Title Pierre Beitz commented on JENKINS-53430 Re: Capture logged in username and IP Address Audit Trail Plugin Closing for inactivity, please reopen in case you still have this need and have details on the feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193623.153616120.15157.1577109240740%40Atlassian.JIRA.
[JIRA] (JENKINS-22246) Audit Trail Plugin should record system changes
Title: Message Title Pierre Beitz commented on JENKINS-22246 Re: Audit Trail Plugin should record system changes Closing for inactivity. Please reopen in case you have details on the missing feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154026.1395153072000.15165.1577109300294%40Atlassian.JIRA.
[JIRA] (JENKINS-22246) Audit Trail Plugin should record system changes
Title: Message Title Pierre Beitz closed an issue as Incomplete Jenkins / JENKINS-22246 Audit Trail Plugin should record system changes Change By: Pierre Beitz Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154026.1395153072000.15167.1577109300322%40Atlassian.JIRA.
[JIRA] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-23601 Modify Audit Trail plugin to log information based on user type Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155983.1403863263000.15171.1577109720245%40Atlassian.JIRA.
[JIRA] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type
Title: Message Title Pierre Beitz commented on JENKINS-23601 Re: Modify Audit Trail plugin to log information based on user type David Thomas coming late on this issue, I'm not sure I understand properly. You want to filter the logs based on a given user/role? Currently the plugin does not have any knowledge about any role. In case you still have this need, I'd like to understand better what exactly you expect out of this task. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155983.1403863263000.15169.1577109720219%40Atlassian.JIRA.
[JIRA] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-23601 Modify Audit Trail plugin to log information based on user type Change By: Pierre Beitz Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155983.1403863263000.15173.1577109780458%40Atlassian.JIRA.
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Stefan Spieker commented on JENKINS-36720 Re: Investigate/cleanup medium-severity FindBugs issues in the Jenkins core Current status: [INFO] Total bugs: 400 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172755.1468600777000.15175.1577109900200%40Atlassian.JIRA.
[JIRA] (JENKINS-60574) Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin
Title: Message Title Konstantin Satunin commented on JENKINS-60574 Re: Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin Vincent Latombe can you please take a look on this issue ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203697.1577109011000.15179.1577110261250%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Assignee: Alan Harder Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.15182.1577110380843%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz started work on JENKINS-11048 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.15188.1577110380985%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Issue Type: Bug Task Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.15186.1577110380916%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated JENKINS-11048 Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.15191.1577110440323%40Atlassian.JIRA.
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Oleg Nenashev commented on JENKINS-36720 Re: Investigate/cleanup medium-severity FindBugs issues in the Jenkins core Ugh. But it is still a very good progress, thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172755.1468600777000.15197.1577113200271%40Atlassian.JIRA.
[JIRA] (JENKINS-60575) Blueocean should show triggered jobs while pending
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-60575
Blueocean should show triggered jobs while pending
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
image-2019-12-23-11-52-51-685.png
Components:
blueocean-plugin
Created:
2019-12-23 16:57
Priority:
Minor
Reporter:
Josh Soref
Consider a pipeline like this:
pipeline {
stages {
stage("Trigger Deploy") {
steps {
build "happy-integration"
}
}
}
}
While the triggered build is running, the blue ocean view doesn't provide any way to get to the resultant build. Once it's built, an extra table is presented called Triggered Builds which provides easy access to it:
Add Comment
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Kalana Wijethunga commented on JENKINS-60117 Re: Rework sorting for the Enabled columns of Installed in Plugin Manager I have achieved the following expected result. Sorting by Enabled should sort into three sets: Enabled (checkbox checked) Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) Disabled (checkbox unchecked) But it can be seen that there is one more group in addition to the above and that is 'Enabled (checkbox checked) and can be disabled(because it has mandatory dependents, but all the dependents are disabled)'. I used Plugin.hasMandatoryDependencies() to check whether the plugin can be disabled or not. But seems it is incorrect in the identified case because a plugin can be disabled even if it hasMandatoryDependencies() when those dependencies are disabled. Oleg Nenashev, Daniel Beck Can somebody suggest me a better criteria to identify whether the plugins can be disabled or not, please? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenk
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Ian Katz commented on JENKINS-44924 Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting I'm on 2.190.2 of Jenkins, with BlueOcean 1.21.0. Not sure how to find workflow-cps version. I didn't see a warning, but my point is that it should produce an error, not a warning. What is the justification for allowing me to call a function that you know in advance will not do its job? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182995.1497544785000.15241.1577127421547%40Atlassian.JIRA.
[JIRA] (JENKINS-60547) KubernetesDeclarativeAgent workingDir is ignored in templating Jenkins agent pod
Title: Message Title Andrew Feller assigned an issue to Vincent Latombe Jenkins / JENKINS-60547 KubernetesDeclarativeAgent workingDir is ignored in templating Jenkins agent pod Change By: Andrew Feller Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203650.1576777975000.15243.1577129280202%40Atlassian.JIRA.
[JIRA] (JENKINS-60576) Only X-1/X files are successfully uploaded
Title: Message Title Roger Wong created an issue Jenkins / JENKINS-60576 Only X-1/X files are successfully uploaded Issue Type: Bug Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2019-12-23 22:42 Environment: Jenkins Version 2.190.2 on Windows Windows Azure Storage plugin 1.1.2 Priority: Major Reporter: Roger Wong When uploading our artifacts to storage, we have been seeing sometimes that one file will fail to upload randomly which causes the plugin to throw and ends up failing the build. The files are all under the 100mb limit so we aren't hitting the payload size limit for a single file. I don't see any specific error related to the why one of the files failed to upload, only the summary that shows one of the files that didn't upload successfully. Is there somewhere else to check to find why the upload failed? Also it would be nice if there was an option to retry the upload rather than fail the build. Here's the console log error: MicrosoftAzureStorage - Container name: artifactsMicrosoftAzureStorage - Container name: artifactsMicrosoftAzureStorage - share name: MicrosoftAzureStorage - File path: **\*.png, fingerPrint.txt,TestResults/*.xml, **\*.trx, **\*.logMicrosoftAzureStorage - Virtual path: MicrosoftAzureStorage - Exclude path: MicrosoftAzureStorage - Uploading files to Microsoft AzureUploaded to file storage with uri https://[REMOVED].blob.core.windows.net/artifacts/test-splits/reports/11/TestResults/EditableGridValidation-2019-12-23_11-35-37-9.png in 00:00:00.073 (HH:mm:ss.S)Uploaded to file storage with uri https://[REMOVED].blob.core.windows.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Here's some very course bisect-style testing. It suggests JGit 5.x might have some sort of breaking API change or perhaps a bug. These first two tests were just replication controls. The third featured a doctored Git Client plugin. All runs started with a clean workspace. Fresh repo clone each time. G 4.0.0 + GC 3.0.0 with stock JGit 5.5.1 jars NPE replicated G 3.12.1 + GC 3.0.0 with stock JGit 5.5.1 jars NPE replicated G 3.12.1 + GC 3.0.0 with downgraded JGit 4.5.7* No NPE G == Git plugin GC == Git Client plugin * == The JGit vintage bundled with GC 2.9.0. Maybe 5.5.1 is returning a null commit hash for certain references. I could not yield one by wiring JGit 5.5.1 into a Groovy shell and pointing to to the problem repo, then fetching branches and tags (and the detached HEAD). Nor did anything jump out by spelunking JGit source. But I'm no expert. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/je
[JIRA] (JENKINS-60577) computer/(master)/builds/rssLatest error 404 not found
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-60577 computer/(master)/builds/rssLatest error 404 not found Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-23 23:45 Priority: Minor Reporter: Owen Wood First, navigate to JENKINS_URL/computer/(master)/builds Attempting to click the "Atom feed for just latest builds" link results in "Error 404 not found". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Brian Ray edited a comment on JENKINS-57205
Re: Null pointer exception in JGit pre-build merge
Here's some very course coarse bisect-style testing. It suggests JGit 5.x might have some sort of breaking API change or perhaps a bug.These first two tests were just replication controls. The third featured a doctored Git Client plugin.All runs started with a clean workspace. Fresh repo clone each time.{noformat}G 4.0.0 + GC 3.0.0 with stock JGit 5.5.1 jars NPE replicatedG 3.12.1 + GC 3.0.0 with stock JGit 5.5.1 jars NPE replicatedG 3.12.1 + GC 3.0.0 with downgraded JGit 4.5.7* No NPEG == Git pluginGC == Git Client plugin* == The JGit vintage bundled with GC 2.9.0.{noformat}Maybe 5.5.1 is returning a null commit hash for certain references. I could not yield one by wiring JGit 5.5.1 into a Groovy shell and pointing to to the problem repo, then fetching branches and tags (and the detached {{HEAD}}). Nor did anything jump out by spelunking JGit source. But I'm no expert.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.15259.1577145000301%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Thanks very muhc, Brian Ray! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.15264.1577145180413%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite edited a comment on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Thanks very muhc much , [~brianeray]! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.15265.1577145180456%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Peter Wiseman Attachment: config.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.15290.1577160901280%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Peter Wiseman Attachment: org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.15301.1577160901779%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Config.xml and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml attached. config.xml org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.15303.1577160960309%40Atlassian.JIRA.
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-59401 After Upgrade to Inedo Plugin 2.5.0 could not create package Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201958.1568681322000.15316.1577169480515%40Atlassian.JIRA.
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title Andrew Sumner resolved as Fixed This is fixed by release 3.0.0 - unfortunately this is a breaking release. I've been doing some work to align the BuildMaster Jenkins Extension and the Jenkins BuildMaster Plugin and took the opportunity to finish of change back from package to build api and rename all parameters and exported variables. Jenkins / JENKINS-59401 After Upgrade to Inedo Plugin 2.5.0 could not create package Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this
[JIRA] (JENKINS-60578) Support to export failure causes in excel
Title: Message Title Gajanan Mahajan created an issue Jenkins / JENKINS-60578 Support to export failure causes in excel Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-12-24 07:00 Priority: Minor Reporter: Gajanan Mahajan Jenkins does not keep track of changes and if failure cause is deleted from Jenkins, there is no way to retrieve it. Can we please have a support to export failure causes in excel so user can periodically export it and add it to version control systems? Add Comment
