[JIRA] (JENKINS-61902) "authenticated" group doesn't work with Authorize Project plugin
Title: Message Title ikedam assigned an issue to akostadinov Groups that a user is assigned depends on the security realm you use. I suppose the security realm you use doesn't assign "authenticated" group to the user when authorize-project queries the user. I could not reproduce the issue with built-in "Jenkins’ own user database" as it always assigns "authenticated" group to the user. I don't think it's a bug of the security realm as the query by the authorize-project plugin is independent from user's login process. The security realm can't say to authorized-project plugin whether the user is authenticated. I suppose "authenticated" group is always assigned for Web UI operations as Jenkins knows the user is actually authenticated. I won't fix this issue as managing actual permissions is out of the domain of authorize-project and managing permissions carelessly can easily cause security issues. Please instead create a new group for all Jenkins users and assign the role to that group. Jenkins / JENKINS-61902 "authenticated" group doesn't work with Authorize Project plugin Change By: ikedam Assignee: ikedam akostadinov Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61902) "authenticated" group doesn't work with Authorize Project plugin
Title: Message Title ikedam updated an issue Jenkins / JENKINS-61902 "authenticated" group doesn't work with Authorize Project plugin Change By: ikedam Summary: Slave roles not respected "authenticated" group doesn't work with Authorize Project plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.13742.1587268560372%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title ikedam updated JENKINS-33476 This looks rather an issue of promoted-build plugin. The permalink created by promoted-build points not the build that is promoted latest, but the latest build that is promoted. Create a new job with "Promote builds when..." Run the job twice. It generates build#1, build#2. Promote #2. Go to the job page, and check the permalink. It points #2. Promote #1. Go to the job page, and check the permalink. It still points #2. I'm not sure this is a problematic behavior. It looks a designated behavior of promoted-build to me. Anyway, this ticket is really old, and please create another ticket if you think this is a bug of promoted-build. Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: ikedam Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title ikedam updated JENKINS-61276 Jenkins / JENKINS-61276 Unittest fails for accessing http://repo1.maven.org/ Change By: ikedam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204851.1582946177000.2150.1583565780203%40Atlassian.JIRA.
[JIRA] (JENKINS-33003) Copy Artifacts from Another Projects Strange Behavior
Title: Message Title ikedam updated JENKINS-33003 Copyartifact requires upstream am project name explicitly as: For its design. Copyartifact decides the job to copy from, and then search builds. The build selection comes later and cannot affect job decision phase. There can be multiple upstream jobs. A case that there’s a grand parent build, or the job is triggered from multiple upstreams and merged into one build. Jenkins / JENKINS-33003 Copy Artifacts from Another Projects Strange Behavior Change By: ikedam Status: Open Fixed but Unreleased Assignee: Esteban Vargas Resolution: Won't Fix Add Comment This
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title ikedam stopped work on JENKINS-33476 Change By: ikedam Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168891.1457697475000.2142.1583564880703%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title ikedam updated JENKINS-33476 Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: ikedam Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168891.1457697475000.2137.1583564880563%40Atlassian.JIRA.
[JIRA] (JENKINS-44019) Copy empty folders
Title: Message Title ikedam updated an issue Jenkins / JENKINS-44019 Copy empty folders Sounds an issue for archiveArtifacts, a feature of Jenkins core. Updated component/s. I rather recommend you to pack files with `tar` (for example) before archive them. Change By: ikedam Component/s: core Component/s: copyartifact-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title ikedam updated JENKINS-39174 This was fixed in copyartifact-1.42.1. Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Change By: ikedam Status: Open Fixed but Unreleased Assignee: James Femia Resolution: Fixed Released As: copyartifact-1.42.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title ikedam updated JENKINS-39174 Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Change By: ikedam Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175597.1477058513000.2126.1583564221051%40Atlassian.JIRA.
[JIRA] (JENKINS-61283) Tests fail for certificate expiration
Title: Message Title ikedam started work on JENKINS-61283 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204858.1583035825000.1916.1583036820314%40Atlassian.JIRA.
[JIRA] (JENKINS-61283) Tests fail for certificate expiration
Title: Message Title ikedam commented on JENKINS-61283 Re: Tests fail for certificate expiration https://github.com/jenkinsci/update-sites-manager-plugin/pull/17 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204858.1583035825000.1920.1583036820362%40Atlassian.JIRA.
[JIRA] (JENKINS-61283) Tests fail for certificate expiration
Title: Message Title ikedam updated JENKINS-61283 Jenkins / JENKINS-61283 Tests fail for certificate expiration Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204858.1583035825000.1918.1583036820341%40Atlassian.JIRA.
[JIRA] (JENKINS-60272) Stuck on Installing Plugins/Upgrades
Title: Message Title ikedam updated an issue Jenkins / JENKINS-60272 Stuck on Installing Plugins/Upgrades Change By: ikedam Component/s: core Component/s: update-sites-manager-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203262.1574707046000.1914.1583035980221%40Atlassian.JIRA.
[JIRA] (JENKINS-61283) Tests fail for certificate expiration
Title: Message Title ikedam created an issue Jenkins / JENKINS-61283 Tests fail for certificate expiration Issue Type: Task Assignee: ikedam Components: update-sites-manager-plugin Created: 2020-03-01 04:10 Priority: Minor Reporter: ikedam shouldSuccessfullyUpdateWithWorkingUC – jp.ikedam.jenkins.plugins.updatesitesmanager.ManagedUpdateSiteJenkinsTest2s shouldAddCustomCertToTrustAnchors – jp.ikedam.jenkins.plugins.updatesitesmanager.internal.ExtendedCertJsonSignValidatorTest<1s Should be redirect Expected: an instance of org.kohsuke.stapler.HttpResponses$5 but: for test '#' class='showDetails'>(show details)'display:none'>java.security.cert.CertPathValidatorException: validity check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:223) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:76) at hudson.model.UpdateSite.verifySignature(UpdateSite.java:219) at hudson.model.UpdateSite.updateData(UpdateSite.java:198) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:170) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:890) at jp.ikedam.jenkins.plugins.updatesitesmanager.ManagedUpdateSiteJenkinsTest.shouldSuccessfullyUpdateWithWorkingUC(ManagedUpdateSiteJenkinsTest.java:127) at
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title ikedam updated JENKINS-61276 Jenkins / JENKINS-61276 Unittest fails for accessing http://repo1.maven.org/ Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204851.1582946177000.1574.1582951860343%40Atlassian.JIRA.
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title ikedam commented on JENKINS-61276 Re: Unittest fails for accessing http://repo1.maven.org/ https://github.com/jenkinsci/copyartifact-plugin/pull/117 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204851.1582946177000.1576.1582951860371%40Atlassian.JIRA.
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-61276
Unittest fails for accessing http://repo1.maven.org/
Change By:
ikedam
{code :java }[INFO] [INFO] Building moduleA[INFO]task-segment: [clean, package][INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pomDownloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom[INFO] [ERROR] BUILD ERROR[INFO] [INFO] Error building POM (may not be this project's POM).{code} failed tests: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fcopyartifact-plugin/detail/PR-116/1/tests/ * linux-8 / Build (linux-8) / testMavenJobWithArchivePostBuildStep – hudson.plugins.copyartifact.CopyArtifactTest9s* linux-8 / Build (linux-8) / testEnvDataInMavenProject – hudson.plugins.copyartifact.CopyArtifactTest8s* linux-8 / Build (linux-8) / testMavenAll – hudson.plugins.copyartifact.CopyArtifactTest5s* linux-8 / Build (linux-8) / testMavenJob – hudson.plugins.copyartifact.CopyArtifactTest5s* linux-8 / Build (linux-8) / testPermissionWhenParameterizedForMavenModule –* hudson.plugins.copyartifact.CopyArtifactTest5slinux-8 / Build (linux-8) / testMavenModule –* hudson.plugins.copyartifact.TriggeredBuildSelectorTest
Add Comment
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title ikedam started work on JENKINS-61276 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204851.1582946177000.1567.1582949700229%40Atlassian.JIRA.
[JIRA] (JENKINS-61276) Unittest fails for accessing http://repo1.maven.org/
Title: Message Title ikedam created an issue Jenkins / JENKINS-61276 Unittest fails for accessing http://repo1.maven.org/ Issue Type: Task Assignee: ikedam Components: copyartifact-plugin Created: 2020-02-29 03:16 Priority: Minor Reporter: ikedam [INFO] [INFO] Building moduleA [INFO]task-segment: [clean, package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). failed tests:
[JIRA] (JENKINS-61265) Job with Extensible Groovy script does NOT get latest value when triggered by another job
Title: Message Title ikedam updated JENKINS-61265 Chris Fouts Because the extensible-choice runs when a build is scheduled, not when starts. It has nothing to do with the `wait` parameter. Here is an issue tracker, not your support center nor stackoverflow. Please don't reopen closed ticket without any concrete evidences, like log outputs. I believe you can verify what happen easily with removing the `if` statement. Jenkins / JENKINS-61265 Job with Extensible Groovy script does NOT get latest value when triggered by another job Change By: ikedam Status: Reopened Fixed but Unreleased Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61265) Job with Extensible Groovy script does NOT get latest value when triggered by another job
Title: Message Title ikedam assigned an issue to Chris Fouts I failed to change the assignee. Please see the previous comment. Jenkins / JENKINS-61265 Job with Extensible Groovy script does NOT get latest value when triggered by another job Change By: ikedam Assignee: ikedam Chris Fouts Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204836.1582850363000.1100.1582854120155%40Atlassian.JIRA.
[JIRA] (JENKINS-61265) Job with Extensible Groovy script does NOT get latest value when triggered by another job
Title: Message Title ikedam updated JENKINS-61265 Because the build of Job1 is still running at that time. I believe getBuildStatusSummary() returns “?” https://github.com/jenkinsci/jenkins/blob/jenkins-2.164.3/core/src/main/java/hudson/model/Run.java#L2151 https://github.com/jenkinsci/jenkins/blob/jenkins-2.164.3/core/src/main/resources/hudson/model/Messages.properties#L246 And I recommend you not to use getBuildStatusSummary() as its output may be localized and changes for languages. I could not get what you wanted to do with passing StringParameterValue. I believe it does nothing. Jenkins / JENKINS-61265 Job with Extensible Groovy script does NOT get latest value when triggered by another job Change By: ikedam Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-60221) Copy artifact on agent sometimes hangs while copying
Title: Message Title ikedam commented on JENKINS-60221 Re: Copy artifact on agent sometimes hangs while copying And I believe you'd better to use Jenkins LTS versions (2.190.3 for now), as non-LTS versions are often unstable. I want to know if the issue occurs even with LTS versions. 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.203194.1574232943000.2386.1575700320125%40Atlassian.JIRA.
[JIRA] (JENKINS-60221) Copy artifact on agent sometimes hangs while copying
Title: Message Title ikedam commented on JENKINS-60221 Re: Copy artifact on agent sometimes hangs while copying Hmm... no one is assigned... Stefan Drissen > during copying build artifacts an agent went offline, upon being brought online again, the job is still hanging on the copy build artifact job This sounds really important to me as reproducing instructions make it easy to resolve the issue. I tried same operations but cannot reproduce the issue. Let me know followings as it might help resolving the issue (actually, I don't know much about the remoting library, but it would help someone who know much about remoting): How do you launch agent with scheduled tasks? By executing java -jar agent.jar -jnlpUrl ... ? Why did the agent go offline? Accidentally (e.g. the windows machine crashed), or by operation of an administrator? How often is the issue reproduced if you make the agent offline during builds? Does it hang if you make the agent offline before CopyArtifact starts? Does it hang if you make the agent offline after CopyArtifact finished? (I suppose it won't) 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-60221) Copy artifact on agent sometimes hangs while copying
Title: Message Title ikedam assigned an issue to Unassigned From the stacktrace, it looks an issue of hudson.remoting, and I changed the component of the ticket and expect someone in chage of remoting will be assigned. Jenkins / JENKINS-60221 Copy artifact on agent sometimes hangs while copying Change By: ikedam Component/s: remoting Component/s: copyartifact-plugin Assignee: Stefan Drissen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60221) Copy artifact on agent sometimes hangs while copying
Title: Message Title ikedam assigned an issue to Stefan Drissen Stefan Drissen Could you attach the thread dump of the master node? It might sound strange, but who actually controls job executions is the master node. Jenkins / JENKINS-60221 Copy artifact on agent sometimes hangs while copying Change By: ikedam Assignee: ikedam Stefan Drissen 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.203194.1574232943000.4383.1574251440329%40Atlassian.JIRA.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam updated JENKINS-41729 Jenkins / JENKINS-41729 Using utf-8 letters in property files Change By: ikedam 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.178566.1486267011000.2494.1572154080219%40Atlassian.JIRA.
[JIRA] (JENKINS-59949) Fix build error of update-sites-manager for javadoc issue
Title: Message Title ikedam commented on JENKINS-59949 Re: Fix build error of update-sites-manager for javadoc issue https://github.com/jenkinsci/update-sites-manager-plugin/pull/17 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.202753.1572147816000.2492.1572152820130%40Atlassian.JIRA.
[JIRA] (JENKINS-59949) Fix build error of update-sites-manager for javadoc issue
Title: Message Title ikedam started work on JENKINS-59949 Change By: ikedam 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.202753.1572147816000.2490.1572152700399%40Atlassian.JIRA.
[JIRA] (JENKINS-59949) Fix build error of update-sites-manager for javadoc issue
Title: Message Title ikedam created an issue Jenkins / JENKINS-59949 Fix build error of update-sites-manager for javadoc issue Issue Type: Bug Assignee: ikedam Components: update-sites-manager-plugin Created: 2019-10-27 03:43 Priority: Minor Reporter: ikedam Build fails with java8: [2019-10-09T08:28:12.465Z] [ERROR] /mnt/agent-workspace/workspace/date-sites-manager-plugin_master/src/main/java/jp/ikedam/jenkins/plugins/updatesitesmanager/UpdateSitesManager.java:148: error: invalid use of @return [2019-10-09T08:28:12.465Z] [ERROR] * @return redirect to same url if all ok [2019-10-09T08:28:12.465Z] [ERROR]^ Add Comment
[JIRA] (JENKINS-51317) Update center: block upgrade with comment
Title: Message Title ikedam updated an issue Jenkins / JENKINS-51317 Update center: block upgrade with comment Change By: ikedam Component/s: core Component/s: update-sites-manager-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.190654.1526364902000.2486.1572147660734%40Atlassian.JIRA.
[JIRA] (JENKINS-53826) do not get update for jenkins and plugins
Title: Message Title ikedam updated JENKINS-53826 This is not an issue of update-sites-manager. Anyway, it's already fixed in JENKINS-53710, and please try the latest core. Jenkins / JENKINS-53826 do not get update for jenkins and plugins Change By: ikedam Status: Open Fixed but Unreleased Assignee: Sergey Solozhentsev Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53826) do not get update for jenkins and plugins
Title: Message Title ikedam updated an issue Jenkins / JENKINS-53826 do not get update for jenkins and plugins Change By: ikedam Component/s: core Component/s: update-sites-manager-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.194341.153811366.2479.1572147600182%40Atlassian.JIRA.
[JIRA] (JENKINS-55680) Update site does not change where to download plugins
Title: Message Title ikedam updated an issue Jenkins / JENKINS-55680 Update site does not change where to download plugins Change By: ikedam Component/s: core Component/s: update-sites-manager-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.196866.1547816828000.2476.1572147540155%40Atlassian.JIRA.
[JIRA] (JENKINS-56498) IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title ikedam updated JENKINS-56498 Here is an issue tracker, not a support center. It looks a configuration issue for your proxy, so please consult your proxy administrator. Jenkins / JENKINS-56498 IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" Change By: ikedam Status: Open Fixed but Unreleased Assignee: Azra Begzadic Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56498) IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title ikedam updated JENKINS-56498 Jenkins / JENKINS-56498 IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" Change By: ikedam Status: Fixed but Unreleased 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.198105.1552297336000.2473.1572147420680%40Atlassian.JIRA.
[JIRA] (JENKINS-56498) IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title ikedam updated an issue Jenkins / JENKINS-56498 IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" Change By: ikedam Component/s: core Component/s: update-sites-manager-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.198105.1552297336000.2468.1572147240258%40Atlassian.JIRA.
[JIRA] (JENKINS-59441) Jenkins can't reach update json despite browser load it correctly
Title: Message Title ikedam updated an issue Jenkins / JENKINS-59441 Jenkins can't reach update json despite browser load it correctly Change By: ikedam Component/s: core Component/s: update-sites-manager-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.202026.1568879688000.2466.1572147180236%40Atlassian.JIRA.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam commented on JENKINS-41729 Re: Using utf-8 letters in property files https://github.com/kohsuke/localizer/pull/20 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.178566.1486267011000.2421.1569144660196%40Atlassian.JIRA.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam commented on JENKINS-41729 Re: Using utf-8 letters in property files https://github.com/stapler/stapler/pull/171 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.178566.1486267011000.2419.1569140940299%40Atlassian.JIRA.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam started work on JENKINS-41729 Change By: ikedam 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.178566.1486267011000.2414.1569140700247%40Atlassian.JIRA.
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam updated JENKINS-59472 Jenkins / JENKINS-59472 Instructions to use Apache HttpComponents Client 4.x API Plugin Change By: ikedam 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.202076.1569136483000.2412.1569137940169%40Atlassian.JIRA.
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam started work on JENKINS-59472 Change By: ikedam 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.202076.1569136483000.2408.1569137880210%40Atlassian.JIRA.
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam commented on JENKINS-59472 Re: Instructions to use Apache HttpComponents Client 4.x API Plugin https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/pull/22 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.202076.1569136483000.2410.1569137880233%40Atlassian.JIRA.
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam updated an issue Jenkins / JENKINS-59472 Instructions to use Apache HttpComponents Client 4.x API Plugin Change By: ikedam Libraries packaged into hpi files are decided with the "nearest definition" rule of maven.httpclient would be packaged into hpi files even though the plugin depends on apache-httpcomponent-client-4-api if the dependency declaration was inappropriate. Developers have to know some rules to migrate to apache-httpcomponents-client-4-api-plugin:* For plugins directly depending on org.apache.httpcomponents:httpclient:** Replace the dependency to org.apache.httpcomponents:httpclient with the dependency to org.jenkins-ci.plugins:apache-httpcomponents-client-4-api* For plugins depending on libraries depending on org.apache.httpcomponents:httpclient:** Insert the dependency to org.apache.httpcomponents:httpclient BEFORE the dependency to the libraries. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam updated an issue Jenkins / JENKINS-59472 Instructions to use Apache HttpComponents Client 4.x API Plugin Change By: ikedam Libraries packaged into hpi files are decided with the "nearest definition" rule of maven. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html httpclient would be packaged into hpi files even though the plugin depends on apache-httpcomponent-client-4-api if the dependency declaration was inappropriate.Developers have to know some rules to migrate to apache-httpcomponents-client-4-api-plugin:* For plugins directly depending on org.apache.httpcomponents:httpclient:** Replace the dependency to org.apache.httpcomponents:httpclient with the dependency to org.jenkins-ci.plugins:apache-httpcomponents-client-4-api* For plugins depending on libraries depending on org.apache.httpcomponents:httpclient:** Insert the dependency to org.apache.httpcomponents:httpclient BEFORE the dependency to the libraries. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59472) Instructions to use Apache HttpComponents Client 4.x API Plugin
Title: Message Title ikedam created an issue Jenkins / JENKINS-59472 Instructions to use Apache HttpComponents Client 4.x API Plugin Issue Type: Improvement Assignee: ikedam Components: apache-httpcomponents-client-4-api-plugin Created: 2019-09-22 07:14 Priority: Minor Reporter: ikedam Developers have to know some rules to migrate to apache-httpcomponents-client-4-api-plugin: For plugins directly depending on org.apache.httpcomponents:httpclient: Replace the dependency to org.apache.httpcomponents:httpclient with the dependency to org.jenkins-ci.plugins:apache-httpcomponents-client-4-api For plugins depending on libraries depending on org.apache.httpcomponents:httpclient: Insert the dependency to org.apache.httpcomponents:httpclient BEFORE the dependency to the libraries.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam commented on JENKINS-41729 Re: Using utf-8 letters in property files I found existing property files are not encoded in ASCII, but ISO-8859-1. See more details in https://github.com/stapler/stapler/pull/105. ISO-8859-1 and UTF-8 are not compatible, and it looks difficult to detect decoding errors in Java. It would be better to consider using XML property files: https://docs.oracle.com/javase/8/docs/api/java/util/Properties.html#loadFromXML-java.io.InputStream- 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.178566.1486267011000.3773.1568528400144%40Atlassian.JIRA.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam stopped work on JENKINS-41729 Change By: ikedam 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.178566.1486267011000.3771.1568528280259%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title ikedam assigned an issue to Wadeck Follonier Wadeck Follonier Would you have a look on this issue? (I mention you as you look the author of the fix for SECURITY-901) I want your comment about this: > This might be a bug of Jenkins core as setting session seed of user B to user A doesn't look appropriate behavior. Jenkins / JENKINS-59107 User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) Change By: ikedam Component/s: core Assignee: Wadeck Follonier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title ikedam commented on JENKINS-59107 Re: User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) Actually, I don't have any idea for this. The change causing this issue is SECURITY-901 https://jenkins.io/security/advisory/2019-01-16/#SECURITY-901 https://github.com/jenkinsci/jenkins/commit/8c490d14c4ffe6162f6e97d25a66612330fe2ace When authenticated as user B, the session seed for user B is set by UserSeedSecurityListener. This invalidates session for user A. Users can disable this behavior with "-Djenkins.security.seed.UserSeedProperty.disableUserSeed=true" This might be a bug of Jenkins core as setting session seed of user B to user A doesn't look appropriate behavior. On the other hand, Jenkins core doesn't expect "authenticate" is used by other users. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201530.1566934526000.3895.1567300680116%40Atlassian.JIRA.
[JIRA] (JENKINS-56774) Support Configuration as Code
Title: Message Title ikedam commented on JENKINS-56774 Re: Support Configuration as Code Authorize-project and especially SpecificUserAuthorizationStrategy expects configuration via UI to check the configurator has appropriate permissions. That issue can be fixed by updating constructor parameters, but I’m afraid it might cause a path bypassing permission checks. I’m not so sure, and also I don’t know much about JCaC, but I suppose this extension costs much not for the extension itself, but for checking whether the extension don’t affect existing security mechanisms. I’ve just posted a topic on jenkinsci-dev, and please also have a look on that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198418.1553680552000.490.1566894660359%40Atlassian.JIRA.
[JIRA] (JENKINS-54433) do we have view based permission partitioning strategy for jenkins？
Title: Message Title ikedam updated JENKINS-54433 I agree to René Scheibe . Views work just like “favorites” and are not appropriate to handle authentications. Please watch JENKINS-50559 if you’re talking about folders, not about views. Jenkins / JENKINS-54433 do we have view based permission partitioning strategy for jenkins？ Change By: ikedam Status: Open Fixed but Unreleased Assignee: chaorong guo Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm with specific authorize project settings
Title: Message Title ikedam updated JENKINS-38126 I tested the behavior of the combination of git-plugin, credentials-plugin and authorize-project-plugin and I believe this issue is caused for following three issues: There're three underlying issues causing this issue: Why this happens only for "Run as specific user" , not for other strategies like "Run as User who Triggered"?: Because credentials in configuration pages are not for the user of builds, but for the user of the job. Jenkins can say that the user of the job is "user1" when you are using "Run as specific user" with "user1" though Jenkins cannot decide the user of the job when you are using "Run as User who Triggered" as the user can be decided only after a build is actually triggered by someone. So "Run as User who Triggered" results configuration pages behave just as when no authorization strategy is set. And this issue is specific to "Run as specific user". What is credentials for specific users? You can configure user-scoped credentials in the user page, which can open from the link over the user name in the right-up part of Jenkins web UI. I suppose many users configures only system-scoped credentials and this results "no credentials are shown". Why system global credentials are not displayed in the job configuration pages even when the user has Credentials/View permissions? It might be a bug of credentials plugin (I'm not so sure as I don't know much about the design of credentials-plugin). I created JENKINS-58902 and please watch that ticket. The first and second ones can be resolved as "Not A Defect", as they are designated behavior. For the third one, I created JENKINS-58902. I believe this issue (JENKINS-38126) can be resolved as Duplicate, and please watch that ticket instead. Those causes are really complicated and I'm afraid they are beyond my English and difficult to read. I expect someone improve the explanation. And this ticket lasted for so long time and I might fail to get exactly what happened. Please add a comment or reopen the ticket if you have something that looks not resolved. Jenkins / JENKINS-38126 Credentials dropdown empty on git scm with specific authorize project settings
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title ikedam updated JENKINS-55624 There're three underlying issues causing this issue: Why this happens only for "Run as specific user" , not for other strategies like "Run as User who Triggered"?: Because credentials in configuration pages are not for the user of builds, but for the user of the job. Jenkins can say that the user of the job is "user1" when you are using "Run as specific user" with "user1" though Jenkins cannot decide the user of the job when you are using "Run as User who Triggered" as the user can be decided only after a build is actually triggered by someone. So "Run as User who Triggered" results configuration pages behave just as when no authorization strategy is set. And this issue is specific to "Run as specific user". What is credentials for specific users? You can configure user-scoped credentials in the user page, which can open from the link over the user name in the right-up part of Jenkins web UI. Why system global credentials are not displayed in the job configuration pages even when the user has Credentials/View permissions? It might be a bug of credentials plugin (I'm not so sure as I don't know much about the design of credentials-plugin). I created JENKINS-58902 and please watch that ticket. Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: ikedam Status: Open Fixed but Unreleased Assignee: Mike Nicholson Resolution: Duplicate
[JIRA] (JENKINS-58902) Non-user-scoped credentials are not shown when build authentication is configured
Title: Message Title ikedam created an issue Jenkins / JENKINS-58902 Non-user-scoped credentials are not shown when build authentication is configured Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2019-08-13 04:08 Environment: Credentials Plugin 2.2.1 Tested with: Jenkins 2.176.2 Authorize Project 1.3.0 Matrix Authorization Strategy Plugin 2.4.2 Git 3.11.0 Priority: Minor Reporter: ikedam Only user-scoped credentials are displayed in job configuration pages when the job is configured to authenticate as a specific user. But non-user-scoped credentials also should be displayed when the user has the Credentials/View permission. This behavior is inconsistent with the behavior that users with Credentials/View permissions can see non-user-scoped credentials in the credentials page. This is confusing for many users. Steps to reproduce: Launch Jenkins Install following plugins: Credentials Plugin 2.2.1 Authorize Project 1.3.0 Matrix Authorization Strategy Plugin 2.4.2 Git 3.11.0 Create following users
[JIRA] (JENKINS-58636) Tests failing with mvn package with jdk8
Title: Message Title ikedam updated an issue Jenkins / JENKINS-58636 Tests failing with mvn package with jdk8 Change By: ikedam Summary: Tests failing with mvn package with jdk8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1273.1564085880163%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title ikedam updated an issue Jenkins / JENKINS-58636 Tests failing with mvn package Change By: ikedam Issue Type: Bug Task Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200804.1563962522000.1270.1564085760303%40Atlassian.JIRA.
[JIRA] (JENKINS-58636) Tests failing with mvn package
Title: Message Title ikedam updated JENKINS-58636 See JENKINS-18537. It can be fixed with any of following ways: Target jenkins 1.557 or 1554.1 or later. Use java6. Using a docker image is the easy way to prepare an environment. Add xstream-1.4.7-jenkins-1 as test dependency. Jenkins / JENKINS-58636 Tests failing with mvn package Change By: ikedam Status: Open Fixed but Unreleased Assignee: ikedam AB S Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam assigned an issue to Adrian Vlad Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Assignee: ikedam Adrian Vlad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.6983.1561357200793%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam resolved as Fixed Fixed in groovy-postbuild-2.5. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Status: In Progress Resolved Resolution: Fixed Released As: groovy-postbuild-2.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title ikedam updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile The issue in groovy-postbuild is fixed in groovy-postbuild-2.5. (Removed groovy-postbuild from component/s) It will be available in the update center in a day. Please try that. Change By: ikedam Component/s: groovy-postbuild-plugin Released As: workflow-job 2.29 groovy-postbuild-2.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194755.1539777336000.6956.1561357080605%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam closed an issue as Fixed Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.6954.1561356421013%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated JENKINS-57917 Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam Status: In Review Resolved Resolution: Fixed Released As: groovy-postbuild-2.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.6952.1561356420966%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated JENKINS-57917 Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23964.1559971320250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated an issue Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild https://github.com/jenkinsci/groovy-postbuild-plugin/pull/42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23966.1559971320278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam started work on JENKINS-57917 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23962.1559971260233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam created an issue Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Issue Type: New Feature Assignee: ikedam Components: groovy-postbuild-plugin Created: 2019-06-08 04:30 Priority: Minor Reporter: ikedam HTML texts are escaped for addShortText or other badge-related features since groovy-postbuild-2.4. I decided NOT to revert that change as it causes security issues. addHtmlBadge is introduced since badge-plugin-1.3 and it would be useful also for groovy-postbuild and can help users used HTML texts in addShortText. Add Comment
[JIRA] (JENKINS-51370) Error on using Groovy Postbuild plugin
Title: Message Title ikedam updated JENKINS-51370 No response from the reporter. Please reopen when more detailed information is available. Jenkins / JENKINS-51370 Error on using Groovy Postbuild plugin Change By: ikedam Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190717.1526489375000.23956.1559966820459%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Assignee: Stefan Wolf ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.23943.1559965020636%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam started work on JENKINS-54262 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.23950.1559965020835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57529) Unable to identify builds run as SYSTEM user
Title: Message Title ikedam assigned an issue to Unassigned This is an issue of Jenkins core as this warning is shown by Jenkins core. Jenkins / JENKINS-57529 Unable to identify builds run as SYSTEM user Change By: ikedam Component/s: core Component/s: authorize-project-plugin Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199436.1558108275000.4696.1558140120274%40Atlassian.JIRA. For more
[JIRA] (JENKINS-52404) Job fails randomly when using copyArtifact
Title: Message Title ikedam updated JENKINS-52404 There’s no fundamental resolution for this issue as it comes from the OS level issue. And I don’t plan to add retry feature to copyartifact as it cause codes complicated and hard to maintain. Please consider workarounds like excluding scan directory, remove files in the target directory before copying, and so on. Jenkins / JENKINS-52404 Job fails randomly when using copyArtifact Change By: ikedam Status: Open Fixed but Unreleased Assignee: Marco Steffan Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52552) Cloudbees folders do not work when using parameters
Title: Message Title ikedam updated JENKINS-52552 It sounds like a permission issue. Please have a look on https://wiki.jenkins.io/pages/viewpage.action?pageId=42470728#CopyArtifactPlugin-Specifyingprojectdynamically(withvariables) Jenkins / JENKINS-52552 Cloudbees folders do not work when using parameters Change By: ikedam Status: Open Fixed but Unreleased Assignee: Martin Cassidy Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-53366) `keep forever` is no longer inherit to sub configurations
Title: Message Title ikedam assigned an issue to Kohsuke Kawaguchi It looks rather an issue of matrix-project plugin. Please update this if you know from what version of matrix-project this issue happened. Jenkins / JENKINS-53366 `keep forever` is no longer inherit to sub configurations Change By: ikedam Summary: [CopyArtifact] fails when using latestSavedBuild selector from Multi-Configuration project `keep forever` is no longer inherit to sub configurations Component/s: matrix-project-plugin Component/s: copyartifact-plugin Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57224) Plugin Failed to Initialize after Jenkins restart
Title: Message Title ikedam updated JENKINS-57224 Actually, the root cause of this issue is unknown at last. It looks related to processing of Jenkins core in boot time, and cannot be reproduce in my environment. Though, I updated the implementation looking related to this issue in copyartifact-1.39 and should be fixed. https://github.com/jenkinsci/copyartifact-plugin/commit/946f9e47059cede6a6b50934f86efca42b574e05#diff-a1fdcd3da2dbec876fd20075be0d4108 You’re using a really old version of copyartifact, and please update to the latest and see the problem is resolved. Jenkins / JENKINS-57224 Plugin Failed to Initialize after Jenkins restart Change By: ikedam Status: Open Fixed but Unreleased Assignee: siva bora Resolution: Fixed Released As: copyartifact-1.39 Add Comment
[JIRA] (JENKINS-57241) Copy Artifact copying files when shouldn't and parameter filter errors
Title: Message Title ikedam updated JENKINS-57241 Though it’s really difficult to see what’s the actual problem you’re facing as your description is really long and looks describing unrelated things, it sounds that your problem is that “Copy Artifact is run unexpectedly though you’re expecting it’s controlled with parameter values”. You looks confuse the parameter filter feature of Copy Artifact plugin and the condition defined with Conditional Buildstep plugin and Run Condition plugin. The parameter filter feature of Copy Artifact plugin filters builds to copy from, and don’t skip the step itself. From the console output, Conditional Buildstep is applied to "Send build artifacts over SSH". Please reconfigure your project and put Copy Artifact under Conditional Buildstep. If that doesn’t resolve your problem, please reopen this ticked with information to how to reproduce the problem with least steps in a new Jenkins instance. Jenkins / JENKINS-57241 Copy Artifact copying files when shouldn't and parameter filter errors Change By: ikedam Status: Open Fixed but Unreleased Assignee: Kim Abbott Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-56149) Copy artifact fails on first pipeline run with buildParameter selector
Title: Message Title ikedam updated JENKINS-56149 Pass the parameter value, not the parameter name, like: selector: buildParameter(params.UPSTREAM) Please also see the help of parameterName: https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/resources/hudson/plugins/copyartifact/ParameterizedBuildSelector/help-parameterName.html Jenkins / JENKINS-56149 Copy artifact fails on first pipeline run with buildParameter selector Change By: ikedam Status: Open Fixed but Unreleased Assignee: Ryan Desmond Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam updated JENKINS-35417 feng yu (cc: Chad Gilman) Released copyartifact-1.42. It will be available in the update center in a day. Jenkins / JENKINS-35417 Support "last exist" condition. Change By: ikedam Status: In Review Resolved Assignee: ikedam feng yu Resolution: Fixed Released As: copyartifact-1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title ikedam updated an issue Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Change By: ikedam Released As: naginator-1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam updated an issue Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Released As: naginator-1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title ikedam updated JENKINS-50751 Robert Baker Ryan Tse This is fixed in naginator-1.18. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Change By: ikedam Status: Fixed but Unreleased Resolved Assignee: ikedam Robert Baker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55316) Naginator link formatting
Title: Message Title ikedam updated JENKINS-55316 Fixed in naginator-1.18. Jenkins / JENKINS-55316 Naginator link formatting Change By: ikedam Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam updated JENKINS-43803 Fixed in naginator-1.18. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Status: Fixed but Unreleased Resolved Assignee: ikedam Spencer Yost Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam updated JENKINS-43803 Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title ikedam updated JENKINS-50751 Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Change By: ikedam Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam updated JENKINS-43803 Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam commented on JENKINS-35417 Re: Support "last exist" condition. https://github.com/jenkinsci/copyartifact-plugin/pull/109#issuecomment-461343143 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam updated JENKINS-35417 Jenkins / JENKINS-35417 Support "last exist" condition. Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam edited a comment on JENKINS-35417 Re: Support "last exist" condition. https://github.com/jenkinsci/copyartifact-plugin/pull/109 #issuecomment-461343143 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam started work on JENKINS-35417 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-35417 Support "last exist" condition. Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam updated JENKINS-43803 Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam commented on JENKINS-43803 Re: Interval calculation skewed by multiple builds of same job https://github.com/jenkinsci/naginator-plugin/pull/46 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam started work on JENKINS-43803 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43803) Interval calculation skewed by multiple builds of same job
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-43803 Interval calculation skewed by multiple builds of same job Change By: ikedam Assignee: Nicolas De Loof ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title ikedam commented on JENKINS-50751 Re: Link created by naginator plugin contains comma in job numbers over 999 Ryan Tse I plan to make a new release in February with other fixes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55672) Howto define a fallback label in case all hosts for default label are busy?
Title: Message Title ikedam updated JENKINS-55672 Looks resolved by the reporter. Anyway, it’s an issue of the language specification of groovy. This plugin expects users know how to write groovy codes. You may add example codes in the plugin page as it’s a Wiki page. Improvements are welcome. Jenkins / JENKINS-55672 Howto define a fallback label in case all hosts for default label are busy? Change By: ikedam Status: Open Fixed but Unreleased Assignee: ikedam Dirk Heinrichs Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title ikedam assigned an issue to Unassigned That looks caused for the newly added user doesn’t have a permission to access that credentials. It sounds an expected behavior. Anyway, this is an issue of credentials-plugin and I update the cemponent and the assignee. Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: ikedam Component/s: credentials-plugin Component/s: authorize-project-plugin Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
