[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Sam Van Oort commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Jared Kauppila Tell you what, I'll wait a bit for you to confirm and all that checks out, we'll close this one out as fixed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51257) Multi String parameter values are not saved when it is updated while build
Title: Message Title Karthick Shanmugamoorthy created an issue Jenkins / JENKINS-51257 Multi String parameter values are not saved when it is updated while build Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-05-11 03:34 Priority: Minor Reporter: Karthick Shanmugamoorthy 1) Multi String parameter is configured in the jenkins job 2) While triggering a build Multi String parameter is updated with new values and build is triggered and the changes made in the multi string parameter on build need to be saved in the parameters. Please let me know if any further details / clarifications required Add Comment
[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title Mark Waite commented on JENKINS-49757 Re: Git plugin calls fetch twice for a single job Kaiyuan Zhao you're welcome to propose a pull request to the plugin to improve its behavior. Alternately, you could try replacing the "depth=2" with a reference repository to see if that would reduce the fetch time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Mark Waite Using "${GERRIT_REFSPEC}" fix the first problem.
10:38:45 Cloning the remote Git repository
10:38:45 Using shallow clone
10:38:45 shallow clone depth 2
10:38:45 Avoid fetching tags
10:38:45 Honoring refspec on initial clone
10:38:45 Cloning repository hide
10:38:45 > git init hide # timeout=10
10:38:45 Fetching upstream changes from hide
10:38:45 > git --version # timeout=10
10:38:45 using GIT_SSH to set credentials
10:38:45 > git fetch --no-tags --progress hide refs/changes/50/4750/1 --depth=2 # timeout=10
10:39:34 > git config remote.origin.url hide # timeout=10
10:39:34 > git config --add remote.origin.fetch refs/changes/50/4750/1 # timeout=10
10:39:34 > git config remote.origin.url hide # timeout=10
10:39:34 Fetching upstream changes from hide
10:39:34 using GIT_SSH to set credentials
10:39:34 > git fetch --no-tags --progress hide refs/changes/50/4750/1 --depth=2 # timeout=10
10:40:34 > git rev-parse 44fd5ca794ef1d4ccbfb437d94ef804626dea726^{commit} # timeout=10
10:40:34 Checking out Revision 44fd5ca794ef1d4ccbfb437d94ef804626dea726 (refs/changes/50/4750/1)
10:40:34 > git config core.sparsecheckout # timeout=10
10:40:34 > git checkout -f 44fd5ca794ef1d4ccbfb437d94ef804626dea726 # timeout=10
10:40:38 Commit message: "hide"
10:40:38 > git rev-parse FETCH_HEAD^{commit} # timeout=10
10:40:38 > git rev-list --no-walk eb696053ba8f4c94c388db0334b886879e6aaa42 # timeout=10
But it's also triggering fetch twice and the second fetch is not cost free. In our case, both fetch cost about one minute.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39824) Plugin does not work with read-only perforce replica
Title: Message Title Hokwang Lee commented on JENKINS-39824 Re: Plugin does not work with read-only perforce replica Karl Wirth Thanks for your comment. But I can't understand well. I think process is like below, perforce create workspace for reading Jenkinsfile(s) and creating pipeline. (In this case, I want to create workspace and read it and delete workspace automatically) and then running pipeline of some branch, kubernetes create pod for this and perforce create workspace written in Jenkinsfile and sync file, compile, and delete workspace automatically I want In this senario, why need master server ? I don't know which action is needed for workspace I just think create workspace and then sync and the delete it. and If so many jobs in Jenkins and scheduling very often, is that correct way ? I don't think so, Jenkins should use broker or build farm replica . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Jared Kauppila commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Sam Van Oort Okay, that's probably what it was. At least in the dev instance I've worked around it by just clearing out old builds, but in our nonprod instance we have ~13,000 builds that'd we've been talking about just archiving the build logs off. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Sam Van Oort commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Jared Kauppila Sorry, to clarify: this is a symptom of bugs that resulted in some FlowNodes not being persisted when they should have been – the actual bugs have now been fixed (pretty recently), but older builds that ran before that would still have issues, since the missing data is still gone. The cause of the missing Stage View UI is that the REST API request used to generate the data that feeds the UI fails (due to the inconsistent data). Thus it does not have the data for rendering. If it's just one or two older builds, you might be able to delete them and straighten them out. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Kevin Lannen commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library This functionality is available with the scripted syntax if that's what you are trying to do though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41094) For Unittest++ xml, only the content of the first tag of each test case is recognized
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-41094 For Unittest++ xml, only the content of the first tag of each test case is recognized Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41093) For Unittest++ xml, only the first failure of each test case is recognized
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-41093 For Unittest++ xml, only the first failure of each test case is recognized Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51256) properties step fails cryptically if previous build failed due to shard library loading error
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-51256
properties step fails cryptically if previous build failed due to shard library loading error
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
stacktrace.txt, support_2018-05-11_00.32.02.zip
Components:
workflow-multibranch-plugin
Created:
2018-05-11 00:42
Environment:
macOS 10.13.4 jdk1.8.0_144 core 2.116 workflow-multibranch 2.18
Priority:
Minor
Reporter:
Denys Digtiar
For the sake of simplifying the reproduction steps, the simple Pipeline is used.
Create an empty git repo
Configure it as a implicitly loaded global shared library
Create a Pipeline:
properties([disableConcurrentBuilds()]) node { echo 'Hello World' }
Run the Pipeline and see it fail due to ERROR: Library library expected to contain at least one of src or vars directories
Add a sayHello step to the shared library https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-custom-steps
Run the Pipeline again
Actual: Build
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Marcello de Sales commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library Kevin Lannen The status says RESOLVED ... shouldn't it be changed then? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Marcello de Sales commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library OOps as a duplicate... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Kevin Lannen commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library Yes, there's a very good reason why the code won't work. I wrote that code to demonstrate what how I would like the API to work as a feature request, not as code that currently works hence why this feature request exists. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10911) xUnit not detecting Ignored MSTest and NUnit Tests
Title: Message Title SCM/JIRA link daemon commented on JENKINS-10911 Re: xUnit not detecting Ignored MSTest and NUnit Tests Code changed in jenkins User: Nikolas Falco Path: src/main/resources/org/jenkinsci/plugins/xunit/types/mstest-1.0-to-junit-1.0.xsl src/test/java/org/jenkinsci/plugins/xunit/types/MSTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/junit_mstest_2_tests_1_class.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/junit_mstest_2_tests_from_different_assemblies.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/junit_mstest_4_tests_2_classes.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/junit_mstest_more_than-one_minute_test.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/junit_mstest_vs_2010.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/mstest_2_tests_1_class.trx src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/mstest_2_tests_from_different_assemblies.trx src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/mstest_4_tests_2_classes.trx src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/mstest_more_than_one_minute_test.trx src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/mstest_vs_2010.trx src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase1/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase2/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase2/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase3/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase4/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase4/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase5/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase5/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase6/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/mstest/testcase6/result.xml http://jenkins-ci.org/commit/xunit-plugin/9aaab6e40e4c66ea6c1268beffcfa826ba4707d2 Log: JENKINS-10911 xUnit not detecting Ignored MSTest and NUnit Tests Support skipped testcase for MSTest using Inconclusive value for outcome attribute of the UnitTestResult XML element. Add Comment
[JIRA] (JENKINS-10911) xUnit not detecting Ignored MSTest and NUnit Tests
Title: Message Title SCM/JIRA link daemon commented on JENKINS-10911 Re: xUnit not detecting Ignored MSTest and NUnit Tests Code changed in jenkins User: Nikolas Falco Path: src/main/resources/org/jenkinsci/plugins/xunit/types/nunit-1.0-to-junit-2.xsl src/main/resources/org/jenkinsci/plugins/xunit/types/nunit-3.0-to-junit.xsl src/test/java/org/jenkinsci/plugins/xunit/types/NUnit3Test.java src/test/java/org/jenkinsci/plugins/xunit/types/NUnitTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/nunit/testcase4/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/nunit/testcase5/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/nunit/testcase7/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/nunit/testcase7/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/nunit3/testcase2/result.xml http://jenkins-ci.org/commit/xunit-plugin/0670b5c88dce7bc0db97d2a42cab0f872a4a9046 Log: JENKINS-10911 xUnit not detecting Ignored MSTest and NUnit Tests Fix skipped testcase in NUnit and NUnit3 when there are failed testcase before. generalfailure variable in XSL seems brokes the dom navigation. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10911) xUnit not detecting Ignored MSTest and NUnit Tests
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-10911 xUnit not detecting Ignored MSTest and NUnit Tests Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title
Marcello de Sales commented on JENKINS-49662
Re: Ability to create custom stages in parallel blocks in pipeline shared library
Kevin Lannen I'm getting the following error: ": Starting with version 0.5, steps in a stage must be in a steps block. Any reason why? I'm reusing your example...
pipeline {
agent any
stages {
stage('Build everywhere') {
runOnAllPlatforms {
sh 'doing build things'
}
}
}
The error is the following:
Branch indexing
Connecting to https://github.intuit.com/api/v3 using mdesales/** (GitHub Enterprise Access Token)
Obtained Jenkinsfile from 3d42560bb3044468f1acd3c75f1d904e5df15247
Running in Durability level: MAX_SURVIVABILITY
GitHub has been notified of this commit’s build result
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 9: Unknown stage section "runOnAllPlatforms". Starting with version 0.5, steps in a stage must be in a steps block. @ line 9, column 5.
stage('Build everywhere') {
^
WorkflowScript: 9: No "steps" or "parallel" to execute within stage "Build everywhere" @ line 9, column 5.
stage('Build everywhere') {
^
2 errors
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:133)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:557)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:518)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:290)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
[JIRA] (JENKINS-10911) xUnit not detecting Ignored MSTest and NUnit Tests
Title: Message Title Nikolas Falco started work on JENKINS-10911 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10911) xUnit not detecting Ignored MSTest and NUnit Tests
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-10911 xUnit not detecting Ignored MSTest and NUnit Tests Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33726) xunit test results inconsistently displayed
Title: Message Title Nikolas Falco closed an issue as Incomplete Please reopen with more details on job configuration and report analysed Jenkins / JENKINS-33726 xunit test results inconsistently displayed Change By: Nikolas Falco Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-33726) xunit test results inconsistently displayed
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-33726 xunit test results inconsistently displayed Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47194) xUnit should not consider report generated by other xUnit step
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-47194 xUnit should not consider report generated by other xUnit step Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47194) xUnit should not consider report generated by other xUnit step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-47194 Re: xUnit should not consider report generated by other xUnit step Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java src/main/java/org/jenkinsci/plugins/xunit/service/XUnitTransformer.java src/test/java/org/jenkinsci/plugins/xunit/XUnitPublisherTest.java src/test/java/org/jenkinsci/plugins/xunit/XUnitWorkflowTest.java src/test/java/org/jenkinsci/plugins/xunit/service/TempWorkspace.java src/test/java/org/jenkinsci/plugins/xunit/service/XUnitTransformerTest.java src/test/java/org/jenkinsci/plugins/xunit/service/XUnitValidationServiceTest.java src/test/resources/org/jenkinsci/plugins/xunit/XUnitPublisherTest/workspace/JENKINS-47194/input.xml src/test/resources/org/jenkinsci/plugins/xunit/config.xml http://jenkins-ci.org/commit/xunit-plugin/10d52804cbf03c855fc0b9208ff6d8a62cf0efa0 Log: JENKINS-47194 xUnit should not consider report generated by other xUnit step XUnit build step or publisher use an instance of processor than generates output report to a shared common folder. This cause on latest step thresholds consider also reports produced by previous steps. Processor now generate an identifier that permits to generate reports into an unique output folder. *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-47194) xUnit should not consider report generated by other xUnit step
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-47194 xUnit should not consider report generated by other xUnit step Change By: Nikolas Falco Summary: Can't have a different failure threshold with xunit per stage xUnit should not consider report generated by other xUnit step Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51255) Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Title: Message Title
Kevin Carrasco created an issue
Jenkins / JENKINS-51255
Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-05-10 22:02
Priority:
Minor
Reporter:
Kevin Carrasco
Using the following settings declarative pipeline:
pipeline {
agent {
kubernetes {
cloud 'OpenShift'
label 'jenkins-agent-pod'
yaml readFile('k8s-podspec.yaml')
}
}
...
Results in the following error from Jenkins:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] readFile
Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node
[Pipeline] End of Pipeline
[JIRA] (JENKINS-50087) Integration Test for Table Model (in LabelProvider)
Title: Message Title Ulli Hafner commented on JENKINS-50087 Re: Integration Test for Table Model (in LabelProvider) Der zweite Punkt ist wahrscheinlich unabhängig und ein Bug! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50087) Integration Test for Table Model (in LabelProvider)
Title: Message Title Ulli Hafner commented on JENKINS-50087 Re: Integration Test for Table Model (in LabelProvider) Zum ersten Punkt: das habe ich vergessen zu sagen. Da habe ich auch schon mal den Debugger angeworfen und nichts gefunden. (Siehe JENKINS-50355) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46090) Cannot run two parallel builds with SCM Jenkinsfile script
Title: Message Title Randy Simat commented on JENKINS-46090 Re: Cannot run two parallel builds with SCM Jenkinsfile script I can reproduce this with lightweight checkout enabled as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Olivier Lamy commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job pr here https://github.com/jenkinsci/maven-plugin/pull/118 I tried to avoid core changes but need more testing especially with large projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50087) Integration Test for Table Model (in LabelProvider)
Title: Message Title Stephan Plöderl commented on JENKINS-50087 Re: Integration Test for Table Model (in LabelProvider) Außerdem scheint auch die Eingabe verschiedener Werte für die Thresholds nicht beachtet zu werden. Es werden scheinbar immer die Default-Werte von 50 und 25 genommen, egal was man auch eingibt. Bin mir zwar gerade nicht sicher, ob die beiden Probleme zusammen hängen, aber es scheint mir nicht so. Da die Werte ja gespeichert werden, auch wenn die Ajax-Validierung von Jenkins fehl schlägt. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title Jesse Glick updated JENKINS-51187 Jenkins / JENKINS-51187 Move git-changelist-maven-extension into incrementals-tools Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml http://jenkins-ci.org/commit/artifact-manager-s3-plugin/8f3e10aba6c807beb92e59dc6dcaa16c8d59f0db Log: Merge pull request #22 from jglick/relocate-JENKINS-51187 JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/d6e29ae93791...8f3e10aba6c8 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml http://jenkins-ci.org/commit/jenkins/2b4288155a95d9810c58308234254ee6afa91f56 Log: JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml http://jenkins-ci.org/commit/jenkins/72f4a592d28d25d095577b74212c98e29569928a Log: Merge pull request #3435 from jglick/relocate-JENKINS-51187 JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools Compare: https://github.com/jenkinsci/jenkins/compare/6bb85ec23bf8...72f4a592d28d *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml http://jenkins-ci.org/commit/artifact-manager-s3-plugin/357a1e566f2cfc43b5a10a8a58786718566dfbd9 Log: JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51036) -Dignore.dirt flag
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51036 -Dignore.dirt flag Change By: Jesse Glick Component/s: incrementals-tools Component/s: git-changelist-maven-extension Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43370) Pipeline Github Notify Step plugin fails to set commit status on private organization repo
Title: Message Title Adam Bennett commented on JENKINS-43370 Re: Pipeline Github Notify Step plugin fails to set commit status on private organization repo I had this problem in multi-branch pipeline when my Jenkins credentials were using my GitHub username and password. The SCM checkout worked, but status check notifications did not. Setting the Jenkins credentials password to a GitHub access token seems to have fixed it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51252) agent label "windows" causes swarm client to go into reconnect loop
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51252
agent label "windows" causes swarm client to go into reconnect loop
Change By:
Alexander Komarov
Specifying the label "windows" causes the client to go into reconnect loop as follows:{quote}{{INFO: Attempting to connect to }} {{May 10, 2018 1:17:30 PM hudson.plugins.swarm.SwarmClient getCsrfCrumb}} {{SEVERE: Could not obtain CSRF crumb. Response code: 404}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main createEngine}} {{INFO: Setting up slave: slave-010-9533db6e}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener }} {{INFO: Jenkins agent is running in headless mode.}} {{May 10, 2018 1:17:31 PM hudson.remoting.Engine startEngine}} {{WARNING: No Working Directory. Using the legacy JAR Cache location:...}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Locating server among []}} {{May 10, 2018 1:17:31 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve}} {{INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect]}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Agent discovery successful}} \{\{ Agent address: .}} \{\{ Agent port: 42442}} \{\{ Identity: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Handshaking}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Connecting to tc-jenkins-master-001.eur.ad.sag:42442}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Trying protocol: JNLP4-connect}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Remote identity confirmed: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Connected}} {{May 10, 2018 1:17:32 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Terminated}} {{May 10, 2018 1:17:32 PM hudson.plugins.swarm.Client run}} {{INFO: Retrying in 10 seconds}}{quote}This occurs whether using auto-discovery or if specifying -master. It behaves the same way with client 3.7 or 3.12. It doesn't matter if the label is specified on command line or in a labelsFile . There are no errors in the server log file. The following command *works*: {quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -e xecutors 1 -labels "test test2 windows64"{quote}The following command *fails*:{quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -e xecutors 1 -labels "test test2 windows"{quote} This problem did not exist in Jenkins 2.98 and swarm plugin 3.7
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title
Mostyn Bramley-Moore updated an issue
Jenkins / JENKINS-51253
jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Change By:
Mostyn Bramley-Moore
It seems that jenkins_2.107.3_all.deb no longer has an explicit dependency on default-jre-headless or java8-runtime-headless, which means jenkins installations are easily broken if "apt-get autoremove" is run (and it's generally good practice for debian/ubuntu admins to run this command periodically). jenkins_2.107.2_all.deb and earlier had the correct dependency. There is a comment on [https://pkg.jenkins.io/debian/] which suggests that this is intentional:{quote}You will need to explicitly install a Java runtime environment, *because Jenkins does not work with Java 9*, this is the safest way to ensure your system ends properly configured. Adding an explicit dependency requirement on Java could force installation of undesired versions of the JVM. Check JENKINS-40689 for more details about Jenkins and Java 9 compatibility.{quote} ...but this seems wrong- the package should just depend on java8 packages specifically.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51252) agent label "windows" causes swarm client to go into reconnect loop
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51252
agent label "windows" causes swarm client to go into reconnect loop
Change By:
Alexander Komarov
Specifying the label "windows" among other labels causes the client to go into reconnect loop as follows:{quote}{{INFO: Attempting to connect to }} {{May 10, 2018 1:17:30 PM hudson.plugins.swarm.SwarmClient getCsrfCrumb}} {{SEVERE: Could not obtain CSRF crumb. Response code: 404}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main createEngine}} {{INFO: Setting up slave: slave-010-9533db6e}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener }} {{INFO: Jenkins agent is running in headless mode.}} {{May 10, 2018 1:17:31 PM hudson.remoting.Engine startEngine}} {{WARNING: No Working Directory. Using the legacy JAR Cache location:...}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Locating server among []}} {{May 10, 2018 1:17:31 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve}} {{INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect]}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Agent discovery successful}} \{\{ Agent address: .}} \{\{ Agent port: 42442}} \{\{ Identity: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Handshaking}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Connecting to tc-jenkins-master-001.eur.ad.sag:42442}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Trying protocol: JNLP4-connect}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Remote identity confirmed: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}} {{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Connected}} {{May 10, 2018 1:17:32 PM hudson.remoting.jnlp.Main$CuiListener status}} {{INFO: Terminated}} {{May 10, 2018 1:17:32 PM hudson.plugins.swarm.Client run}} {{INFO: Retrying in 10 seconds}}{quote}This occurs whether using auto-discovery or if specifying -master. It behaves the same way with client 3.7 or 3.12. It doesn't matter if the label is specified on command line or in a labelsFileThe following command *works*: {quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -e xecutors 1 -labels "test test2 windows64"{quote}The following command *fails*:{quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -e xecutors 1 -labels "test test2 windows"{quote} This problem did not exist in Jenkins 2.98 and swarm plugin 3.7
[JIRA] (JENKINS-50804) Enforcer rules for incremental/snapshot deps
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50804 Enforcer rules for incremental/snapshot deps Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51032) Add excludes option to Fingerprinter
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-51032 Add excludes option to Fingerprinter Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50723) Consider impact on CERT workflows
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50723 Consider impact on CERT workflows Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51254) Incrementalify plugin archetypes
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51254 Incrementalify plugin archetypes Issue Type: Improvement Assignee: Unassigned Components: archetypes Created: 2018-05-10 20:27 Priority: Minor Reporter: Jesse Glick Since there is no harm done in enabling Incrementals in a plugin repository (so far as I can tell), we might as well do so on the standard archetypes (at least the empty plugin one) so that people can start deploying to Incrementals right away (assuming RPU has been updated). Add Comment
[JIRA] (JENKINS-50698) Integration tests
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50698 Integration tests Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51252) agent label "windows" causes swarm client to go into reconnect loop
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51252
agent label "windows" causes swarm client to go into reconnect loop
Change By:
Alexander Komarov
Specifying the label "windows" among other labels causes the client to go into reconnect loop as follows:{quote}{{INFO: Attempting to connect to }}{{May 10, 2018 1:17:30 PM hudson.plugins.swarm.SwarmClient getCsrfCrumb}}{{SEVERE: Could not obtain CSRF crumb. Response code: 404}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main createEngine}}{{INFO: Setting up slave: slave-010-9533db6e}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener }}{{INFO: Jenkins agent is running in headless mode.}}{{May 10, 2018 1:17:31 PM hudson.remoting.Engine startEngine}}{{WARNING: No Working Directory. Using the legacy JAR Cache location:...}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Locating server among []}}{{May 10, 2018 1:17:31 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve}}{{INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect]}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Agent discovery successful}} \ { \ { Agent address: .}} \ { \ { Agent port: 42442}} \ { \ { Identity: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Handshaking}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Connecting to tc-jenkins-master-001.eur.ad.sag:42442}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Trying protocol: JNLP4-connect}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Remote identity confirmed: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}}{{May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Connected}}{{May 10, 2018 1:17:32 PM hudson.remoting.jnlp.Main$CuiListener status}}{{INFO: Terminated}}{{May 10, 2018 1:17:32 PM hudson.plugins.swarm.Client run}}{{INFO: Retrying in 10 seconds}}{quote} This occurs whether using auto-discovery or if specifying -master. It behaves the same way with client 3.7 or 3.12. It doesn't matter if the label is specified on command line or in a labelsFile The following command * works * : {quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -executors 1 -labels "test test2 windows64"{quote}The following command * fails * :{quote}java -Xrs -jar swarm-client-3.7.jar -mode exclusive -name slave-010 -executors 1 -labels "test test2 windows"{quote} This problem did not exist in Jenkins 2.98 and swarm plugin 3.7
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Matt Sicker updated JENKINS-21670 Jenkins / JENKINS-21670 Option to anonymize customer labels Change By: Matt Sicker Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Mostyn Bramley-Moore created an issue Jenkins / JENKINS-51253 jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-10 20:26 Environment: debian/ubuntu Priority: Major Reporter: Mostyn Bramley-Moore It seems that jenkins_2.107.3_all.deb no longer has an explicit dependency on default-jre-headless or java8-runtime-headless, which means jenkins installations are easily broken if "apt-get autoremove" is run (and it's generally good practice for debian/ubuntu admins to run this command periodically). jenkins_2.107.2_all.deb and earlier had the correct dependency. Add Comment
[JIRA] (JENKINS-51252) agent label "windows" causes swarm client to go into reconnect loop
Title: Message Title
Alexander Komarov created an issue
Jenkins / JENKINS-51252
agent label "windows" causes swarm client to go into reconnect loop
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
swarm-plugin
Created:
2018-05-10 20:25
Environment:
Jenkins 2.121 Swarm plugin 3.12 Client: tested with swarm plugin 3.7 and 3.12
Priority:
Minor
Reporter:
Alexander Komarov
Specifying the label "windows" among other labels causes the client to go into reconnect loop as follows:
INFO: Attempting to connect to May 10, 2018 1:17:30 PM hudson.plugins.swarm.SwarmClient getCsrfCrumb SEVERE: Could not obtain CSRF crumb. Response code: 404 May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: slave-010-9533db6e May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. May 10, 2018 1:17:31 PM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location:... May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [] May 10, 2018 1:17:31 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect] May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful {{ Agent address: .}} {{ Agent port: 42442}} {{ Identity: 2b:48:59:ed:b6:88:6b:da:b5:7c:ef:8e:f4:70:a6:41}} May 10, 2018 1:17:31 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking May 10, 2018 1:17:31 PM
[JIRA] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick updated JENKINS-51046 Jenkins / JENKINS-51046 Tool to incrementalify POM Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51046 Re: Tool to incrementalify POM Code changed in jenkins User: Jesse Glick Path: README.md maven-plugin/src/main/java/io/jenkins/tools/incrementals/maven/IncrementalifyMojo.java maven-plugin/src/main/resources/io/jenkins/tools/incrementals/maven/prototype-extensions.xml http://jenkins-ci.org/commit/incrementals-tools/6c4456847d6a250e67a3c70d54b91fd36b20dc8b Log: JENKINS-51046 mvn incrementals:incrementalify Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51251) Unable to login to Cisco Jabber Server (bad-request - modify)
Title: Message Title Andrew Null created an issue Jenkins / JENKINS-51251 Unable to login to Cisco Jabber Server (bad-request - modify) Issue Type: Bug Assignee: Florian Schmaus Components: jabber-plugin Created: 2018-05-10 19:56 Environment: Jenkins ver. 2.107.3 jabber plugin 1.36 Ubuntu 16.04.3 LTS x64 java.runtime.version 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12 Labels: Jabber xmpp Cisco Priority: Blocker Reporter: Andrew Null Remote XMPP server is a Cisco IM and Presense Server (10.5.2). I am able to login with the Cisco Jabber client, and Pidgin Putting an incorrect password in Jabber plugin for Jenkins gives an "failed to login message" Using the correct user/password result in the following; May 10, 2018 2:59:13 PM INFO hudson.plugins.jabber.im.transport.JabberIMConnectionProvider createConnection Creating XMPP JabberIMConnection May 10, 2018 2:59:13 PM INFO hudson.plugins.jabber.im.transport.JabberIMConnection connect Trying to connect XMPP connection May 10, 2018 2:59:13 PM FINE hudson.plugins.jabber.im.transport.JabberIMConnection creating new XMPP connection May 10, 2018 2:59:13 PM INFO hudson.plugins.jabber.im.transport.JabberIMConnection createConnection Trying to connect to XMPP on /domain.com May 10, 2018 2:59:13 PM FINER org.jivesoftware.smack.tcp.XMPPTCPConnection Trying to establish TCP connection to CiscoIMP.domain.local/172.16.172.172 at port
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Justin Carpenter commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 The Jenkins log and thread dump are attached. It does not happen on versions before 2.117. 2.116 is working fine for right now. I could not get the response headers for the stapler tracing as no response is ever returned to the browser. I appreciate the help. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Justin Carpenter updated an issue Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Justin Carpenter Attachment: jenkins.log Attachment: jenkins-thread-dump.log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml http://jenkins-ci.org/commit/buildtriggerbadge-plugin/ce5d4ac630e15ee79948f23dd263f01e8c0665e4 Log: JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Sam Van Oort commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Simon Watts This is a known and now-fixed issue, resolved in the latest workflow-cps releases and verified to resolve the issue. Two strategies to get a stable system to apply the update: if you shutdown your Jenkins and go into the FlowExecutionList.xml you will find a list of builds there and can hunt down and delete the builds – this will prevent them resuming upon restart. You'll want to update plugins ASAP though in case new builds get triggered. Alternately, since you were pretty much up to date otherwise, you should be able to grab the latest workflow-cps plugin and drop it in /plugins/ (replacing the existing one). No new dependencies were added in the last 2 releases. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Sam Van Oort closed an issue as Duplicate Jenkins / JENKINS-51241 Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51250) Prototype output format for manifest to be ingested by Update service
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-51250 Prototype output format for manifest to be ingested by Update service Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-05-10 18:56 Priority: Minor Reporter: R. Tyler Croy Jesse needs some example output of what his update tool should produce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title Jesse Glick updated JENKINS-51187 Jenkins / JENKINS-51187 Move git-changelist-maven-extension into incrementals-tools Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: README.md pom.xml src/main/java/io/jenkins/tools/git_changelist_maven_extension/Main.java http://jenkins-ci.org/commit/git-changelist-maven-extension/b7385861d6e68bfa51a3836a14c958af52a7d77f Log: JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50087) Integration Test for Table Model (in LabelProvider)
Title: Message Title Stephan Plöderl commented on JENKINS-50087 Re: Integration Test for Table Model (in LabelProvider) Vielen Dank, läuft wunderbar. Mir ist gerade noch ein Bug aufgefallen, allerdings finde ich die Stelle nicht, wo dieser genau auftritt, weshalb ich ihn nicht fixen kann. Die Validation bei CPD und Simian zeigt immer die Fehlermeldungen an, das die Thresholds nicht stimmen. Ich konnte es soweit runter tracken, dass jenkins hier den Wert des jeweiligen Feldes immer nur als 0 schickt. Die Referenz der QueryParameter scheint er in diesem Fall also irgendwie nicht zu erkennen, jedoch konnte ich bisher noch nicht herausfinden, warum dies so ist. Der Wert checkdependson ist auf jeden Fall bei den beiden Werten ein leerer String. In den check-Funktionen sind deshalb die beiden Werte immer 0 und deshalb schlägt die Validation fehl. Da deshalb der normalThreshold gleich dem highThreshold ist. Ich hoffe Sie können mir an dieser Stelle weiter helfen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools Code changed in jenkins User: Jesse Glick Path: README.md git-changelist-maven-extension/pom.xml git-changelist-maven-extension/src/main/java/io/jenkins/tools/incrementals/git_changelist_maven_extension/Main.java lib/pom.xml maven-plugin/pom.xml pom.xml http://jenkins-ci.org/commit/incrementals-tools/d6aeef7e0d85798ac8473fc029d99c5e5dbc2112 Log: JENKINS-51187 Moving git-changelist-maven-extension into incrementals-tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47194) Can't have a different failure threshold with xunit per stage
Title: Message Title Nikolas Falco started work on JENKINS-47194 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47194) Can't have a different failure threshold with xunit per stage
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-47194 Can't have a different failure threshold with xunit per stage Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51249) Job never finishes, appears to be deadlocked
Title: Message Title Lance Jessup commented on JENKINS-51249 Re: Job never finishes, appears to be deadlocked I just added jenkins-jabba35-systeminfo.pdf and jenkins-jabba35-threaddump.pdf for a second Jenkins installation that seems to be hanging exactly the same way as the other system. They both have the same environment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51249) Job never finishes, appears to be deadlocked
Title: Message Title Lance Jessup updated an issue Jenkins / JENKINS-51249 Job never finishes, appears to be deadlocked Change By: Lance Jessup Attachment: jenkins-jabba35-systeminfo.pdf Attachment: jenkins-jabba35-threaddump.pdf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title Jesse Glick commented on JENKINS-51187 Re: Move git-changelist-maven-extension into incrementals-tools FYI Alex Earl. I decided to simplify things and consolidate under incrementals-tools, so git-changelist-maven-extension will become a tombstone repo. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51249) Job never finishes, appears to be deadlocked
Title: Message Title Lance Jessup created an issue Jenkins / JENKINS-51249 Job never finishes, appears to be deadlocked Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-plugins.pdf, Jenkins-threaddump.pdf Components: core, flow-plugin Created: 2018-05-10 17:51 Environment: Windows 2012 R2 Standard Java is one installed with Jenkins C:\Program Files (x86)\Jenkins\jre\bin>java.exe -version java version "1.8.0_66" Java(TM) SE Runtime Environment (build 1.8.0_66-b18) Java HotSpot(TM) Client VM (build 25.66-b18, mixed mode) Jenkins & plugins: Jenkins ver. 2.120 For plugins see attachment Installed Jenkins originally using Windows jenkins-2.53 installer. Have since used the "Upgrade Automatically" button in "Manage Jenkins" section. Chrome: Version 65.0.3325.181 (Official Build) (64-bit) /systeminfo System Properties Name ↓ Value awt.toolkit sun.awt.windows.WToolkit executable-war C:\Program Files (x86)\Jenkins\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path C:\Program Files (x86)\Jenkins\jenkins.war java.class.version 52.0 java.endorsed.dirs C:\Program Files (x86)\Jenkins\jre\lib\endorsed java.ext.dirs C:\Program Files (x86)\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home C:\Program Files (x86)\Jenkins\jre java.io.tmpdir C:\Users\SVCBUI~1\AppData\Local\Temp\ java.library.path C:\Program Files (x86)\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\IBM\RationalSDLC\common;C:\Program Files\IBM\RationalSDLC\Clearquest\cqcli\bin;C:\ProgramData\Oracle\Java\javapath;C:\Software\apfdev\dlls;C:\cygwin\usr\local\bin;C:\cygwin\bin;C:\asi_11_1_0\bin;C:\asi_11_1_0\lib;C:\asi_11_1_0\asiext\dbaccess;C:\cygwin\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\ProgramData\chocolatey\bin;C:\Software\apfdev\dlls;C:\Program Files (x86)\vim\vim80;C:\Program
[JIRA] (JENKINS-51187) Move git-changelist-maven-extension into incrementals-tools
Title: Message Title Jesse Glick started work on JENKINS-51187 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37081) Keep Forever button missing from Pipeline build
Title: Message Title
Elise Louie edited a comment on JENKINS-37081
Re: Keep Forever button missing from Pipeline build
This is probably old. Using the properties setting above would erase all parameters in pipeline. To get the 'keep build forever', users should use options \{buildDiscarder(logRotator(numToKeepStr: '5'))}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51248) Check for Invalid Names/Labels During Template Creation
Title: Message Title Enrique Canales created an issue Jenkins / JENKINS-51248 Check for Invalid Names/Labels During Template Creation Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-05-10 17:27 Priority: Minor Reporter: Enrique Canales A client reported that their employees were able to enter invalid names/labels during template creation which resulted in pods not starting. A suggestion to validate them on creation in order to avoid this issue. Add Comment
[JIRA] (JENKINS-37081) Keep Forever button missing from Pipeline build
Title: Message Title
Elise Louie commented on JENKINS-37081
Re: Keep Forever button missing from Pipeline build
This is probably old. Using the properties setting above would erase all parameters in pipeline. To get the 'keep build forever', users should use options { buildDiscarder(logRotator(numToKeepStr: '5')) }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50790) GitPluginTest are failing in the ATH
Title: Message Title Jesse Glick commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH Makes sense. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51205) Slow performance of /pluginManager/available rendering
Title: Message Title Jesse Glick updated JENKINS-51205 Jenkins / JENKINS-51205 Slow performance of /pluginManager/available rendering Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51205) Slow performance of /pluginManager/available rendering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51205 Re: Slow performance of /pluginManager/available rendering Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/resources/hudson/PluginManager/table.jelly http://jenkins-ci.org/commit/jenkins/3b61b96119b9fd8c80b1fa79a19f8f770af434b7 Log: JENKINS-51205 Improve performance of /pluginManager/available service. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51205) Slow performance of /pluginManager/available rendering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51205 Re: Slow performance of /pluginManager/available rendering Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/resources/hudson/PluginManager/table.jelly http://jenkins-ci.org/commit/jenkins/6bb85ec23bf824515f65616f72527ba784a54adc Log: Merge pull request #3428 from jglick/perf-JENKINS-51205 JENKINS-51205 Improve performance of /pluginManager/available service Compare: https://github.com/jenkinsci/jenkins/compare/d004eea0caf7...6bb85ec23bf8 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Jared Kauppila commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Sam Van Oort Hm, okay. We keep our Dev instance up to date and I thought I've seen it there too, but I'll monitor it to see if it pops up again. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41272) Pipeline "currentBuild" should expose build causes
Title: Message Title Dan Albu commented on JENKINS-41272 Re: Pipeline "currentBuild" should expose build causes Hey guys, any update on this? We would really appreciate if we can get the cause of the pipeline trigger via the currentBuild: e.g: currentBuild.TriggerCause -> returns String (Started by user John Doe) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51169) Optional setting to ignore failing the build job if the notification fails
Title: Message Title Jim Stys commented on JENKINS-51169 Re: Optional setting to ignore failing the build job if the notification fails Is this a new feature or a bug with the "failOnError" flag that is mentioned in the documentation for the plugin (https://jenkins.io/doc/pipeline/steps/rocketchatnotifier/#rocketsend-send-rocketchat-message) ? I am having the same issue where rocketSend commands are failing the build and it doesn't seem like the failOnError fixes that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH It seems it worked, I am going to get this open for a pair of days and close if nothing new arises Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Dazu langt es, das im Ergebnis (d.h. in der Instanz des AnalysisResult) der Methode {code}/** * Returns the reference static analysis run that has been used to compute the new issues. * * @return the reference build */public Optional getReferenceBuild() {if (referenceJob == NO_REFERENCE) {return Optional.empty();}return new JenkinsFacade().getBuild(referenceJob, referenceBuild);}{code}auszuwerten. Dort sollte der entsprechende Build drin stehen.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Dazu langt es, im das Ergebnis (d.h. in der Instanz des AnalysisResult) der Methode {code}/** * Returns the reference static analysis run that has been used to compute the new issues. * * @return the reference build */public Optional getReferenceBuild() {if (referenceJob == NO_REFERENCE) {return Optional.empty();}return new JenkinsFacade().getBuild(referenceJob, referenceBuild);}{code}auszuwerten. Dort sollte der entsprechende Build drin stehen.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Waite commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds Jonathan Kuleff I can't duplicate the problem you're reporting. Steps I took trying to duplicate the problem: Created a JENKINS-50886 branch in my jenkins-bugs repository so that the job will be created in my multi-branch Pipelines Define an ant script that sleeps for MINUTES_TO_WAIT=13 + 30 seconds Define a scripted Pipeline in the Jenkinsfile that defines polling interval as MINUTES_TO_WAIT Scan the repository to detect the new branch Confirm that a single build is run when a change is detected and that no additional builds are run until the next polling interval detects changes I assumed that the difference between scripted and declarative is not relevant in this case. I assumed that a multi-branch Pipeline was a sufficient approximation for your case. Are you using a Pipeline (without multi-branch) or are you using multi-branch Pipeline? I was able to cause two concurrent builds of the same commit if I used curl to the Jenkins notifyCommit URL shortly after the commit happened. Since you're using polling, I assume you're not using notifyCommit and I assume you're not using webhooks. If you are using notifyCommit or webhooks, then you don't need polling. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Dazu langt es, das Ergebnis der Methode /** * Returns the reference static analysis run that has been used to compute the new issues. * * @return the reference build */ public OptionalgetReferenceBuild() { if (referenceJob == NO_REFERENCE) { return Optional.empty(); } return new JenkinsFacade().getBuild(referenceJob, referenceBuild); } auszuwerten. Dort sollte der entsprechende Build drin stehen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Verglichen Der Status soll überprüft werden nachdem die Issues zwischen dem aktuellem Build und dem Vorherigen vorherigen verglichen wurden .Dabei müssen alle möglichen Ausgangszustände einberüchsichtigt werden. (Die Einstellungen im Build:- Ignore Previous Result - Overall Success- Reference Job - Vergleich mit einem anderen Jenkins Job) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Verglichen werden die Issues zwischen dem aktuellem Build und dem Vorherigen. Dabei müssen alle möglichen Ausgangszustände einberüchsichtigt werden. (Die Einstellungen im Build:- Ignore Previous Result +/- - Overall Success +/- - Reference Job - Vergleich mit einem anderen Build Jenkins Job) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Wie kann ich auf die Ergebnisse des ReferenceFinders (Dem Vergleich zum Vorherigen Build) zugreifen? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick updated JENKINS-51247 Jenkins / JENKINS-51247 Move flattened POM into target directory Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47927) Final text fields cannot use other fields to initialize
Title: Message Title Aaron Marasco closed an issue as Won't Fix As noted, this seems to be a "trying to use data too early" issue. Jenkins / JENKINS-47927 Final text fields cannot use other fields to initialize Change By: Aaron Marasco Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title
Jesse Glick commented on JENKINS-51247
Re: Move flattened POM into target directory
I think I have it. Given this mojo
@Mojo(name = "test", defaultPhase = LifecyclePhase.GENERATE_SOURCES)
public class TestMojo extends AbstractMojo {
@Parameter(defaultValue = "${basedir}")
private File workingDirectory;
public void execute() throws MojoExecutionException {
getLog().info("running in " + workingDirectory);
}
}
invoked as
test
flatten-maven-plugin-53
1.0-SNAPSHOT
test
test
If produce-incrementals is configure to use source:jar, it gets run twice, once with the basedir, once with target. Using source:jar-no-fork, it runs just once, with the correct basedir.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title
Jesse Glick commented on JENKINS-51247
Re: Move flattened POM into target directory
What seems to be working so far in most cases: remove executions of the clean goal, and override
${project.build.directory}
${project.artifactId}-${project.version}.pom
I noticed one behavioral change in findbugs-maven-plugin (relative paths in findbugs.excludeFilterFile are not resolved), but it is not clear what the correct behavior was there anyway; prepending ${project.basedir}/ fixes it. Now I am tracking down a problem in frontend-maven-plugin: node commands get run from target as the CWD. This code seems to be getting the wrong value—but only when the project version is not a snapshot. Of course I cannot reproduce a similar problem using a simple test mojo. This seems to have something to do with source:jar running a forked Maven execution, thus rerunning lots of mojos, in which the basedir is apparently wrong. The produce-incrementals profile runs this mojo, which is presumably the trigger. I notice that MavenProject.deepCopy is wrong (calls setFile and thus sets basedir of the clone to target). I am guessing that is the culprit behind both problems—they involve forked executions. (@Execute annotation) Summary: making this switch is not completely safe, but can be done.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick started work on JENKINS-51247 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick commented on JENKINS-51046 Re: Tool to incrementalify POM Tracking that as JENKINS-51247. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51247 Move flattened POM into target directory Issue Type: Task Assignee: Jesse Glick Components: plugin-pom Created: 2018-05-10 14:05 Priority: Major Reporter: Jesse Glick You should not need to ignore .flattened-pom.xml: it should live inside target. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"
Title: Message Title Jonathan Kuleff commented on JENKINS-50857 Re: Docker agent on windows fails with Cannot run program "id" Andrew Bayer not sure if you are the right person to get this looked at by someone but would really appreciate if someone can look at this as docker agent for declarative pipeline is broken for windows containers. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"
Title: Message Title Jonathan Kuleff updated an issue Jenkins / JENKINS-50857 Docker agent on windows fails with Cannot run program "id" Change By: Jonathan Kuleff Environment: Windows Server Code Core 2016Jenkins 2.89.4Pipeline: Declarative 1.2.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Jonathan Kuleff commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds Mark Waite Andrew Bayer the build does not complete in less then 2 minutes. Excuse me if I have misunderstood how this feature is meant to work but I am assuming that when a scan runs and it detects a new commit, it triggers a build for the commit and records the commit hash as being triggered/seen. 2 minutes later it scans again if no new commits nothing happens, however if there is a new commit is triggers for that commit. From Mark's comment it sounds like the build has to be finished before the next poll. If there is any other information I can provide to get to the bottom of this, please let me know. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51246) "/api/xml?wrapper=hudson=1=/hudson/job" is broken
Title: Message Title Nuno Castilho updated an issue Jenkins / JENKINS-51246 "/api/xml?wrapper=hudson=1=/hudson/job" is broken Change By: Nuno Castilho Hi,On Jenkins 2.120 build the /api/xml?wrapper=hudson=1=/hudson/job is broken. See stacktrace in comments. This URL Think this is used by Mylyn causing and as such error when adding a Build Server to Mylyn reports : Server validation failed: Unexpected error: Unexpected response from Hudson server for '/api/xml': Internal Server Error CheersNuno Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts edited a comment on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. We just restarted the Jenkins service. I managed to get into the web front end briefly, but it then hung again (so about 10 minutes since restart, and only a couple of minutes on the gui).Possible that there is an on-going job which regenerates the deadlock when the service restarts? Is there a way to stop jobs without access to the web or REST? I would like to abort the jobs listed in connection with the deadlock.Also to note: Plugins were all up-to-date as of *4 May 2018* at 10:40 hrs (UTC+1) .I note that there have been updates to pipeline plugins since that time, but if I cannot access the GUI or REST it is going to be hard to update them... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
