[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Jay Ache commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Still not fixed, Blue Ocean 1.21.0, Autofavorite for Blue Ocean 1.2.4, Jenkins 2.150.3 Anyone working on this? I probably have to completely remove Blue Ocean from our pipeline because of this little Autofavorite bug (I can't use Christian Häussler's suggestions of -DBLUEOCEAN_FEATURE_AUTOFAVORITE_ENABLED=false because I don't have admin access to my team's Jenkins instance). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189812.1523357354000.4127.1579766280418%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60133
Re: Default HOME folder in containers does not exist
This is probably a side effect of the change of working directory to {{/home/jenkins/agent}} (i.e. https://issues.jenkins-ci.org/browse/ JENKINS-58705). If the {{/home/jenkins}} does not exist in the image, it will be automatically added during the mounting of the workspace volume but will not be writable.The {{DEFAULT_HOME}} might need to be changed. Otherwise images need to be adapted for arbitrary users as documented in https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/creating_images/creating-images-guidelines.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4118.1579760640234%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60133 Re: Default HOME folder in containers does not exist Pablo Gomez Setting the system property -Dorg.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder=/home/jenkins/agent should workaround that problem and mock the behavior that was there before JENKINS-58705. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4116.1579760640207%40Atlassian.JIRA.
[JIRA] (JENKINS-55426) Using "for in" loop for generating tasks for "parallel" execution, causes all tasks to have last value from iterated collection
Title: Message Title
Stuart Rowe commented on JENKINS-55426
Re: Using "for in" loop for generating tasks for "parallel" execution, causes all tasks to have last value from iterated collection
Avoid using "for-in" loops. Instead try:
machines.each { machine ->
def agentName = machine
def labelParameters = []
labelParameters.add([$class: 'NodeParameterValue', name: 'node_name', labels: [agentName], nodeEligibility: [$class: 'AllNodeEligibility']])
labelParameters.add([$class: 'StringParameterValue', name: 'ARBITRARY_PARAMETER', value: 'ARBITRARY_VALUE'])
machinePreparations[agentName] = {
stage(agentName + ' preparation') {
build job: '../Preparation/' + agentName, parameters: labelParameters
def node = Jenkins.get().nodes.find({it.name == agentName})
node.setLabelString(node.getLabelString() + 'successful')
println(String.format("Job with machine %s successfully done!", agentName))
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.go
[JIRA] (JENKINS-60842) Add version-comparision to Conditional Buildstep plugin
Title: Message Title Mikhail T created an issue Jenkins / JENKINS-60842 Add version-comparision to Conditional Buildstep plugin Issue Type: Improvement Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin Created: 2020-01-23 00:04 Priority: Major Reporter: Mikhail T I use Jenkins to build releases of software with multiple dependencies and, some times, need to do things differently depending on a dependency's version... Some versions can be compared as numbers, but not all. It would be very useful to be able to compare things like 1.3 against 1.2.1.1, or 1.3a vs. 1.3b. Python's LooseVersion can be used as a reference. Thank you! Add Comment
[JIRA] (JENKINS-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value
Title: Message Title Andrei Neagu started work on JENKINS-50669 Change By: Andrei Neagu Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189753.1523272907000.4094.1579737780258%40Atlassian.JIRA.
[JIRA] (JENKINS-49905) Jenkins core build should verify Remoting code signing during the release
Title: Message Title Andrei Neagu closed an issue as Fixed Jenkins / JENKINS-49905 Jenkins core build should verify Remoting code signing during the release Change By: Andrei Neagu Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188894.1520207401000.4092.1579737180382%40Atlassian.JIRA.
[JIRA] (JENKINS-60841) Incrementals publisher causes corrupt configuration files in maven
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60841 Incrementals publisher causes corrupt configuration files in maven Change By: Ulli Hafner After activating incrementals for all my plugins maven seems to produce very often corrupt configuration files for SpotBugs, PMD, and so on. This did not happen without incrementals. These configuration files are part of a jar file (dependency for each static analysis tool) and unpacked automatically before the analysis tool is started in maven. Examples:- http://jenkins-ci.361315.n4.nabble.com/Incrementals-and-static-analysis-configuration-from-a-dependency-td5011947.html - https:// pipelines ci . actions jenkins . githubusercontent.com io / 9z5Z04LeOv0bqVj7OJZYELFwCHqkJ1zOYDpHprBY4n0MonHihT job / _apis Plugins / pipelines job / 1 jquery3-api-plugin / runs job / 55 parent-pom / signedlogcontent/ 3 ?urlExpires=2020-01-22T22%3A28%3A36.9900747Z&urlSigningMethod=HMACV1&urlSignature=CPaVs5WYIzRLR2dbZ7Gi35eBUFBGy7YbpUclREE3Zu4%3D /console Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60841) Incrementals publisher causes corrupt configuration files in maven
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-60841 Incrementals publisher causes corrupt configuration files in maven Issue Type: Task Assignee: Unassigned Components: incrementals-tools Created: 2020-01-22 22:39 Priority: Minor Reporter: Ulli Hafner After activating incrementals for all my plugins maven seems to produce very often corrupt configuration files for SpotBugs, PMD, and so on. This did not happen without incrementals. These configuration files are part of a jar file (dependency for each static analysis tool) and unpacked automatically before the analysis tool is started in maven. Examples: http://jenkins-ci.361315.n4.nabble.com/Incrementals-and-static-analysis-configuration-from-a-dependency-td5011947.html https://pipelines.actions.githubusercontent.com/9z5Z04LeOv0bqVj7OJZYELFwCHqkJ1zOYDpHprBY4n0MonHihT/_apis/pipelines/1/runs/55/signedlogcontent/3?urlExpires=2020-01-22T22%3A28%3A36.9900747Z&urlSigningMethod=HMACV1&urlSignature=CPaVs5WYIzRLR2dbZ7Gi35eBUFBGy7YbpUclREE3Zu4%3D
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-57918 SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 Change By: Devin Nusbaum Released As: repo 1.11.0 , workflow-scm-step 2.10 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199890.1560007155000.4069.1579731360599%40Atlassian.JIRA.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Devin Nusbaum commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 This was also fixed on Pipeline: SCM Step Plugin's side in version 2.10. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199890.1560007155000.4067.1579731300992%40Atlassian.JIRA.
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just release in Pipeline: SCM Step Plugin version 2.10. Jenkins / JENKINS-59560 NPE exception on pipeline checkout step (Pipeline multibranch) Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: workflow-scm-step 2.10 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60840) workflow-cps-plugin upgrade issue
Title: Message Title madhu muchukota created an issue Jenkins / JENKINS-60840 workflow-cps-plugin upgrade issue Issue Type: Task Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-01-22 21:57 Priority: Critical Reporter: madhu muchukota Hi Team, we recently upgraded our jenkins to 2.190.3 and after the upgrade, also upgraded the plugins. Our jenkins system is huge(more jobs/branches/builds) and after the upgrade, at the time of jenkins startup, we see that workflow cps plugin is scanning all the builds which eventually taking jenkins to come up after 3-4hrs. Could you please let us know if this is a normal behavior and if yes, what is needed to startup jenkins immediately? Can we disable the scanning? Below are the messages that we see in the logs: 26-Dec-2019 21:08:25.088 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-integration-api/release%2Fmaster-build-81-oct/1:customer-integration-api/release%2Fmaster-build-81-oct #1] heads:1::1:StepStartNode[id=6, exec=CpsFlowExecutionOwner[customer-integration-api/release%2Fmaster-build-81-oct/1:customer-integration-api/release%2Fmaster-build-81-oct #1]] 26-Dec-2019 21:15:40.442 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-service/master/392:customer-service/master #392] heads:empty-heads 26-Dec-2019 21:16:47.823 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-service/project%2Fcoexistence/470:customer-service/project%2Fcoexistence #470] heads:empty-heads 26-Dec-2019 21:34:14.095 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[joe-application/release%2F16.10.0-master-build-Nov-2019/113:joe-application/release
[JIRA] (JENKINS-57660) Git plugin stack trace saving job with invalid refspec
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57660 Git plugin stack trace saving job with invalid refspec Change By: Mark Waite Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.4026.1579727220156%40Atlassian.JIRA.
[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59327
No credentials specified Multibranch Pipeline - Branch script
Change By:
Mark Waite
Hi Team,When I am creating Multibranch Pipeline job which executes another pipeline job as a branch apparently it's not reading git credentials in branch. So in a branch which is a pipeline script, I have stage stage('git checkout') \{stage('git checkout') {steps { git credentialsId: 'My credentials', poll: false, url: 'mygit.git' }}But it's falling on Windows machine with the following error. When I create just a simple pipeline job with the same stage it's working as should.From test which I did when I specified credentials in a multibranch job which is managing my script in the branch then it's working. So apparently git credentials from the stage are ignored.Steps to Reproduce:1. Create Multibranch Job without specified git credentials with script-path where is a script.2. In a script create step with git checkout and specified credentials3. Run the branch script and it should fail.4. Add in Multibranch configuration credentials and run branch script it should work.{noformat}No credentials specifiedNo credentials specifiedWiping out workspace first.Cloning the remote Git repositoryCloning with configured refspecs honoured and without tagsERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --no-tags --force --progress MyRepo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: mygitserver: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: R
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated JENKINS-38608 Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.4022.1579726801270%40Atlassian.JIRA.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated JENKINS-38608 Will be fixed in first release after git plugin 4.1.1 Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web v
[JIRA] (JENKINS-60308) CompositeIOException is unhelpful for diagnostics
Title: Message Title Jesse Glick resolved as Duplicate Fixed as part of JENKINS-60716. Jenkins / JENKINS-60308 CompositeIOException is unhelpful for diagnostics Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/m
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated JENKINS-38608 Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.4001.1579725061049%40Atlassian.JIRA.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite started work on JENKINS-38608 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.3999.1579725061009%40Atlassian.JIRA.
[JIRA] (JENKINS-60832) Polling on matrix build always gives "P4: Polling error; no previous change.
Title: Message Title Karl Wirth commented on JENKINS-60832 Re: Polling on matrix build always gives "P4: Polling error; no previous change. Confirm I can reproduce this problem even if I have forced a build before. Manual builds work fine. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204183.1579654315000.3987.1579715160270%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Just hit this problem while testing JENKINS-60832 so wanted to highlight it to dev. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197398.1549406943000.3984.1579714260158%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title Hazim Malik commented on JENKINS-60725 Re: "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Thanks for the quick response and fix Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.3970.1579709280316%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Oleg Nenashev commented on JENKINS-54596 Re: can't parse argument number: changelog.url I will check whether we could get an out of order release Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.3956.1579708200307%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54596 can't parse argument number: changelog.url Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.3942.1579708140458%40Atlassian.JIRA.
[JIRA] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-21986 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153763.1393533805000.3936.1579707480272%40Atlassian.JIRA.
[JIRA] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-21987 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153764.1393534557000.3931.1579707420230%40Atlassian.JIRA.
[JIRA] (JENKINS-44405) Unable to archive reports after test
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-44405 Unable to archive reports after test Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182231.1495437546000.3925.1579707360335%40Atlassian.JIRA.
[JIRA] (JENKINS-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-45411 Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183579.1499713653000.3915.1579707303608%40Atlassian.JIRA.
[JIRA] (JENKINS-46843) Run Cleanup Test Case if Test is Failed
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-46843 Run Cleanup Test Case if Test is Failed Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185199.1505286372000.3909.1579707180275%40Atlassian.JIRA.
[JIRA] (JENKINS-47293) Timeout is Not Stopping UFT
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-47293 Timeout is Not Stopping UFT Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185715.1507217046000.3902.1579707121051%40Atlassian.JIRA.
[JIRA] (JENKINS-48509) Push UFT test results to JIRA via Jenkins
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-48509 Push UFT test results to JIRA via Jenkins Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187124.1513079603000.3895.1579707000649%40Atlassian.JIRA.
[JIRA] (JENKINS-50277) View UFT results directly in Jenkins
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-50277 View UFT results directly in Jenkins Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189311.1521535522000.3891.1579706940657%40Atlassian.JIRA.
[JIRA] (JENKINS-51265) Run Result Recorder: Didn't find any test results to record
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-51265 Run Result Recorder: Didn't find any test results to record Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190596.1526044639000.3885.1579706462721%40Atlassian.JIRA.
[JIRA] (JENKINS-51606) OTA Connectivity Issue with Jenkins 2.125 and HP ALM12.21 OTA (4848)
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-51606 OTA Connectivity Issue with Jenkins 2.125 and HP ALM12.21 OTA (4848) Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191011.1527680313000.3881.1579706400517%40Atlassian.JIRA.
[JIRA] (JENKINS-52270) Cannot use a parameter in Run Remote mode
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-52270 Cannot use a parameter in Run Remote mode Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192038.1530269531000.3874.1579706280321%40Atlassian.JIRA.
[JIRA] (JENKINS-52587) On reaching the timeOut is not saving the 'Test Result'
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-52587 On reaching the timeOut is not saving the 'Test Result' Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192430.1531758704000.3867.1579706220275%40Atlassian.JIRA.
[JIRA] (JENKINS-52612) User can run tests in a test set based on a filter
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-52612 User can run tests in a test set based on a filter Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192460.1531856881000.3862.1579706164111%40Atlassian.JIRA.
[JIRA] (JENKINS-54760) Allow the users to specify the test results path
Title: Message Title Paul-Adrian Tofan updated an issue Jenkins / JENKINS-54760 Allow the users to specify the test results path Change By: Paul-Adrian Tofan Labels: UFT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195565.1542822092000.3858.1579705980581%40Atlassian.JIRA.
[JIRA] (JENKINS-54760) Allow the users to specify the test results path
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-54760 Allow the users to specify the test results path Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195565.1542822092000.3855.1579705740250%40Atlassian.JIRA.
[JIRA] (JENKINS-56864) "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM
Title: Message Title Paul-Adrian Tofan updated JENKINS-56864 Jenkins / JENKINS-56864 "No certificate available" pop up is displayed when executing functional tests from Micro Focus ALM Change By: Paul-Adrian Tofan Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198531.1554292774000.3852.1579705385301%40Atlassian.JIRA.
[JIRA] (JENKINS-60832) Polling on matrix build always gives "P4: Polling error; no previous change.
Title: Message Title
Joel Brown commented on JENKINS-60832
Re: Polling on matrix build always gives "P4: Polling error; no previous change.
My Workspace name is jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER} Axis is VARIANT with valueA, valueB Polling is for syncID of jenkins-master-MultiConfigProject-VARIANT-valueA-0 The last build.xml has syncID jenkins-NODE_NAME-MultiConfigProject-EXECUTOR_NUMBER
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204183.1579654315000.3849.1579704840126%40Atlassian.JIRA.
[JIRA] (JENKINS-60839) Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail
Title: Message Title Roman Bäriswyl commented on JENKINS-60839 Re: Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail I could probably do it myself and open a PR but I miss some more background. The biggest problem is that in nunit-plugin at the specific place, I only see a `build (Run)` object. And it is based on `SimpleBuildStep` where I do not see the `getContext` method to get the `node` where I should add the `addOrReplaceAction(new WarningAction(Result.UNSTABLE)`. If someone could give me some hints, I could create a PR myself for this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204194.1579701404000.3848.1579703580047%40Atlassian.JIRA.
[JIRA] (JENKINS-60071) [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-60071 [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202905.1573021329000.3847.1579703520317%40Atlassian.JIRA.
[JIRA] (JENKINS-60595) Jenkins Multiple node to auto pick UFT test for execution serially
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-60595 Jenkins Multiple node to auto pick UFT test for execution serially Change By: Paul-Adrian Tofan Assignee: Tamas Florin Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203817.1577454305000.3843.1579703040881%40Atlassian.JIRA.
[JIRA] (JENKINS-60839) Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail
Title: Message Title Roman Bäriswyl created an issue Jenkins / JENKINS-60839 Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail Issue Type: Improvement Assignee: Unassigned Components: nunit-plugin Created: 2020-01-22 13:56 Priority: Major Reporter: Roman Bäriswyl Currently, when any of the tests fail, the whole build is marked as unstable without further incofmation (happens probably here) Now that there is a new API which passes more information about the failed step. That change is documented here. So the nunit plugin should be adjusted so that it can be displayed, where the build got unstable. In JUnit, this PR introduced this change. This PR might be used as idea on how to implement this. Add Comment
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Attachment: Screenshot 2020-01-22 at 14.17.14.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.3790.1579700760324%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Our config section looks a "little strange" - double up with settings. What could cause this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.3792.1579700760352%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title James Green commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) I have checked the option "Associate Public IP" for each agent and relaunched with ec2-plugin:1.49 - brand new agents are working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3763.1579699140339%40Atlassian.JIRA.
[JIRA] (JENKINS-60838) Undesirable killing process 'systemd --user' and its sub-tree
Title: Message Title Pavel Janoušek commented on JENKINS-60838 Re: Undesirable killing process 'systemd --user' and its sub-tree PR created. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204193.1579696574000.3759.1579697340047%40Atlassian.JIRA.
[JIRA] (JENKINS-56220) Artifactory Plugin not Publishing Build Information
Title: Message Title
Jed Jacobs updated an issue
Jenkins / JENKINS-56220
Artifactory Plugin not Publishing Build Information
Change By:
Jed Jacobs
We are testing our Jenkins upgrade to version 2.150.2. Using the UI, we are running existing jobs as a test. Note, these jobs run fine on version 2.121.3, which is our current version. This is preventing us from upgrading.This is what we call a health check job running every 30 minutes to confirm our connection to Artifactory is working. *Errors:* 17:46:11 [consumer_0] Deploying artifact: [https://us-artifactory.ourURL.com/artifactory/ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt|https://us-artifactory.oururl.com/artifactory/ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt] Our Artifactory URL 17:46:11 Deploying build info to: [https://us-artifactory.ourURL.com/artifactory/api/build|https://us-artifactory.oururl.com/artifactory/api/build] Our Artifactory URL 17:46:11 ERROR: Could not publish build-info: Failed to send build descriptor. 400 Response message: { 17:46:11 "errors" : [{ 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 }] 17:46:11 } 17:46:11 java.io.IOException: Could not publish build-info: Failed to send build descriptor. 400 Response message: { 17:46:11 "errors" : [{ 17:46:11 "status" : 400, 17:46:11 "message" : "Dependency id name cannot be null!" 17:46:11 }] 17:46:11 } 17:46:11 at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:261) 17:46:11 at org.jfrog.build.extractor.retention.Utils.sendBuildAndBuildRetention(Utils.java:63) 17:46:11 at org.jfrog.hudson.generic.GenericBuildInfoDeployer.deploy(GenericBuildInfoDeployer.java:62) 17:46:11 at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator$1.tearDown(ArtifactoryGenericConfigurator.java:360) 17:46:11 at hudson.model.Build$BuildExecution.doRun(Build.java:174) 17:46:11 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 17:46:11 at hudson.model.Run.execute(Run.java:1810) 17:46:11 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 17:46:11 at hudson.model.ResourceController.execute(ResourceController.java:97) 17:46:11 at hudson.model.Executor.run(Executor.java:429)*Configuration:* { "files": [ { "pattern": "TestUpload.txt", "target": "ili-libs-snapshot-local/com/ourURL/ConfigMgmt/1.1.1/TestUploadPlugin.txt", "props": "build.latest=true;dateDeploy.dev=1/16/18" } ] } Updated Information:We have isolated this error to the download using the plugin. It looks like it tries to publish build information on the download before even trying to download the artifact. In the output below, you'll see a directory listing from a prior job step. Then it will show it's trying to publish the build information and the failure. I don't see it trying to download the artifact, which I though w
[JIRA] (JENKINS-56239) Gradle cache locked
Title: Message Title Jed Jacobs updated an issue Jenkins / JENKINS-56239 Gradle cache locked Change By: Jed Jacobs Attachment: log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197806.1550783918000.3756.1579696800283%40Atlassian.JIRA.
[JIRA] (JENKINS-60838) Undesirable killing process 'systemd --user' and its sub-tree
Title: Message Title Pavel Janoušek started work on JENKINS-60838 Change By: Pavel Janoušek Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204193.1579696574000.3754.1579696680084%40Atlassian.JIRA.
[JIRA] (JENKINS-60838) Undesirable killing process 'systemd --user' and its sub-tree
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-60838 Undesirable killing process 'systemd --user' and its sub-tree Issue Type: Bug Assignee: Pavel Janoušek Components: proc-cleaner-plugin Created: 2020-01-22 12:36 Environment: RHEL8 Priority: Major Reporter: Pavel Janoušek Plugin kills "systemd --user" process and its sub-tree during clean-up. It is undesirable for sure. The whole process subtree is better left untouched. The issue manifests on RHEL8 and similar Linuxes. Add Comment
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60133 Re: Default HOME folder in containers does not exist This is probably a side effect of the change of working directory to /home/jenkins/agent (i.e. https://issues.jenkins-ci.org/browse/JENKINS-58705). If the /home/jenkins does not exist in the image, it will be automatically added during the mounting of the workspace volume but will not be writable. The DEFAULT_HOME might need to be changed. Otherwise images need to be adapted for arbitrary users as documented in https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/creating_images/creating-images-guidelines. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.3745.1579695600150%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate documentation from Wiki to GitHub
Title: Message Title Victor Martinez assigned an issue to Victor Martinez Jenkins / JENKINS-60837 Migrate documentation from Wiki to GitHub Change By: Victor Martinez Assignee: Victor Martinez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204192.1579694274000.3742.1579694400330%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate documentation from Wiki to GitHub
Title: Message Title Victor Martinez started work on JENKINS-60837 Change By: Victor Martinez Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204192.1579694274000.3743.1579694400726%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate documentation from Wiki to GitHub
Title: Message Title Victor Martinez commented on JENKINS-60837 Re: Migrate documentation from Wiki to GitHub PR https://github.com/jenkinsci/google-compute-engine-plugin/pull/178 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204192.1579694274000.3741.1579694400246%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate documentation from Wiki to GitHub
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-60837 Migrate documentation from Wiki to GitHub Change By: Victor Martinez Component/s: google-compute-engine-plugin Component/s: other Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204192.1579694274000.3740.1579694340092%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate documentation from Wiki to GitHub
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-60837 Migrate documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2020-01-22 11:57 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Victor Martinez We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be update
[JIRA] (JENKINS-60836) "No such property: JENKINS_URL" on cron-triggered job, resolved by manual trigger
Title: Message Title
Allan Lewis created an issue
Jenkins / JENKINS-60836
"No such property: JENKINS_URL" on cron-triggered job, resolved by manual trigger
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
consoleText, plugins.txt
Components:
core, pipeline
Created:
2020-01-22 11:34
Environment:
Jenkins 2.176.2 See attached plugins.txt
Priority:
Major
Reporter:
Allan Lewis
I have a multi-branch pipeline with the following as the first line, outside of pipeline:
JENKINS_HOST = JENKINS_URL.toURL().host.tokenize('.')[0]
This value is used inside the pipeline. The pipeline generally works but, apparently at random, builds will fail with the following exception:
groovy.lang.MissingPropertyException: No such property: JENKINS_URL for class: groovy.lang.Binding
See consoleText for a redacted console log including the stack trace. This has only been observed on cron-triggered builds: manually building the job, or rebuilding a failed job, works fine. The pipeline defines so
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) James Green that sounds like the exact same case then Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3725.1579691340259%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title benoit guerin commented on JENKINS-54596 Re: can't parse argument number: changelog.url See https://issues.jenkins-ci.org/browse/JENKINS-60822?focusedCommentId=383444&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-383444 You will not see this issue anymore once you are up to date, and until a new release of Jenkins is published Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.3709.1579689540358%40Atlassian.JIRA.
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title
Kalle Niemitalo commented on JENKINS-43556
Re: Stage View shows incorrect build result
I was able to remove the incorrect data from the cache by calling com.cloudbees.workflow.flownode.FlowNodeUtil.CacheExtension.all().get(0).getRunCache().invalidate("the externalizable ID of the run") from the script console. Before that, I had tried "Reload Configuration from Disk" under "Manage Jenkins", but it had not cleared the cache, even though its description appears to say otherwise: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk."
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180873.1492034462000.3681.1579687860843%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title James Green commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) FWIW our working Jenkins installation (with ec2-plugin:1.45) has instances configured to launch within the same VPC as Jenkins itself, and the "Associate Public IP address" checkbox is not checked. Yet ec2 instances do have public IPs - we just never noticed. I am guessing that updated plugin versions now require this checkbox to be checked. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3672.1579687380520%40Atlassian.JIRA.
[JIRA] (JENKINS-60835) Publish information about currently running builds via API
Title: Message Title
Nik Reiman created an issue
Jenkins / JENKINS-60835
Publish information about currently running builds via API
Issue Type:
Improvement
Assignee:
Unassigned
Components:
swarm-plugin
Created:
2020-01-22 09:16
Priority:
Minor
Reporter:
Nik Reiman
When using slave.jar, build nodes publish information about currently running builds via the Jenkins API. I'm not super well-versed in the API internals, but as far as I can tell, this involves publishing extra information for each executor. Otherwise, Jenkins replaces this with a PlaceholderTask, which doesn't contain any information about what is actually building, and the API consumer can only see if the executor is idle or not. Effectively, this means that API calls such as [{{get_running_builds}} in the python-jenkins API|]https://python-jenkins.readthedocs.io/en/latest/api.html#jenkins.Jenkins.get_running_builds return an empty list, which is not terribly useful.
Add Comment
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Alessandro Dionisi commented on JENKINS-60831 Re: Localisation to non-english is causing a lot of issues, bug and crashes I confirm the same for italian Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204182.1579617297000.3657.1579684020250%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer Updated the plugin to version 1.25.0, the issue is gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203018.1573630888000.3651.1579683360212%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) Raihaan Shouhell sure, I do my best to get you the required details: All I do is done with cloudformation, so it should be reproducible. Everytime we install a new version, i create it from scratch: I remove everything and build it up from ground with cloudformation only (no manual steps and no cloudformation updates). You can find a stripped down version of the cloudformation templates here: https://gist.github.com/imod/fb702d545dbe77292e8f4796c7804059 The templates should contain all the details you need. The 'vpc-cloudformation-template,json' creates the full VPC with route tables, subnet and gateway and can be executed as is, but I had to remove quite a bit from the 'jenkins-cloudformation-template,json' - this one would install Jenkins on a EC2 instance and configure the security groups. I hope this is useful, if you don't get a long with cloudformation, please let me know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3645.1579680900314%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Norbert Pfistner edited a comment on JENKINS-54596 Re: can't parse argument number: changelog.url Same to mee me after upgrading to 2.214 but I solved it by# forcing english locale (using Quick Locale Switcher in FF)# opening manage page (now works fine when in EN)# updating to Jenkins ver. 2.215In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.3642.1579680661205%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Norbert Pfistner commented on JENKINS-54596 Re: can't parse argument number: changelog.url Same to mee but I solved it by forcing english locale (using Quick Locale Switcher in FF) opening manage page (now works fine when in EN) updating to Jenkins ver. 2.215 In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.3617.1579680360538%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page Solved by# forcing english locale (using Quick Locale Switcher in FF)# opening manage page (now works fine when in EN)# updating to Jenkins ver. 2.215In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204185.1579678665000.3614.1579680360294%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner commented on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page Solved by forcing english locale (using Quick Locale Switcher in FF) opening manage page (now works fine when in EN) updating to Jenkins ver. 2.215 In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204185.1579678665000.3613.1579680300053%40Atlassian.JIRA.
