[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva created an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin
Created:
2019-10-03 07:00
Environment:
CentOS Linux release 7.6.1810 Jenkins ver. 2.195 Timestamper plugin v1.10
Priority:
Major
Reporter:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output: 2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 89 2019-10-03 01:28:35 originally caused by: 2019-10-03 01:28:35 Started by timer 2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED 2019-10-03 01:28:42 [Pipeline] Start of Pipeline 2019-10-03 01:28:42 [Pipeline] properties 2019-10-03 01:28:43 [Pipeline] timestamps 2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. 2019-10-03 01:28:43 [Pipeline] { 2019-10-03 01:28:43 [Pipeline] library 2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption 2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates But when looking at the same build instance using [View as plain text] the timestamp is wrong: [2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89 [2019-10-02T22:28:35.925Z] originally caused by: [2019-10-02T22:28:35.925Z] Started by timer [2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED [2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline [2019-10-02T22:28:42.703Z] [Pipeline] properties [2019-10-02T22:28:43.191Z] [Pipeline] timestamps [2019-10-02T22:28:43.191Z] The
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Change By:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output:2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 892019-10-03 01:28:35 originally caused by:2019-10-03 01:28:35 Started by timer2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED2019-10-03 01:28:42 [Pipeline] Start of Pipeline2019-10-03 01:28:42 [Pipeline] properties2019-10-03 01:28:43 [Pipeline] timestamps2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.2019-10-03 01:28:43 [Pipeline] {2019-10-03 01:28:43 [Pipeline] library2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates But when looking at the same build instance using [View as plain text] the timestamp is wrong:[2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89[2019-10-02T22:28:35.925Z] originally caused by:[2019-10-02T22:28:35.925Z] Started by timer[2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED[2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline[2019-10-02T22:28:42.703Z] [Pipeline] properties[2019-10-02T22:28:43.191Z] [Pipeline] timestamps[2019-10-02T22:28:43.191Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.[2019-10-02T22:28:43.192Z] [Pipeline] {[2019-10-02T22:28:43.404Z] [Pipeline] library[2019-10-02T22:28:43.416Z] WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption[2019-10-02T22:28:43.448Z] Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesThe timestamper is enabled for all pipeline build and has the following formating: ''-MM-dd HH:mm:ss' ' which appears correct in the [Console Output] but not in [View as plain text]We have the following java argument added to our master configuration: JAVA_ARGS="-Dorg.apache.commons.jelly.tags.fmt.timeZone=Europe/Sofia" The hardware clock of the VM on which the master is hosted ouputs correct timing as well: sudo hwclock --showThu 03 Oct 2019 10:03:11 AM EEST -0.355352 seconds dateThu Oct 3 10:04:14 EEST 2019
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Change By:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output:2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 89 2019-10-03 01:28:35 originally caused by: 2019-10-03 01:28:35 Started by timer 2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED 2019-10-03 01:28:42 [Pipeline] Start of Pipeline 2019-10-03 01:28:42 [Pipeline] properties 2019-10-03 01:28:43 [Pipeline] timestamps 2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. 2019-10-03 01:28:43 [Pipeline] { 2019-10-03 01:28:43 [Pipeline] library 2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption 2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesBut when looking at the same build instance using [View as plain text] the timestamp is wrong:[2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89 [2019-10-02T22:28:35.925Z] originally caused by: [2019-10-02T22:28:35.925Z] Started by timer [2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED [2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline [2019-10-02T22:28:42.703Z] [Pipeline] properties [2019-10-02T22:28:43.191Z] [Pipeline] timestamps [2019-10-02T22:28:43.191Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. [2019-10-02T22:28:43.192Z] [Pipeline] { [2019-10-02T22:28:43.404Z] [Pipeline] library [2019-10-02T22:28:43.416Z] WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption [2019-10-02T22:28:43.448Z] Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesThe timestamper is enabled for all pipeline build and has the following formating: ''-MM-dd HH:mm:ss' ' which appears correct in the [Console Output] but not in [View as plain text]We have the following java argument added to our master configuration: JAVA_ARGS="-Dorg.apache.commons.jelly.tags.fmt.timeZone=Europe/Sofia" The hardware clock of the VM on which the master is hosted ouputs correct timing as well: sudo hwclock --showThu 03 Oct 2019 10:03:11 AM EEST -0.355352 seconds dateThu Oct 3 10:04:14 EEST 2019 I wonder where is the wrong timestamp read from?Perhaps, if I knew I would be able to work around the issue by changing some system settings. Browsing the console text with correct timestamps is quite important especially when you have big outputs in general...
[JIRA] (JENKINS-59199) E-mail Notification - Stack trace
Title: Message Title pradeep N R updated JENKINS-59199 Jenkins / JENKINS-59199 E-mail Notification - Stack trace Change By: pradeep N R Resolution: Done Status: Closed In 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.201642.1567493023000.372.1570087200307%40Atlassian.JIRA.
[JIRA] (JENKINS-59545) PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed
Title: Message Title Liran Levy commented on JENKINS-59545 Re: PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed Thank you René Scheibe for the fast comment. The tickets attachment has a different error, but there is one thing in common with ticket JENKINS-18736 - using user root resolve the error. But again, i have to use a different user (not root). 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.202175.156950339.374.1570087500246%40Atlassian.JIRA.
[JIRA] (JENKINS-59545) PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed
Title: Message Title Liran Levy edited a comment on JENKINS-59545 Re: PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed Thank you [~renescheibe] for the fast comment.The tickets attachment tickets has a different error, but there is one thing in common with ticket JENKINS-18736 - using user root resolve the error.But again, i have to use a different user (not root). 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.202175.156950339.377.1570087560278%40Atlassian.JIRA.
[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-47591 Allow each Kubernetes slave pod to use unique Persistent Volume / Storage Change By: Vincent Latombe Released As: v1 kubernetes-1 .19.2 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.186064.1508775809000.381.1570088220733%40Atlassian.JIRA.
[JIRA] (JENKINS-59224) Add kubernetes-client-api plugin dependency to kubernetes and credentials provider plugins
Title: Message Title Vincent Latombe resolved as Fixed Jenkins / JENKINS-59224 Add kubernetes-client-api plugin dependency to kubernetes and credentials provider plugins Change By: Vincent Latombe Status: In Progress Resolved Resolution: Fixed Released As: kubernetes-1.19.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.201681.1567604817000.390.1570088280220%40Atlassian.JIRA.
[JIRA] (JENKINS-59637) In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)
Title: Message Title Musarrat Nawaz created an issue Jenkins / JENKINS-59637 In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results) Issue Type: Bug Assignee: Michael Gärtner Attachments: Summary.PNG Components: testcomplete11-xunit-plugin Created: 2019-10-03 07:39 Labels: test-results Priority: Major Reporter: Musarrat Nawaz We have Testcomplete project . There are more than 265 test items (Testcases). Divided thir execution test items into two free style jobs. (Json file configuration) Now on execution of one jobs in results un-executed count is showing the results of all test items that are noty supposed to be part of execution for this particular job. Aslo count Testcases count and no of failures is also not correct. This issue is appearing from the day when this un-execute status is added in TestExecution summary.
[JIRA] (JENKINS-59637) In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)
Title: Message Title Musarrat Nawaz updated an issue Jenkins / JENKINS-59637 In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results) Change By: Musarrat Nawaz We have Testcomplete project .There are more than 265 test items (Testcases).Divided thir there execution test items into two free style jobs. ( execution is handled through Json file configuration)Now on execution of one jobs in results un-executed count is showing the results of all test items that are noty not supposed to be part of execution for this particular job. Aslo Also count Testcases count and no of failures is also not correct. This issue is appearing from the day when this un-execute status is added in TestExecution summary. 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 receivin
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Vincent Latombe started work on JENKINS-58975 Change By: Vincent Latombe 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.201324.1566067268000.400.1570088581280%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Vincent Latombe assigned an issue to Narayanan Singaram Jenkins / JENKINS-58975 Executing shell in a container with a custom workingDir times out Change By: Vincent Latombe Assignee: Narayanan Singaram 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.201324.1566067268000.397.1570088581237%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Vincent Latombe updated JENKINS-58975 Jenkins / JENKINS-58975 Executing shell in a container with a custom workingDir times out Change By: Vincent Latombe 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.201324.1566067268000.403.1570088581318%40Atlassian.JIRA.
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Niall Kelly created an issue Jenkins / JENKINS-59638 Notify Testers Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-10-03 07:44 Priority: Minor Reporter: Niall Kelly Currently the `notifyTesters` field in the `DistributeResourceTask` is hardcoded to `false` but could be easily set as a parameter when generating the `UploadTask` Adding this will give developers control over whether the testers should be notified of the new release, rather than assuming that they always do not want to notify. Add Comment
[JIRA] (JENKINS-59639) LDAP tries to connect to DomainDNSZones, instead of connecting to the specified controller
Title: Message Title Anatoliy Pavlov created an issue Jenkins / JENKINS-59639 LDAP tries to connect to DomainDNSZones, instead of connecting to the specified controller Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: screen_settings.png Components: active-directory-plugin, ldap-plugin Created: 2019-10-03 07:51 Environment: Jenkins ver. 2.150.2 LDAP Plugin 1.20 Labels: jenkins ldaperr LDAPS ldap Priority: Minor Reporter: Anatoliy Pavlov LDAP tries to connect to DomainDNSZones, instead of connecting to the specified controller. This is a problem because we have one DC in a specific subnet that I don't have access. And sometimes we try connect to it. Because of this, sometimes we get an error: WARNING: Failed communication with ldap server JGkd1ZeRNKYEKqw498EhYw== (ldaps://appauth.corp.emc.com:636), will try the next configuration org.acegisecurity.AuthenticationServiceException: LdapCallback;null; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: DomainDnsZones.corp.emc.com:636 [Root exception is java.net.SocketTimeoutException: connect timed out]]; nested exception is org.acegisecurity.ldap.LdapD
[JIRA] (JENKINS-59637) In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)
Title: Message Title Musarrat Nawaz updated an issue Jenkins / JENKINS-59637 In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results) Change By: Musarrat Nawaz Attachment: Now-Before.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202319.1570088387000.409.1570089180348%40Atlassian.JIRA.
[JIRA] (JENKINS-56068) Code Coverage not being pushed to ALM Octane
Title: Message Title James Withers commented on JENKINS-56068 Re: Code Coverage not being pushed to ALM Octane We couldn't see that this was added to pipeline-as-code in version 5.8 or 5.9 however we were able to reuse the java code from the method 'perform' from package 'com.microfocus.application.automation.tools.octane.actions.CoveragePublisher' and we are able to see code coverage reports in Octane 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.197492.1549750741000.414.1570089360301%40Atlassian.JIRA.
[JIRA] (JENKINS-59637) In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)
Title: Message Title Musarrat Nawaz updated an issue Jenkins / JENKINS-59637 In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results) Change By: Musarrat Nawaz Component/s: test-results-analyzer-plugin Component/s: testcomplete11-xunit-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.202319.1570088387000.411.1570089360260%40Atlassian.JIRA.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-10-03 08:24 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page wil
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite started work on JENKINS-59640 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202322.1570091047000.420.1570091160676%40Atlassian.JIRA.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Change By: Mark Waite Assignee: Mark Waite 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.202322.1570091047000.419.1570091160661%40Atlassian.JIRA.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated JENKINS-59640 Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202322.1570091047000.421.1570091160699%40Atlassian.JIRA.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Change By: Mark Waite Component/s: versioncolumn-plugin Component/s: other We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve (versioncolumn-plugin) , clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on https://plugins.jenkins.io/. Add Comment
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Alex Earl Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl 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.202172.1569500879000.423.1570092360280%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Unassigned Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl 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.202172.1569500879000.425.1570092360305%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Hi Alex, To whom we can assign this 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.202172.1569500879000.427.1570092420100%40Atlassian.JIRA.
[JIRA] (JENKINS-59641) "java.lang.OutOfMemoryError: Java heap space" while Uploading attachments to Confluence page
Title: Message Title Suresh kothapet created an issue Jenkins / JENKINS-59641 "java.lang.OutOfMemoryError: Java heap space" while Uploading attachments to Confluence page Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 2019-10-03 08:54 Priority: Blocker Reporter: Suresh kothapet "java.lang.OutOfMemoryError: Java heap space" while Uploading attachments to Confluence page Please find the sample exception that is raised while uploading attachments [confluence] Uploading attachments to Confluence page: https://confluence.ncr.com/pages/viewpage.action?pageId=315214000 [confluence] Evaluating fileset pattern: ArchiveNow/*/.xls [confluence] Found 25 workspace artifact(s) to upload to Confluence... [confluence] Uploading 25 file(s) to Confluence... [confluence] - Uploading file: BalanceInquiry_DetailResults.xls (application/octet-stream) [confluence] done: https://confluence.ncr.com/download/attachments/315214000/BalanceInquiry_DetailResults.xls?version=12&modificationDate=156514974&api=v2 [confluence] - Uploading file: BalanceInquiry_NCR.APTRA.CnsmrAppActivateEnterprise.xls (application/octet-stream) [confluence] done: https://confluence.ncr.com/download/attachments/315214000/BalanceInquiry_NCR.APTRA.CnsmrAppActivateEnterprise.xls?version=14&modificationDate=156516332&api=v2 [confluence] - Uploading file: BalanceInquiry_NCR.APTRA.SSTMonitor.xls (application/octet-stream) [confluence] done: https://confluence.ncr.com/download/attachments/315214000/BalanceInquiry_NCR.APTRA.SSTMonitor.xls?version=14&modificationDate=156517674&api=v2 [confluence] - Uploading file: BalanceInquiry_NCR.APTRA.WMIXFSMonitor.xls (application/octet-stream) [confluence] done: https://confluence.ncr.com/download/attachments/315214000/BalanceInquiry_NCR.APTRA.WMIXFSMonitor.xls?version=14&modificationDate=156519122&api=v2 [confluence] - Uploading file: BalanceInquiry_Ncr.Connections.Client.Browser.Process.xls (application/octet-stream) [confluence] d
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Issue Type: New Feature Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2019-10-03 09:30 Priority: Minor Reporter: Gunter Grodotzki would be great to configure organizationChildTriggersProperty via CasC Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati started work on JENKINS-59280 Change By: Naresh Rayapati 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.201811.1568029791000.441.1570095422481%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati updated JENKINS-59280 Jenkins / JENKINS-59280 jiraJqlSearch Error Message: null value after upgrade Change By: Naresh Rayapati 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.201811.1568029791000.448.1570095422601%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati commented on JENKINS-59280 Re: jiraJqlSearch Error Message: null value after upgrade Thank you for reporting Jasmin Börsig Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201811.1568029791000.462.1570095481038%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati commented on JENKINS-59280 Re: jiraJqlSearch Error Message: null value after upgrade Merged and released with 1.5.1, should be available in update center soon. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201811.1568029791000.455.1570095480949%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati updated JENKINS-59280 Jenkins / JENKINS-59280 jiraJqlSearch Error Message: null value after upgrade Change By: Naresh Rayapati Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201811.1568029791000.469.1570095481157%40Atlassian.JIRA.
[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.
Title: Message Title Larkoie updated an issue Jenkins / JENKINS-39874 Abilty to disable pipeline-replay in Job Configuration. Change By: Larkoie Attachment: image-2019-10-03-11-38-21-093.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176488.1479513265000.475.1570095540466%40Atlassian.JIRA.
[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.
Title: Message Title Larkoie commented on JENKINS-39874 Re: Abilty to disable pipeline-replay in Job Configuration. Jesse Glick I'm having the same issue. I'd like to prevent "replay" option on my pipelines but any user with "Job - Build" right also have the replay right. (bellow is a screenshot of their rights. In the global config the only permission they have is the global Read permission which is mandatory to access Jenkins 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.176488.1479513265000.484.1570095600287%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Alex Earl Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl 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.202172.1569500879000.493.1570095720177%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Hi Alex, Please let me know Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.495.1570095720203%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Gunter Grodotzki Component/s: configuration-as-code-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.202324.1570095021000.499.1570096021337%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Gunter Grodotzki Component/s: branch-api-plugin Component/s: job-dsl-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.202324.1570095021000.497.1570096021181%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title
Gunter Grodotzki updated an issue
Jenkins / JENKINS-59642
implement organizationChildTriggersProperty
Change By:
Gunter Grodotzki
would be great to configure organizationChildTriggersProperty via CasC , like so maybe? {code:java}organizationChildTriggersProperty { templates { interval('1h') }}{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.202324.1570095021000.501.1570096080212%40Atlassian.JIRA.
[JIRA] (JENKINS-59642) implement organizationChildTriggersProperty
Title: Message Title Ewelina Wilkosz assigned an issue to Daniel Spilker Jenkins / JENKINS-59642 implement organizationChildTriggersProperty Change By: Ewelina Wilkosz Assignee: Ewelina Wilkosz Daniel Spilker 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.202324.1570095021000.504.1570096620403%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title
Robert Platt commented on JENKINS-59456
Re: Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
After a Tomcat upgrade, this affected us too. As a workaround, we added {{relaxedQueryChars="[,]" }}in the remote Tomcat's server.xml
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.202049.1568954668000.507.1570097761221%40Atlassian.JIRA.
[JIRA] (JENKINS-59643) parameter store plugin doesn't use instance profile or assumed role
Title: Message Title robin yonge created an issue Jenkins / JENKINS-59643 parameter store plugin doesn't use instance profile or assumed role Issue Type: Bug Assignee: Rik Turnbull Components: aws-parameter-store-plugin Created: 2019-10-03 10:30 Priority: Minor Reporter: robin yonge Hi! I understand this probably isn't a bug but I couldn't find anywhere else to ask a question. I want to be able to fetch parameters using either a role assumed with the `withAWS` build step provided in the pipeline-aws plugin, or to use the instance profile on the Jenkins node, but this doesn't seem to work?? Is there something I'm missing? Add Comment
[JIRA] (JENKINS-59048) Config as Code plugin throws exception when trying to read spotBlockReservationDurationStr from EC2 agent when spot instance enabled.
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-59048 Config as Code plugin throws exception when trying to read spotBlockReservationDurationStr from EC2 agent when spot instance enabled. Change By: Gunter Grodotzki Component/s: configuration-as-code-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.201402.156646108.512.1570102020268%40Atlassian.JIRA.
[JIRA] (JENKINS-33628) Support bundle corrupt via UI
Title: Message Title Arnaud Héritier resolved as Fixed Jenkins / JENKINS-33628 Support bundle corrupt via UI Change By: Arnaud Héritier Status: In Progress Resolved Resolution: Fixed Released As: support-core-2.57 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.169075.145823170.517.1570106580868%40Atlassian.JIRA.
[JIRA] (JENKINS-57138) Performance issue due to the bundle anonymization
Title: Message Title Arnaud Héritier commented on JENKINS-57138 Re: Performance issue due to the bundle anonymization FYI Allan BURDAJEWICZ 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.19.1555935767000.522.1570106820416%40Atlassian.JIRA.
[JIRA] (JENKINS-59613) Rename the plugin "Jenkins Health Advisor by CloudBees"
Title: Message Title Arnaud Héritier updated JENKINS-59613 Jenkins / JENKINS-59613 Rename the plugin "Jenkins Health Advisor by CloudBees" Change By: Arnaud Héritier 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.202254.1569951438000.525.1570106820546%40Atlassian.JIRA.
[JIRA] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error
Title: Message Title pau sabats commented on JENKINS-33708 Re: Invocation of 'sh' on Windows should provide a more helpful error The error related with : Cannot run program "nohup" means that it's searching for nohup.exe because is what jenkins requires when using 'sh' in the pipeline, so you can use nuhup.exe from here: "C:\Program Files\Git\usr\bin". Eventhough, what I have done in order to solve this issue is the following: Create a if else statement in your jenkinsfile that does: if (isUnix()) --> sh "command" else --> bat "command" doing so the pipeline running on agent windows will run as bat and this error no longer appears. Note: You can also use "tool config configuration" of jenkins and install tools from there. In case your sh commands were related with installation files 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.169163.1458600265000.528.1570107300956%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk updated an issue Jenkins / JENKINS-59633 EC2 Plguin: Windows EC2 instances are not launching Change By: tapvir virk Attachment: access_denied_windows_ec2_plugin.gif 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.202315.157004916.554.1570110060233%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Attaching the screenshot of the ec2 slave setting. Do you know which permission is required? 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.202315.157004916.558.1570110120174%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen started work on JENKINS-58639 Change By: Paul Allen 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.200807.156396953.567.1570110240557%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Assignee: Charusheela Bopardikar 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.200807.156396953.564.1570110240469%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Labels: P4_VERIFY P4_A 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.200807.156396953.571.1570110300279%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk edited a comment on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Attaching the screenshot of the ec2 slave setting. Do you know which permission is required? Though I can see the instance getting launched on aws account. 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.202315.157004916.574.1570110360258%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang commented on JENKINS-59456 Re: Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Fixed in b44fb12 , will be included in next release. BTW, Robert Platt, thanks for your mail & solution. 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.202049.1568954668000.578.1570110660288%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang updated JENKINS-59456 Fixed in b44fb12 Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang 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 vi
[JIRA] (JENKINS-59629) Not validating the TOS is confusing
Title: Message Title Arnaud Héritier updated JENKINS-59629 Jenkins / JENKINS-59629 Not validating the TOS is confusing Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-plugin-2.11 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.202310.1570035924000.587.1570111320243%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 14:03 Priority: Minor Reporter: Arnaud Héritier + use BOM Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier + use BOM The idea will be to upgrade de support-core dependency too (it has the same requirement) 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.202334.1570111402000.589.1570111560495%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier + use BOM The idea will be to upgrade de support-core dependency too (it has the same requirement) With a more recent version of support-core we get more informations and we have less performances issues with the anonymisation (For now we require support-core 2.44 which doesn't propose the anonymisation) Any thoughts [~recampbell] ? 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.202334.1570111402000.594.1570111742983%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Ryan Campbell commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 1 Agree, we only support 2.138 now anyway. 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.202334.1570111402000.596.1570111920125%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang closed an issue as Fixed fixed & released Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang 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.202049.1568954668000.602.1570112104082%40Atlassian.JIRA.
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title KaiHsiang Chang updated JENKINS-59456 Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Change By: KaiHsiang Chang Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202049.1568954668000.599.1570112103493%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Jai Mishra commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) i have the same problem.Please let me know when are you planning to release this fix. 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.192737.1533040103000.605.1570112160948%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails Need to retest after changes in 10.0.1.4 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.201296.1565876577000.620.1570113120131%40Atlassian.JIRA.
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves created an issue Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Issue Type: Bug Assignee: Unassigned Attachments: Capturar.PNG, Capturar2.PNG, image (3).png Components: _unsorted Created: 2019-10-03 14:33 Environment: Docker Image: jenkins / jenkins : 2.190.1 Using Blueocean and all default plugins in the latest version Priority: Major Reporter: Jonathan Gonçalves After update from 2.176.1 to 2.190.1 some projects with accents can't be access anymore because the Job link appears empty. Another problem is in Blueocean, that doesnt show project names with accents. Another problem is in the job execution, that throw an Exception when try to build projects with accents on name. Add Comment
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves updated an issue Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Change By: Jonathan Gonçalves Attachment: jenkins.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202335.1570113234000.623.1570113600251%40Atlassian.JIRA.
[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1
Title: Message Title Jonathan Gonçalves commented on JENKINS-59645 Re: Encoding problems after update to version 2.190.1 Added some error logs 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.202335.1570113234000.624.1570113600264%40Atlassian.JIRA.
[JIRA] (JENKINS-58320) KeyGenerator without initialization
Title: Message Title Sergey Khokhlov assigned an issue to Sergey Khokhlov Jenkins / JENKINS-58320 KeyGenerator without initialization Change By: Sergey Khokhlov Assignee: Sergey Khokhlov 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.200428.156215583.622.1570113600209%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth commented on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers: Concurrency bug = JENKINS-58119 Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. 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.202099.1569244102000.626.1570113960198%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Karl Wirth Issue Type: Bug Improvement 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.202099.1569244102000.630.1570114080388%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth edited a comment on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers:Concurrency bug = JENKINS-58119 TBD. Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. 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.202099.1569244102000.628.1570114080331%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth edited a comment on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Have met with the developers: Concurrency bug =TBD. Sub-directory support is an enhancement request. To work around JENKINS-48882 we have to look at the directory name to figure out which executor we are on. If you use 'dir()' it breaks this check hence '0' every time. We will need a redesign of this check to allow for the it to work at lower levels and it will need to cope with Windows and Linux paths. 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.202099.1569244102000.632.1570114620147%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title pau sabats commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I reproduced this error on win10 removing the slave-agent.jnlp or having more than 1 of this files. The problem is that the slaves loses somehow the connection configuration to the master so this error is shown. My solution was to create a new agent slave, so a new .jnlp can be downloaded, and this one will be well configured so it will work. If the .jnlp doesn't show you in jenkins to download, you can try with the command : java -jar agent.jar -jnlpUrl http://jenkinsurl:port/computer/windows-agent/slave-agent.jnlp -secret -workDir "C:\JenkinsSlave" 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.164090.1437742638000.634.1570114681250%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Component/s: badge-plugin Component/s: other Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.673.1570115280764%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve (badge-plugin) , clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on https://plugins.jenkins.io/. Add Comment
[JIRA] (JENKINS-30267) Maven repository artifact does not showing newly updated version from Nexus Maven Repository
Title: Message Title Julien Béti commented on JENKINS-30267 Re: Maven repository artifact does not showing newly updated version from Nexus Maven Repository I have version 1.2.6, and I have the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164854.1441201253000.688.1570115281142%40Atlassian.JIRA.
[JIRA] (JENKINS-29166) Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository
Title: Message Title Julien Béti commented on JENKINS-29166 Re: Repository Connector Plugin doesn't refresh the list of artifacts stored on maven repository I have version 1.2.6, and I have the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163627.1435755906000.681.1570115281050%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-10-03 15:07 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be upd
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite started work on JENKINS-59646 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.690.1570115460248%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated JENKINS-59646 Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202336.1570115224000.691.1570115460293%40Atlassian.JIRA.
[JIRA] (JENKINS-59646) Migrate badge plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59646 Migrate badge plugin documentation from Wiki to GitHub Change By: Mark Waite Assignee: Mark Waite 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.202336.1570115224000.692.1570115640088%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails Tested and bug still seen. Additional changes going in at the moment so retest in 1 week. 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.201296.1565876577000.696.1570116120112%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Mark Waite commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Jai Mishra no fix has been implemented. Cenk Tosun reported a workaround in an earlier comment. Are you absolutely certain after reading all the descriptions and comments that your issue is the same problem as described here? If so, does the workaround from Cenk Tosun also fix it for 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.192737.1533040103000.699.1570116240475%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Jenkins workspace can not be updated automatically
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59622 Jenkins workspace can not be updated automatically Change By: Mark Waite Assignee: Mark Waite 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.202266.1570009158000.709.1570116780262%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Sparse checkout definition change not applied to workspace
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59622 Sparse checkout definition change not applied to workspace Change By: Mark Waite Summary: Jenkins workspace can Sparse checkout definition change not be updated automatically applied to workspace 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.202266.1570009158000.711.1570116780327%40Atlassian.JIRA.
[JIRA] (JENKINS-59622) Sparse checkout definition change not applied to workspace
Title: Message Title Mark Waite commented on JENKINS-59622 Re: Sparse checkout definition change not applied to workspace The git plugin does not apply changes to the sparse checkout definition to the workspace. A workaround in Pipeline is to use deleteDir() in the Jenkinsfile when making this type of structural change. The workspace will be removed by the call to deleteDir() and then the currently defined sparse checkout will be applied to the fresh checkout. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202266.1570009158000.715.1570116900167%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 We can remove the code related to the support of jenkins core < 2.103 ( JENKINS-43786 ) 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.202334.1570111402000.719.1570117260332%40Atlassian.JIRA.
[JIRA] (JENKINS-42825) input steps should be able to automatically popup a dialogue box in the stage view
Title: Message Title Jim D commented on JENKINS-42825 Re: input steps should be able to automatically popup a dialogue box in the stage view This definitely helps the case where the user has clicked on the job page and a build is waiting for input. Each time I explain to job users that they must hover, it takes a while for them to get used to it. And it also helps the case where the user has opened the popup by hovering and there are inputs to fill out like strings or choices, since the popup is so small and constantly users are letting their mouse pointer drift, which kills the popup in the middle of editing the input form. I've seen our users try to fill out a popup over and over again unsuccessfully, and finally have to show them there's a way to get to the plain HTML "Paused for input" form page instead. Even if the popup weren't automatic when the job page is rendered, if there were a way to open it besides the hover, it would improve usability. An explicit link or button inside the "paused" stage cell would be more obvious, and it wouldn't require a delay before showing the popup, and since the user actually clicked, presumably the popup could just stay open. (Note that I don't know why the popup has an "X" close button either, since it disappears so easily when you move the mouse. This might make the "X" close button be more useful too.) The version we're using currently is: org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view:2.12 Jenkins 2.176.3 Firefox 68.0.2esr Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier started work on JENKINS-59644 Change By: Arnaud Héritier 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.202334.1570111402000.722.1570117441062%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated JENKINS-59644 Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier 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.202334.1570111402000.724.1570117441432%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 PR: https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/36 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.202334.1570111402000.721.1570117440919%40Atlassian.JIRA.
[JIRA] (JENKINS-59647) Upgrade support-core dependency to 2.62
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59647 Upgrade support-core dependency to 2.62 Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 15:54 Priority: Major Reporter: Arnaud Héritier 2.62 isn't yet released but it should be soon by Evaristo Gutierrez 2.62 has also 2.138.4 as core requirement ( we are upgrading with JENKINS-59644 ) We are now depending of 2.44 which was released in dec 2017. Recent versions of support-core are providing a lot of improvements (like anonymisation), are grabbing new details useful for some probes. FYI Ryan Campbell I suppose you're ok Owen Wood ? Add Comment
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier started work on JENKINS-59648 Change By: Arnaud Héritier 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.202338.1570118477000.728.1570118520200%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59648 UX improvements Issue Type: Task Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-03 16:01 Priority: Major Reporter: Arnaud Héritier While testing the plugin I found various small improvements to do to improve a bit the user experience: Logs are showing that the upload task is starting/finishing while it does nothing (because TOS aren't accepted for example). It's confusing and could let think that an upload happens which isn't the case Oct 03, 2019 3:17:55 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Bundle Upload Oct 03, 2019 3:17:55 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Bundle Upload. 1 ms The configuration screen could be improved a bit by just reordering some fields (it's confusing to accept the TOS at the bottom of the form while it it is the most important setting. Without accepting the TOS nothing happens) Few messages / sentences could be improved
[JIRA] (JENKINS-59614) New icon for Jenkins Health Advisor by CloudBees
Title: Message Title Arnaud Héritier updated JENKINS-59614 Jenkins / JENKINS-59614 New icon for Jenkins Health Advisor by CloudBees Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 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.202255.156995264.730.1570118826483%40Atlassian.JIRA.
[JIRA] (JENKINS-59618) Upgrade parent pom + configure plugin metadata
Title: Message Title Arnaud Héritier updated JENKINS-59618 Jenkins / JENKINS-59618 Upgrade parent pom + configure plugin metadata Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 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.202259.1569961496000.731.1570118826517%40Atlassian.JIRA.
[JIRA] (JENKINS-59613) Rename the plugin "Jenkins Health Advisor by CloudBees"
Title: Message Title Arnaud Héritier updated JENKINS-59613 Jenkins / JENKINS-59613 Rename the plugin "Jenkins Health Advisor by CloudBees" Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.11 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.202254.1569951438000.729.1570118820239%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: Alex Earl Assignee: Alex Earl 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.202172.1569500879000.742.1570119300658%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Stop assigning this to me. 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.202172.1569500879000.744.1570119360142%40Atlassian.JIRA.
