[JIRA] (JENKINS-61717) jenkins-cli.jar missing from war
Title: Message Title Daniel Beck closed an issue as Won't Fix It's now at WEB-INF/lib/cli-2.222.1.jar. Don't rely on undocumented internals, obtain it via …/jnlpJars/jenkins-cli.jar URL. Jenkins / JENKINS-61717 jenkins-cli.jar missing from war Change By: Daniel Beck Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61726) Nexus Platform plugin fail to connect to the Nexus 2 repository Server
Title: Message Title Tun Wei created an issue Jenkins / JENKINS-61726 Nexus Platform plugin fail to connect to the Nexus 2 repository Server Issue Type: Bug Assignee: Justin Young Attachments: jenkins configure nexus.png, retrive nexus repo list.txt Components: nexus-platform-plugin Created: 2020-03-28 01:13 Environment: ubuntu 18.04 LTS and Docker Priority: Major Reporter: Tun Wei Nexus Repository Manager OSS 2.14.16-01 Jenkins ver. 2.204.3 Both are installed through docker-compose. Both are typical confiuration except the nexus server is given context_path as '/', so it is using http://localhost:8081 to access to the nexus repository manager. Installed the Nexus Platform Plugin version 3.8.20200310-130318.c482b58 Please see the jenkins configuration on nexus in the snapshot. When I click the Test connection button. The following exception is thrown. *Howeve*r, I can successfully run "curl -X GET -u admin: http://localhost:8081/service/local/repositories" to retrieve list of repositories. Please see the attrached text. --
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Daniel Beck commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access secretPassword is no longer stored in proxy.xml I am unable to reproduce this on 2.222.1. The password is always stored after form submission. Are you using Groovy init hook scripts, or Configuration-as-Code to define your proxy? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205518.1585229665000.1687.1585357440165%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Daniel Beck commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access My PR only addresses the form validation. I thought I saw something that would cause this problem, but it appears not the case. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205518.1585229665000.1679.1585354800183%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Liam Newman commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters Craig Rodrigues I completely agree with what you are asking for here, but this is at least two independent issues. Both/All of the issues are valid and worth fixing, but by mushing them together it makes them less well defined and harder to make progress on. Would you mind if we scope this down to just being able to call the linter from the Web UI? The problem of "reloading" the pipeline and refreshing parameters is related, but is actually a harder problem to solve. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.192911.153375138.1672.1585354380383%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-52939 Need to lint pipeline from UI, and also parse parameters Change By: Liam Newman Component/s: blueocean-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.192911.153375138.1664.1585353900379%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Liam Newman commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head IMPORTANT: NOTE FROM A MAINTAINER: STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP SOLVE THIS! (sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information) We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ($JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks! Ramon Leon **Sorry, I don't think we can get that information from ci.jenkins.io - the infra team is overloaded and we need the zip of the build folder immediately (or very soon) after the error. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.196374.1545361815000.1623.1585352640789%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-55287
Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Change By:
Liam Newman
*IMPORTANT: NOTE FROM A MAINTAINER:*+STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP US SOLVE THIS!+(sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information)*Note from maintainer: We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ({{$JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/}}) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks!* {noformat}Creating placeholder flownodes because failed loading originals.java.io.IOException: Tried to load head FlowNodes for execution Owner[Platform Service FBI Test/1605:Platform Service FBI Test #1605] but FlowNode was not found in storage for head id:FlowNodeId 1:17 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:525) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:896) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:907) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:975) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{noformat}
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-55287
Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Change By:
Liam Newman
*IMPORTANT: NOTE FROM A MAINTAINER:*+STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP US SOLVE THIS!+(sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information)* Note from maintainer: We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ({{$JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/}}) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks! * {noformat}Creating placeholder flownodes because failed loading originals.java.io.IOException: Tried to load head FlowNodes for execution Owner[Platform Service FBI Test/1605:Platform Service FBI Test #1605] but FlowNode was not found in storage for head id:FlowNodeId 1:17 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:525) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:896) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:907) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:975) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{noformat}
[JIRA] (JENKINS-59378) Scripted Pipeline linting works from CLI but not from Api
Title: Message Title daniel taub updated an issue Jenkins / JENKINS-59378 Scripted Pipeline linting works from CLI but not from Api Change By: daniel taub Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201934.1568520391000.1540.1585349640197%40Atlassian.JIRA.
[JIRA] (JENKINS-51454) Pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title
pixman20 commented on JENKINS-51454
Re: Pipeline retry operation doesn't retry when there is a timeout inside of it
FWIW: I did a slight modification to the initial workaround and added it to our global shared libraries as retryEvenOnTimeout. It's slightly more robust:
def call(Map retryOptions, Closure closure) {
retry(retryOptions) {
try {
closure()
} catch(org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ex){
def causes = ex.getCauses()
if(causes.find { ! (it instanceof org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ExceededTimeout) }) {
throw ex
}
// Wrap the real exception and throw a RuntimeException that'll trigger the retry
throw new RuntimeException(ex)
}
}
}
Other potential solution options are to merge retry and timeout functionality to be able to allow the user to have the option of which functionality they need.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-59378) Scripted Pipeline linting works from CLI but not from Api
Title: Message Title daniel taub commented on JENKINS-59378 Re: Scripted Pipeline linting works from CLI but not from Api Same for me, but i've noticed that the java-jar jenkins-cli.jar declarative-linter < Jenkinsfile returns Jenkinsfile successfully validated even if the scripted pipeline is having syntax errors, I hope they will fix the bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201934.1568520391000.1516.1585345560253%40Atlassian.JIRA.
[JIRA] (JENKINS-55790) Enable opt-out of RawHtmlMarkupFormatter processing
Title: Message Title Marc Brugger closed an issue as Fixed Jenkins / JENKINS-55790 Enable opt-out of RawHtmlMarkupFormatter processing Change By: Marc Brugger Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.197179.1548464218000.1513.1585344720229%40Atlassian.JIRA.
[JIRA] (JENKINS-55790) Enable opt-out of RawHtmlMarkupFormatter processing
Title: Message Title Marc Brugger updated an issue Jenkins / JENKINS-55790 Enable opt-out of RawHtmlMarkupFormatter processing Change By: Marc Brugger Released As: badge-1.8 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.197179.1548464218000.1511.1585344660349%40Atlassian.JIRA.
[JIRA] (JENKINS-59603) Create unit test for MatrixBridge
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-59603 Create unit test for MatrixBridge Change By: Ulli Hafner Assignee: Ganghui Hu Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202244.1569923168000.1502.1585340580177%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick resolved as Cannot Reproduce Hmm, cannot reproduce now. I know I have seen this at least twice. Jenkins / JENKINS-61371 API tokens not persisted until user config screen is saved Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Daniel Beck has proposed PR 4607 to Jenkins core that I believe addresses this issue. It would be a great help if you could download the pull request build and run it in your environment to confirm the issue is resolved. Note that the pull request build will be deleted shortly after the pull request is merged. Once the pull request is merged, the fix will be included in the next weekly release (likely Jenkins 2.229). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205518.1585229665000.1481.1585339620125%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Mark Waite Component/s: core Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205518.1585229665000.1479.1585339380208%40Atlassian.JIRA.
[JIRA] (JENKINS-61725) Create tests for PitScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61725
Create tests for PitScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{ TestScore PitScore }} part in method [ gradePit| https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java# L146|gradeTests L109 ].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205551.1585338673000.1477.1585338900202%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61724
Create tests for CoverageScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{CoverageScore}} part in method [ gradeCoverage| https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L127 |gradeTests ].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205550.1585338652000.1476.1585338900101%40Atlassian.JIRA.
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61722
Create tests for TestScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{TestScore}} part in method [ gradeTests| https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146 |gradeTests ].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205548.1585338376000.1474.1585338840122%40Atlassian.JIRA.
[JIRA] (JENKINS-61723) Create tests for AnalysisScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61723
Create tests for AnalysisScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{AnalysisScore}} part in method [ gradeAnalysis| https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L165 |gradeAnalysis ].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205549.158533863.1475.1585338841502%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61724
Create tests for CoverageScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{CoverageScore}} part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java# L146 L127 |gradeTests].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205550.1585338652000.1473.1585338780203%40Atlassian.JIRA.
[JIRA] (JENKINS-61723) Create tests for AnalysisScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61723
Create tests for AnalysisScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{ TestScore AnalysisScore }} part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java# L146 L165 | gradeTests gradeAnalysis ].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205549.158533863.1471.1585338780138%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61724
Create tests for CoverageScore (in AutoGrader)
Change By:
Ulli Hafner
Write a test for the {{ TestScore CoverageScore }} part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146|gradeTests].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205550.1585338652000.1472.1585338780184%40Atlassian.JIRA.
[JIRA] (JENKINS-61725) Create tests for PitScore (in AutoGrader)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61725 Create tests for PitScore (in AutoGrader) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:51 Labels: Mockito testing-course Priority: Minor Reporter: Ulli Hafner Write a test for the TestScore part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146|gradeTests]. Add Comment
[JIRA] (JENKINS-61723) Create tests for AnalysisScore (in AutoGrader)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61723 Create tests for AnalysisScore (in AutoGrader) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:50 Labels: Mockito testing-course Priority: Minor Reporter: Ulli Hafner Write a test for the TestScore part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146|gradeTests]. Add Comment
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-61722
Create tests for TestScore (in AutoGrader)
Change By:
Ulli Hafner
Create different configurations and verify all getters as well Write a test for the {{TestScore}} part in method [https://github . com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146|gradeTests].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205548.1585338376000.1467.1585338660214%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61724 Create tests for CoverageScore (in AutoGrader) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:50 Labels: Mockito testing-course Priority: Minor Reporter: Ulli Hafner Write a test for the TestScore part in method [https://github.com/jenkinsci/autograding-plugin/blob/master/src/main/java/io/jenkins/plugins/grading/AutoGrader.java#L146|gradeTests]. Add Comment
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61722 Create tests for TestScore (in AutoGrader) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:46 Labels: Mockito testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-59603) Create unit test for MatrixBridge
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59603 Create unit test for MatrixBridge Change By: Ulli Hafner Labels: Mockito help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202244.1569923168000.1457.1585338300172%40Atlassian.JIRA.
[JIRA] (JENKINS-59619) Create unit test for JobAction
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59619 Create unit test for JobAction Change By: Ulli Hafner Labels: Mockito help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202260.1569961579000.1455.1585338240061%40Atlassian.JIRA.
[JIRA] (JENKINS-61713) Improve tests for PitScore (in PitScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61713 Improve tests for PitScore (in PitScoreTest) Change By: Ulli Hafner Labels: Mockito testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205539.1585329712000.1453.1585338180220%40Atlassian.JIRA.
[JIRA] (JENKINS-61714) Improve tests for AnalysisScore (in AnalysisScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61714 Improve tests for AnalysisScore (in AnalysisScoreTest) Change By: Ulli Hafner Labels: Mockito testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205540.1585329764000.1452.1585338180156%40Atlassian.JIRA.
[JIRA] (JENKINS-61716) Improve tests for Score (in ScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61716 Improve tests for Score (in ScoreTest) Change By: Ulli Hafner Labels: Mockito testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205542.1585329997000.1454.1585338180244%40Atlassian.JIRA.
[JIRA] (JENKINS-61712) Improve tests for TestScore (in TestScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61712 Improve tests for TestScore (in TestScoreTest) Change By: Ulli Hafner Labels: Mockito testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205538.1585328871000.1451.1585338120068%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title
Jorge Yanes edited a comment on JENKINS-58753
Re: Add proxy support for the zoom plugin
I also have this problem.{code:java}2020-03-27 18:34:06.404+ [id=159] INFO i.j.p.zoom.ZoomNotifyClient#notify: Send notification to https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null2020-03-27 18:34:27.464+ [id=159] SEVERE i.j.p.zoom.ZoomNotifyClient#notify: Error posting to Zoom, url: https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null{code} At first I thought it was just ignoring the proxy settings on the advanced tab of the plugins management page, and that setting the following java opts could work{code:java}-Dhttp.proxyHost="proxy.xx.com" -Dhttp.proxyPort=3128 -Dhttps.proxyHost="proxy.xx.com" -Dhttps.proxyPort=3128 -Dhttp.nonProxyHosts="localhost||.xx.com||.xx.com"{code}but it did not. I can access the URL both with Chrome and with the following in the Jenkins script console{code:java}ProxyConfiguration.open(new java.net.URL("https://applications.zoom.us/addon/v2/jenkins/webhooks/")).content{code}I get a 401 error, but that's ok, because this test is not providing the API token. So it is not a connectivity issue. It is clearly a code problem. I found the plugin's code [here]([https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java)|https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java]And it's using the Apache HTTP client to post to the API URL, but it never takes any proxy into account. Something like this example must be implemented: [ link Example | ]( [https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java )|https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java ] ] There's another explanation here: [ link Tutorial | ]( [https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm )|https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm ] ] If I have time this weekend I might open a pull request. This doesn't seem difficult to do at all.
Add Comment
[JIRA] (JENKINS-59619) Create unit test for JobAction
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59619 Create unit test for JobAction Change By: Ulli Hafner See https://github.com/jenkinsci/warnings-ng-plugin/blob/master/plugin/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.javaNot all methods need to be covered, we need to discuss which make sense to have a test case. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202260.1569961579000.1438.1585337340225%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title
Jorge Yanes edited a comment on JENKINS-58753
Re: Add proxy support for the zoom plugin
I also have this problem.{code:java}2020-03-27 18:34:06.404+ [id=159] INFO i.j.p.zoom.ZoomNotifyClient#notify: Send notification to https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null2020-03-27 18:34:27.464+ [id=159] SEVERE i.j.p.zoom.ZoomNotifyClient#notify: Error posting to Zoom, url: https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null{code} At first I thought it was just ignoring the proxy settings on the advanced tab of the plugins management page, and that setting the following java opts could work{code:java}-Dhttp.proxyHost="proxy.xx.com" -Dhttp.proxyPort=3128 -Dhttps.proxyHost="proxy.xx.com" -Dhttps.proxyPort=3128 -Dhttp.nonProxyHosts="localhost||.xx.com||.xx.com"{code}but it did not. I can access the URL both with Chrome and with the following in the Jenkins script console{code:java}ProxyConfiguration.open(new java.net.URL("https://applications.zoom.us/addon/v2/jenkins/webhooks/")).content{code}I get a 401 error, but that's ok, because this test is not providing the API token. So it is not a connectivity issue. It is clearly a code problem. I found the plugin's code [ link here | ]( [https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java )|https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java ] ] And it's using the Apache HTTP client to post to the API URL, but it never takes any proxy into account. Something like this example must be implemented: [link Example|[https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java]]There's another explanation here: [link Tutorial| [https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm]] If I have time this weekend I might open a pull request. This doesn't seem difficult to do at all.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title
Jorge Yanes edited a comment on JENKINS-58753
Re: Add proxy support for the zoom plugin
I also have this problem.{code:java}2020-03-27 18:34:06.404+ [id=159] INFO i.j.p.zoom.ZoomNotifyClient#notify: Send notification to https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null2020-03-27 18:34:27.464+ [id=159] SEVERE i.j.p.zoom.ZoomNotifyClient#notify: Error posting to Zoom, url: https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null{code} At first I thought it was just ignoring the proxy settings on the advanced tab of the plugins management page, and that setting the following java opts could work{code:java}-Dhttp.proxyHost="proxy.xx.com" -Dhttp.proxyPort=3128 -Dhttps.proxyHost="proxy.xx.com" -Dhttps.proxyPort=3128 -Dhttp.nonProxyHosts="localhost||.xx.com||.xx.com"{code}but it did not. I can access the URL both with Chrome and with the following in the Jenkins script console{code:java}ProxyConfiguration.open(new java.net.URL("https://applications.zoom.us/addon/v2/jenkins/webhooks/")).content{code}I get a 401 error, but that's ok, because this test is not providing the API token. So it is not a connectivity issue. It is clearly a code problem. I found the plugin's code [ link here| [https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java]]And it's using the Apache HTTP client to post to the API URL, but it never takes any proxy into account. Something like this example must be implemented: [ link Example|[https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java]]There's another explanation here: [ link Tutorial| [https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm]] If I have time this weekend I might open a pull request. This doesn't seem difficult to do at all.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title
Jorge Yanes edited a comment on JENKINS-58753
Re: Add proxy support for the zoom plugin
I also have this problem.{code:java}2020-03-27 18:34:06.404+ [id=159] INFO i.j.p.zoom.ZoomNotifyClient#notify: Send notification to https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null2020-03-27 18:34:27.464+ [id=159] SEVERE i.j.p.zoom.ZoomNotifyClient#notify: Error posting to Zoom, url: https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null{code} At first I thought it was just ignoring the proxy settings on the advanced tab of the plugins management page, and that setting the following java opts could work{code:java}-Dhttp.proxyHost="proxy.xx.com" -Dhttp.proxyPort=3128 -Dhttps.proxyHost="proxy.xx.com" -Dhttps.proxyPort=3128 -Dhttp.nonProxyHosts="localhost||.xx.com||.xx.com"{code}but it did not. I can access the URL both with Chrome and with the following in the Jenkins script console{code:java}ProxyConfiguration.open(new java.net.URL("https://applications.zoom.us/addon/v2/jenkins/webhooks/")).content{code}I get a 401 error, but that's ok, because this test is not providing the API token. So it is not a connectivity issue. It is clearly a code problem. I found the plugin's code [ here : | [https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java] ] And it 's using the apache Apache HTTP client to post to the API url URL , but it never takes any proxy into account. Something like this example must be implemented: [ Example|[ https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java] ] There's another explanation here: [ Tutorial| [ https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm] ] If I have time this weekend I might open a pull request. This doesn't seem difficult to do at all.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title
Jorge Yanes commented on JENKINS-58753
Re: Add proxy support for the zoom plugin
I also have this problem.
2020-03-27 18:34:06.404+ [id=159] INFO i.j.p.zoom.ZoomNotifyClient#notify: Send notification to https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null
2020-03-27 18:34:27.464+ [id=159] SEVERE i.j.p.zoom.ZoomNotifyClient#notify: Error posting to Zoom, url: https://applications.zoom.us/addon/v2/jenkins/webhooks/xx_xxx, message: null
At first I thought it was just ignoring the proxy settings on the advanced tab of the plugins management page, and that setting the following java opts could work
-Dhttp.proxyHost="proxy.xx.com" -Dhttp.proxyPort=3128 -Dhttps.proxyHost="proxy.xx.com" -Dhttps.proxyPort=3128 -Dhttp.nonProxyHosts="localhost||.xx.com||.xx.com"
but it did not. I can access the URL both with Chrome and with the following in the Jenkins script console
ProxyConfiguration.open(new java.net.URL("https://applications.zoom.us/addon/v2/jenkins/webhooks/")).content
I get a 401 error, but that's ok, because this test is not providing the API token. So it is not a connectivity issue. It is clearly a code problem. I found the plugin's code here: https://github.com/jenkinsci/zoom-plugin/blob/master/src/main/java/io/jenkins/plugins/zoom/ZoomNotifyClient.java And it using the apache HTTP client to post to the API url, but it never takes any proxy into account. Something like this example must be implemented: https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/examples/org/apache/http/examples/client/ClientExecuteProxy.java There's another explanation here: https://www.tutorialspoint.com/apache_httpclient/apache_httpclient_using_proxy.htm If I have time this weekend I might open a pull request. This doesn't seem difficult to do at all.
Add Comment
[JIRA] (JENKINS-61721) Create tests for PitConfiguration (in PitScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61721 Create tests for PitConfiguration (in PitScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:14 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create configuration via JSON input and check that every line has been covered by a test (including the existing tests that use the configuration to compute the score). Example: AnalysisConfigurationTest. Add Comment
[JIRA] (JENKINS-61720) Create tests for CoverageConfiguration (in CoverageScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61720 Create tests for CoverageConfiguration (in CoverageScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 19:13 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create configuration via JSON input and check that every line has been covered by a test (including the existing tests that use the configuration to compute the score). Example: AnalysisConfigurationTest. Add Comment
[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61719 Create tests for TestConfiguration (in TestScoreTest) Change By: Ulli Hafner Create configuration via JSON input and check that every line has been covered by a test (including the existing tests that use the configuration to compute the score). Example: AnalysisConfigurationTest. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205545.1585335461000.1417.1585335600151%40Atlassian.JIRA.
[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61719 Create tests for TestConfiguration (in TestScoreTest) Change By: Ulli Hafner Create different configurations configuration via JSON input and verify all getters as well check that every line has been covered by a test (including the existing tests that use the configuration to compute the score) . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205545.1585335461000.1416.1585335540285%40Atlassian.JIRA.
[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61719 Create tests for TestConfiguration (in TestScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 18:57 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title AJ Schmidt edited a comment on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator This issue was closed and marked as a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-33051However, the spread ` \ *` and spread-dot ` \ *.` operators are separate, not the same. See the below links for reference. [https://www.javaworld.com/article/2074149/groovy-s-spread-and-spread-dot-operators.html][https://www.logicbig.com/tutorials/misc/groovy/spread-operator.html][https://groovy-lang.org/operators.html#_spread_operator][https://groovy-lang.org/operators.html#_spreading_method_arguments] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.184403.150263524.1404.1585334940506%40Atlassian.JIRA.
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title AJ Schmidt edited a comment on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator This issue was closed and marked as a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-33051However, the spread ` \* ` and spread-dot ` \*. ` operators are separate, not the same. See the below links for reference. [https://www.javaworld.com/article/2074149/groovy-s-spread-and-spread-dot-operators.html][https://www.logicbig.com/tutorials/misc/groovy/spread-operator.html][https://groovy-lang.org/operators.html#_spread_operator][https://groovy-lang.org/operators.html#_spreading_method_arguments] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.184403.150263524.1406.1585334940538%40Atlassian.JIRA.
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title AJ Schmidt reopened an issue This issue was closed and marked as a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-33051 However, the spread `` and spread-dot `.` operators are separate, not the same. See the below links for reference. https://www.javaworld.com/article/2074149/groovy-s-spread-and-spread-dot-operators.html https://www.logicbig.com/tutorials/misc/groovy/spread-operator.html https://groovy-lang.org/operators.html#_spread_operator https://groovy-lang.org/operators.html#_spreading_method_arguments Jenkins / JENKINS-46163 Pipeline CPS Groovy does not seem to support spread '*' operator Change By: AJ Schmidt Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61718) Allow newer ADO services to work with the TFS plugin
Title: Message Title
James Stapleton created an issue
Jenkins / JENKINS-61718
Allow newer ADO services to work with the TFS plugin
Issue Type:
Improvement
Assignee:
redsolo
Components:
tfs-plugin
Created:
2020-03-27 18:23
Environment:
tfs-plugin: 5.157.1
Labels:
plugin
Priority:
Major
Reporter:
James Stapleton
Right now it seems impossible to use the TFS plugin with a ADO (dev.azure.com) repository. This seems like its because the plugin skips over the authentication piece for urls that host doesn't end with `.visualstudio.com`. That is because in the TeamRestClient constructor, it does:
if (isTeamServices && credentials != null) {
authorization = createAuthorization(credentials);
}
else {
authorization = null;
}
which then it doesn't send along the authorization that you configured in the jenkin's system configuration panel. I made my own fix: https://github.com/jdstapleton/tfs-plugin/tree/fix-dev-azure Then while looking at the pull requests, I saw a pretty identical pull request already: https://github.com/jenkinsci/tfs-plugin/pull/224 So the request of this ticket is that can the pull request 224 be merged and then deployed to Jenkin's plugin server.
[JIRA] (JENKINS-61717) jenkins-cli.jar missing from war
Title: Message Title Jonathan Gray created an issue Jenkins / JENKINS-61717 jenkins-cli.jar missing from war Issue Type: Bug Assignee: Unassigned Components: cli Created: 2020-03-27 18:00 Environment: The latest jenkins lts docker image using version 2.222.1 Labels: regression jenkins lts docker Priority: Critical Reporter: Jonathan Gray In all prior releases the jenkins-cli.jar file was packaged as part of the jenkins war and was accessable from within the docker image at /var/jenkins_home/war/WEB-INF/jenkins-cli.jar. In the 2.222.1 release it was removed. I didn't see anything in the release changelog about it, so I'm assuming it's an accident. Please re-add it. Add Comment
[JIRA] (JENKINS-60113) IssueFieldUpdateStep wrong fieldValue type
Title: Message Title Radek Antoniuk updated JENKINS-60113 Jenkins / JENKINS-60113 IssueFieldUpdateStep wrong fieldValue type Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202959.1573238032000.1385.1585330800348%40Atlassian.JIRA.
[JIRA] (JENKINS-60113) IssueFieldUpdateStep wrong fieldValue type
Title: Message Title Radek Antoniuk updated JENKINS-60113 Jenkins / JENKINS-60113 IssueFieldUpdateStep wrong fieldValue type Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202959.1573238032000.1387.1585330800376%40Atlassian.JIRA.
[JIRA] (JENKINS-4439) Matrix builds jira comments are overly numerous
Title: Message Title Radek Antoniuk updated JENKINS-4439 This is really old, I'm just going to close it down as I don't expect anyone is running Jira 3.x nowadays. Jenkins / JENKINS-4439 Matrix builds jira comments are overly numerous Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated JENKINS-44989 Fixed long time ago in v. 2.5.2: https://github.com/jenkinsci/jira-plugin/pull/142 Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Labels: jira-plugin-2.5.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.183074.1497951893000.1373.1585330321554%40Atlassian.JIRA.
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated JENKINS-44989 Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.183074.1497951893000.1375.1585330321609%40Atlassian.JIRA.
[JIRA] (JENKINS-61716) Improve tests for Score (in ScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61716 Improve tests for Score (in ScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 17:26 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title Radek Antoniuk updated JENKINS-54108 Jenkins / JENKINS-54108 "JIRA: Progress issues by workflow action" fails when job is located within a folder Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.194733.1539712134000.1358.1585329840775%40Atlassian.JIRA.
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title Radek Antoniuk updated JENKINS-54108 I have just tested this scenario with current 2.222.1 and 3.0.14, looks like it works for me. If you still have an issue, please open a new ticket and try to attach a stacktrace (in DEBUG logging if needed) Jenkins / JENKINS-54108 "JIRA: Progress issues by workflow action" fails when job is located within a folder Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to
[JIRA] (JENKINS-61715) Improve tests for CoverageScore (in CoverageScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61715 Improve tests for CoverageScore (in CoverageScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 17:23 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-61714) Improve tests for AnalysisScore (in AnalysisScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61714 Improve tests for AnalysisScore (in AnalysisScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 17:22 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-61713) Improve tests for PitScore (in PitScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61713 Improve tests for PitScore (in PitScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 17:21 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Radek Antoniuk commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level Since JENKINS-44524 this is configurable on the Folder level, which I think serves the purpose of security and transparency on who has access to what. Therefore I propose to close this and use folder configuration instead. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.167054.1450212239000.1336.1585329120353%40Atlassian.JIRA.
[JIRA] (JENKINS-61712) Improve tests for TestScore (in TestScoreTest)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61712 Improve tests for TestScore (in TestScoreTest) Issue Type: Task Assignee: Unassigned Components: autograding-plugin Created: 2020-03-27 17:07 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Create different configurations and verify all getters as well. Add Comment
[JIRA] (JENKINS-61689) java.lang.NullPointerException when configuring JIRA site in Folder level
Title: Message Title Radek Antoniuk commented on JENKINS-61689 Re: java.lang.NullPointerException when configuring JIRA site in Folder level I have just tested this using my Jira Cloud instance and a Docker Jenkins LTS 2.222.1 and current Jenkins Jira plugin 3.1.14 - all works fine for me. Try using a docker instance for troubleshooting to check if it works with your Jira instance - see https://github.com/jenkinsci/docker for help. If it still doesn't work for you with 3.0.14, please post new stacktrace. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205512.158519371.1333.1585328520154%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck started work on JENKINS-61692 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1320.1585328040814%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Daniel Beck Assignee: Tim Jacomb Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1326.1585328040896%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck updated JENKINS-61692 Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1330.1585328040945%40Atlassian.JIRA.
[JIRA] (JENKINS-60417) Print log if post processing has been skipped
Title: Message Title Ulli Hafner updated JENKINS-60417 Jenkins / JENKINS-60417 Print log if post processing has been skipped Change By: Ulli Hafner Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203478.1575970934000.1317.1585327800326%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly fails to find git in PATH
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61711 Git plugin global config incorrectly fails to find git in PATH Change By: Mark Waite The git client plugin global configuration section allows the user to define git implementations which are then used as tools. One of the fields is "Path". When that field has the simple name 'git', it should find command line git on the system path.The error message reports that git cannot be found on the path, yet git works great on that machine and is definitely found on the path. !screencapture-home-markwaite-net-jenkins-configureTools-2020-03-27-10_01_17-edit.png|thumbnail!Users may continue to use command line git in this configuration, they can ignore the incorrect warning message from the dialog. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-61711) Git plugin global config incorrectly fails to find git in PATH
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61711 Git plugin global config incorrectly fails to find git in PATH Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205537.1585325185000.1310.1585325280053%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly fails to find git in PATH
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61711 Git plugin global config incorrectly fails to find git in PATH Issue Type: Bug Assignee: Mark Waite Attachments: screencapture-home-markwaite-net-jenkins-configureTools-2020-03-27-10_01_17-edit.png Components: git-plugin Created: 2020-03-27 16:06 Environment: Jenkins 2.22.1 Git plugin 4.2.2 Git client plugin 3.2.1 Labels: configuration Priority: Minor Reporter: Mark Waite The git client plugin global configuration section allows the user to define git implementations which are then used as tools. One of the fields is "Path". When that field has the simple name 'git', it should find command line git on the system path. The error message reports that git cannot be found on the path, yet git works great on that machine and is definitely found on the path.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly fails to find git in PATH
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61711 Git plugin global config incorrectly fails to find git in PATH Change By: Mark Waite Labels: configuration newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205537.1585325185000.1309.1585325220262%40Atlassian.JIRA.
[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working
Title: Message Title Philipp Jung commented on JENKINS-53919 Re: SVN: Repository URL parameterized stopped working Version 2.13.1 does not work for us as well. We have downgraded to 2.11.1 for now but would really like to update soon. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.194517.153873170.1294.1585323780164%40Atlassian.JIRA.
[JIRA] (JENKINS-61710) Active Directory plugin - Group name change/mapping
Title: Message Title Paweł Kaczanowski created an issue Jenkins / JENKINS-61710 Active Directory plugin - Group name change/mapping Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2020-03-27 15:35 Environment: Jenkins 2.222.1 OpenJDK 11.0.6+10-post-Ubuntu-1ubuntu118.04.1 Ubuntu 18.04 LTS active-directory 2.16 Priority: Minor Reporter: Paweł Kaczanowski I have problem with Active directory plugin, when I change name of group after I add it to project-based security, mapping is disappear. I think it caused by the way like this plugin or Jenkins remember typed group. In my configuration CN/Name of groups are changing some time. Each time group name change whole group lose permissions to job. I found two way to fix this: After first successful find group in AD, store it by its GUID Give Jenkins admin option chose, based on what attribute he/she want to store/search for groups in AD
[JIRA] (JENKINS-61430) Credentials 2.31 dramatically slows lookups
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61430 Credentials 2.31 dramatically slows lookups Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205108.1583932048000.1281.1585322700184%40Atlassian.JIRA.
[JIRA] (JENKINS-61709) Map.get("${var}") returns null
Title: Message Title
Raphael Höser created an issue
Jenkins / JENKINS-61709
Map.get("${var}") returns null
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-03-27 13:45
Environment:
Jenkins 2.204.4 LTS
Labels:
pipeline jenkins
Priority:
Minor
Reporter:
Raphael Höser
When accessing a map key via .get() with a var replacement in the key the get operation always returns null. Example snippet: def map = ["key_identifier": "test"] def id = "identifier" def resA = map.get("key_identifier") print(resA) def resB = map.get("key_${id}") print(resB) This will return in the output: Test null
Add Comment
[JIRA] (JENKINS-59110) Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally'
Title: Message Title Jakub Bochenski commented on JENKINS-59110 Re: Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally' Sorry, I don't have time to work on this ATM. If anybody want's to send a PR I'll be happy to assist and review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201535.1566943198000.1272.1585315680165%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Ben M commented on JENKINS-60979 Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Natasha Stopa I think there is now everything you need. Can we start working on this issue at some point? Other users will also be affected. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204447.1580906476000.1269.1585315260146%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck commented on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ...but AFAIK it is only on validation. "submit" works... Thanks for the clarification. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1265.1585314840205%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig commented on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ..can't access the links ...but AFAIK it is only on validation. "submit" works... but then the other issue happens: proxy doesn't work with git... https://issues.jenkins-ci.org/browse/JENKINS-61693 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1248.1585313340237%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Daniel Beck commented on JENKINS-61692
Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Looks like a regression in 2.205: secretPassword gets set: https://github.com/jenkinsci/jenkins/blob/489e4b3bcb8aeb06c962e793fc5ddca0649b6de4/core/src/main/resources/hudson/ProxyConfiguration/config.groovy#L15 Form validation uses password which doesn't exist: https://github.com/jenkinsci/jenkins/blob/489e4b3bcb8aeb06c962e793fc5ddca0649b6de4/core/src/main/resources/hudson/ProxyConfiguration/config.groovy#L25
Thomas Patzig Could you clarify whether this affects only form validation ("Validate Proxy") or whether saving the password doesn't work either?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205516.1585227401000.1243.1585311780220%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Tim Jacomb Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1236.1585311420281%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Tim Jacomb Assignee: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1232.1585311360257%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig edited a comment on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ok... changed the order of parameters: !screenshot-5.png |thumbnail !...same behaviornothing changed!screenshot-6.png|thumbnail! !screenshot-7.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1230.1585311300249%40Atlassian.JIRA.
[JIRA] (JENKINS-43632) Not Possible to Set Blank Environment Variables?
Title: Message Title
Volker von Einem edited a comment on JENKINS-43632
Re: Not Possible to Set Blank Environment Variables?
Same here...I wanted something like this: VERSION_SUFFIX = "${env.BRANCH_NAME == "master" ? "" : "-alpha"}"It fails without information about the problem.Is there a workaround? Update:A workaround - not nice - that worked for me aw to use a blank " ".VERSION_SUFFIX = "${env.BRANCH_NAME == "master" ? " " : "-alpha"}"
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.181039.1492457818000.1219.1585309620313%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig commented on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ...and I don't use any plugin... no JCasC. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1216.1585309440173%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Wadeck Follonier edited a comment on JENKINS-61371 Re: API tokens not persisted until user config screen is saved [~jglick] Could you provide additional information there?I tried reproducing the bug, but was not able to create an API Token without saving the user. In terms of code, the doGenerateNewToken method which create creates the token, contains a save call => https://github.com/jenkinsci/jenkins/blob/838f4ab504ccd6f8fe14afa9a650a53a366bd131/core/src/main/java/jenkins/security/ApiTokenProperty.java#L488 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205024.1583509348000.1211.1585309320477%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig edited a comment on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ok... changed the order of parameters: !screenshot-5.png!...same behaviornothing changed!screenshot-6.png|thumbnail! !screenshot-7.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1207.1585309320436%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Attachment: screenshot-7.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1206.1585309320419%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Attachment: screenshot-6.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1200.1585309260287%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig commented on JENKINS-61692 Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException ok... changed the order of parameters: ...same behaviornothing changed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1201.1585309260303%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Thomas Patzig updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Thomas Patzig Attachment: screenshot-5.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.1197.1585309200356%40Atlassian.JIRA.
[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working
Title: Message Title Philipp Jung edited a comment on JENKINS-53919 Re: SVN: Repository URL parameterized stopped working I have the same issue. The much larger checkouts when disabling this option is a real problem for us.Has anyone tested this on 2.13.1? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.194517.153873170.1192.1585308720222%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.168534.1456438321000.1185.1585308000290%40Atlassian.JIRA.
[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working
Title: Message Title Philipp Jung commented on JENKINS-53919 Re: SVN: Repository URL parameterized stopped working I have the same issue. The much larger checkouts when disabling this option is real problem for us. Has anyone tested this on 2.13.1? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.194517.153873170.1180.1585307820179%40Atlassian.JIRA.
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title Paul Frischknecht commented on JENKINS-41929 Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found I would like to bring this issue to your attention again. We have many pseudo-failing builds on our Jenkins because of this, which renders the "Weather Icon" build state monitoring tool useless. Also, DevOps are confused when they first see "Build now" when they expect "Build with Parameters" which they see only after that first build failed... Andrew Bayer, Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.178785.1486740246000.919.1585307405508%40Atlassian.JIRA.
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title Paul Frischknecht edited a comment on JENKINS-41929 Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found I would like to bring this issue to your attention again. We have many pseudo-failing builds on our Jenkins (we are hundreds of developers...) because of this, which renders the "Weather Icon" build state monitoring tool useless. Also, DevOps are confused when they first see "Build now" when they expect "Build with Parameters" which they see only after that first build failed...[~abayer], [~jglick] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.178785.1486740246000.1178.1585307415759%40Atlassian.JIRA.
