[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Raihaan Shouhell commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart ec2.hpi For your latest issue the linked HPI should solve it. The issue you seem to see is when starting from a stopped instance due to eventual consistency of AWS APIs it occasionally sees a freshly started instance as stopped as a result for newly started instances I added a retry to deal with 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.199745.1559315049000.4734.1568694780366%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Raihaan Shouhell edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart [^ec2.hpi] [~sirzic] ^For your latest issue the linked HPI should solve it. The issue you seem to see is when starting from a stopped instance due to eventual consistency of AWS APIs it occasionally sees a freshly started instance as stopped as a result for newly started instances I added a retry to deal with 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.199745.1559315049000.4739.1568694780466%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Raihaan Shouhell updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Raihaan Shouhell Attachment: ec2.hpi 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.199745.1559315049000.4729.1568694720485%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Assignee: Kohsuke Kawaguchi 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.201856.1568169015000.4726.1568689560217%40Atlassian.JIRA.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Brendan Hatton commented on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start I encountered a similar issue after updating the script-security plugin. For me the problem was related to the OWASP family of plugins (dependency-check, dependency-track, formatter). The way I solved it was to Disabled the script-security plugin to allow jenkins to start install two additional plugins which were complaining in the logs - Active Choices and Static Analysis Utilities This was a big pain for us 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.198873.1555704698000.4720.1568683800299%40Atlassian.JIRA.
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title
Jon Starbird created an issue
Jenkins / JENKINS-59401
After Upgrade to Inedo Plugin 2.5.0 could not create package
Issue Type:
Bug
Assignee:
Andrew Sumner
Components:
inedo-buildmaster-plugin
Created:
2019-09-17 00:48
Environment:
Jenkins 2.176.3 Inedo Buildmaster plugin 2.5.0 BuildMaster 6.1.10
Priority:
Major
Reporter:
Jon Starbird
After updating to plugin 2.5.0 it fails to create a build in BuildMaster. I don't get an error I merely get a msg of:
[2019-09-16T22:36:13.574Z] [BuildMaster] Create build for the PNM Main and Admin application, release 15.6.0
Conversion = 'F'
I was previously on 2.4.0 and after downgrading the plugin it does work again so the plugin update is the only change. This is using Jenkinsfile and the request to do create a build is like this:
buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") { buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") { script { def verstr = gitprops.GitVersion_FullSemVer if (env.BRANCH_NAME == 'master') { verstr = gitprops.GitVersion_MajorMinorPatch } def (reponame,jobname) = JOB_NAME.split('/') def bmjenkinsjobname= "${reponame}/job/${jobname}"
[JIRA] (JENKINS-42435) Add support for Blue Ocean to Git Parameter plugin
Title: Message Title Brent Zeiss commented on JENKINS-42435 Re: Add support for Blue Ocean to Git Parameter plugin It doesn't work with version 1.19.0 either. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179342.1488450162000.4712.1568681340347%40Atlassian.JIRA.
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha created an issue Jenkins / JENKINS-59400 Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-17 00:27 Environment: * Jenkins 2.176.2 * Master(x1) and Build(x6) nodes are running Windows 10 64B Enterprise * Java Version 8 Update 201 (build 1.8.0_201-b09) Oracle * Jenkins is running on Master from command line call * Jenkins is running on Slaves as a service * Web browser: Chrome Version 76.0.3809.132 (Official Build) (64-bit) Labels: slave slaves Slave hang hanging delay Priority: Critical Reporter: John Rocha Jenkins slave nodes hangs for up to 12+ minutes after build phase completes. I have a master node and 7 nodes in the build pool. The master is configured to only run jobs labeled master. Builds are always only done from the build nodes. There are no post-build steps configured. Hang/delay is observed if the build step passes and/or fails. Example Console Output follows --- 2019-09-16 16:51:45 ERROR: last command returned failure: 1 2019-09-16 16:51:45 2019-09-16 16:51:45 build.bat failed
[JIRA] (JENKINS-59398) blueocean header should show who replayed a job run
Title: Message Title Josh Soref commented on JENKINS-59398 Re: blueocean header should show who replayed a job run I can see a couple of ways to do this: as in PR#323, changing the ReplayCause to report the user directly – there's a slight risk of showing the same information more than once. changing all clients of ReplayCause to do the same work – lots of consumers are stuck reinventing some code. changing blueocean to report (and try to flatten) all of the causes into this field – I don't think this will be particularly pretty (which is probably why it wasn't done already). I don't really care which way it's implemented, I'd just like to see the information I need when I'm looking at blueocean. 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.201955.1568664348000.4708.1568671740055%40Atlassian.JIRA.
[JIRA] (JENKINS-59398) blueocean header should show who replayed a job run
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-59398 blueocean header should show who replayed a job run Change By: Josh Soref Assignee: Josh Soref 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.201955.1568664348000.4707.1568671440069%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Jenkins_Restart.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4692.1568667661047%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4691.1568667660898%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins [^Jenkins_Restart] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4701.1568667661809%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4702.1568667661839%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins[^Jenkins_Restart] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4686.1568667600405%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins Jenkins_Restart Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4677.1568667540570%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.4676.1568667540558%40Atlassian.JIRA.
[JIRA] (JENKINS-59399) 404 when trying to connect Windows node to Linux Master
Title: Message Title Mark Russell created an issue Jenkins / JENKINS-59399 404 when trying to connect Windows node to Linux Master Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-09-16 20:43 Environment: _ /usr/bin/daemon HOME /var/lib/jenkins JENKINS_HOME /data/jenkins LANG en_US.UTF-8 LOGNAME jenkins MAIL /var/mail/jenkins PATH /var/lib/jenkins/bin:/var/lib/jenkins/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin PWD /var/lib/jenkins SHELL /bin/bash SHLVL 1 USER jenkins XDG_DATA_DIRS /usr/local/share:/usr/share:/var/lib/snapd/desktop XDG_RUNTIME_DIR /run/user/113 XDG_SESSION_ID c5 Labels: remote node windows Priority: Minor Reporter: Mark Russell When I try to run a Windows Node to a Jenkins Linux master I get a 404 that tcpSlaveAgentListener can not be found. I connect to my Jenkins master from the Windows node and go to the node's computer page I copy the java command to a powershell command window and then run like below: java -jar agent.jar -jnlpUrl https://xxx-yyy-build-jenkins-0.zzz.cloud/computer/jslave-win-fw-0/slave-agent.jnlp -secret secret -workDir "C:\data\jenkins" I get the following:
[JIRA] (JENKINS-59398) blueocean header should show who replayed a job run
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59398 blueocean header should show who replayed a job run Issue Type: Improvement Assignee: Unassigned Attachments: image-2019-09-16-15-59-46-428.png, image-2019-09-16-16-00-21-900.png Components: blueocean-plugin, workflow-cps-plugin Created: 2019-09-16 20:05 Priority: Minor Reporter: Josh Soref I can look at a job header (e.g. /blue/organizations/.../detail/master/102/pipeline) and see this: If I click: I'm taken to /job/.../master/102 Which shows "Started by user" (core/src/main/resources/hudson/model/Cause/UserCause/description.properties: started_by_user) Note: I don't really need this for "push event to branch" as that is the reason. This appears to be: https://github.com/jenkinsci/workflow-cps-plugin/blob/9b768a42f60cc3389031646c24927fa062d444e1/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/Messages.properties#L4 Add Comment
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59381 Re: OWASP Plugin 1.6 crashed Jenkins I haven't tested with the scenario described here. The exception looks the same users got in active choices when upgrading to 2.2. Released 2.2.1 last night (New Zealand time) with a tentative fix. One user reported it worked so far. 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.201937.1568575654000.4601.1568662020211%40Atlassian.JIRA.
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang updated an issue Jenkins / JENKINS-59397 iOS upload timeout for large size of app Change By: david huang When I try to upload an iOS app about 400MB to App center, the plugin returns a timeout error and upload failed. Error: Creating an upload resource.Upload resource successful.Uploading app to resource.Upload app unsuccessful.java.net.SocketTimeoutException: timeoutio.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeoutBuild step 'Upload app to AppCenter' changed build result to FAILURE expect the plugin can upload a large size app without timeout error 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
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang created an issue Jenkins / JENKINS-59397 iOS upload timeout for large size of app Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-09-16 19:17 Priority: Minor Reporter: david huang When I try to upload an iOS app about 400MB to App center, the plugin returns a timeout error and upload failed. Error: Creating an upload resource. Upload resource successful. Uploading app to resource. Upload app unsuccessful. java.net.SocketTimeoutException: timeout io.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeout Build step 'Upload app to AppCenter' changed build result to FAILURE Add Comment
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati commented on JENKINS-59280 Re: jiraJqlSearch Error Message: null value after upgrade Sorry to hear that... I will look into this soon, probably I am guessing we need to make fields as optional, mean don't even send it when it is not present. 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.201811.1568029791000.4592.1568659260342%40Atlassian.JIRA.
[JIRA] (JENKINS-59374) svn checkout fails when running jenkins master in docker container
Title: Message Title Moyo Lawal commented on JENKINS-59374 Re: svn checkout fails when running jenkins master in docker container Hi Ivan, Thanks. I updated the svn plugin in my test environment to the very latest (v2.12.2) and svn checkout seems to work fine now. Was avoiding doing this as we didn't want to deviate from the plugin versions in our prod environment. Thanks anyways. 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.201930.1568460368000.4570.1568653860134%40Atlassian.JIRA.
[JIRA] (JENKINS-59373) JenkinsRule not working with Gradle JPI Plugin
Title: Message Title Steve Hill commented on JENKINS-59373 Re: JenkinsRule not working with Gradle JPI Plugin Hi Andrew Sumner, thanks for the report! Is there a set of commands I can run to reproduce the error you're getting? After cloning your repo's master branch (commit 7988b3a76b8f1203f13d83e58e6edaec28902108), I'm able to run both ./gradlew check on the command line and com.inedo.proget.jenkins.PluginTests from IntelliJ. From the logs, it does appear to be starting and stopping the server as expected. Thanks Daniel Beck for the link to the changelog! We could potentially make this transition a little easier in the plugin, but this is the first time it's come up as an issue. The changelog is from 2017, so this change has been out for quite a while. As an aside, do you know why I have to explicity add repo 'http://repo.jenkins-ci.org/public' rather than just use jcenter? Yes, it's because most jenkins-specific dependencies and plugins are not published to jcenter. They're published to the maven repository at repo.jenkins-ci.org. Gradle Version I see you're running Gradle 4.7. Have you considered upgrading? This version is quite old (released 2018-04-18) and the next release due out is Gradle 6.0. There are many nice features introduced in Gradle 5.x and coming in 6.x. Ideally a future release of gradle-jpi-plugin will stop supporting the Gradle 4.x series. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-59374) svn checkout fails when running jenkins master in docker container
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59374 Re: svn checkout fails when running jenkins master in docker container Sure it is related with the mapped windows volume, I cannot help you too much from here, I don’t maintain the subversion plugin anymore. 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.201930.1568460368000.4565.1568653200175%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. I opened the second ticket and tried the new beta patch and I feel like the new patch is working without errors but I am still experiencing the HostName problem. I am unable to run a test on a specific HostName. I've update the other ticket with the details and I think one of these is now a duplicate of the other. Let me know how you would like to proceed or if both tickets should remain open. Jim 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.198392.1553542192000.4558.1568652780328%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Jayp Pascua updated JENKINS-59395 Jenkins / JENKINS-59395 unable to build projects via nodes Change By: Jayp Pascua Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201952.1568647162000.4556.1568652480424%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Jayp Pascua commented on JENKINS-59395 Re: unable to build projects via nodes okay thanks! after updating the subversion plugin everything worked again. thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201952.1568647162000.4554.1568652420142%40Atlassian.JIRA.
[JIRA] (JENKINS-59374) svn checkout fails when running jenkins master in docker container
Title: Message Title Moyo Lawal commented on JENKINS-59374 Re: svn checkout fails when running jenkins master in docker container Hi Ivan, No symbolic links. No externals. I actually created a brand new svn repo with just a Jenkinsfile in there. Still the same issue. Nothing has been checked out in the workspace directory on the jenkins slave. I however see that repo has been checked out on jenkins master under $JENKINS_HOME/workspace. I'm guessing this is how it can read the jenkinsfile successfully to initiate the actual pipeline process I should mention the checkout on the master was failing previously when I was using a mapped volume onto a windows server. I had to switch to using a docker volume; and grant rw access to everyone on that volume. Only after this did the temp svn checkouts which jenkins does on master start to work. I got the clue from this post "https://forums.docker.com/t/error-in-jenkins-on-docker-toolbox-for-windows-volume-permission-issue/67283". I believe it might be the same issue, but this time on the slave. I however can't use a similar workaround. Once again my git repositories worked absolutely fine even with the mapped windows volume, and still 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
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-59395 Re: unable to build projects via nodes I am no longer the maintainer of the subversion plugin (more than a year ago) , please do not assign me any issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201952.1568647162000.4550.1568651880410%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59395 Re: unable to build projects via nodes I am no longer the maintainer of the subversion plugin (more than a year ago) 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.201952.1568647162000.4548.1568651880373%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-59395 unable to build projects via nodes Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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.201952.1568647162000.4546.1568651820140%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Jim Sears updated an issue Jenkins / JENKINS-59391 Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Change By: Jim Sears Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201948.1568640537000.4544.1568651640477%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Jim Sears commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start The new plug-in works better than before, I can run a test as long as I don't care which PC is running the test and I populate "RunMode" with a Host List. Unfortunately, I'm having issue with the Planned Host Name. If I set the value to "Run Remotely" and leave the "Run Mode" value blank then I get an exception. (I leave it blank because I have the Planned HostName on the Test in the QC Test Set already defined.) Goal: Run a test on a specific HostName. I need the test to run on a specific PC because the test deletes temp files and reboots the PC. (Maintenance process). Works but doesn't satisfy my goal: I can run on a remote PC only if the HostList and the Plugin RunMode value matches. In this case, I set the PlannedHostName and RunMode to TAF_LAB_UFT. Test doesn't actually run on the PC I need it to. How do I get the test to run on the Planned Host Name in QC instead of the HostName listed in Plugin RunMode? I've tried all three RunMode options. 1) RunMode = "Run Remotely" and leaving the HostName list blank but I get this error. 2) RunMode = "Run Locally" won't work bc the test only runs on the Slave and that isn't the correct PC. 3) RunMode = "Run on Planned Host" and leave it blank and I get the same error. If I put in the Host List then the test runs on any available Host. I have no way of controlling the PC (Host) where the test is expected to execute. Started by user Jim Sears Building on master in workspace d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-Reboot [TAF LAB PC Maintenance-Reboot] $ "d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-Reboot\HpToolsLauncher.exe" -paramfile props16092019112733046.txt "Started..." Timeout is set to: 180 Run mode is set to: RUN_REMOTE Unable to retrieve test set folder: Node not found. Starting test set execution Test set name: LabMaintenance-Reboot, Test set id: 210 Test 1: [1]RebootLabPC will run on host: Test 2: [2]RebootLabPC will run on host: Test 3: [3]RebootLabPC will run on host: Test 4: [4]RebootLabPC will run on host: Test 5: [5]RebootLabPC will run on host: Test 6: [6]RebootLabPC will run on host: Test 7: [7]RebootLabPC will run on host: Problem while running TestSet: Exception from HRESULT: 0x80040459 "Scheduler started at:16/09/2019 11:27:38 --- Unhandled Exception: System.ArgumentNullException: Value cannot be null. Parameter name: Current test set is null. at HpToolsLauncher.AlmTestSetsRunner.SetTestResults(ITSTest currentTest, IExecutionStatus executionStatus, ITestSet targetTestSet, TestRunResults activeTestDesc, TestSuiteRunResults runDesc, String testPath, String abortFilename) at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, String testParameters, Double timeout, QcRunMode runMode, String runHost, Boolean isFilterSelected, String filterByName, List`1 filterByStatuses, TestStorageType testStorageType) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] done Triggering a new build of MF QC Test Set Execution » Automation CoE » LabMainteance QA EmailReport Finished: SUCCESS
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Nikolas Falco assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-59395 unable to build projects via nodes Change By: Nikolas Falco Assignee: Nikolas Falco Ivan Fernandez Calvo 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.201952.1568647162000.4540.1568648640197%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59395 unable to build projects via nodes Change By: Nikolas Falco Component/s: subversion-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201952.1568647162000.4537.1568648580436%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-59395 unable to build projects via nodes Change By: Nikolas Falco Component/s: scm-api-plugin Component/s: nodejs-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201952.1568647162000.4535.1568648520126%40Atlassian.JIRA.
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Nikolas Falco commented on JENKINS-59395 Re: unable to build projects via nodes I do not see any nodejs plugin class in the stacktrace. The only one I can see are: jenkins.scm.SCMCheckoutStrategy hudson.scm.SubversionWorkspaceSelector.syncWorkspaceFormatFromMaster This means that it fails on checkout phase. Here nodejs plugin seems not called yet 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.201952.1568647162000.4533.1568648460743%40Atlassian.JIRA.
[JIRA] (JENKINS-59374) svn checkout fails when running jenkins master in docker container
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59374 Re: svn checkout fails when running jenkins master in docker container Do you have symbolic links on your subversion repo? Do you use svn externals in the repo? Check if in the Agent workdir inside the workspace folder the job has created something from the svn repo checkout 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.201930.1568460368000.4531.1568648040832%40Atlassian.JIRA.
[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Title: Message Title Francois Ferrand commented on JENKINS-37557 Re: Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs I created a pull-request which allows to overcome this, by passing explicitely `getContext(hudson.EnvVars)` when creating the RepoScm object. https://github.com/jenkinsci/repo-plugin/pull/54 May not be a full solution, but works fine as a stop-gap pending, until support for (multiple) credentials is baked into the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173669.1471622564000.4529.1568648040806%40Atlassian.JIRA.
[JIRA] (JENKINS-59396) AWT initialized event with -Djava.awt.headless=true
Title: Message Title Julien Bréda created an issue Jenkins / JENKINS-59396 AWT initialized event with -Djava.awt.headless=true Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-16 15:26 Environment: Jenkins v2.176.1, RedHat 7, AdoptOpenJDK jdk8u222-b10 Priority: Major Reporter: Julien Bréda I tried to use AdoptOpenJDK jdk8u222-b10 instead of Oracle JDK 8. I need to change my JDK, that's not my choice, and I couldn't launch Jenkins because of this issue : hudson.util.AWTProblem: java.lang.NullPointerException at hudson.WebAppMain.contextInitialized(WebAppMain.java:193) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4776) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5240) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:629) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1838) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by:
[JIRA] (JENKINS-59395) unable to build projects via nodes
Title: Message Title Jayp Pascua created an issue Jenkins / JENKINS-59395 unable to build projects via nodes Issue Type: Bug Assignee: Nikolas Falco Components: nodejs-plugin Created: 2019-09-16 15:19 Priority: Major Reporter: Jayp Pascua unable to run builds via nodes after updating jenkins to latest version. all nodes are connected and on idle. Nodes status: <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.35 This is a Unix agent Evacuated stdout Agent successfully connected and online Sep 16, 2019 9:05:20 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class net.bull.javamelody.RemoteCallHelper$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Build error: FATAL: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to QA1Web at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1071) at hudson.FilePath.act(FilePath.java:1060) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:901) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:837) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) java.lang.IllegalStateException: Jenkins.instance is
[JIRA] (JENKINS-50292) maven-vault-plugin error
Title: Message Title Nick Carlyle closed an issue as Fixed Jenkins / JENKINS-50292 maven-vault-plugin error Change By: Nick Carlyle Status: Open 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.189331.1521558603000.4510.1568645701691%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Mark Waite commented on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ Thanks for the clarification Devin Nusbaum. I think you're correct based on the comment in that pull request. Fix is to run git plugin 3.12.x with workflow-cps-global-lib 2.14 or newer. 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.201311.1565953154000.4506.1568645280196%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title
Adrian Prieto updated an issue
Jenkins / JENKINS-59394
Veracode Plugin configuration error
Change By:
Adrian Prieto
I'm getting the following error while trying to upload files to Veracode:{code:java}C:\Program Files (x86)\Jenkins\workspace\SC20>exit 1 Build step 'Execute Windows batch command' marked build as failureUpload and Scan with VeracodeVeracodeJavaAPI v19.6.5.8 c1.8.0_144Parsing error(s): -filepath is required for the selected action.The following parameters are optional for the selected action: -autoscan -exclude -format -inputfilepath -logfilepath -phost -ppassword -pport -puser -sandboxid -scanallnonfataltoplevelmodules -scantimeout -selected -selectedpreviously -teams -toplevel[19.09.16 15:27:59] Invalid inputError- Returned code from wrapper:1Build step 'Upload and Scan with Veracode' marked build as failureFinished: FAILURE{code}Below the configuration used:!config.PNG! Any idea about what I'm missing or doing wrong? Thanks in advance
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto created an issue Jenkins / JENKINS-59394 Veracode Plugin configuration error Issue Type: Bug Assignee: Mike Bockus Attachments: config.PNG Components: veracode-scanner-plugin Created: 2019-09-16 14:39 Labels: veracode plug-in Priority: Minor Reporter: Adrian Prieto I'm getting the following error while trying to upload files to Veracode: C:\Program Files (x86)\Jenkins\workspace\SC20>exit 1 Build step 'Execute Windows batch command' marked build as failure Upload and Scan with Veracode VeracodeJavaAPI v19.6.5.8 c1.8.0_144Parsing error(s): -filepath is required for the selected action.The following parameters are optional for the selected action: -autoscan-exclude -format -inputfilepath -logfilepath -phost -ppassword -pport -puser -sandboxid -scanallnonfataltoplevelmodules -scantimeout -selected-selectedpreviously -teams -toplevel[19.09.16 15:27:59] Invalid inputError- Returned code from wrapper:1 Build step 'Upload and Scan with Veracode' marked build as failure Finished: FAILURE
[JIRA] (JENKINS-59393) Fix malformed XML in Atom and RSS 2.0 feeds
Title: Message Title Basil Crow created an issue Jenkins / JENKINS-59393 Fix malformed XML in Atom and RSS 2.0 feeds Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-16 14:38 Priority: Minor Reporter: Basil Crow While fixing JENKINS-59231, I noticed that Jenkins RSS 2.0 and Atom XML feeds have malformed XML. Inserting an interactive break and fetching the URL, we see that Jenkins is returning malformed XML: $ curl http://localhost:43969/jenkins/rssAll All all builds2001-01-01T00:00:00ZJenkins Serverurn:uuid:903deee0-7bfa-11db-9fe1-0800200c9a66 Note that the tag is not terminated, despite the fact that it is terminated in the template: $ grep link core/src/main/resources/hudson/atom.jelly So Jelly must be screwing this up when filling in the template. Where is that happening? Stepping through the code in the debugger reveals this stack trace: createXMLOutput:68, DefaultScriptInvoker (org.kohsuke.stapler.jelly) invokeScript:51, DefaultScriptInvoker (org.kohsuke.stapler.jelly) execute:56, ScriptInvoker (org.kohsuke.stapler.jelly) execute:43, ScriptInvoker (org.kohsuke.stapler.jelly) forward:95, ScriptRequestDispatcher (org.kohsuke.stapler) forwardToRss:91, RSS
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin edited a comment on JENKINS-59381 Re: OWASP Plugin 1.6 crashed Jenkins Thanks [~kinow] Is this related , correct no ? 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.201937.1568575654000.4496.1568644260147%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin commented on JENKINS-59381 Re: OWASP Plugin 1.6 crashed Jenkins Bruno P. Kinoshita, correct? 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.201937.1568575654000.4489.1568644200400%40Atlassian.JIRA.
[JIRA] (JENKINS-58974) Unable to configure manageWebHooks in JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58974 Unable to configure manageWebHooks in JCasC Change By: Oleg Nenashev Labels: gsoc-2019 jcasc-compatibility 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.201323.1566065267000.4491.1568644200467%40Atlassian.JIRA.
[JIRA] (JENKINS-58974) Unable to configure manageWebHooks in JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58974 Unable to configure manageWebHooks in JCasC Change By: Oleg Nenashev Released As: Gitlab Branch Source 1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201323.1566065267000.4493.1568644200557%40Atlassian.JIRA.
[JIRA] (JENKINS-57947) [FUTURE] More secured method to manage credentials in JCasC yaml
Title: Message Title Oleg Nenashev commented on JENKINS-57947 Re: [FUTURE] More secured method to manage credentials in JCasC yaml JCasC offers standard tools for it. What is wrong with them? https://github.com/jenkinsci/configuration-as-code-plugin#handling-secrets 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.199924.1560215713000.4486.1568644140253%40Atlassian.JIRA.
[JIRA] (JENKINS-57947) [FUTURE] More secured method to manage credentials in JCasC yaml
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57947 [FUTURE] More secured method to manage credentials in JCasC yaml Change By: Oleg Nenashev Labels: gsoc-2019 jcasc-compatibility 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.199924.1560215713000.4482.1568644080208%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin updated an issue Jenkins / JENKINS-59381 OWASP Plugin 1.6 crashed Jenkins Change By: Joe Tavin Component/s: active-choices-plugin Component/s: antisamy-markup-formatter-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201937.1568575654000.4478.1568643900462%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin updated an issue Jenkins / JENKINS-59381 OWASP Plugin 1.6 crashed Jenkins Change By: Joe Tavin Environment: - Jenkins Server: 2.194 ( currently latest at 15/9/2019 )- Installed as System Service (init.d) on Ubuntu 14.04 LTS- Java: OpenJDK build 1.8.0_141-8u141 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.201937.1568575654000.4475.1568643900414%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin updated an issue Jenkins / JENKINS-59381 OWASP Plugin 1.6 crashed Jenkins Change By: Joe Tavin Environment: - Jenkins Server: 2.194 (currently latest) - Installed as System Service (init.d) on Ubuntu 14.04 LTS - Java: OpenJDK build 1.8.0_141-8u141 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.201937.1568575654000.4474.1568643900401%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Joe Tavin updated an issue Jenkins / JENKINS-59381 OWASP Plugin 1.6 crashed Jenkins Change By: Joe Tavin Labels: active-choices markup-formatter ActiveChoices 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.201937.1568575654000.4471.1568643840222%40Atlassian.JIRA.
[JIRA] (JENKINS-57230) Postbuildscript: NullPointerException
Title: Message Title Alfred Wong commented on JENKINS-57230 Re: Postbuildscript: NullPointerException The jenkins master is Linux and the slaves are Windows. 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.198990.1556565743000.4455.1568642580875%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Devin Nusbaum edited a comment on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ I think that [~olivergondza] thought that workflow-cps-global-lib was a compile scope dependency in git plugin, so that [ https://github.com/jenkinsci/git-plugin/pull/742 ] would enforce the dependency requirements for all users, [but it is actually test scope|https://github.com/jenkinsci/git-plugin/pull/742/files#r315197236], so 3.12.0 should be functionally the same as 3.11.0, and the only fix is to manually make sure you only use those versions of git plugin with workflow-cps-global -lib 2.14 or newer. 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.201311.1565953154000.4451.1568642460175%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Devin Nusbaum commented on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ I think that Oliver Gondža thought that workflow-cps-global-lib was a compile scope dependency in git plugin, so that https://github.com/jenkinsci/git-plugin/pull/742 would enforce the dependency requirements for all users, but it is actually test scope, so 3.12.0 should be functionally the same as 3.11.0, and the only fix is to manually make sure you only use those versions with workflow-cps-global 2.14 or newer. 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.201311.1565953154000.4449.1568642402732%40Atlassian.JIRA.
[JIRA] (JENKINS-59374) svn checkout fails when running jenkins master in docker container
Title: Message Title Moyo Lawal commented on JENKINS-59374 Re: svn checkout fails when running jenkins master in docker container Hi Ivan, I checked the log for the slave which is located in the logs folder of the master node. No error message in here. Just the following lines " Inbound agent connected from 10.0.2.2/10.0.2.2 Remoting version: 3.33 This is a Windows agent Agent successfully connected and online " Are there any other logs I should be checking? I'm not sure I fully understand the statement "check the permission on the workdir of the user you use to connect the agent". Are you saying I should check the permission of the agent dir on the windows slave? Or the user which I'm using to run jenkins in the docker container(which is jenkins by default) should have access to the slave workdir i.e agent folder? P.S: This works fine out of the box when using a git repository for the same slave. git checkout runs fine and job runs 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.201930.1568460368000.4445.1568642280732%40Atlassian.JIRA.
[JIRA] (JENKINS-59081) Test automation for JCasC import
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59081 Test automation for JCasC import Change By: Oleg Nenashev Labels: jcasc-compatibility -tests 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.201471.1566817037000.4443.1568642220167%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Mark Waite updated JENKINS-58964 Jenkins / JENKINS-58964 Git not considered modern SCM for git-3.11.0+ Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201311.1565953154000.4441.1568642161372%40Atlassian.JIRA.
[JIRA] (JENKINS-50571) Add support of Configuration-as-Code in Artifact Manager S3
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50571 Add support of Configuration-as-Code in Artifact Manager S3 Change By: Oleg Nenashev Released As: Artifact Manager S3 1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189645.1522852463000.4436.1568642161142%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Mark Waite commented on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ I believe this is resolved by using git plugin 3.12.0 or later. As far as understand from Oliver Gondža, the bug was in the git plugin and the fix is also in the git plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201311.1565953154000.4435.1568642161108%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev commented on JENKINS-54662 Re: hudson.model.UsageStatistics not compatible with CasC plugin Does not look so. I reset the status 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.195453.1542317055000.4430.1568641920295%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev stopped work on JENKINS-54662 Change By: Oleg Nenashev Status: In Progress Open 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.195453.1542317055000.4425.1568641860512%40Atlassian.JIRA.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54662 hudson.model.UsageStatistics not compatible with CasC plugin Change By: Oleg Nenashev Labels: jcasc-compatibility stalled-pr 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.195453.1542317055000.4427.1568641860592%40Atlassian.JIRA.
[JIRA] (JENKINS-56684) Config as Code Nullpointer when instanceCapStr is not initialized
Title: Message Title Oleg Nenashev updated JENKINS-56684 It was released in EC2 Plugin 1.44 Jenkins / JENKINS-56684 Config as Code Nullpointer when instanceCapStr is not initialized Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: EC2 Plugin 1.44 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
[JIRA] (JENKINS-52995) Make Display URL Provider configurable via JCasC
Title: Message Title Oleg Nenashev stopped work on JENKINS-52995 Change By: Oleg Nenashev Status: In Progress Open 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.192980.1533982963000.4418.1568641809406%40Atlassian.JIRA.
[JIRA] (JENKINS-52995) Make Display URL Provider configurable via JCasC
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-52995 Make Display URL Provider configurable via JCasC Change By: Oleg Nenashev Assignee: Mrinal Dutta 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.192980.1533982963000.4420.1568641809473%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Maria Narcisa Galan commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Hi! Last week we released a new version of our plugin. Please install it and tell us if the problem persists . Here is the link from where you can download it: Directly or through Jenkins using the instructions here. 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.201948.1568640537000.4414.1568641808851%40Atlassian.JIRA.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53486 email-ext fails when CasC attempts to set smtpHost Change By: Oleg Nenashev Labels: configuration-as-code jcasc-compatibility 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.193954.1536546047000.4403.1568641740737%40Atlassian.JIRA.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57603 Git Plugin: No JCasC configurator for Submodule configurations Change By: Oleg Nenashev Released As: Git plugin 3.10.1 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.199528.1558527868000.4399.1568641681262%40Atlassian.JIRA.
[JIRA] (JENKINS-59103) jira-steps-plugin JCasC export fails with ConfiguratorException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59103 jira-steps-plugin JCasC export fails with ConfiguratorException Change By: Oleg Nenashev Labels: jcasc-compatibility 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.201524.1566916441000.4383.1568641620588%40Atlassian.JIRA.
[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57182 When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config Change By: Oleg Nenashev Released As: JIRA Steps 1.5.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198934.1556196877000.4386.1568641620761%40Atlassian.JIRA.
[JIRA] (JENKINS-59392) Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs'
Title: Message Title
Damian Szuberski updated an issue
Jenkins / JENKINS-59392
Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs'
Change By:
Damian Szuberski
Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs' Jenkins ver 2.176.1. To reproduce the problem: (1) create multibranch pipeline with 1 *Behaviour* *Discover other refs.* Refs should be located OUTSIDE of refs/heads (in my example it was *refs/merge-requests/ \ */merge*) so no default git mapping -> refs/heads/ could be used implicitly(2) run branch discovery, job for specific branch would be run with result: Branch indexing > git rev-parse --is-inside-work-tree # timeout=10Setting origin to [|https://scm.cci.nokia.net/nsw-ce-3g/test1.git] > git config remote.origin.url [|https://scm.cci.nokia.net/nsw-ce-3g/test1.git] # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10 > git config --get remote.origin.url # timeout=10 > git fetch --tags --force --progress origin +refs/merge-requests/ \ */merge:refs/remotes/origin/merge-requests/ \ */merge > git rev-parse refs/merge-requests/1/merge^\{commit} # timeout=10ERROR: Could not determine exact tip revision of merge-request-1; falling back to nondeterministic checkoutThen Jenkins tried to get commit 2 more times but the result is the same. The culprit is the false assumption ingit rev-parse *refs/merge-requests/1/merge^\{commit}*invocation that the selected branch would be available directly under refs/ \ * which is not true and even refspec used during fetch confirms that. git rev-parse should be run on local remote tracking branch ref refs/remotes/origin/merge-requests/1/merge, not its server counterpart refs/merge-requests/1/merge. There is a quick workaround for this: create *Specify ref specs* which would mirror server branch to client branch 1-to-1, in my example '+*refs/merge-requests/ \ */merge: ** refs/merge-requests/ \ */merge'.* ** Additionally (this is not directly related to the problem above) reading Jenkinsfile stage could be optimized by passing --depth 1 switch to git fetch (only during Jenkinsfile discovery!). We don't have to fech full branch history to be able to read Jenkinsfile from the tip of the branch.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Oleg Nenashev Released As: JIRA Plugin 3.0.7 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.192863.1533584356000.4376.1568641561161%40Atlassian.JIRA.
[JIRA] (JENKINS-56697) Simplify constructor, main URL is the only mandatory field
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56697 Simplify constructor, main URL is the only mandatory field Change By: Oleg Nenashev Released As: JIRA Plugin 3.0.6 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.198335.1553331175000.4372.1568641561085%40Atlassian.JIRA.
[JIRA] (JENKINS-53864) CasC compatibility with Log Parser Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53864 CasC compatibility with Log Parser Plugin Change By: Oleg Nenashev Released As: Log Parser 2.1 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.194390.153843636.4366.1568641500620%40Atlassian.JIRA.
[JIRA] (JENKINS-59392) Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs'
Title: Message Title
Damian Szuberski created an issue
Jenkins / JENKINS-59392
Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs'
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-09-16 13:42
Priority:
Major
Reporter:
Damian Szuberski
Multibranch pipeline is unable to checkout branches discovered by 'Discover other refs' Jenkins ver 2.176.1. To reproduce the problem: (1) create multibranch pipeline with 1 Behaviour Discover other refs. Refs should be located OUTSIDE of refs/heads (in my example it was refs/merge-requests//merge*) so no default git mapping -> refs/heads/ could be used implicitly (2) run branch discovery, job for specific branch would be run with result: Branch indexing > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to > git config remote.origin.url
timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git config --get remote.origin.url # timeout=10 > git fetch --tags --force --progress origin +refs/merge-requests//merge:refs/remotes/origin/merge-requests//merge > git rev-parse refs/merge-requests/1/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of merge-request-1; falling back to nondeterministic checkout
Then Jenkins tried to get commit 2 more times but the result is the same. The culprit is the false assumption in git rev-parse refs/merge-requests/1/merge^{commit} invocation that the selected branch would be available directly under refs/* which is not true and even refspec used during fetch confirms that. git rev-parse should be run on local remote tracking branch ref refs/remotes/origin/merge-requests/1/merge, not its server counterpart refs/merge-requests/1/merge. There is a quick workaround for
[JIRA] (JENKINS-58491) Cannot configure Nomad plugin with JCasC
Title: Message Title Oleg Nenashev updated JENKINS-58491 Jenkins / JENKINS-58491 Cannot configure Nomad plugin with JCasC Change By: Oleg Nenashev 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.200629.1563185265000.4358.1568640903908%40Atlassian.JIRA.
[JIRA] (JENKINS-58491) Cannot configure Nomad plugin with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58491 Cannot configure Nomad plugin with JCasC Change By: Oleg Nenashev Released As: Nomad Plugin 0.6.8 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.200629.1563185265000.4354.1568640840973%40Atlassian.JIRA.
[JIRA] (JENKINS-57719) Pegdown plugin not supported by JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57719 Pegdown plugin not supported by JCasC Change By: Oleg Nenashev Released As: JCasC 1.21 or earlier 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.199662.1559061709000.4351.1568640840860%40Atlassian.JIRA.
[JIRA] (JENKINS-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52695 Update External Task API to natively support JCasC Change By: Oleg Nenashev Component/s: external-logging-api-plugin Component/s: plugin-proposals 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.192580.153233000.4345.1568640780311%40Atlassian.JIRA.
[JIRA] (JENKINS-59126) Add compatibility test with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59126 Add compatibility test with JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility -tests 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.201558.1567006548000.4341.1568640541047%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Jim Sears created an issue Jenkins / JENKINS-59391 Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Issue Type: Bug Assignee: Maria Narcisa Galan Attachments: Jenkins ALM settings.png Components: hp-application-automation-tools-plugin Created: 2019-09-16 13:28 Environment: Micro Focus Quality Center 12.55, Patch 3 Labels: ALM execution Priority: Major Reporter: Jim Sears Jenkins Console output shows the Test execution does not start. The HostName is . The plug-in option for where to run the test has "Planned Host Name" and Quality Center is populated with a Host list value. I've also attached a screenshot of the Jenkins ALM plugin settings. 5.8 has an issue and doesn't start the test run. Please see the log below. [RouteOne Medium] $ "d:\Jenkins\.jenkins\workspace\Agile Enablement Factories\Sales And Product\1-2 Dealer Sales\RouteOne Medium\HpToolsLauncher.exe" -paramfile props13092019181324010.txt "Started..." Timeout is set to: 7200 Run mode is set to: RUN_PLANNED_HOST Starting test set execution Test set name: Demo, Test set id: 1423 Number of tests in set: 5 Test 1: [1]R1_AKL_CAL_BUS_LSE will run on host: Test 2: [1]R1_AKL_CAL_BUS_RET will run on host: Test 3: [1]R1_AKL_CAL_IND_LSE will run on host:
[JIRA] (JENKINS-57824) Add Full JCasC test to SSH Credentials Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57824 Add Full JCasC test to SSH Credentials Plugin Change By: Oleg Nenashev Labels: jcasc-compatibility 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.199779.1559579051000.4337.1568640540925%40Atlassian.JIRA.
[JIRA] (JENKINS-57824) Add Full JCasC test to SSH Credentials Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57824 Add Full JCasC test to SSH Credentials Plugin Change By: Oleg Nenashev Labels: jcasc-compatibility-tests 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.199779.1559579051000.4339.1568640540963%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Devin Nusbaum commented on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ Oleg Nenashev No, but I can try to release in the next few weeks. Note though that neither the git nor workflow-cps-global-lib PRs fix the problem, the fix in this case is to only run git 3.11.0 or newer along with workflow-cps-global-lib 2.14 or newer. If you run git 3.11.0 or newer with an older version of workflow-cps-global-lib, that is how you run into the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201311.1565953154000.4334.1568640360181%40Atlassian.JIRA.
[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"
Title: Message Title Andrew Mullens commented on JENKINS-57537 Re: catchError - Expecting "class hudson.model.Result" for parameter "buildResult" Hey Devin, thank you. I saw that and was passing in a string, but turns out our Plug in Version is 2.66. So it should work once we update the plug in. Thanks again. 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.199445.1558161153000.4329.1568640060972%40Atlassian.JIRA.
[JIRA] (JENKINS-58964) Git not considered modern SCM for git-3.11.0+
Title: Message Title Oleg Nenashev commented on JENKINS-58964 Re: Git not considered modern SCM for git-3.11.0+ Devin Nusbaum Hi. Is there a ETA for the https://github.com/jenkinsci/workflow-cps-global-lib-plugin/pull/78 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.201311.1565953154000.4325.1568640001433%40Atlassian.JIRA.
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Mikko Mattila commented on JENKINS-50558 Re: Valgrind plugin results error I'm running Ubuntu 16.04, and today started seeing this error after installing `libjfreechart-java`. After removing it, Valgrind plugin seems to work alright again! 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.189627.1522812897000.4286.1568639580711%40Atlassian.JIRA.
[JIRA] (JENKINS-59390) EC2 slave disconnects with EOFException
Title: Message Title Rogério Colferai created an issue Jenkins / JENKINS-59390 EC2 slave disconnects with EOFException Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-09-16 13:06 Environment: Server Ubuntu 18.04.3 LTS Jenkins ver. 2.176.3 Plugins Amazon EC2 plugin 1.45 SSH Slaves 1.30.1 Slaves: Priority: Critical Reporter: Rogério Colferai Hello, After upgrading jenkins from 2.164.3, to 2.176.3 and EC2 plugin to 1.45 EC2 slaves are disconnecting (intermittent disconnects) in the middle of builds with an EOFException. java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport. I tried to make the rollback
[JIRA] (JENKINS-48259) Purge Build History throws an exception if a build is running
Title: Message Title Aytunc BEKEN commented on JENKINS-48259 Re: Purge Build History throws an exception if a build is running Thanks! Probably I will fix the issue this week. I will let you 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.186842.1511862405000.4281.1568638560207%40Atlassian.JIRA.
[JIRA] (JENKINS-48221) Add parser for abi-compliance-checker
Title: Message Title Ulli Hafner commented on JENKINS-48221 Re: Add parser for abi-compliance-checker I see. There are 2 different XML parser approaches used so far: EclipseXMLParser.java JcReportParser.java 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.186800.1511616866000.4277.1568638140464%40Atlassian.JIRA.
[JIRA] (JENKINS-58441) can I use changeset in when pipeline syntax
Title: Message Title Hokwang Lee commented on JENKINS-58441 Re: can I use changeset in when pipeline syntax Thanks. You can close this case. 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.200573.1562851583000.4269.1568637900102%40Atlassian.JIRA.
[JIRA] (JENKINS-48259) Purge Build History throws an exception if a build is running
Title: Message Title Marcus Goitowski commented on JENKINS-48259 Re: Purge Build History throws an exception if a build is running Skipping the running builds would be perfectly fine and what I assume is the expected behavior. Thanks for joining the Jenkins team and maintaining this plugin! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186842.1511862405000.4267.1568637180121%40Atlassian.JIRA.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev commented on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Updating Active choice to 2.2.1 has solved the issue https://issues.jenkins-ci.org/browse/JENKINS-59389 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.198873.1555704698000.4261.1568637060381%40Atlassian.JIRA.
