[JIRA] (JENKINS-48327) Support for GitHub Organization style Project
Title: Message Title James Withers commented on JENKINS-48327 Re: Support for GitHub Organization style Project I believe this is fixed in release 6.1 of the hp-application-automation-tools-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.186919.1512076403000.6359.1581407580184%40Atlassian.JIRA.
[JIRA] (JENKINS-21073) Fix forceLdaps system property
Title: Message Title Sebastian Willdo commented on JENKINS-21073 Re: Fix forceLdaps system property Jenkins version: 2.220 Plugin version: 2.16 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152635.1387381836000.6353.1581406500229%40Atlassian.JIRA.
[JIRA] (JENKINS-21073) Fix forceLdaps system property
Title: Message Title
Sebastian Willdo reopened an issue
I seems that issue returns. I'm not able to connect with TLS to our AD. In logs(hudson.plugins.active_directory) i can see that plugin tries to connect with plain protocol ldap even after forcing ldpas in start parameters.
PATH=/opt/wii/test/csvn/bin:$PATH
export JAVA_ARGS='-Dorg.eclipse.jetty.server.HttpConfiguration.requestHeaderSize=32768 -Dorg.eclipse.jetty.server.HttpConfiguration.responseHeaderSize=32768 -Dorg.eclipse.jetty.server.Request.maxFormContentSize=50 -Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true -Djavax.net.ssl.trustStore=/opt/wii/java/jdk1.8.0_111/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://jenkins:8080'
export JENKINS_JAVA_OPTIONS="${JAVA_ARGS}"
source /home/jenkins/.bash_profile 2>&1 >/dev/null
LOG_NAME=$(date +%d_%m_%Y).logs
$JAVA_HOME/jre/bin/java -Xms4096m -Xmx4096m $JAVA_ARGS -jar $JENKINS_HOME/server/lib/jenkins.war --requestHeaderSize=32768 > $JENKINS_HOME/server/logs/$LOG_NAME 2>&1 &
echo $LOG_NAME
exit 0
Jenkins / JENKINS-21073
Fix forceLdaps system property
Change By:
Sebastian Willdo
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke updated JENKINS-60649 Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.6341.1581404280529%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke updated JENKINS-60649 Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke 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.203891.1578329007000.6336.1581404221452%40Atlassian.JIRA.
[JIRA] (JENKINS-60611) Not specifying a repo platform results in "Invalid Platform Flag" error
Title: Message Title Gopal Ahir edited a comment on JENKINS-60611 Re: Not specifying a repo platform results in "Invalid Platform Flag" error e We are also facing the same issue with latest jenkins version. Is there any solution yet? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203840.1577719616000.6332.1581403020250%40Atlassian.JIRA.
[JIRA] (JENKINS-60611) Not specifying a repo platform results in "Invalid Platform Flag" error
Title: Message Title Gopal Ahir commented on JENKINS-60611 Re: Not specifying a repo platform results in "Invalid Platform Flag" error e are also facing the same issue with latest jenkins version. Is there any solution yet? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203840.1577719616000.6328.1581402960174%40Atlassian.JIRA.
[JIRA] (JENKINS-61039) Generic JS Portlet broken with Dashboard View 2.12
Title: Message Title Georg Henzler created an issue Jenkins / JENKINS-61039 Generic JS Portlet broken with Dashboard View 2.12 Issue Type: Improvement Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 2020-02-11 06:29 Priority: Minor Reporter: Georg Henzler getId() in https://github.com/jenkinsci/mashup-portlets-plugin/blob/2f5d5a2cfa742e65d9e2a51912d6cc6493e72f07/src/main/java/javagh/jenkins/mashupportlets/GenericJsPortlet.java#L27 contains now a dash which is not a valid variable/function name in JS Add Comment
[JIRA] (JENKINS-61038) Ability to disable source code view at master and/or project level
Title: Message Title Hang Dong created an issue Jenkins / JENKINS-61038 Ability to disable source code view at master and/or project level Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-02-11 01:53 Priority: Minor Reporter: Hang Dong We would like to request for an option to disable warning plugin's parsing and displaying of project source code (source code view feature); ideally having the ability to set it at instance/master level as well as project's parser level. For very large project where we are more interest in tracking metric, we found this parse/displaying to be expensive on storage; in addition we notice view content permission is tied to job read permission (more open in our instance), instead workspace permission (limited to admin) - in our env with mix-ed repo with diff permission level but builds together, this can potentially exposes source code when we want intended to share build result/console output. Add Comment
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Brian Ray edited a comment on JENKINS-57205
Re: Null pointer exception in JGit pre-build merge
Diffing JGit code was unproductive. I rebuilt Git 4.1.1 and Git Client 3.1.1 with some more logging spliced in and seem to be getting closer. A lot of tags are ultimately resolving to null commit hashes. {{PreBuildMerge}} scoops up branches and tags at the outset. {noformat}Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=1.6.18.1, raw tagRef=Ref[refs/tags/1.6.18.1=c617fb6b71266adb9ca6bff59a89ad7e06638864(-1)]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[9935fd11f9a3c6a93bf3120ef7d7e15a5d130ed8]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.10, raw tagRef=Ref[refs/tags/3.1.10=94adcf654c5ae0d4d2bb88ec01bdc43ed0bea442(-1)]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=nullFeb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.10.1, raw tagRef=Ref[refs/tags/3.1.10.1=be995402548cad1220fb4ed20c083323bb50d303(-1)]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=nullFeb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.2.2, raw tagRef=Ref[refs/tags/3.1.2.2=fdc33c0ca48ba47afe2ba36d2016d346f42120df(-1)]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[263187a0f9d5ed3747520c230728f276f6fd848d]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.6, raw tagRef=Ref[refs/tags/3.1.6=7e9ed43e4838b31eacdbd60d25908f1566bfe7cd(-1)]Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[3d686b8d9bc8c02c7dab25f16b8a79217e568b1d] ...{noformat} That's {{JGitAPIImpl.getTags()}} [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.1.1/src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java#L2785-L2810]. My suspicion is still on JGit 4.9.0 but rigging up the plugins looked a little less intimidating than JGit.
Add Comment
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Diffing JGit code was unproductive. I rebuilt Git 4.1.1 and Git Client 3.1.1 with some more logging spliced in and seem to be getting closer. A lot of tags are ultimately resolving to null commit hashes. Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=1.6.18.1, raw tagRef=Ref[refs/tags/1.6.18.1=c617fb6b71266adb9ca6bff59a89ad7e06638864(-1)] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[9935fd11f9a3c6a93bf3120ef7d7e15a5d130ed8] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.10, raw tagRef=Ref[refs/tags/3.1.10=94adcf654c5ae0d4d2bb88ec01bdc43ed0bea442(-1)] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=null Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.10.1, raw tagRef=Ref[refs/tags/3.1.10.1=be995402548cad1220fb4ed20c083323bb50d303(-1)] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=null Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.2.2, raw tagRef=Ref[refs/tags/3.1.2.2=fdc33c0ca48ba47afe2ba36d2016d346f42120df(-1)] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[263187a0f9d5ed3747520c230728f276f6fd848d] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 tagName=3.1.6, raw tagRef=Ref[refs/tags/3.1.6=7e9ed43e4838b31eacdbd60d25908f1566bfe7cd(-1)] Feb 10, 2020 4:10:59 PM org.jenkinsci.plugins.gitclient.JGitAPIImpl getTags WARNING: CICD-128 adding tagRef.getPeeledObjectId()=AnyObjectId[3d686b8d9bc8c02c7dab25f16b8a79217e568b1d] ... That's JGitAPIImpl.getTags() here. My suspicion is still on JGit 4.9.0 but rigging up the plugins looked a little less intimidating than JGit. Add Comment
[JIRA] (JENKINS-55519) ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob
Title: Message Title Liam Newman updated JENKINS-55519 Jenkins / JENKINS-55519 ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196652.154714790.6263.1581382201148%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title victor paul edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository [~fajran] Is is it possible to share the code removing your firms references? Seems this has been the issue with Jenkins since years and there is not a stable 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.181165.1492753177000.6256.1581381964975%40Atlassian.JIRA.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman commented on JENKINS-57195 Re: Scan organization fails with FileNotFoundException Giorgio Sironi Please try this with github-branch-source 2.6.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.198949.1556274194000.6147.1581381900105%40Atlassian.JIRA.
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title Liam Newman resolved as Duplicate Jenkins / JENKINS-57942 Found multiple extensions which provide method originPullRequestDiscoveryTrait Change By: Liam Newman Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199918.1560187438000.6140.1581381720546%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke edited a comment on JENKINS-60492 Re: Connection with Bitbucket server over SSH Hi Roman,This was intended for the first release of the plugin- only login-password credentials are provided so I will change the type of this ticket to " improvement new feature ". Thanks for the suggestion- we will consider it for a future release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6143.1581381720589%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke updated an issue Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Martin Henschke Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6134.1581381661019%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke commented on JENKINS-60492 Re: Connection with Bitbucket server over SSH Hi Roman, This was intended for the first release of the plugin- only login-password credentials are provided so I will change the type of this ticket to "improvement". Thanks for the suggestion- we will consider it for a future release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6129.1581381660926%40Atlassian.JIRA.
[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-58172 Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.6118.1581381600733%40Atlassian.JIRA.
[JIRA] (JENKINS-58115) Tag not being picked up in organization scan
Title: Message Title Liam Newman commented on JENKINS-58115 Re: Tag not being picked up in organization scan Giorgio Sironi Please try this with Github-branch-source 2.6.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.200159.1561024443000.6126.1581381600915%40Atlassian.JIRA.
[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source
Title: Message Title Liam Newman commented on JENKINS-58172 Re: Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source Ethan Diamond I think we might have fixed this in v2.6.0. This is likely another example of JENKINS-54126. Give the new version a try. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.6114.1581381540229%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title victor paul commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Fajran Rusadi Is is possible to share the code removing your firms references? Seems this has been the issue with Jenkins since years and there is not a stable 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.181165.1492753177000.6005.1581381481770%40Atlassian.JIRA.
[JIRA] (JENKINS-58696) Github Branch Source plugin thottle broken by unexpected rate limit headers
Title: Message Title Liam Newman resolved as Fixed Added the option per the PR. Thanks for contributing! Jenkins / JENKINS-58696 Github Branch Source plugin thottle broken by unexpected rate limit headers Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-59318) fill in user-agent with something specific to github-branch-source-plugin
Title: Message Title Liam Newman commented on JENKINS-59318 Re: fill in user-agent with something specific to github-branch-source-plugin Josh Soref Totally support this being done. It might require some update to github-api library which you're already familiar with. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201869.1568218923000.5999.1581380820099%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman commented on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating Steve Boardwell I tried to get this into v2.6.0, but are were some unexpected snags. It is on the list of things to do, but I'll have to circle back to it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.5995.1581380700356%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Liam Newman commented on JENKINS-59485 Re: Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Fred G Please submit a PR to change this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202100.1569247714000.5981.1581380520420%40Atlassian.JIRA.
[JIRA] (JENKINS-59756) NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-59756 NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt Change By: Liam Newman Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202479.1570827139000.5979.1581380460245%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Liam Newman updated JENKINS-59797 Thanks for your contribution! Jenkins / JENKINS-59797 AvatarCache does not support authenticated scm access Change By: Liam Newman Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60509) Name column in Pull Request/Branch view should use number aware sorting
Title: Message Title Liam Newman commented on JENKINS-60509 Re: Name column in Pull Request/Branch view should use number aware sorting @Ryan Fenton-Garcia Thanks for looking into how to fix this. I'm not sure I can help, but I believe you are in the right area. Could you put up a PR of what you've done and we can discuss from there? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203601.1576519448000.5963.1581379440152%40Atlassian.JIRA.
[JIRA] (JENKINS-60730) Add possibility to exclude branches and tags older than X days
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-60730 Add possibility to exclude branches and tags older than X days Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203980.1578658846000.5961.1581379140282%40Atlassian.JIRA.
[JIRA] (JENKINS-60730) Add possibility to exclude branches and tags older than X days
Title: Message Title Liam Newman commented on JENKINS-60730 Re: Add possibility to exclude branches and tags older than X days Per discussion, this is already achievable using a combination of existing plugins. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203980.1578658846000.5959.1581379080123%40Atlassian.JIRA.
[JIRA] (JENKINS-60783) Delete pipelines for archived repositories
Title: Message Title Liam Newman resolved as Duplicate Released in github-branch-source 2.6.0 Jenkins / JENKINS-60783 Delete pipelines for archived repositories Change By: Liam Newman Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60792) GH Source Branch Plugin ignores system-wide proxy settings
Title: Message Title Liam Newman commented on JENKINS-60792 Re: GH Source Branch Plugin ignores system-wide proxy settings Please try with github-branch-source 2.6.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.204120.1579176493000.5955.1581378660247%40Atlassian.JIRA.
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title William Brode commented on JENKINS-61035 Re: Polling build filters case sensitive on -C1 server Karl Wirth I think this is a duplicate of the one I opened a while back? https://issues.jenkins-ci.org/browse/JENKINS-48584 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204514.1581360737000.5928.1581374640256%40Atlassian.JIRA.
[JIRA] (JENKINS-61037) Cucumber Slack Notifier Plugin incompatible with CasC
Title: Message Title Joseph Petersen assigned an issue to Franco Frangipane Jenkins / JENKINS-61037 Cucumber Slack Notifier Plugin incompatible with CasC Change By: Joseph Petersen Assignee: Ewelina Wilkosz Franco Frangipane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204517.1581373884000.5926.1581374460395%40Atlassian.JIRA.
[JIRA] (JENKINS-61037) Cucumber Slack Notifier Plugin incompatible with CasC
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-61037 Cucumber Slack Notifier Plugin incompatible with CasC Change By: Joseph Petersen 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.204517.1581373884000.5922.1581374460306%40Atlassian.JIRA.
[JIRA] (JENKINS-61037) Cucumber Slack Notifier Plugin incompatible with CasC
Title: Message Title Jamie Jackson created an issue Jenkins / JENKINS-61037 Cucumber Slack Notifier Plugin incompatible with CasC Issue Type: Improvement Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, cucumber-slack-notifier-plugin Created: 2020-02-10 22:31 Labels: jcasc-compatibility Priority: Minor Reporter: Jamie Jackson The Cucumber Slack Notifier plugin's global configuration doesn't seem to work with Casc Jenkins version: - 2.204.2 CasC version - 1.35 cucumber-slack-notifier - 0.8.3 Refs: My original ticket: https://github.com/jenkinsci/configuration-as-code-plugin/issues/1271 Page that brought me here: https://wiki.jenkins.io/display/JENKINS/Plugins+compatibility+with+Jenkins+Configuration-as-Code+plugin#PluginscompatibilitywithJenkinsConfiguration-as-Codeplugin-Knownissuesandresolutions
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title Fernando Nasser commented on JENKINS-28178 Re: Option to disable sandbox in CpsScmFlowDefinition Third that. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162496.1430411624000.5778.1581371162198%40Atlassian.JIRA.
[JIRA] (JENKINS-61025) Unable to update private key using CLI
Title: Message Title Joe Steffee updated an issue Jenkins / JENKINS-61025 Unable to update private key using CLI Change By: Joe Steffee I am using the following script, the xml is the exact same as provided by list-credentials-as-xml system::system::jenkins, with the key specified This is a completely fresh, latest install of jenkins with the recommended plugins installed This is blocking us from implementing a github key rotation strategy which we need for compliance reasons This happens with or without the additional XML as described in the docs (the additional or tags: [ https://github.com/jenkinsci/credentials-plugin/blob/master/docs/user.adoc ] ```cat > credential.xml < GLOBAL USERNAME USERNAME USERNAME -BEGIN RSA PRIVATE KEY--END RSA PRIVATE KEY- EOFjava -jar jenkins-cli.jar -auth username:password -s [ http://localhost:8080 |http://localhost:8080/] update-credentials-by-xml system::system::jenkins _ USERNAME< credential.xml```However, this errors:```RROR: Unexpected exception occurred while performing update-credentials-by-xml command. [48/12914]java.lang.InstantiationException: com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource at sun.misc.Unsafe.allocateInstance(Native Method) at com.thoughtworks.xstream.converters.reflection.SunLimitedUnsafeReflectionProvider.newInstance(SunLimitedUnsafeReflectionProvider.java:76)Caused: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Cannot construct com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource at com.thoughtworks.xstream.converters.reflection.SunLimitedUnsafeReflectionProvider.newInstance(SunLimitedUnsafeReflectionProvider.java:80) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:433) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:266) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Cannot construct com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource : Cannot construct com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource Debugging information message : Cannot construct com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Cannot construct com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$PrivateKeySource :
[JIRA] (JENKINS-61025) Unable to update private key using CLI
Title: Message Title Joe Steffee updated an issue Jenkins / JENKINS-61025 Unable to update private key using CLI Change By: Joe Steffee Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204498.1581286128000.5774.1581369300249%40Atlassian.JIRA.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Yuriy Burtsev commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library shagun jian, no, this is not happening. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184658.1503497167000.5749.1581367680575%40Atlassian.JIRA.
[JIRA] (JENKINS-61036) Add withCloudTags() to programatically set tags
Title: Message Title Stefan Scherer created an issue Jenkins / JENKINS-61036 Add withCloudTags() to programatically set tags Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2020-02-10 20:31 Priority: Minor Reporter: Stefan Scherer I've seen JENKINS-55865 and also the advanced setting in the UI to add custom tags. We use a groovy code to roll out our Azure cloud config to several Jenkins masters and want to add tags per cloud. I looked into the samples, but couldn't find a `withCloudTags()` method. From what I understand it should be something similar to `withCloudName()`, but taking an array or a map. Add Comment
[JIRA] (JENKINS-51066) pipeline-editor always commit to default jenkinsfile
Title: Message Title J P closed an issue as Fixed Fixed in BlueOcean 1.22.0 Jenkins / JENKINS-51066 pipeline-editor always commit to default jenkinsfile Change By: J P Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.22.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set
Title: Message Title J P edited a comment on JENKINS-50328 Re: Pipeline editor not working if Script Path is set Fixed in BlueOcean 1.22.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.189375.152167439.5726.1581366420439%40Atlassian.JIRA.
[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set
Title: Message Title J P closed an issue as Fixed Fixed in 1.22.0. Jenkins / JENKINS-50328 Pipeline editor not working if Script Path is set Change By: J P Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.22.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves It appears that this was implemented in https://github.com/jenkinsci/ec2-plugin/pull/382 However, I don't see a way to edit the properties in the AMI template, even though the config.jelly entry is supposed to be there. Am I missing something? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.5711.1581365880578%40Atlassian.JIRA.
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title Yash Amrut Jain assigned an issue to Yash Amrut Jain Jenkins / JENKINS-27508 Cannot use ENV variable for repository url in Git Publisher Change By: Yash Amrut Jain Assignee: Yash Amrut Jain Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161310.1426780171000.5698.1581365640602%40Atlassian.JIRA.
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Annie Chen commented on JENKINS-61005 Re: Builds failing because Run defining the context within which to find P4 credential is null Hi Karl Wirth, Daniel Beck, Thank you so much for your advice! I have several different Perforce builds running on 3 different machines. 2 of the machines are Windows; the other is Linux. The Windows builds still run normally, as do 2 of the 4 Linux builds. It is the other 2 Linux builds that are failing. Last Friday, I tried creating a new Perforce job and also creating a new credential with the same userid and password and having the 2 failing jobs use the new credential instead. I did not encounter this NullPointerException again. The new Perforce job works normally. The 2 failing jobs hung, but this seems to be because I ran them at the same time. I stopped those 2 jobs this morning and restarted just 1 of them. It ran normally. I have not tried running the other 1 yet, though it is scheduled to run tonight. In summary, creating a new credential seems to have fixed the problem. Therefore, I think this Bug can be closed. (I can close it if you prefer, but I just wanted to check whether you would like to close it so it shows you handled it.) Thank you so much for your help! I really appreciate it! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-27508 Cannot use ENV variable for repository url in Git Publisher Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161310.1426780171000.5678.1581364081683%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title John Flynn started work on JENKINS-61011 Change By: John Flynn 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.204481.158106000.5676.1581363000291%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title John Flynn commented on JENKINS-61011 Re: New Feature "Delete / Rename request for entired Folder" I'm working on the changes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204481.158106000.5674.1581363000247%40Atlassian.JIRA.
[JIRA] (JENKINS-44972) Truncated log displayed in middle of line, showing Base64-encoded ConsoleNote garbage
Title: Message Title Jesse Glick commented on JENKINS-44972 Re: Truncated log displayed in middle of line, showing Base64-encoded ConsoleNote garbage You would need to use various plugins (or certain core features) which insert serialized console notes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183055.1497882341000.5672.1581362700290%40Atlassian.JIRA.
[JIRA] (JENKINS-44972) Truncated log displayed in middle of line, showing Base64-encoded ConsoleNote garbage
Title: Message Title Arun Shrestha commented on JENKINS-44972 Re: Truncated log displayed in middle of line, showing Base64-encoded ConsoleNote garbage Jesse Glick Hey Jesse. I tried to replicate it by adding a very long string so that it has to skip but could not replicate it. I believe the problem with that is that my longs strings had no annotations. I was wondering if you could help me how to get annotations by using the Jenkinsfile. I would really appreciate it. I have studied the code base a bit and understand the relationship a bit with jelly files. But, if I am able to replicate it, I can move on to fixing it. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183055.1497882341000.5666.1581362400292%40Atlassian.JIRA.
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title
Mark Waite edited a comment on JENKINS-27508
Re: Cannot use ENV variable for repository url in Git Publisher
This issue report is specifically about the git publisher within the git plugin. The git publisher is not available in Pipeline. The git publisher is available in Freestyle jobs.* [~qbix], lightweight checkout is not available in Freestyle jobs* [~jlpinardon] git publisher does not perform a fetch and does not work with Pipelines* [~dcarreira] git publisher does not work with Pipelines I'm unable to duplicate the issue as described. Steps I took while trying to duplicate the issue:# Create a Freestyle job with a parameter, {{REPO_URL_FRAGMENT}} with choices MarkEWaite/jenkins-bugs, MarkEWaite/git-client-plugin, MarkEWaite/git-plugin, and MarkEWaite/platformlabeler-plugin# Use git as the SCM in that Freestyle job from repository {{https://github.com//${REPO_URL}}}# Checkout the master branch in that Freestyle job# Enable the "Merge before build" git plugin extension with repository {{origin}}, branch {{master}}, and default settings for merge strategy and fast forward mode# Add a conditional step to the Freestyle job that runs {{ant increment}} if the file {{build.xml}} is found in the workspace# Enable Git Publisher as a Post-build Action, configured to push only if the build succeeds, merge the result to the branch {{master}} with remote named {{origin}}When I perform those steps, the job runs successfully. If I choose the {{REPO_URL_FRAGMENT}} value as {{MarkEWaite/jenkins-bugs}}, the job runs successfully, increments a build number, and pushes the change to the master branch of my jenkins-bugs repository.If I choose the {{REPO_URL_FRAGMENT}} value as something other than {{MarkEWaite/jenkins-bugs}}, the job runs successfully, does not increment a build number, and does not push anything to the master branch of the selected repository.See my job definition for the precise details [^JENKINS-27508-config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title
Mark Waite edited a comment on JENKINS-27508
Re: Cannot use ENV variable for repository url in Git Publisher
This issue report is specifically about the git publisher within the git plugin. The git publisher is not available in Pipeline. The git publisher is available in Freestyle jobs.* [~qbix], lightweight checkout is not available in Freestyle jobs* [~jlpinardon] git publisher does not perform a fetch and does not work with Pipelines* [~dcarreira] git publisher does not work with Pipelines I'm unable to duplicate the issue as described. Steps I took while trying to duplicate the issue:# Create a Freestyle job with a parameter, {{REPO_URL_FRAGMENT}} with choices MarkEWaite/jenkins-bugs, MarkEWaite/git-client-plugin, MarkEWaite/git-plugin, and MarkEWaite/platformlabeler-plugin# Use git as the SCM in that Freestyle job from repository {{https://github.com//${REPO_URL}}}# Checkout the master branch in that Freestyle job# Enable the "Merge before build" git plugin extension with repository {{origin}}, branch {{master}}, and default settings for merge strategy and fast forward mode# Add a conditional step to the Freestyle job that runs {{ant increment}} if the file {{build.xml}} is found in the workspace# Enable Git Publisher as a Post-build Action, configured to push only if the build succeeds, merge the result to the branch {{master}} with remote named {{origin}}When I perform those steps, the job runs successfully. If I choose the {{REPO_URL_FRAGMENT}} value as {{MarkEWaite/jenkins-bugs}}, the job runs successfully, increments a build number, and pushes the change to the master branch of my jenkins-bugs repository.If I choose the {{REPO_URL_FRAGMENT}} value as something other than {{MarkEWaite/jenkins-bugs}}, the job runs successfully, does not increment a build number, and does not push anything to the master branch of the selected repository.See my job definition for the precise details [^JENKINS-27508-config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-27508 Cannot use ENV variable for repository url in Git Publisher Change By: Mark Waite Attachment: JENKINS-27508-config.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.161310.1426780171000.5637.1581362160961%40Atlassian.JIRA.
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-27508 Cannot use ENV variable for repository url in Git Publisher Change By: Mark Waite Attachment: JENKINS-27508-config.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.161310.1426780171000.5639.1581362160981%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204479.1581041026000.5627.1581361260310%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Mark Waite commented on JENKINS-61009 Re: How to use a reference repository in an organization folder? You've misunderstood the concept of a reference repository. Refer to the command line git documentation where it says: Using an already existing repository as an alternate will require fewer objects to be copied from the repository being cloned, reducing network and local storage costs. (emphasis added) A reference repository does not change the source from which the workspace is cloned. A reference repository reduces the network traffic and the local disc use by reusing existing local objects rather than requesting them from the remote git server. You can confirm that you are using a reference repository by comparing the size of the workspace on disc with the size of a repository cloned without a reference repository. If the workspace on disc is not significantly smaller than the clone created without a reference repository, then there is a risk that the reference repository argument is being ignored or the reference repository does not exist or the reference repository does not contain objects which will assist the repository being cloned. I'm closing this report as "Not a defect" because it has now become a personal question and answer session. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61035 Polling build filters case sensitive on -C1 server Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204514.1581360737000.5622.1581360780172%40Atlassian.JIRA.
[JIRA] (JENKINS-61035) Polling build filters case sensitive on -C1 server
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61035 Polling build filters case sensitive on -C1 server Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-02-10 18:52 Environment: p4-plugin 1.10.10 Jenkins 2.176.1 P4D 2019.2 Priority: Minor Reporter: Karl Wirth Polling build filters are case sensitive when connected to a case insensitive server. For example if the polling build filter is '//depot/sub' submitting '//depot/sub/f1' will be ignored but submitting '//depot/SUB/f1' will trigger a build. Note this behavior on a Linux client. If I create a directory called SUB and sync when connected to a C1 server this is what I see: $ cd SUB $ p4 sync ... //depot/SUB/f10#1 - added as /wsC1/SUB/f10 //depot/sub/f6#1 - added as /wsC1/SUB/f6 //depot/sub/f7#1 - added as /wsC1/SUB/f7 //depot/sub/f9#1 - added as /wsC1/SUB/f9 Note that in depot syntax files in SUB and sub are treated the same. Reproduction Steps: (1) Start a Perforce server with the -C1 flag: p4d -r /p1/1/root -L log -C1 -p 1666 (2) Create a 'jenkins' users in this P4D. (3) Create a workspace on a Linux box and submit the file '//depot/sub/f1'. (4) Create a
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Kyle Manna commented on JENKINS-61020 Re: Allow custom context for commit status Interested in this as well. Provided an example of how I use it and how it worked for Bitbucket on the GitHub PR. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.5620.1581360600169%40Atlassian.JIRA.
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title
Mark Waite edited a comment on JENKINS-27508
Re: Cannot use ENV variable for repository url in Git Publisher
This issue report is specifically about the git publisher within the git plugin. The git publisher is not available in Pipeline. The git publisher is available in Freestyle jobs.* [~qbix], lightweight checkout is not available in Freestyle jobs* [~jlpinardon] git publisher does not perform a fetch and does not work with Pipelines* [~dcarreira] git publisher does not work with PipelinesI'm unable to duplicate the issue as described. Steps I took while trying to duplicate the issue:# Create a Freestyle job with a parameter, {{REPO_URL_FRAGMENT}} with choices MarkEWaite/jenkins-bugs, MarkEWaite/git-client-plugin, MarkEWaite/git-plugin, and MarkEWaite/platformlabeler-plugin# Use git as the SCM in that Freestyle job from repository {{https://github.com//${REPO_URL}}}# Checkout the master branch in that Freestyle job# Enable the "Merge before build" git plugin extension with repository {{origin}}, branch {{master}}, and default settings for merge strategy and fast forward mode# Add a conditional step to the Freestyle job that runs {{ant increment}} if the file {{build.xml}} is found in the workspace# Enable Git Publisher as a Post-build Action, configured to push only if the build succeeds, merge the result to the branch {{master}} with remote named {{origin}}When I perform those steps, the job runs successfully. If I choose the {{REPO_URL_FRAGMENT}} value as {{MarkEWaite/jenkins-bugs}}, the job runs successfully, increments a build number, and pushes the change to the master branch of my jenkins-bugs repository.If I choose the {{REPO_URL_FRAGMENT}} value as something other than {{MarkEWaite/jenkins-bugs}}, the job runs successfully, does not increment a build number, and does not push anything to the master branch of the selected repository. See my job definition for the precise details
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title
Mark Waite edited a comment on JENKINS-27508
Re: Cannot use ENV variable for repository url in Git Publisher
This issue report is specifically about the git publisher within the git plugin. The git publisher is not available in Pipeline. The git publisher is available in Freestyle jobs.* [~qbix], lightweight checkout is not available in Freestyle jobs* [~jlpinardon] git publisher does not perform a fetch and does not work with Pipelines* [~dcarreira] git publisher does not work with PipelinesI'm unable to duplicate the issue as described. Steps I took while trying to duplicate the issue:# Create a Freestyle job with a parameter, {{REPO_URL_FRAGMENT}} with choices MarkEWaite/jenkins-bugs, MarkEWaite/git-client-plugin, MarkEWaite/git-plugin, and MarkEWaite/platformlabeler-plugin# Use git as the SCM in that Freestyle job from repository {{https://github.com//${REPO_URL}}}# Checkout the master branch in that Freestyle job# Enable the "Merge before build" git plugin extension with repository {{origin}}, branch {{master}}, and default settings for merge strategy and fast forward mode# Add a conditional step to the Freestyle job that runs {{ant increment}} if the file {{build.xml}} is found in the workspace# Enable Git Publisher as a Post-build Action, configured to push only if the build succeeds, merge the result to the branch {{master}} with remote named {{origin}}When I perform those steps, the job runs successfully. If I choose the {{REPO_URL_FRAGMENT}} value as {{MarkEWaite/jenkins-bugs}}, the job runs successfully, increments a build number, and pushes the change to the master branch of my jenkins-bugs repository.If I choose the {{REPO_URL_FRAGMENT}} value as something other than {{MarkEWaite/jenkins-bugs}}, the job runs successfully, does not increment a build number, and does not push anything to the master branch of the selected repository.See my job definition for the precise details [^JENKINS-27508-config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-27508) Cannot use ENV variable for repository url in Git Publisher
Title: Message Title
Mark Waite commented on JENKINS-27508
Re: Cannot use ENV variable for repository url in Git Publisher
This issue report is specifically about the git publisher within the git plugin. The git publisher is not available in Pipeline. The git publisher is available in Freestyle jobs.
Maciej Kubiak, lightweight checkout is not available in Freestyle jobs
jlpinardon git publisher does not perform a fetch and does not work with Pipelines
Daniel Carreira git publisher does not work with Pipelines
I'm unable to duplicate the issue as described. Steps I took while trying to duplicate the issue:
Create a Freestyle job with a parameter, REPO_URL_FRAGMENT with choices MarkEWaite/jenkins-bugs, MarkEWaite/git-client-plugin, MarkEWaite/git-plugin, and MarkEWaite/platformlabeler-plugin
Use git as the SCM in that Freestyle job from repository https://github.com//${REPO_URL}
Checkout the master branch in that Freestyle job
Enable the "Merge before build" git plugin extension with repository origin, branch master, and default settings for merge strategy and fast forward mode
Add a conditional step to the Freestyle job that runs ant increment if the file build.xml is found in the workspace
Enable Git Publisher as a Post-build Action, configured to push only if the build succeeds, merge the result to the branch master with remote named origin
When I perform those steps, the job runs successfully. If I choose the REPO_URL_FRAGMENT value as MarkEWaite/jenkins-bugs, the job runs successfully, increments a build number, and pushes the change to the master branch of my jenkins-bugs repository. If I choose the REPO_URL_FRAGMENT value as something other than MarkEWaite/jenkins-bugs, the job runs successfully, does not increment a build number, and does not push anything to the master branch of the selected repository.
Add Comment
[JIRA] (JENKINS-61023) Jenkins slave threads deadlock due to remoting.jar
Title: Message Title Jeff Thompson commented on JENKINS-61023 Re: Jenkins slave threads deadlock due to remoting.jar As described on the page you link to, you'll need to provide further information before anything can be done with this report. There is insufficient here for any action. Things you will need to investigate include: versions used, types of agents used, operations of the different threads, what the agents are doing, etc. Most of the time, issues like this are caused by something external to the Remoting library. These things can be system, network, or configuration. It might be a misbehaving plugin or interaction between multiple plugins. Issues like this usually cannot be addressed without providing a reproducible scenario or sufficient diagnostics. Best of luck in troubleshooting and isolating the problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204496.1581259936000.5590.1581359220118%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake commented on JENKINS-61009 Re: How to use a reference repository in an organization folder? Mark Waite sir thanks for your help now I'm using above option 01 in Jenkinsfile checkout step code and successfully skipping the Default Checkout from GIT-HUB URL. Below is my new Jenkinsfile code after changes. When I'm running a Build in Jenkins Pipeline for the first time only (rather than the first build any other build's Jenkins Console output doesn't show that keyword "Using reference repository".), It's printing the "Using reference repository" statement in the Build's Jenkins Console Output (Jenkins log) as below. Using reference repository: C:/Program Files (x86)/Jenkins/workspace/GIT_REF/WebPortals.git But also in the Jenkins Console output log its printing as "Fetching upstream changes from remote URL" as well. So here my concern is Mr. Mark if we using the reference repository why Jenkins fetching source code still from GIT Remote repository URL ? Fetching upstream changes from g...@github.com:AmilaDevops/WebPortals.git Below is the entire Jenkins Log Console Output for that build. Mr. Mark Waite, So here how can I make sure that Jenkins using my GIT Reference Repository successfully ? Is my Jenkinsfile code (checkout: userRemoteConfigs section) for reference repository is okay? Thanks & Best Regards, Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Amila Gunathilake Attachment: image-2020-02-10-23-47-02-131.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.204479.1581041026000.5585.1581358560416%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Basil Crow commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 I am not aware of anyone who is still using the support for automatic detection. Since it exposes us to security vulnerabilities, it seems better to remove support for automatic detection rather than to inline the UDP broadcast functionality. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204503.1581328352000.5579.1581357960343%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Amila Gunathilake Attachment: image-2020-02-10-23-16-48-189.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.204479.1581041026000.5577.1581356760318%40Atlassian.JIRA.
[JIRA] (JENKINS-47299) Multibranch pipelines with Jenkinsfile in big svn repositories is unusable
Title: Message Title James Reynolds commented on JENKINS-47299 Re: Multibranch pipelines with Jenkinsfile in big svn repositories is unusable This is a blocking issue for us using multi-branch pipelines on subversion as well. A cut-down mirror of the full repository allows the build to proceed in a couple of minutes - but the full repository will cause the build to take nearly 30. Our workaround is to use normal pipelines and fiddle around with BRANCH parameters. It works, but it is significantly more effort. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185721.150722741.5560.1581356040326%40Atlassian.JIRA.
[JIRA] (JENKINS-60913) Remove network discovery services
Title: Message Title Jeff Thompson commented on JENKINS-60913 Re: Remove network discovery services Oleg Nenashev, I'm not sure what you're asking for. You wanted a reference to the ticket Jesse mentioned to also be included in the PR on GitHub? I noticed that you said you were going to do something like that, so I figured you would take care of what you thought was needed. And it was already mentioned here and at least one other place. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204304.158033844.5558.1581355440160%40Atlassian.JIRA.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Brian J Murrell commented on JENKINS-49142 Re: Be able to customize checkout as "options" in declarative pipeline This is sorely needed. It's a pity to see that the PR for it died on the vine. It seems the perfect became the enemy of the good perhaps. In any case, all of the zillions of work-arounds (git command in sh step, scm command in stage steps, etc.) for updating submodules once the per-stage default scm checkout is done don't work if the Dockerfile that the stage is supposed to use for it's agent is in the submodule that needs to be checked-out/updated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187978.1516811382000.5553.1581354780243%40Atlassian.JIRA.
[JIRA] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
Title: Message Title Martin Bickel commented on JENKINS-13632 Re: AbstractMethodError with PTC Integrity Plugin We encountered the same problem in our own plugin that uses mksapi - and were able to solve it. The classloader of Jenkins plugins prefers classes from other plugins or Jenkins core to the classes bundled in the plugin itself, as documented here: https://jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ If the Jenkins installation already contains a different version of org.apache.commons.httpclient.HttpConnection , you get this problem. That's why it's difficult to reproduce in another installation, because it depends on the exact version of plugins installed. We solved it in our plugin by configuring the classloader of our plugin to use its own classes for the given packages. Excerpt from POM.xml org.jenkins-ci.tools maven-hpi-plugin org.apache.commons.httpclient. org.apache.commons.httpclient.auth. org.apache.commons.httpclient.cookie. org.apache.commons.httpclient.methods. org.apache.commons.httpclient.methods.multipart. org.apache.commons.httpclient.protocol. org.apache.commons.httpclient.util. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-60997) Unexpected thread blocking
Title: Message Title Oleg Nenashev commented on JENKINS-60997 Re: Unexpected thread blocking Regarding the issue itself, there is no evidence that the provided thread is blocking anything. It would be great to have a thread dump from the instance Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204465.1580995132000.5544.1581353340418%40Atlassian.JIRA.
[JIRA] (JENKINS-60997) Unexpected thread blocking
Title: Message Title Oleg Nenashev commented on JENKINS-60997 Re: Unexpected thread blocking Владислав Ненашев I doubt that you wanted to attach a screenshot of a private conversation in WhatsApp Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204465.1580995132000.5542.1581353220133%40Atlassian.JIRA.
[JIRA] (JENKINS-61030) Runtime results from UFT to Jenkins Console
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-61030 Runtime results from UFT to Jenkins Console Change By: MANJU GL Attachment: image-2020-02-10-22-02-24-575.png Hi team,i would like to report whats happening in UFT script during runtime to Jenkins consloe output.Example: In my UFT script i have a first step which creates the sales order and it will continue with second step, now i would like to inform jenkins console that sales order is created and sales order number is "1234" and the 2nd step "order fulfilment step is started. is there any method already available which fulfill this functionality? here is the requirement in detail:i am using [hpe-application-automation-tools-plugin |https://github.com/jenkinsci/hpe-application-automation-tools-plugin/blob/latest/doc/README.md]in Jenkins.when i execute the UFT script from jenkins, i get the following console output in jenkins. (refer the screenshot)in this, we will get only a information of whether the testscript is failed/passed. (refer the highlighted section in the below screenshot). this output is not sufficient for me.!image-2020-02-10-22-02-24-575.png!while the execution is going on, i would like to send an intermediate information from UFT to jenkins console to tell what's happening in the script.say an example: In my UFT script, i have a first step which creates the sales order and it will continue with second step, Now i would like to inform jenkins console that sales order is created and sales order number is "1234" and the 2nd step "order fulfilment step is started. this is an intermediate step before the UFT send the execution status (pass/fail) at the end of execution. Add Comment
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title shagun jian commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library Is this feature released? I have the same case. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184658.1503497167000.5515.1581352380844%40Atlassian.JIRA.
[JIRA] (JENKINS-39742) Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException)
Title: Message Title shagun jian commented on JENKINS-39742 Re: Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException) I am also facing this issue, was the fix for NotSerializableException been released? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176327.1479212513000.5506.1581351000480%40Atlassian.JIRA.
[JIRA] (JENKINS-60415) Deleting project does not delete artifacts from S3
Title: Message Title Joe Barker commented on JENKINS-60415 Re: Deleting project does not delete artifacts from S3 This is also something that's impacting us. We're using the Bitbucket Branch Source plugin, and if any of our developers delete a branch from Bitbucket then Jenkins correctly removes the branch but any artifacts would remain in S3. Deleting a build through Jenkins does correctly remove the artifacts from S3, however. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203473.1575952804000.5502.1581348780331%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Nickolas, I had 7 successful builds before the pingThread killed the node during xunit processing when running xunit version 2.3.8-rc831.cbb77af6dfed. Console Output:Console Output: [2020-02-10T13:35:50.172Z] WARNING: XUnitBuilder step is deprecated since 2.x, it has been replaced by XUnitPublisher. This builer will be remove in version 3.x [2020-02-10T13:35:50.175Z] INFO: Starting to record. [2020-02-10T13:35:50.175Z] INFO: Processing GoogleTest-1.8[2020-02-10T13:35:50.250Z] INFO: [GoogleTest-1.8] - 959 test report file(s) were found with the pattern 'j/wr/build/_TestArtifacts*/*.xml' relative to '/home/jenkins/workspace/kb/os' for the testing framework 'GoogleTest-1.8'. Theads related to this aws node i-0b11d0f08d8d59c51: dev-large (i-0b11d0f08d8d59c51) "org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#93] / waiting for EC2 (foo-aws) - dev-large (i-0b11d0f08d8d59c51) id=166000" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) hudson.FilePath.act(FilePath.java:1069) hudson.FilePath.act(FilePath.java:1058) org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:195) org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:159) org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:126) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$339/847132060.run(Unknown Source) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) "Channel reader thread: EC2 (foo-aws) - dev-large (i-0b11d0f08d8d59c51)" daemon prio=5 WAITING java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:502) com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:933) com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:91) hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-61034
Re: retry step is ignored when a timeout happens a timeout
The ugly workaround is to use a try-catch pipeline { agent any stages { stage('Hello') { steps { retry(3){ script { try { timeout(time: 10, unit: 'SECONDS') { sleep 30 } } catch(err) { error("retry this please") } } } } } } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204509.1581344158000.5467.1581345540089%40Atlassian.JIRA.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61034
Re: retry step is ignored when a timeout happens a timeout
The ugly workaround is to use a try-catch {code} pipeline { agent any stages { stage('Hello') { steps {retry(3){script {try { timeout(time: 10, unit: 'SECONDS'){ sleep 30 }} catch(err){ error("retry this please")}}} } } }} {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.204509.1581344158000.5468.1581345540163%40Atlassian.JIRA.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61034
Re: retry step is ignored when a timeout happens a timeout
I was looking for a workaround and I found that catchError does not catch the Abort launched by timeout too, I think that it is the same bug.{code}pipeline { agent any stages { stage(' Hello Test timeout ') { steps {retry(3){catchError(stageResult: 'FAILURE', catchInterruptions: true,) {timeout(time: 10, unit: 'SECONDS'){ sleep 30}}} } } }}{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.204509.1581344158000.5466.1581345480433%40Atlassian.JIRA.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-61034
Re: retry step is ignored when a timeout happens a timeout
I was looking for a workaround and I found that catchError does not catch the Abort launched by timeout too, I think that it is the same bug.
pipeline {
agent any
stages {
stage('Hello') {
steps {
retry(3){
catchError(stageResult: 'FAILURE', catchInterruptions: true,) {
timeout(time: 10, unit: 'SECONDS'){
sleep 30
}
}
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204509.1581344158000.5465.1581345420062%40Atlassian.JIRA.
[JIRA] (JENKINS-60939) Multiple Echo in stage not rendering.
Title: Message Title CHRISTOPHER KELLY closed an issue as Duplicate Jenkins / JENKINS-60939 Multiple Echo in stage not rendering. Change By: CHRISTOPHER KELLY Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204338.1580607014000.5464.1581345120127%40Atlassian.JIRA.
[JIRA] (JENKINS-60939) Multiple Echo in stage not rendering.
Title: Message Title CHRISTOPHER KELLY commented on JENKINS-60939 Re: Multiple Echo in stage not rendering. This is a duplicate of JENKINS-53649 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204338.1580607014000.5463.1581345060054%40Atlassian.JIRA.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61034 Re: retry step is ignored when a timeout happens a timeout I think is related to JENKINS-60354 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204509.1581344158000.5442.1581344400086%40Atlassian.JIRA.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-61034
retry step is ignored when a timeout happens a timeout
Change By:
Ivan Fernandez Calvo
After upgrade to the latest version of the Jenkins core and workflow-basic-steps-plugin, we have detected that the behavior of the retry + timeout steps changes, the following code before the change was retied 3 times, now the job is aborted in the first timeout so the retry is ignored. ``` {code} pipeline { agent any stages { stage('Test timeout') { steps {retry(3){timeout(time: 10, unit: 'SECONDS'){sleep 30}} } } }} ``` {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.
[JIRA] (JENKINS-61034) retry step is ignored when a timeout happens a timeout
Title: Message Title
Ivan Fernandez Calvo created an issue
Jenkins / JENKINS-61034
retry step is ignored when a timeout happens a timeout
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2020-02-10 14:15
Environment:
Jenkins core 2.219 workflow-basic-steps-plugin 2.19
Priority:
Minor
Reporter:
Ivan Fernandez Calvo
After upgrade to the latest version of the Jenkins core and workflow-basic-steps-plugin, we have detected that the behavior of the retry + timeout steps changes, the following code before the change was retied 3 times, now the job is aborted in the first timeout so the retry is ignored. ``` pipeline { agent any stages { stage('Test timeout') { steps { retry(3){ timeout(time: 10, unit: 'SECONDS') { sleep 30 } } } } } } ```
Add Comment
[JIRA] (JENKINS-61030) Runtime results from UFT to Jenkins Console
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-61030 Runtime results from UFT to Jenkins Console Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204504.1581330691000.5439.1581343860399%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Jesse Glick commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 swarm-plugin could either remove support for automatic detection, or simply inline the UDP broadcast functionality if it is still useful in some contexts. I have no idea which is appropriate; a topic for the plugin maintainer. (Basil Crow perhaps?) No, Jenkins core does not use semantic versioning. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204503.1581328352000.5435.1581343560294%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Gabriel Ostrolucký commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 Jenkins doesn't use semantic versioning? Bump to 3.x if you need to do API changes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204503.1581328352000.5429.1581343020141%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Philipp Baer commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 I'd also recommend to adjust swarm-plugin and disable auto detection if that's not supported anymore. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204503.1581328352000.5427.1581342960186%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Jesse Glick commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 CC Jeff Thompson. This removal was deliberate. The fix should be in swarm-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.204503.1581328352000.5423.1581342781252%40Atlassian.JIRA.
[JIRA] (JENKINS-39108) Add recipient exclusion field to email notifications for broken builds
Title: Message Title Alex Earl closed an issue as Won't Do This can be achieved by using a pre-send script to filter email addresses. Jenkins / JENKINS-39108 Add recipient exclusion field to email notifications for broken builds Change By: Alex Earl Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-39904) No email sent when build a submodule
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-39904 No email sent when build a submodule Change By: Alex Earl Assignee: David van Laatum 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.176523.1479722319000.5419.1581342240684%40Atlassian.JIRA.
[JIRA] (JENKINS-39108) Add recipient exclusion field to email notifications for broken builds
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-39108 Add recipient exclusion field to email notifications for broken builds Change By: Alex Earl Assignee: David van Laatum 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.175528.1476883356000.5414.1581342240596%40Atlassian.JIRA.
[JIRA] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Title: Message Title Alex Earl updated JENKINS-14508 Jenkins / JENKINS-14508 Default pre-send script in Jenkins Configuration Change By: Alex Earl Status: In Review 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.145144.134272127.5411.1581342180492%40Atlassian.JIRA.
[JIRA] (JENKINS-61028) Not Able to Send Cucumber Report through Jenkins Email Extension Plugin
Title: Message Title Alex Earl commented on JENKINS-61028 Re: Not Able to Send Cucumber Report through Jenkins Email Extension Plugin How are you configuring the email ext plugin in your job? Usually if you get the message you highlighted it means the mailserver rejected the email. Please see if you can check the logs for the SMTP server you are using. You can also try enabling debug mode for email-ext in the Global Configuration for Jenkins and see if more information is logged. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204502.1581328304000.5405.1581341520300%40Atlassian.JIRA.
