[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Mez Pahlan commented on JENKINS-60262 Re: Jenkins AppCenter Plugin cannot used Guogang Gao can you also stop changing the status of this ticket. It hasn't been accepted not has any fault found yet. Please wait for me to assess the impact. Many 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.203249.1574676517000.6889.1574754900183%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Mez Pahlan updated JENKINS-60262 Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Change By: Mez Pahlan Resolution: Fixed Status: Fixed but Unreleased Reopened 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.203249.1574676517000.6887.1574754780195%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao updated JENKINS-60262 Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Change By: Guogang Gao 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.203249.1574676517000.6885.1574754060337%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao stopped work on JENKINS-60262 Change By: Guogang Gao 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.203249.1574676517000.6883.1574754000199%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Mez Pahlan commented on JENKINS-60262 Re: Jenkins AppCenter Plugin cannot used Hi Guogang Gao can you please post your configuration for the job please. I can't tell what your specific issue is from the description. Many 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.203249.1574676517000.6881.1574753100238%40Atlassian.JIRA.
[JIRA] (JENKINS-60280) Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data
Title: Message Title Stephan Vogt created an issue Jenkins / JENKINS-60280 Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data Issue Type: Bug Assignee: Unassigned Components: core, swarm-plugin Created: 2019-11-26 07:12 Environment: Jenkins Master (v 2.164.1) running directly (no container) on a Windows 7 (64bit) host. Several Jenkins clients running in Windows 10 (64bit) VMs on different machines. Clients connect via swarm client (v3.17). Both master and clients are started as batch files, and are running in a console window (no Windows service). Issue seen both with Oracle Java 8u141 and OpenJDK 8u232. Priority: Major Reporter: Stephan Vogt We are sporadically seeing jobs failing with this callstack shown in the log: javax.crypto.BadPaddingException: Invalid TLS padding data at sun.security.ssl.CipherBox.removePadding(CipherBox.java:802) at sun.security.ssl.CipherBox.decrypt(CipherBox.java:574) at sun.security.ssl.EngineInputRecord.decrypt(EngineInputRecord.java:200) at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:963) Caused: javax.net.ssl.SSLException: Invalid TLS padding data at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1709) at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:970) at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:896) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:766) at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) at
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Uwe Brackenhoff updated an issue Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Uwe Brackenhoff Summary: Warnings-NG: recordIssue attribute 'name' probalby probably ignored 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.203260.157469810.6878.1574752320202%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Stefan Scherer commented on JENKINS-59752 Re: Add support for ephemeral OS disk Thanks Bradley Wangia for your PR. And thanks Jie Shen for the new release. I planned to compile it and run some tests, but now it's even simpler to give this feature a try today. 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.202475.1570808392000.6874.1574747340241%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao assigned an issue to Unassigned Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Change By: Guogang Gao Assignee: Guogang Gao 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.203249.1574676517000.6872.1574745780145%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao started work on JENKINS-60262 Change By: Guogang Gao Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203249.1574676517000.6869.1574745720418%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao assigned an issue to Guogang Gao Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Change By: Guogang Gao Assignee: Mez Pahlan Guogang Gao 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.203249.1574676517000.6871.1574745720468%40Atlassian.JIRA.
[JIRA] (JENKINS-60279) build symlink plugin creating incorrect links
Title: Message Title
Eric Wallengren created an issue
Jenkins / JENKINS-60279
build symlink plugin creating incorrect links
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
build-symlink-plugin
Created:
2019-11-26 03:56
Environment:
Jenkins version 2.190.3, build symlink plugin 1.1
Priority:
Major
Reporter:
Eric Wallengren
Create a new pipeline job called linktest:
pipeline {
agent { label 'master' }
stages {
stage('build') {
steps {
echo "Hello World!"
}
}
}
}
Execute the job. The resulting symlinks for lastCompletedBuild, lastSuccessfulBuild and lastStableBuild are all linked to '-1'. Execute the job again and the links will now point to '1'. The resulting links for build which are successful or stable are always 1 less than the actual good build number. The permalinks file is reporting correct build numbers.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested but the master is still logging the same error: ` {code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s. ` {code} However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
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.170238.1462391043000.6839.1574739600674%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested (all the settings for WinRM and everything else) but the master is still logging the same error:{code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.{code}However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
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.170238.1462391043000.6850.1574739600825%40Atlassian.JIRA.
[JIRA] (JENKINS-59972) Can I automate 'launch of Java web start slave agent ' to run selenium jenkins jobs.
Title: Message Title Federico Pellegrin commented on JENKINS-59972 Re: Can I automate 'launch of Java web start slave agent ' to run selenium jenkins jobs. One easy (working) solution, it may fit or not your case security wise: Configure the machine to login automatically as a given user Put in the Startup folder of that user a batch file that starts the agent, something like (of course modify the URL and credentials per your needs): java -jar C:\slave.jar -jnlpUrl "http://jenkins.site.url:8080/computer/MACHINEXYZ/slave-agent.jnlp" -jnlpCredentials : 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.202776.157234752.6836.1574738160130%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Jie Shen updated JENKINS-59752 Jenkins / JENKINS-59752 Add support for ephemeral OS disk Change By: Jie Shen Status: In Review Resolved Resolution: Done Released As: 1.3.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.202475.1570808392000.6832.1574737920789%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Jie Shen commented on JENKINS-59752 Re: Add support for ephemeral OS disk Bradley Wangia thanks for your contribution here! I have released this feature in the version of 1.3.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.202475.1570808392000.6828.1574737860255%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Federico Pellegrin commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar Amila Gunathilake: sure you should add the pipeline and the coverage file that the job generates (the XMLs) to be able to get help. 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.6825.1574737200291%40Atlassian.JIRA.
[JIRA] (JENKINS-60278) Empty field in Whitelisted Commands will cause an Oops and prevent saving
Title: Message Title Federico Pellegrin assigned an issue to Federico Pellegrin Jenkins / JENKINS-60278 Empty field in Whitelisted Commands will cause an Oops and prevent saving Change By: Federico Pellegrin Assignee: Federico Pellegrin 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.203268.1574736858000.6822.1574737080063%40Atlassian.JIRA.
[JIRA] (JENKINS-60278) Empty field in Whitelisted Commands will cause an Oops and prevent saving
Title: Message Title Federico Pellegrin created an issue Jenkins / JENKINS-60278 Empty field in Whitelisted Commands will cause an Oops and prevent saving Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-11-26 02:54 Priority: Minor Reporter: Federico Pellegrin If the "Currently Whitelisted Commands" in "Manage Jenkins → Configure Global Security → Agent → Master Access Control" is left totally empty and form is submitted with the button "Update", then an Oops will occur: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.AbstractStringBuilder.charAt(AbstractStringBuilder.java:237) at java.lang.StringBuilder.charAt(StringBuilder.java:76) at jenkins.security.s2m.AdminWhitelistRule.doSubmit(AdminWhitelistRule.java:165) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) And no data will be saved.
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title ovi craciun resolved as Cannot Reproduce Jenkins / JENKINS-60258 NullPointerException using EC2-plugin version 1.46.1 Change By: ovi craciun Status: Open Resolved Assignee: FABRIZIO MANFREDI ovi craciun Resolution: Cannot Reproduce 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.203245.1574601298000.6820.1574735580326%40Atlassian.JIRA.
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title ovi craciun commented on JENKINS-60258 Re: NullPointerException using EC2-plugin version 1.46.1 I had a bunch of other plugins not up to date, I have updated them and now the error is gone. Those other plugins did not seem to be related at all with the EC2 plugin. Anyhow , I am glad I am passed this, but I am facing no a different issue, this one here: https://issues.jenkins-ci.org/browse/JENKINS-34610 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.203245.1574601298000.6818.1574734920165%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what [ Alex Taylor |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76]have suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you 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.170238.1462391043000.6808.1574734200325%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has and [Brendan Stewart |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76]have suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you 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.170238.1462391043000.6797.1574734140495%40Atlassian.JIRA.
[JIRA] (JENKINS-60277) NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250)
Title: Message Title Nutan Sawant created an issue Jenkins / JENKINS-60277 NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250) Issue Type: Bug Assignee: Unassigned Attachments: Jenkins_EMEPluginIssue_Package_support_2019-11-26_00.42.45.zip Components: pipeline Created: 2019-11-26 01:39 Environment: Jenkins 2.150.3, Please refer attached support package file. Priority: Minor Reporter: Nutan Sawant Facing below issue when creating pipeline in Jenkins which polls the AbInitio EME under SCM. Stack trace java.lang.NullPointerException at EMEJenkinsPlugin.EME_SCM.(EME_SCM.java:250) at sun.reflect.GeneratedConstructorAccessor448.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:778) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title Marcello Romani commented on JENKINS-41929 Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found [...] adds a "Refresh Job Definition" button to the sidebar of a job. That doesn't sound like a bad idea... 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.178785.1486740246000.6674.1574730962262%40Atlassian.JIRA.
[JIRA] (JENKINS-60276) several dependencies are missing from the Jenkins bom
Title: Message Title James Nord created an issue Jenkins / JENKINS-60276 several dependencies are missing from the Jenkins bom Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-11-26 00:57 Priority: Minor Reporter: James Nord there are quite a few dependency versionsdefined in core and not the bom. whilst some of them are internal a few are oversights that should be pulled out. (non exhaustive list) : org.apache.commons:commons-compress org.apache.commons:commons-collections Add Comment
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Connection timedout uploading the pom (looks like the hpi went through). Will have more time tonight to try the release of 1.5 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.184922.1504289511000.6665.1574729760201%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title
Mark Waite edited a comment on JENKINS-60267
Re: Shorthand git step doesn't handle commit hashes
The {{git}} shorthand is considered a [ dead end |https://issues.jenkins-ci.org/browse/JENKINS-58503?focusedCommentId=371284=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-371284] by [~jglick]. He recommends [no further additions|https://issues.jenkins-ci.org/browse/JENKINS-58503?focusedCommentId=371284=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-371284] be made to it. The preferred path forward is to define symbols for the various classes and extensions which are now declared more verbosely when using the {{checkout}} step. That will allow simpler syntax in the checkout step and allow the full capabilities of the checkout step, rather than attempting to add all the capabilities of the checkout step to the git step.I assume the same behavior is visible when you use a full SHA-1 rather than the abbreviated SHA-1 hash that is used in the examples you listed. Can you confirm that?
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.203255.1574683768000.6652.1574729520477%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000Connecting to (17.30.6.34) with WinRM as AdministratorWaiting for WinRM to come up. Sleeping 10s.Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you 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.170238.1462391043000.6655.1574729520547%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title
Mark Waite edited a comment on JENKINS-60267
Re: Shorthand git step doesn't handle commit hashes
The {{git}} shorthand is considered a dead end by @ [~ jglick ] . He recommends [no further additions|https://issues.jenkins-ci.org/browse/JENKINS-58503?focusedCommentId=371284=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-371284] be made to it. The preferred path forward is to define symbols for the various classes and extensions which are now declared more verbosely when using the {{checkout}} step. That will allow simpler syntax in the checkout step and allow the full capabilities of the checkout step, rather than attempting to add all the capabilities of the checkout step to the git step.I assume the same behavior is visible when you use a full SHA-1 rather than the abbreviated SHA-1 hash that is used in the examples you listed. Can you confirm that?
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.203255.1574683768000.6650.1574729465625%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title Mark Waite commented on JENKINS-60267 Re: Shorthand git step doesn't handle commit hashes The git shorthand is considered a dead end by @jglick. He recommends no further additions be made to it. The preferred path forward is to define symbols for the various classes and extensions which are now declared more verbosely when using the checkout step. That will allow simpler syntax in the checkout step and allow the full capabilities of the checkout step, rather than attempting to add all the capabilities of the checkout step to the git step. I assume the same behavior is visible when you use a full SHA-1 rather than the abbreviated SHA-1 hash that is used in the examples you listed. Can you confirm that? 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.203255.1574683768000.6648.1574729465529%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun commented on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has suggested but the master is still logging the same error: `EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.` However, I can telnet the slave on the 5985 port and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM? Any other ideas what should I try here? I've lost already two days to get this to work. Thank you 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.170238.1462391043000.6638.1574728740349%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake assigned an issue to Stephen Connolly Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Assignee: Martin Sander Stephen Connolly 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.6634.1574728260226%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Sure thing Scott Logan. Releasing now, unless something goes wrong with the Maven process, it should be available in the next hours. 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.184922.1504289511000.6628.1574728140175%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita updated JENKINS-46592 Jenkins / JENKINS-46592 Issue with Graph Plugin Change By: Bruno P. Kinoshita 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.184922.1504289511000.6623.1574728081362%40Atlassian.JIRA.
[JIRA] (JENKINS-55151) GitHub Branch Source Plugin: Failed branch indexing
Title: Message Title Owen Mehegan commented on JENKINS-55151 Re: GitHub Branch Source Plugin: Failed branch indexing A customer encountered this issue yesterday. After examining the code (https://github.com/github-api/github-api/blob/github-api-1.95/src/main/java/org/kohsuke/github/GitHub.java#L475) it seems that we are trying to do some string parsing on a response from the GitHub API, and the response is not in the expected format, so the parsing fails ungracefully. In the case of my customer, it turned out that the credentials they were using did not have the appropriate access in GitHub to perform the required operation. They had to enable/authorize this credential/user for SSO in GitHub in order to resolve the issue. Perhaps the plugin could be improved with some exception handling 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.196218.1544623225000.6620.1574727780232%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake assigned an issue to Martin Sander Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Assignee: Martin Sander 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.6617.1574727360322%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title Jeff MacLoue commented on JENKINS-60267 Re: Shorthand git step doesn't handle commit hashes Any reason not to fix this the other way around? Besides the effort needed, of course. The thing is - "detached HEAD" builds by commit hash is just too popular. It's much too often you see tasks like "Our latest commit broke the production, deploy revision ad3ad12 immediately!" (and, of course, there is no tag or branch head pointing to this revision, it's just HEAD^ from master or something like it), and to be able to perform such tasks efficiently you have to stick with the "long" Git checkout syntax in your pipelines. Regardless of the syntax, checking out by commit hash by putting it in "branches" parameter is confusing enough already, so different behaviour of a shortcut adds yet another quirk to keep in mind. Also checkout([$class: "GitSCM", ...]) looks too similar to how you used to wrap pre-pipeline era plugins in generic build steps, so it's counter-intuitive that you should use this syntax to get the things done: you don't do step([$class: "ArtifactArchiverStep", ...]) instead of clearer archiveArtifact ..., why do checkout([$class: "GitSCM", ...]) instead of git ... ? 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-60275) Connecting via https with Jenkins_URL as http breaks Favicon theme element
Title: Message Title William Brode created an issue Jenkins / JENKINS-60275 Connecting via https with Jenkins_URL as http breaks Favicon theme element Issue Type: Bug Assignee: William Brode Components: simple-theme-plugin Created: 2019-11-25 23:55 Environment: Jenkins 2.190.2 Simple Theme Plugin 0.5.1 Priority: Minor Reporter: William Brode We have both https and http access supported for our Jenkins instance. We set our Jenkins Location -> Jenkins URL to the http address. We noticed that when connecting to the instance via https, the theme element for Favicon URL wasn't functioning properly (favicon was NOT repalced). However, using the http address to the server worked fine (the favicon was replaced). Doing some digging I was able to find what I think was the problem (uploading a simple change did fix the issue). Basically it was using the jenkins url to load a file in the plugin - /plugin/simple-theme-plugin/simple-theme.js . But I believe since the url was to the http address something was not allowing it (like you can't load a site without SSL from an SSL site?). I believe the simple fix is to remove the URL since directly accessing the file should work. I'll send a pull request with the fix.
[JIRA] (JENKINS-30101) Keep user specific reason for offline slave when slave getting disconnected
Title: Message Title Eric Daigneault commented on JENKINS-30101 Re: Keep user specific reason for offline slave when slave getting disconnected I would make this as a bug rather than an improvement. This makes Offline reasons provided by the user completely useless as a communication tool within the team regarding why this specific agent is offline. The Offline Reason is Effectively broken in the current behavior 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.164681.1440344015000.6608.1574720820206%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title
Mark Waite edited a comment on JENKINS-56002
Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin
I don't know why the upgrade of the git plugin would break the SQS notifier notification plugin with:{{Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils}}I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-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.197420.154948501.6604.1574719140673%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title
Mark Waite edited a comment on JENKINS-56002
Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin
I don't know why the upgrade of the git plugin would break the SQS notifier plugin with:{{Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils}}I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-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.197420.154948501.6599.1574719140558%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Mark Waite commented on JENKINS-56002 Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin I don't know why the upgrade of the git plugin would break with: Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils I've taken the liberty of assigning the bug to the "Automatic Assignee" as though the bug had been originally submitted to the sqs-notification-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.197420.154948501.6594.1574719140429%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Mark Waite assigned an issue to Chris Contolini Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin Change By: Mark Waite Assignee: Chris Contolini 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.197420.154948501.6589.1574719020273%40Atlassian.JIRA.
[JIRA] (JENKINS-59195) Plugin archetypes should suggest GitHub as a default URL
Title: Message Title Tim Jacomb updated JENKINS-59195 Jenkins / JENKINS-59195 Plugin archetypes should suggest GitHub as a default URL Change By: Tim Jacomb Status: Fixed but Unreleased Closed Released As: 1.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.201636.1567453983000.6586.1574718780290%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Michele Stuart commented on JENKINS-56002 Re: Upgrading Git Plugin to :latest causes Issues with SQS Plugin I realize this is several months old, but as it's still open, perhaps I can provide more info. I just ran into the problem and posted about it at https://github.com/jenkinsci/aws-sqs-plugin/issues/29#issuecomment-558347125. Versions: Jenkins: 2.190.3 Java OpenJDK: 11.0.4 AWS SQS plugin: 2.0.1 Git plugin: 3.10.0 / 4.0.0 OS: Ubuntu 18.04 LTS To reproduce: With a valid Jenkins SQS configuration in place under Configure System => Configuration of Amazon SQS queues, i.e. with a queue configured and appropriate IAM credentials to connect to it. Upgrade the Git plugin to version 4.0.0. Restart Jenkins If you are tailing the Jenkins log, you will immediately start seeing the attached errors spewing into the log. In the Jenkins web interface, go to Configure System => Configuration of Amazon SQS queues and click "Test Access" on one of your queues. You will see the result "Error." If you click on the Error link, you'll see the Java error, as in the server log. 5. Downgrade the Git plugin to 3.10.0 6. Restart Jenkins 7. If you are tailing the server log, the errors will now stop. 8. In the web interface queue configuration, clicking "Test Access" will now result in success (assuming you have good credentials). sqsError.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Michele Stuart updated an issue Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin Change By: Michele Stuart Attachment: sqsError.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.197420.154948501.6577.1574718660430%40Atlassian.JIRA.
[JIRA] (JENKINS-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Michele Stuart updated an issue Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin Change By: Michele Stuart Attachment: sqsError.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.197420.154948501.6575.1574718660398%40Atlassian.JIRA.
[JIRA] (JENKINS-60167) AtomicFileWriter performance issue on CephFS in case of Empty File creation
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60167 AtomicFileWriter performance issue on CephFS in case of Empty File creation Change By: Oleg Nenashev Labels: lts-candidate 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.203119.1573721452000.6562.1574717160461%40Atlassian.JIRA.
[JIRA] (JENKINS-60167) AtomicFileWriter performance issue on CephFS in case of Empty File creation
Title: Message Title Oleg Nenashev updated JENKINS-60167 Released in Jenkins 2.206. It might be a good LTS candideate, but I am not sure about 2.204.1. Maybe it needs more soak testing though the change itself is definitely valid Jenkins / JENKINS-60167 AtomicFileWriter performance issue on CephFS in case of Empty File creation Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.206 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60092) ArrayIndexOutOfBoundsException in getPrimaryView when no view exists
Title: Message Title Oleg Nenashev updated JENKINS-60092 Fixed it 2.206. I am not sure whether it is a good LTS candidate taking the plan to introduce the default view, but I will leave the decision to Oliver Gondža Jenkins / JENKINS-60092 ArrayIndexOutOfBoundsException in getPrimaryView when no view exists 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
[JIRA] (JENKINS-60092) ArrayIndexOutOfBoundsException in getPrimaryView when no view exists
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60092 ArrayIndexOutOfBoundsException in getPrimaryView when no view exists Change By: Oleg Nenashev Labels: exception lts-candidate 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.202937.1573145385000.6558.1574717100412%40Atlassian.JIRA.
[JIRA] (JENKINS-60189) Open links to plugin pages on a separate tab (plugin manager)
Title: Message Title Oleg Nenashev resolved as Fixed It was released in Jenkins 2.206. Thanks Félix Queiruga Balado! Jenkins / JENKINS-60189 Open links to plugin pages on a separate tab (plugin manager) Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.206 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-60180) Prevent HTTP TRACE in Jetty
Title: Message Title Oleg Nenashev updated JENKINS-60180 Released in Jenkins 2.205 Jenkins / JENKINS-60180 Prevent HTTP TRACE in Jetty Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.205 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
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oleg Nenashev resolved as Fixed It was released in Jenkins 2.205. It is marked as rfe there, but still looks lone a potential LTS candidate Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Oleg Nenashev Released As: Jenkins 2.205 (core fix), 1.24 (JCasC workaround) 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.198167.1552551032000.6547.1574716860677%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Issue Type: Improvement Bug 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.202313.1570043107000.6516.1574716740984%40Atlassian.JIRA.
[JIRA] (JENKINS-6722) Show agent error status on Dashboard
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-6722 Show agent error status on Dashboard Change By: Oleg Nenashev Summary: Show slave agent error status on Dashboard 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.136817.1276001051000.6528.1574716741254%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oleg Nenashev Labels: UX lts-candidate newbie-friendly ui 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.202130.1569325102000.6537.1574716800658%40Atlassian.JIRA.
[JIRA] (JENKINS-6722) Show agent error status on Dashboard
Title: Message Title Oleg Nenashev resolved as Fixed It was released in Jenkins 2.205. Thanks Ilia Zasimov! Jenkins / JENKINS-6722 Show agent error status on Dashboard Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Issue Type: Improvement Bug 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.202357.1570213644000.6508.1574716680791%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated JENKINS-59665 Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.105 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.202357.1570213644000.6504.1574716680724%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Labels: newbie-friendly user-experience 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.202313.1570043107000.6520.1574716741108%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.105 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.202313.1570043107000.6525.1574716741203%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Labels: lts-candidate newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6512.1574716680848%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Valentin Delaye created an issue Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Issue Type: Bug Assignee: Kristy Hughes Attachments: after_save.png, build_status.png, config_work.png Components: atlassian-bitbucket-server-integration-plugin Created: 2019-11-25 20:50 Environment: jenkins:2.190.1 atlassian-bitbucket-server-integration:1.0.3 bitbucket-server:5.12 Priority: Major Reporter: Valentin Delaye Hi! We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~). It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work. To reproduce Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated Save the pipeline The pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.png We don't have this problem with standard Bitbucket project
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Valentin Delaye updated an issue Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Valentin Delaye Hi!We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~).It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work.To reproduce- Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated- Save the pipelineThe pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.pngWe don't have this problem with standard Bitbucket project .Thanks.Valentin 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
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Tim Jacomb updated JENKINS-56553 Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Tim Jacomb 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.198167.1552551032000.6492.1574714100688%40Atlassian.JIRA.
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Tim Jacomb closed an issue as Fixed Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198167.1552551032000.6493.1574714100729%40Atlassian.JIRA.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title John Beckerle commented on JENKINS-28043 Re: Reload configs of all jobs in folder Issue still present: core version 2.190.2 Folder plugin: org.jenkins-ci.plugins:cloudbees-folder:6.9 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.162242.1429721391000.6478.1574713800391%40Atlassian.JIRA.
[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user
Title: Message Title William Brode commented on JENKINS-59448 Re: Distinct jenkins userids for same AD user Félix Belzunce Arcos any luck on this one? I think this issue causes the Matrix Authorization plugin not to work as intended. If I add permissions for a specific user "domainName\userName" - but the user then logs in using "userName@domainName" they won't have the permissions I gave them. I think if we fix this issue then hopefully both logins would use the same user that I gave permissions to. 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.202033.1568905412000.6476.1574713140263%40Atlassian.JIRA.
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title
ovi craciun updated an issue
Jenkins / JENKINS-60258
NullPointerException using EC2-plugin version 1.46.1
Change By:
ovi craciun
Jenkins log shows this error when it is trying to provision a windows jenkins slave:{code:java}SlaveTemplate{ami='ami-0782a9361d328f5fb', labels='windows'}. Attempting to provision slave needed by excess workload of 1 unitsNov 24, 2019 1:10:00 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@462f29b7 failedjava.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:482) at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:552) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:570) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615) at hudson.plugins.ec2.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:47) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:821) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}I tried changing various configuration settings but did not manage to get around this error.Any clues what can I do?thank you *Later edit:*After restarting jenkins now, in the logs I can see this error which seems very much related:{code:java}Started EC2 alive slaves monitorNov 25, 2019 7:55:16 PM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionA thread (EC2 alive slaves monitor thread/202) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2SpotSlave.isSpotRequestDead(EC2SpotSlave.java:144) at hudson.plugins.ec2.EC2SpotSlave.isAlive(EC2SpotSlave.java:60) at hudson.plugins.ec2.EC2SlaveMonitor.removeDeadNodes(EC2SlaveMonitor.java:49) at hudson.plugins.ec2.EC2SlaveMonitor.execute(EC2SlaveMonitor.java:40) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Unknown Source){code}
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Jesse Glick commented on JENKINS-41604 Re: Unique exception for input step abort exposing the causes as JSON to avoid having to whitelist all causes as well That is also in line with what I proposed as an api step. 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.178423.148589741.6462.1574711880380%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum updated JENKINS-41604 Jenkins / JENKINS-41604 Unique exception for input step abort Change By: Devin Nusbaum Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178423.148589741.6450.1574710743450%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum stopped work on JENKINS-41604 Change By: Devin Nusbaum 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.178423.148589741.6460.1574710744148%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum commented on JENKINS-41604 Re: Unique exception for input step abort Given JENKINS-41272 went with the approach of exposing the causes as JSON to avoid having to whitelist all causes as well, I think it would make sense to take the same approach here. If anyone still wants to work on it, I would file a new PR to add new methods to FlowInterruptedException similar to the approach in https://github.com/jenkinsci/workflow-support-plugin/pull/78. 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.178423.148589741.6440.1574710743269%40Atlassian.JIRA.
[JIRA] (JENKINS-49202) ChangeLogSet.Entry does not expose getComment to get entire commit message
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49202 ChangeLogSet.Entry does not expose getComment to get entire commit message Change By: Jesse Glick Labels: newbie-friendly 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.188039.1516983734000.6427.1574709420424%40Atlassian.JIRA.
[JIRA] (JENKINS-60273) Build Now link on the Edit or Console Output page
Title: Message Title Rares Vernica created an issue Jenkins / JENKINS-60273 Build Now link on the Edit or Console Output page Issue Type: Improvement Assignee: Unassigned Components: _unsorted Created: 2019-11-25 19:14 Priority: Minor Reporter: Rares Vernica During the job creation process, I spend a lot of time tweaking the Build > Execute shell steps. I make small edits and then I run the job to see if it worked. I end up needing three tabs open: Edit job Trigger Build Now Console output It would be nice to have a Build Now link on the job edit page or on the console output page. This way I can get away with two tabs. Add Comment
[JIRA] (JENKINS-60272) Stuck on Installing Plugins/Upgrades
Title: Message Title Rares Vernica created an issue Jenkins / JENKINS-60272 Stuck on Installing Plugins/Upgrades Issue Type: Bug Assignee: Unassigned Components: update-sites-manager-plugin Created: 2019-11-25 18:37 Priority: Minor Reporter: Rares Vernica See bellow for what I did. It has been like this for more that 10 minutes. Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success LDAP Downloaded Successfully. Will be activated during the next boot Pipeline: Stage Tags Metadata Downloaded Successfully. Will be activated during the next boot
[JIRA] (JENKINS-59350) Remove mission-control-view tests from ATH
Title: Message Title Andrey Shevtsov assigned an issue to Andrey Shevtsov Jenkins / JENKINS-59350 Remove mission-control-view tests from ATH Change By: Andrey Shevtsov Assignee: Andrey Shevtsov 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.201901.1568377932000.6422.1574706660288%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title James Bateman edited a comment on JENKINS-60213 Re: P4 environment variables non-reentrant Looks like your copy-and-paste went wrong, all the example in your last [ message |https://issues are exactly the same (basically there is no way that each job can use the same bash script – i . jenkins-ci e . org * / browse tmp / JENKINS-60213?focusedCommentId=380489=com jenkins6285754148517933441 . atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380489] are exactly the same sh*) 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.203186.1574180065000.6419.1574705880128%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title James Bateman commented on JENKINS-60213 Re: P4 environment variables non-reentrant Looks like your copy-and-paste went wrong, all the example in your last message are exactly the same 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.203186.1574180065000.6417.1574705580239%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Adam Smith closed an issue as Not A Defect Jenkins / JENKINS-60251 multibranch streams don't allow lightweight checkout? Change By: Adam Smith Status: Open Closed Resolution: Not A Defect 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.203241.1574477155000.6415.1574705345104%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Adam Smith commented on JENKINS-60251 Re: multibranch streams don't allow lightweight checkout? Good morning Karl, I apologize for taking your time on this. I discovered my own misconfiguration late this same night and planned to update the ticket this morning. You beat me to the punch! Under the "Advanced" dropdown, I selected "Preview Only" as the populate option which produced my desired behavior. I'll close this now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6413.1574705345068%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title
Karl Wirth edited a comment on JENKINS-60213
Re: P4 environment variables non-reentrant
After discussing with the developers I tried the nightly with a different variable fix but same behavior: {code:java}#30[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0==#31[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0==#32[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0=={code}
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-59698) file crippled during deploy
Title: Message Title Nitin Biradar commented on JENKINS-59698 Re: file crippled during deploy The changes from this PR (mostly pulled from Azure App Service Plugin) has helped fix the issue - https://github.com/jenkinsci/azure-function-plugin/pull/17 . Jie Shen - Could you please look at 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.202398.1570524247000.6409.1574704260497%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth commented on JENKINS-60213 Re: P4 environment variables non-reentrant After discussing with the developers I tried the nightly with a different variable fix but same behavior: 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.203186.1574180065000.6406.1574704260394%40Atlassian.JIRA.
[JIRA] (JENKINS-60241) Dynamic messages in build failure causes
Title: Message Title
Stephen Humphries commented on JENKINS-60241
Re: Dynamic messages in build failure causes
If you haven't seen it, the "${1,1}" placeholder syntax might be helpful to you: https://wiki.jenkins.io/display/JENKINS/Build+Failure+Analyzer#BuildFailureAnalyzer-Placeholdersindescription .
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.203223.1574339787000.6404.1574704200185%40Atlassian.JIRA.
[JIRA] (JENKINS-58034) Pipeline job is being shown on two executors (master and node) while inside p4step
Title: Message Title Karl Wirth commented on JENKINS-58034 Re: Pipeline job is being shown on two executors (master and node) while inside p4step I hit a brick wall with this one. Cannot see any activity on the Perforce side and unable to find a generic tracing that tells me what a node (slave or master) is up to. 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.200053.1560720825000.6400.1574704140128%40Atlassian.JIRA.
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title William Brode commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Good point on needing to resolve. I hadn't considered how that makes things more complicated. But as you mentioned the best way to handle it is probably to just take the shelved content (as opposed to trying to do some safe resolve or something). I suppose another option would be to fail? Return an error saying a resolve is required so the person can resolve it locally and change the files in the review. That may actually be better - since they will have to resolve before submitting 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.203193.1574213884000.6396.1574703780316%40Atlassian.JIRA.
[JIRA] (JENKINS-60271) Allow selection of field(s) for Issue selector display
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-60271 Allow selection of field(s) for Issue selector display Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 2019-11-25 17:30 Priority: Minor Reporter: Mark Bidewell Sometimes it would be useful to use a different Jira issue field or fields and the title in the issue selector dropdown. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title Paul Allen commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Hi Guys, just back from vacation so may need a bit of time to get up speed on this issue... Using 'head' (the latest change on that branch) might be an alternative, but there could be side effects if the 'head' is newer than the shelf/review. The P4 plugin may need to perform a resolve step (forcing the accept of the shelve's content) - I seem to remember writing something like this, but can't remember if it was released or in a dev branch. I'll take a look and refresh myself on the Swarm review part of the code. 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.203193.1574213884000.6377.1574701020205%40Atlassian.JIRA.
[JIRA] (JENKINS-43403) Pipeline withEnv changes not observable in email-ext groovy template
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-43403 Pipeline withEnv changes not observable in email-ext groovy template Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180646.1491512064000.6360.1574700842040%40Atlassian.JIRA.
[JIRA] (JENKINS-46819) combine plain text and html options into one
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-46819 combine plain text and html options into one Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185172.1505229128000.6348.1574700780660%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman updated JENKINS-60115 Jenkins / JENKINS-60115 NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Change By: Liam Newman 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.202962.1573259182000.6341.1574699340773%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman commented on JENKINS-60115 Re: NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Fixed by https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/363 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.202962.1573259182000.6343.1574699340821%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probalby ignored
Title: Message Title Uwe Brackenhoff created an issue Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probalby ignored Issue Type: Bug Assignee: Ulli Hafner Attachments: active.txt, Untitled.png, Untitled2.png Components: warnings-ng-plugin Created: 2019-11-25 16:08 Environment: Jenkins ver. 2.190.3; list of plugins attached; java.vendor AdoptOpenJDK; java.runtime.version 11.0.5+10; sun.management.compiler HotSpot 64-Bit Tiered Compilers; OS Win7x64pro Priority: Minor Reporter: Uwe Brackenhoff Hallo, The documentation of the attribute 'name' shows: name (optional) You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used. But as you can see within the attached Untitled.png, this is not working. The Jenkins script used is: recordIssues( id: 'Build_Binary', name: 'Build Binary', sourceCodeEncoding: 'UTF-8', enabledForFailure: true, aggregatingResults: true, tools: [ groovyScript( id: 'Build_Binary_SubProj1', name: 'Build Binary SubProj1', parserId: 'myParser', pattern:'Outputs SubProj1Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj2', name: 'Build Binary SubProj2', parserId: 'myParser', pattern:'Outputs SubProj2Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj3', name: 'Build Binary SubProj3', parserId: 'myParser', pattern:'Outputs SubProj3Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj4', name:
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia commented on JENKINS-59752 Re: Add support for ephemeral OS disk Jie Shen I saw you approved/merged my PR into dev ... Is there a release process/schedule? Anything I need to do to this ticket to get it into the next 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.202475.1570808392000.6325.1574694540272%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia updated JENKINS-59752 Jenkins / JENKINS-59752 Add support for ephemeral OS disk Change By: Bradley Wangia Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6321.1574694363221%40Atlassian.JIRA.
