[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Change By: Mark Waite Labels: documentation newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206157.1588958601000.23806.1588958700057%40Atlassian.JIRA.
[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206157.1588958601000.23805.1588958640214%40Atlassian.JIRA.
[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-05-08 17:23 Environment: Git plugin 4.2.2 Labels: newbie-friendly Priority: Minor Reporter: Mark Waite The online reference documentation for the Jenkins Pipeline checkout step is automatically extracted from released plugin online help pages. Several of the fields in the GitSCM online documentation include no description. The following fields are examples of fields that should be described so that readers know how to use them: UserRemoteConfig.credentialsId CGit.repoUrl GogsGit.repoUrl GitSCM.gitTool GitSCM.extensions.GitLFSPull GitSCM.extensions.SparseCheckoutPaths.sparseCheckPaths.path Add help for those fields by following the same naming convention and file placement elsewhere in the plugin. The help files are html files placed in the src/resources directory. See the references option as an example.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title
Mark Waite edited a comment on JENKINS-62195
Re: ec2-1.50.2 doesn't work with SSH <7.5
Yes, Debian Stretch is the current Debian "[oldstable|https://wiki.debian.org/DebianOldStable]" release and is delivering OpenSSH 7.4p1. It is a distribution which the Debian project continues to patch and will continue to patch until the release of [Debian next-stable|https://wiki.debian.org/DebianReleases] ("Bullseye"). No release date has been set for Bullseye. After Bullseye releases, Debian Stretch will stop receiving patches. [~danielbeck] is correct that we'll need to update the Docker base images. That seems like a good topic for the Platform SIG and a good place to reach consensus on labeling patterns and practices. Red Hat 7 and CentOS 7 are also still actively being patched by their maintainers and are delivering OpenSSH 7.4p1. Red Hat Enterprise Linux 7 is slated to be [supported through 2024|https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#Product_life_cycle].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23686.1588947720482%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title
Mark Waite commented on JENKINS-62195
Re: ec2-1.50.2 doesn't work with SSH <7.5
Yes, Debian Stretch is the current Debian "oldstable" release and is delivering OpenSSH 7.4p1. It is a distribution which the Debian project continues to patch and will continue to patch until the release of Debian next-stable ("Bullseye"). No release date has been set for Bullseye. After Bullseye releases, Debian Stretch will stop receiving patches. Red Hat 7 and CentOS 7 are also still actively being patched by their maintainers and are delivering OpenSSH 7.4p1. Red Hat Enterprise Linux 7 is slated to be supported through 2024.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23666.1588946520323%40Atlassian.JIRA.
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Mark Waite Hi,I have upgraded to Jenkins 2.235 and trying to fetch the available plugins. !Plugin list loading.JPG|thumbnail! I can check my proxy is working fine as well I have clicked check now.Even after several minutes the available section is still showing as "Plugin list is loading..." !Plugin list loading 30 minutes.JPG|thumbnail!Could you please help me to resolve as it is blocking whole activity. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206092.158868000.22969.1588800360
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Mark Waite Attachment: Annotation 2020-05-06 145320.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206092.158868000.22941.1588798440185%40Atlassian.JIRA.
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Mark Waite Environment: Jenkins 2.235 with Internet Explorer 11 Linux Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206092.158868000.22965.1588800300197%40Atlassian.JIRA.
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Mark Waite commented on JENKINS-62163 Re: Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." I can confirm the issue with IE 11 and Jenkins 2.235.I can open the "Manage Plugins" page in Internet Explorer 11, download plugin updates, restart Jenkins, and view installed plugins. When I try to view available plugins, it sits with "plugin list is loading". The Available plugins page works well with Microsoft Edge, but fails if I open the page with Internet Explorer 11. In Edge, it looks like this: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206092.158868000.22947.1588798742045%40Atlassian.JIRA.
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Mark Waite Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206092.158868000.22944.1588798680188%40Atlassian.JIRA.
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title Mark Waite edited a comment on JENKINS-62090 Re: Network interfaces and an instance-level security groups may not be specified on the same request I changed the priority on this from "Minor" to "Blocking" because a [Jenkins Security Advisory|https://www.jenkins.io/security/advisory/2020-05-06/] has been published for plugin release prior to 1.50.2 and this issue is visible on ci.jenkins.io with 1.50.2. Downgraded from "Blocking" to "Major" because I resolved the problem on ci.jenkins.io by installing could install [1.49.2|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ec2/1.49.2/ec2-1.49.2.hpi] on ci.jenkins.io rather than 1.50.2. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.22936.1588797960707%40Atlassian.JIRA.
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62090 Network interfaces and an instance-level security groups may not be specified on the same request Change By: Mark Waite Priority: Blocker Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.22931.1588797960625%40Atlassian.JIRA.
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title Mark Waite edited a comment on JENKINS-62090 Re: Network interfaces and an instance-level security groups may not be specified on the same request I changed the priority on this from "Minor" to "Blocking" because a [Jenkins Security Advisory|https://www.jenkins.io/security/advisory/2020-05-06/] has been published for plugin release prior to 1.50.2 and this issue is visible on ci.jenkins.io with 1.50.2 .I resolved the problem on ci.jenkins.io by installing [1.49.2|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ec2/1.49.2/ec2-1.49.2.hpi] rather than 1.50.2. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.22926.1588797420248%40Atlassian.JIRA.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-61515 Git SCM polling fails with skipDefaultCheckout() in pipeline Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205211.1584564029000.22865.1588795680354%40Atlassian.JIRA.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Mark Waite commented on JENKINS-61515 Re: Git SCM polling fails with skipDefaultCheckout() in pipeline Matt G any more information you can share that would allow the issue to be duplicated by me (or others)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205211.1584564029000.22815.1588787460146%40Atlassian.JIRA.
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title Mark Waite commented on JENKINS-62090 Re: Network interfaces and an instance-level security groups may not be specified on the same request I changed the priority on this from "Minor" to "Blocking" because a Jenkins Security Advisory has been published for plugin release prior to 1.50.2 and this issue is visible on ci.jenkins.io with 1.50.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.22809.1588786800240%40Atlassian.JIRA.
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62090 Network interfaces and an instance-level security groups may not be specified on the same request Change By: Mark Waite Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.22802.1588786680410%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Mark Waite edited a comment on JENKINS-26354 Re: First time build does not show changelog > bq. Does the git plugin check for changes using the git commit hash or message?It uses the commit hash. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21177.1588603980579%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Mark Waite commented on JENKINS-26354 Re: First time build does not show changelog > Does the git plugin check for changes using the git commit hash or message? It uses the commit hash. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21173.1588603920627%40Atlassian.JIRA.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?!h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntax * Write documentation for the symbol in the plugin README so that it is available outside of Jenkins h3. Existing Symbol Definitions||JCasC Parent ||JCasC Symbol ||Class Sample ||Symbol Sample |||Col A0 |Col A1 |Col A2 | ||git |branches |branches | ||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||extensions |localBranch|[$class:'LocalBranch', localBranch: '**']|localBranch('**') ||traits |localBranchTrait |N/A (not in a Jenkinsfile) |localBranchTrait |See my [working branch|https://github.com/MarkEWaite/git-plugin/tree/add-localbranch-symbol] for progress.
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Mark Waite updated JENKINS-61357 Was unable to reproduce this on any of my attempts. Jenkins / JENKINS-61357 every time I click the Save button in Configure System Jenkins Crashes Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view th
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Mark Waite updated JENKINS-61357 Jenkins / JENKINS-61357 every time I click the Save button in Configure System Jenkins Crashes Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204942.1583438464000.20547.1588428180412%40Atlassian.JIRA.
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-62132
JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Change By:
Mark Waite
I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead.The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully.Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket. Alternatives to avoid the issue include:* Use CLI git instead of JGit* Use ssh protocol ( {{g...@bitbucket.org:markewaite/bin.git}} ) instead of https protocol ( {{https://markewa...@bitbucket.org/markewaite/bin.git}} )
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62132 JGit won't authenticate to 2FA enabled Bitbucket, CLI git does Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206047.1588282235000.20107.1588282440179%40Atlassian.JIRA.
[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-62132 JGit won't authenticate to 2FA enabled Bitbucket, CLI git does Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2020-04-30 21:30 Environment: Jenkins 2.222.3, git plugin 4.2.2, git client plugin 3.2.1 and pre-release versions from the master branch of the git plugin and git client plugin Priority: Major Reporter: Mark Waite I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead. The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully. Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Mark Waite commented on JENKINS-62078 Re: Jenkins sometimes is not able to index branches That Nonnull message is an expected message that is a result of the transition from the deprecated javax annotations to the spotbugs annotations. Should be unrelated to the issue you are describing. I don't know how to duplicate the problem you're describing. You might check authentication logs on the Bitbucket server or you might enable finer logging for the git plugin and git client plugin and Bitbucket plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19070.1588098840117%40Atlassian.JIRA.
[JIRA] (JENKINS-62078) Jenkins sometimes is not able to index branches
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62078 Jenkins sometimes is not able to index branches Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205981.1588068429000.19065.1588098360145%40Atlassian.JIRA.
[JIRA] (JENKINS-62055) best
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins Jira site is not a location for posting test bugs or links to unrelated domains. Jenkins / JENKINS-62055 best Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit htt
[JIRA] (JENKINS-61881) Jenkins build failing due to failure of creation of docker container(ppwershell failure)
Title: Message Title Mark Waite closed an issue as Cannot Reproduce After almost two weeks without a reply to the request for more information, closing as "Cannot reproduce" Jenkins / JENKINS-61881 Jenkins build failing due to failure of creation of docker container(ppwershell failure) Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, sen
[JIRA] (JENKINS-61347) Checkout problem on a branch
Title: Message Title Mark Waite closed an issue as Not A Defect Please don' t use the Jenkins issue tracker as a question and answer site. The Jenkins.io site provides links to mailing lists and chat channels that can answer your questions. In this specific case, if you're using Git as the SCM, then refer to https://plugins.jenkins.io/git/#checkout-to-specific-local-branch as one way of handling your request. Jenkins / JENKINS-61347 Checkout problem on a branch Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62081 Git tags are not sorted in natural order in multibranch pipeline view Change By: Mark Waite Hi,I'm using multibranch pipeline project and have enabled git behaviour "Discover tags".In the project view, the tags are not sorted in natural order in the tags tab (see attachment), so it's difficult to find the latest tag.Best regards !tag sort.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205987.1588087337000.19054.1588095360311%40Atlassian.JIRA.
[JIRA] (JENKINS-62081) Git tags are not sorted in natural order in multibranch pipeline view
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62081 Git tags are not sorted in natural order in multibranch pipeline view Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205987.1588087337000.19052.1588095300174%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title
Mark Waite edited a comment on JENKINS-62043
Re: EC2 nodes broken
Same issue affected ci.jenkins.io on the upgrade from 1.49.1 to 1.50. Special thanks to [~lifeofguenter] for immediately pointing me to this issue. Much appreciated! We rolled back to 1.49.1 on ci.jenkins.io so that we could return it to production as quickly as possible. We'll plan to remove all EC2 agents at some future time and then upgrade to 1.50 or a newer release.Null pointer exception stack trace was:{noformat}Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: java.lang.NullPointerExceptionApr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.plugins.ec2.EC2AbstractSlave.isAcceptingTasks(EC2AbstractSlave.java:471)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Node.canTake(Node.java:421)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:277)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue.maintain(Queue.java:1634)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$MaintainTask.doRun(Queue.java:2905)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:91)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.lang.Thread.run(Thread.java:834){noformat}
Add Comment
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title Mark Waite commented on JENKINS-62043 Re: EC2 nodes broken Same issue affected ci.jenkins.io on the upgrade from 1.49.1 to 1.50. Special thanks to Gunter Grodotzki for immediately pointing me to this issue. Much appreciated! We rolled back to 1.49.1 on ci.jenkins.io so that we could return it to production as quickly as possible. We'll plan to remove all EC2 agents at some future time and then upgrade to 1.50 or a newer release. Null pointer exception stack trace was: Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: java.lang.NullPointerException Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.plugins.ec2.EC2AbstractSlave.isAcceptingTasks(EC2AbstractSlave.java:471) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Node.canTake(Node.java:421) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:277) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue.maintain(Queue.java:1634) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.model.Queue$MaintainTask.doRun(Queue.java:2905) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:91) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) Apr 28 13:28:36 azure.ci.jenkins.io docker-jenkins[79811]: at java.base/java.lang.Thread.run(Thread.java:834) Add Comment
[JIRA] (JENKINS-61982) jenkins.io docs for 'wait' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61982 jenkins.io docs for 'wait' parameter of pipeline 'build' step are incomplete Change By: Mark Waite Summary: jenkins. . io docs for 'wait' parameter of pipeline 'build' step are incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205872.1587443136000.18698.1588037700072%40Atlassian.JIRA.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?!h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntaxh3. Existing Symbol Definitions||JCasC Parent ||JCasC Symbol ||Class Sample ||Symbol Sample |||Col A0 |Col A1 |Col A2 | ||git |branches |branches | ||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||extensions |localBranch|[$class:'LocalBranch', localBranch: '**']|localBranch('**') ||traits |localBranchTrait |N/A (not in a Jenkinsfile) |localBranchTrait | See my [working branch|https://github.com/MarkEWaite/git-plugin/tree/add-localbranch-symbol] for progress.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title Mark Waite started work on JENKINS-58503 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200643.1563227792000.17844.1587868800196%40Atlassian.JIRA.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?!h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntaxh3. Existing Symbol Definitions ||JCasC Parent ||JCasC Symbol ||Class Sample ||Symbol Sample ||| Col A0 |Col A1 |Col A2 | || git |branches |branches | ||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||extensions |localBranch|[$class:'LocalBranch', localBranch: '**']|localBranch('**') | |traits |localBranchTrait |N/A (not in a Jenkinsfile) |localBranchTrait |
[JIRA] (JENKINS-62052) Default doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62052 Default doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205946.1587819951000.17717.1587821340053%40Atlassian.JIRA.
[JIRA] (JENKINS-62052) Default doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62052 Default doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git Change By: Mark Waite Summary: Defaulf Default doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205946.1587819951000.17716.1587821280064%40Atlassian.JIRA.
[JIRA] (JENKINS-62052) Defaulf doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-62052 Defaulf doGenerateSubmoduleConfigurations: false should not be added by checkout pipeline syntax for git Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2020-04-25 13:05 Environment: git plugin 3.x and later with pipeline plugins Priority: Minor Reporter: Mark Waite When using the Pipeline syntax in a running Jenkins instance, the pipeline fragment generated for git by the checkout step always includes: doGenerateSubmoduleConfigurations: false That is the default value. The pipeline syntax user interface provides no way to change that value and there are no automated tests for a non-default value. doGenerateSubmoduleConfigurations: false should be removed from the pipeline syntax output because it is a default value. Add Comment
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?!h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntax h3. Existing Symbol Definitions||JCasC Parent ||JCasC Symbol ||Class Sample ||Symbol Sample |||Col A0 |Col A1 |Col A2 | ||git |branches |branches | ||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||extensions |localBranch|[$class:'LocalBranch', localBranch: '**']|localBranch('**') |
Add Comment
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?!h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntaxh3. Existing Symbol Definitions||JCasC Parent ||JCasC Symbol ||Class Sample ||Symbol Sample ||| Col A0 |Col A1 |Col A2 | || git |branches |branches | ||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||branches |name |branches: [[name: 'origin/master']] |branches: [[name: 'origin/master']]||extensions |localBranch|[$class:'LocalBranch', localBranch: '**']|localBranch('**') |
Add Comment
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title Mark Waite commented on JENKINS-61998 Re: Jenkins upgrade fails on CentOS - Public key is not installed Constantin Bugneac we'd love to have a pull request from an experienced CentOS / Red Hat user that converts the wiki page into a CentOS / Red Hat section of the installation document. We even have the wiki exporter which can extract the content from the wiki page and propose the ASCIIDoc content as a beginning. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205889.1587495153000.17653.1587768960260%40Atlassian.JIRA.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?! h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntax
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61982) jenkins..io docs for 'wait' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61982 jenkins..io docs for 'wait' parameter of pipeline 'build' step are incomplete Change By: Mark Waite Summary: jenkins..io docs for ' waite wait ' parameter of pipeline 'build' step are incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205872.1587443136000.16216.1587601440069%40Atlassian.JIRA.
[JIRA] (JENKINS-62023) Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62023 Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2592 62023 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62023) Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-62023 Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205242.1584621529000.16201.1587596400351%40Atlassian.JIRA.
[JIRA] (JENKINS-62022) Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-62022 Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205243.1584621563000.16196.1587596340201%40Atlassian.JIRA.
[JIRA] (JENKINS-62022) Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62022 Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2591 62022 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62021) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-62021 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205251.1584621682000.16191.1587596280336%40Atlassian.JIRA.
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62020 Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205254.1584621792000.16186.1587596220307%40Atlassian.JIRA.
[JIRA] (JENKINS-62021) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62021 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2590 62021 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62020 Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205254.1584621792000.16184.1587596160498%40Atlassian.JIRA.
[JIRA] (JENKINS-62020) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62020 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2589 62020 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62017 Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205265.1584621968000.16179.1587596040470%40Atlassian.JIRA.
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62017 Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205265.1584621968000.16177.1587596040445%40Atlassian.JIRA.
[JIRA] (JENKINS-62019) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62019 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2588 62019 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205247.1584621644000.16172.1587595920210%40Atlassian.JIRA.
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62018 Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205255.1584621821000.16168.1587595864370%40Atlassian.JIRA.
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2587 62018 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received th
[JIRA] (JENKINS-62018) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62018 Jenkins / JENKINS-62018 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205255.1584621821000.16170.1587595864468%40Atlassian.JIRA.
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62016 Jenkins / JENKINS-62016 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205911.158759559.16162.1587595800162%40Atlassian.JIRA.
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite updated JENKINS-62016 Jenkins / JENKINS-62016 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205911.158759559.16163.1587595800210%40Atlassian.JIRA.
[JIRA] (JENKINS-62017) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-62017 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2586 62017 Workflow: classic default workflow JNJira + In-Review Component/s: git-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received th
[JIRA] (JENKINS-62016) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title
Mark Waite created an issue
Jenkins / JENKINS-62016
Parameter is not interpreted in GIT Plugin Branch Specifier
Issue Type:
Bug
Assignee:
Unassigned
Components:
git-plugin
Created:
2020-04-22 22:46
Environment:
Git plugin 4.2.2
Priority:
Minor
Reporter:
Mark Waite
I have a pipeline with one branch to be build, it's a paramterized pipeline: refs/tags/${BuildTag} The BuildTag gets not interpreted anymore:
hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune -- origin +refs/tags/${BuildTag}:refs/remotes/origin/${BuildTag}" returned status code 128:
stdout:
stderr: fatal: Couldn't find remote ref refs/tags/${BuildTag}
fatal: the remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:569)
at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:361)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:115)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303)
at hudson.model.ResourceController.execute(ResourceContr
[JIRA] (JENKINS-61568) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-61568 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205265.1584621968000.16153.1587594720197%40Atlassian.JIRA.
[JIRA] (JENKINS-61568) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61568 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205265.1584621968000.16155.1587594720228%40Atlassian.JIRA.
[JIRA] (JENKINS-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Mark Waite updated JENKINS-49349 May be due to not having configured the job to prune stale branches. If prune stale branches is not enabled in the job, then the local workspace will retain branches that no longer exist on the master. Jenkins / JENKINS-49349 git scm plugin attempts to checkout stale SHAs Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Mark Waite updated JENKINS-49349 Jenkins / JENKINS-49349 git scm plugin attempts to checkout stale SHAs Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188214.1517595371000.15477.1587529860951%40Atlassian.JIRA.
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61982
jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Change By:
Mark Waite
The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the {{wait}} argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the {{wait}} argument.It is not clear to me why that page of details is included for the online help of the {{wait}} argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument?The help page for the {{wait}} parameter of the pipeline step {{build}} inside a running Jenkins server looks like this: !screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png|thumbnail! When viewed on [jenkins.io|https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job], the section for parameter {{wait}} is + empty + of any description.I assume the reason it is empty of https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the [source code|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy] to see the implementation.Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects *exactly* the versions they are running.
Add Comment
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61982
jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Change By:
Mark Waite
The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the {{wait}} argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the {{wait}} argument.It is not clear to me why that page of details is included for the online help of the {{wait}} argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument?The help page for the {{wait}} parameter of the pipeline step {{build}} inside a running Jenkins server looks like this: !screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png|thumbnail! When viewed on [jenkins.io|https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job], the section for parameter {{wait}} is +empty+ of any description.I assume the reason it is empty of on https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the [source code|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy] to see the implementation.Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects *exactly* the versions they are running.
Add Comment
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61982 jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete Issue Type: Bug Assignee: Unassigned Attachments: screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png Components: pipeline-build-step-plugin Created: 2020-04-21 04:25 Environment: Jenkins 2.222.1. pipeline build step plugin 2.12 Priority: Minor Reporter: Mark Waite The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the wait argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the wait argument. It is not clear to me why that page of details is included for the online help of the wait argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument? The help page for the wait parameter of the pipeline step build inside a running Jenkins server looks like this:When viewed on jenkins.io, the section for parameter wait is empty of any description. I assume the reason it is empty of https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the source code to see the implementation. Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects exactly the versions they are running
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61850 TFS pull request verification build uses wrong branch Change By: Mark Waite Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.14405.1587436500238%40Atlassian.JIRA.
[JIRA] (JENKINS-61922) Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Closing as cannot reproduce. If you can provide instructions that others can use to consistently duplicate the problem, please provide them and reopen the issue. Jenkins / JENKINS-61922 Invoking another pipeline job from pipeline throws ClosedChannelException at end. Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-60903) Include information about number of CPUs and memory in the node view
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60903 Include information about number of CPUs and memory in the node view Change By: Mark Waite A node property can display additional information in a dedicated jelly.We could use this to display additional information like number of CPUs and installed memory for the machines which are fetched when getting the OS information. We could also include that additional information in the automatically generated labels for the agent. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204294.1580302479000.14400.1587436260222%40Atlassian.JIRA.
[JIRA] (JENKINS-49362) Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols
Title: Message Title Mark Waite commented on JENKINS-49362 Re: Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols Jenkins now also supports JDK 11. AdoptOpenJDK 11 on z390x provides a just in time compiler that should provide good performance with Jenkins without the requirement to upgrade okhttp to a newer version in the various Jenkins components. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188229.1517798676000.14330.1587422400186%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title
Mark Waite edited a comment on JENKINS-53004
Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Yes [~ciscokid], that is the message that happens when a plugin (like git plugin 3.x) attempts to access a method {{getRef}} that no longer exists in the JGit implementation that is bundled with git client plugin 3.x. Git plugin * 4.x * must be used with git client plugin * 3.x * . Git plugin 3.x is * not * intended to be used with git client plugin 3.x. Upgrading the called plugin (git client) from 2 to 3 without upgrading the callers (git plugin from 3 to 4 , git server plugin, GitHub branch source, Gitea, Bitbucket, etc.) can lead to that error.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192990.1534144468000.13811.1587306960356%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite commented on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Yes steven dillon, that is the message that happens when a plugin (like git plugin 3.x) attempts to access a method getRef that no longer exists in the JGit implementation that is bundled with git client plugin 3.x. Git plugin 4.x must be used with git client plugin 3.x. Git plugin 3.x is not intended to be used with git client plugin 3.x. Upgrading the called plugin (git client) without upgrading the callers (git plugin, git server plugin, GitHub branch source, Gitea, Bitbucket, etc.) can lead to that error. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192990.1534144468000.13779.158730258%40Atlassian.JIRA.
[JIRA] (JENKINS-44408) Java.IO.Exception : Invalid encoded sequence encountered
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44408 Java.IO.Exception : Invalid encoded sequence encountered Change By: Mark Waite Component/s: ssh-slaves-plugin Component/s: ssh-agent-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182234.149544320.13765.1587298860191%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61711 Git plugin global config incorrectly reports git not in PATH Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.13763.1587298260409%40Atlassian.JIRA.
[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator
Title: Message Title Mark Waite updated JENKINS-61869 Jenkins / JENKINS-61869 Prune tags during fetch shown incorrectly in pipeline syntax generator Change By: Mark Waite Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205734.1586535653000.13761.1587298260377%40Atlassian.JIRA.
[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes
Title: Message Title Mark Waite updated JENKINS-61870 Jenkins / JENKINS-61870 Git plugin UI transition for shallow clone needs more changes Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205735.1586539743000.13669.1587241560427%40Atlassian.JIRA.
[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test
Title: Message Title Mark Waite updated JENKINS-61871 Jenkins / JENKINS-61871 Prune stale tags does not prune stale tags in my docker test Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205736.1586541813000.13666.1587241560362%40Atlassian.JIRA.
[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test
Title: Message Title Mark Waite updated JENKINS-61871 Jenkins / JENKINS-61871 Prune stale tags does not prune stale tags in my docker test Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205736.1586541813000.13668.1587241560391%40Atlassian.JIRA.
[JIRA] (JENKINS-57720) Legacy pipeline library definition not supported by JCasC
Title: Message Title Mark Waite updated JENKINS-57720 Jenkins / JENKINS-57720 Legacy pipeline library definition not supported by JCasC Change By: Mark Waite Status: Fixed but Unreleased Closed Released As: configuration as code plugin 1.22 and later Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199663.1559067514000.13663.1587241320103%40Atlassian.JIRA.
[JIRA] (JENKINS-60489) beta forensics plugin reports no class def found for FilteredLog
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-60489 beta forensics plugin reports no class def found for FilteredLog Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203578.1576439299000.13662.1587241140393%40Atlassian.JIRA.
[JIRA] (JENKINS-60565) Null pointer exception in analysis beta plugin loading ResultAction
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-60565 Null pointer exception in analysis beta plugin loading ResultAction Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203674.1576889148000.13660.1587241140370%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 Web site is updated and redirect works. Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.13657.1587241080335%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated JENKINS-61597 Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Released As: platformlabeler 6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.12866.1587081420169%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.12867.1587081420422%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 My mistake, should not be closed until the fix is released in a new Jenkins version Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12749.1587069420569%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 Confirmed that the link now briefly shows a working redirect and then shows the destination of the redirect. Thanks for the speedy resolution! Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an e
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12654.1587056580435%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Summary: "Learn more" link from new "Welcome" page is a broken redireect redirect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12647.1587055380148%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61932
"Learn more" link from new "Welcome" page is a broken redireect
Change By:
Mark Waite
The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page.Steps to duplicate the problem:# Download and run Jenkins 2.231 {{$ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231}}# Install plugins including the ssh build agents plugin# Confirm the welcome page appears# Click the "Learn more" link on the welcome page !screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png|thumbnail! # Browser will open https://jenkins.io/redirects/distributed-builds !screencapture- testing jenkins - a io - markwaite redirects - net distributed - 8080 builds -2020-04-16- 09_10_01-edit 09_18_10 .png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Gro
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Change By: Mark Waite Attachment: screencapture-jenkins-io-redirects-distributed-builds-2020-04-16-09_18_10.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12560.1587050340106%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61932
"Learn more" link from new "Welcome" page is a broken redireect
Change By:
Mark Waite
The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page.Steps to duplicate the problem:# Download and run Jenkins 2.231 {{$ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231}}# Install plugins including the ssh build agents plugin# Confirm the welcome page appears# Click the "Learn more" link on the welcome page # Browser will open https://jenkins.io/redirects/distributed-builds!screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroup
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Issue Type: Bug Assignee: Unassigned Attachments: screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png Components: core Created: 2020-04-16 15:16 Environment: Jenkins 2.231 Priority: Minor Reporter: Mark Waite The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page. Steps to duplicate the problem: Download and run Jenkins 2.231 $ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231 Install plugins including the ssh build agents plugin Confirm the welcome page appears Click the "Learn more" link on the welcome page
[JIRA] (JENKINS-46302) Unable to load class once the loading was interrupted
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-46302 Unable to load class once the loading was interrupted Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184556.1503101922000.12180.1586982300256%40Atlassian.JIRA.
