[jira] [Updated] (YETUS-1243) website docs rsync is wrong
[ https://issues.apache.org/jira/browse/YETUS-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1243: Fix Version/s: 0.16.0 > website docs rsync is wrong > --- > > Key: YETUS-1243 > URL: https://issues.apache.org/jira/browse/YETUS-1243 > Project: Yetus > Issue Type: Bug > Components: build, website and documentation >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > that rsync will pull in extra stuff now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1242) release/initial-patches main branch is broken
[ https://issues.apache.org/jira/browse/YETUS-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1242: Fix Version/s: 0.16.0 > release/initial-patches main branch is broken > - > > Key: YETUS-1242 > URL: https://issues.apache.org/jira/browse/YETUS-1242 > Project: Yetus > Issue Type: Bug >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > it doesn't make something that can be easily cherry-picked or merged in > without leaving a merge message unless a rebase is done later. :( -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1243) website docs rsync is wrong
[ https://issues.apache.org/jira/browse/YETUS-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1243: Affects Version/s: 0.15.0 > website docs rsync is wrong > --- > > Key: YETUS-1243 > URL: https://issues.apache.org/jira/browse/YETUS-1243 > Project: Yetus > Issue Type: Bug > Components: build, website and documentation >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > > that rsync will pull in extra stuff now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1240) sed in update-doc-versions.sh not BSD compatible
[ https://issues.apache.org/jira/browse/YETUS-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1240: Fix Version/s: 0.16.0 > sed in update-doc-versions.sh not BSD compatible > > > Key: YETUS-1240 > URL: https://issues.apache.org/jira/browse/YETUS-1240 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > sed fails with "command a expects \ followed by text" because it is not > BSD-compatible (e.g., macOS) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1241: Affects Version/s: 0.15.0 > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1241: Fix Version/s: 0.16.0 > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1242) release/initial-patches main branch is broken
[ https://issues.apache.org/jira/browse/YETUS-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1242: Affects Version/s: 0.15.0 > release/initial-patches main branch is broken > - > > Key: YETUS-1242 > URL: https://issues.apache.org/jira/browse/YETUS-1242 > Project: Yetus > Issue Type: Bug >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > > it doesn't make something that can be easily cherry-picked or merged in > without leaving a merge message unless a rebase is done later. :( -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1244) yetus-homebrew tests are failing
[
https://issues.apache.org/jira/browse/YETUS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-1244:
Affects Version/s: 0.15.0
> yetus-homebrew tests are failing
>
>
> Key: YETUS-1244
> URL: https://issues.apache.org/jira/browse/YETUS-1244
> Project: Yetus
> Issue Type: Bug
> Components: build
>Affects Versions: 0.15.0
>Reporter: Allen Wittenauer
>Priority: Major
>
> Looks like homebrew has gotten more aggressive with EOLing versions of macOS:
> {code}
> Error: You are using macOS 11.
> We (and Apple) do not provide support for this old version.
> It is expected behaviour that some formulae will fail to build in this old
> version.
> It is expected behaviour that Homebrew will be buggy and slow.
> Do not create any issues about this on Homebrew's GitHub repositories.
> Do not create any issues even if you think this message is unrelated.
> Any opened issues will be immediately closed without response.
> Do not ask for help from Homebrew or its maintainers on social media.
> You may ask for help in Homebrew's discussions but are unlikely to receive a
> response.
> Try to figure out the problem yourself and submit a fix as a pull request.
> We will review it but may or may not accept it.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1244) yetus-homebrew tests are failing
[
https://issues.apache.org/jira/browse/YETUS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-1244:
Fix Version/s: 0.16.0
> yetus-homebrew tests are failing
>
>
> Key: YETUS-1244
> URL: https://issues.apache.org/jira/browse/YETUS-1244
> Project: Yetus
> Issue Type: Bug
> Components: build
>Affects Versions: 0.15.0
>Reporter: Allen Wittenauer
>Priority: Major
> Fix For: 0.16.0
>
>
> Looks like homebrew has gotten more aggressive with EOLing versions of macOS:
> {code}
> Error: You are using macOS 11.
> We (and Apple) do not provide support for this old version.
> It is expected behaviour that some formulae will fail to build in this old
> version.
> It is expected behaviour that Homebrew will be buggy and slow.
> Do not create any issues about this on Homebrew's GitHub repositories.
> Do not create any issues even if you think this message is unrelated.
> Any opened issues will be immediately closed without response.
> Do not ask for help from Homebrew or its maintainers on social media.
> You may ask for help in Homebrew's discussions but are unlikely to receive a
> response.
> Try to figure out the problem yourself and submit a fix as a pull request.
> We will review it but may or may not accept it.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (YETUS-1244) yetus-homebrew tests are failing
Allen Wittenauer created YETUS-1244:
---
Summary: yetus-homebrew tests are failing
Key: YETUS-1244
URL: https://issues.apache.org/jira/browse/YETUS-1244
Project: Yetus
Issue Type: Bug
Components: build
Reporter: Allen Wittenauer
Looks like homebrew has gotten more aggressive with EOLing versions of macOS:
{code}
Error: You are using macOS 11.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old
version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a
response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 7:04 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the GCR container build more than the CDN push which may take hours * fix draft announcement * docs must _absolutely_ be built before main merge so that that release version gets a proper documentation/xxx directory was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the GCR container build more than the CDN push which may take hours * fix draft announcement > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1243) website docs rsync is wrong
Allen Wittenauer created YETUS-1243: --- Summary: website docs rsync is wrong Key: YETUS-1243 URL: https://issues.apache.org/jira/browse/YETUS-1243 Project: Yetus Issue Type: Bug Components: build, website and documentation Reporter: Allen Wittenauer that rsync will pull in extra stuff now -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 6:06 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the GCR container build more than the CDN push which may take hours * fix draft announcement was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the GCR container build more than the CDN push which may take hours * > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 5:37 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the GCR container build more than the CDN push which may take hours * was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the container build more than the CDN push which may take hours * > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 5:35 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge * Need to wait for the container build more than the CDN push which may take hours * was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 5:33 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` * delete xxx-main branch after above merge was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 5:30 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main -main merge: ``` git checkout (branch) .mvn/maven.config git commit -S -m 'YETUS-. Bump main version to 0.xx.0-SNAPSHOT' ``` was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1242) release/initial-patches main branch is broken
Allen Wittenauer created YETUS-1242: --- Summary: release/initial-patches main branch is broken Key: YETUS-1242 URL: https://issues.apache.org/jira/browse/YETUS-1242 Project: Yetus Issue Type: Bug Reporter: Allen Wittenauer it doesn't make something that can be easily cherry-picked or merged in without leaving a merge message unless a rebase is done later. :( -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer edited comment on YETUS-1241 at 12/2/23 5:11 AM: -- * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag * no more staging branch * no more merge of staging branch into main was (Author: aw): * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1241) post-release 0.15.0 docs
[ https://issues.apache.org/jira/browse/YETUS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792324#comment-17792324 ] Allen Wittenauer commented on YETUS-1241: - * specifically mention the vote thread should be finished off before proceeding. * core release tasks: git commit of update-release-docs should be signed. * tag main not a specific commit * fix the commit message for the tag > post-release 0.15.0 docs > > > Key: YETUS-1241 > URL: https://issues.apache.org/jira/browse/YETUS-1241 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Priority: Major > > fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1241) post-release 0.15.0 docs
Allen Wittenauer created YETUS-1241: --- Summary: post-release 0.15.0 docs Key: YETUS-1241 URL: https://issues.apache.org/jira/browse/YETUS-1241 Project: Yetus Issue Type: Bug Reporter: Allen Wittenauer fixes post the release of 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1240) sed in update-doc-versions.sh not BSD compatible
Allen Wittenauer created YETUS-1240: --- Summary: sed in update-doc-versions.sh not BSD compatible Key: YETUS-1240 URL: https://issues.apache.org/jira/browse/YETUS-1240 Project: Yetus Issue Type: Bug Components: build Affects Versions: 0.15.0 Reporter: Allen Wittenauer sed fails with "command a expects \ followed by text" because it is not BSD-compatible (e.g., macOS) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1239) post-0.15.0 doc updates
[ https://issues.apache.org/jira/browse/YETUS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785974#comment-17785974 ] Allen Wittenauer edited comment on YETUS-1239 at 11/14/23 8:21 PM: --- * Move verify changelog and release notes to be before the work in git. * Since the tag branch is getting merged in early, you should checkout from main not from YETUS-xxx-release. * That also means the tag happens inside main, which I don't think is documented correctly. was (Author: aw): * Move verify changelog and release notes to be before the work in git. * Since the tag branch is getting merged in early, you should checkout from main not from YETUS-xxx-release. > post-0.15.0 doc updates > --- > > Key: YETUS-1239 > URL: https://issues.apache.org/jira/browse/YETUS-1239 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > needed updates to docs from aftermath of 0.15.0 release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1239) post-0.15.0 doc updates
[ https://issues.apache.org/jira/browse/YETUS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1239: Fix Version/s: 0.16.0 > post-0.15.0 doc updates > --- > > Key: YETUS-1239 > URL: https://issues.apache.org/jira/browse/YETUS-1239 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.16.0 > > > needed updates to docs from aftermath of 0.15.0 release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1239) post-0.15.0 doc updates
[ https://issues.apache.org/jira/browse/YETUS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785974#comment-17785974 ] Allen Wittenauer commented on YETUS-1239: - * Move verify changelog and release notes to be before the work in git. * Since the tag branch is getting merged in early, you should checkout from main not from YETUS-xxx-release. > post-0.15.0 doc updates > --- > > Key: YETUS-1239 > URL: https://issues.apache.org/jira/browse/YETUS-1239 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > > needed updates to docs from aftermath of 0.15.0 release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1239) post-0.15.0 doc updates
Allen Wittenauer created YETUS-1239: --- Summary: post-0.15.0 doc updates Key: YETUS-1239 URL: https://issues.apache.org/jira/browse/YETUS-1239 Project: Yetus Issue Type: Improvement Components: website and documentation Affects Versions: 0.15.0 Reporter: Allen Wittenauer needed updates to docs from aftermath of 0.15.0 release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1237) Release 0.15.0
[ https://issues.apache.org/jira/browse/YETUS-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1237. - Resolution: Fixed > Release 0.15.0 > -- > > Key: YETUS-1237 > URL: https://issues.apache.org/jira/browse/YETUS-1237 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1238) Add code to test gpg signing in initial-patches
[ https://issues.apache.org/jira/browse/YETUS-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1238. - Resolution: Fixed Thanks [~ndimiduk] for the review. merged > Add code to test gpg signing in initial-patches > --- > > Key: YETUS-1238 > URL: https://issues.apache.org/jira/browse/YETUS-1238 > Project: Yetus > Issue Type: Improvement > Components: build >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Test GPG signing prior to doing any work to help debug any broken setups. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1181) post-0.14.0 release doc updates
[jira] [Created] (YETUS-1238) Add code to test gpg signing in initial-patches
Allen Wittenauer created YETUS-1238: --- Summary: Add code to test gpg signing in initial-patches Key: YETUS-1238 URL: https://issues.apache.org/jira/browse/YETUS-1238 Project: Yetus Issue Type: Improvement Components: build Affects Versions: 0.15.0 Reporter: Allen Wittenauer Assignee: Allen Wittenauer Fix For: 0.15.0 Test GPG signing prior to doing any work to help debug any broken setups. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1237) Release 0.15.0
Allen Wittenauer created YETUS-1237: --- Summary: Release 0.15.0 Key: YETUS-1237 URL: https://issues.apache.org/jira/browse/YETUS-1237 Project: Yetus Issue Type: Bug Components: build Affects Versions: 0.15.0 Reporter: Allen Wittenauer Assignee: Allen Wittenauer Fix For: 0.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1236) Publish a `latest` tag for the docker image
[
https://issues.apache.org/jira/browse/YETUS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775399#comment-17775399
]
Allen Wittenauer commented on YETUS-1236:
-
We do document that: https://yetus.apache.org/yetus-docker-image/
Setting up 'latest' will absolutely break people in surprising ways. They
might as well use 'main' if they want the rug pulled out from underneath them.
> Publish a `latest` tag for the docker image
> ---
>
> Key: YETUS-1236
> URL: https://issues.apache.org/jira/browse/YETUS-1236
> Project: Yetus
> Issue Type: Task
>Reporter: Nick Dimiduk
>Priority: Major
>
> Trying to do a quick thing with the docker image, I was confused by the error
> response {{docker: Error response from daemon: manifest unknown.}} I
> eventually realized that I wasn't explicitly providing an image tag, and so
> of course an image could not be resolved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (YETUS-1236) Publish a `latest` tag for the docker image
[
https://issues.apache.org/jira/browse/YETUS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17771970#comment-17771970
]
Allen Wittenauer commented on YETUS-1236:
-
A long time ago (I'll have to dig later where) we decided against not doing a
latest tag because it is ambiguous. latest officially means "last built." But
for a repo, last built of what exactly? Is it the last stable release? Is it
the last commit on the main branch? By not having a latest, we force people to
pick and be aware of what it is they are grabbing.
> Publish a `latest` tag for the docker image
> ---
>
> Key: YETUS-1236
> URL: https://issues.apache.org/jira/browse/YETUS-1236
> Project: Yetus
> Issue Type: Task
>Reporter: Nick Dimiduk
>Priority: Major
>
> Trying to do a quick thing with the docker image, I was confused by the error
> response {{docker: Error response from daemon: manifest unknown.}} I
> eventually realized that I wasn't explicitly providing an image tag, and so
> of course an image could not be resolved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1232) Periodically rebuild container images
[ https://issues.apache.org/jira/browse/YETUS-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1232: Fix Version/s: 0.15.0 > Periodically rebuild container images > - > > Key: YETUS-1232 > URL: https://issues.apache.org/jira/browse/YETUS-1232 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Nick Dimiduk >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > I'm picking up Yetus for a new repo in HBase and while I sit here waiting on > my own image to build, I realised that Yetus images are stale. Starting from > `yetus-base:0.14.1`, I have loads of packages to update. Since we expect > users to be pulling these images directly, I think we should be explicitly > calling `apt-get update && apt-get upgrade` and rebuild on a timer. I propose > a weekly cadence, but almost anything will do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1219) Yetus DOAP file has a parsing error
[
https://issues.apache.org/jira/browse/YETUS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved YETUS-1219.
-
Fix Version/s: 0.15.0
Resolution: Fixed
> Yetus DOAP file has a parsing error
> ---
>
> Key: YETUS-1219
> URL: https://issues.apache.org/jira/browse/YETUS-1219
> Project: Yetus
> Issue Type: Bug
>Affects Versions: 0.14.1
>Reporter: Claude Warren
>Assignee: Allen Wittenauer
>Priority: Minor
> Fix For: 0.15.0
>
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 25, col: 6 ] \{E201} The attributes on this property element, are not
> permitted with any content; expecting end element tag.
> [1] http://yetus.apache.org/doap_yetus.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1219) Yetus DOAP file has a parsing error
[
https://issues.apache.org/jira/browse/YETUS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-1219:
Component/s: website and documentation
> Yetus DOAP file has a parsing error
> ---
>
> Key: YETUS-1219
> URL: https://issues.apache.org/jira/browse/YETUS-1219
> Project: Yetus
> Issue Type: Bug
> Components: website and documentation
>Affects Versions: 0.14.1
>Reporter: Claude Warren
>Assignee: Allen Wittenauer
>Priority: Minor
> Fix For: 0.15.0
>
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 25, col: 6 ] \{E201} The attributes on this property element, are not
> permitted with any content; expecting end element tag.
> [1] http://yetus.apache.org/doap_yetus.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1212) upgrade github workflows checkout@v2 and upload-artifact@v2
[ https://issues.apache.org/jira/browse/YETUS-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1212: Fix Version/s: (was: 0.15.0) > upgrade github workflows checkout@v2 and upload-artifact@v2 > --- > > Key: YETUS-1212 > URL: https://issues.apache.org/jira/browse/YETUS-1212 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Allen Wittenauer >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1181) post-0.14.0 release doc updates
[ https://issues.apache.org/jira/browse/YETUS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764237#comment-17764237 ] Allen Wittenauer commented on YETUS-1181: - part 1 committed (thanks [~ndimiduk]!): * mailing lists converted to lists.apache.org * 24 hour changed to 1 hour * Marketplace topics changed (Code Quality and Code Review now) left to do: * release branch first * release tag merge into main * freeze main branch > post-0.14.0 release doc updates > --- > > Key: YETUS-1181 > URL: https://issues.apache.org/jira/browse/YETUS-1181 > Project: Yetus > Issue Type: Improvement > Components: build >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Updates to the release documentation post-0.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-294) release-doc-maker fails if some custom fields aren't defined on JIRA
[
https://issues.apache.org/jira/browse/YETUS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reassigned YETUS-294:
--
Assignee: (was: Allen Wittenauer)
> release-doc-maker fails if some custom fields aren't defined on JIRA
>
>
> Key: YETUS-294
> URL: https://issues.apache.org/jira/browse/YETUS-294
> Project: Yetus
> Issue Type: Bug
> Components: Release Doc Maker
>Reporter: Kengo Seki
>Priority: Major
>
> YETUS-282 enables release-doc-maker to support JIRAs other than ASF's, but if
> these JIRAs don't have custom fields such as "Hadoop Flags", "Flags" and
> "Release Note", it will fail.
> Examples using a local JIRA server:
> {code}
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 572, in main
> if jira.get_incompatible_change():
> File "release-doc-maker/releasedocmaker.py", line 284, in
> get_incompatible_change
> field = self.parent.field_id_map['Hadoop Flags']
> KeyError: 'Hadoop Flags'
> (after the 'Hadoop Flags' field is defined)
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 574, in main
> elif jira.get_important():
> File "release-doc-maker/releasedocmaker.py", line 298, in get_important
> field = self.parent.field_id_map['Flags']
> KeyError: 'Flags'
> (after the 'Flags' field is defined)
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 628, in main
> if len(jira.get_release_note()) > 0:
> File "release-doc-maker/releasedocmaker.py", line 216, in get_release_note
> field = self.parent.field_id_map['Release Note']
> KeyError: 'Release Note'
> {code}
> Maybe we can assume that the "Release Note" field is defined because it's
> vital for release-doc-making, but it'd be better that dependencies on other
> two custom fields are removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-294) release-doc-maker fails if some custom fields aren't defined on JIRA
[
https://issues.apache.org/jira/browse/YETUS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-294:
---
Fix Version/s: (was: 0.15.0)
> release-doc-maker fails if some custom fields aren't defined on JIRA
>
>
> Key: YETUS-294
> URL: https://issues.apache.org/jira/browse/YETUS-294
> Project: Yetus
> Issue Type: Bug
> Components: Release Doc Maker
>Reporter: Kengo Seki
>Assignee: Allen Wittenauer
>Priority: Major
>
> YETUS-282 enables release-doc-maker to support JIRAs other than ASF's, but if
> these JIRAs don't have custom fields such as "Hadoop Flags", "Flags" and
> "Release Note", it will fail.
> Examples using a local JIRA server:
> {code}
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 572, in main
> if jira.get_incompatible_change():
> File "release-doc-maker/releasedocmaker.py", line 284, in
> get_incompatible_change
> field = self.parent.field_id_map['Hadoop Flags']
> KeyError: 'Hadoop Flags'
> (after the 'Hadoop Flags' field is defined)
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 574, in main
> elif jira.get_important():
> File "release-doc-maker/releasedocmaker.py", line 298, in get_important
> field = self.parent.field_id_map['Flags']
> KeyError: 'Flags'
> (after the 'Flags' field is defined)
> [sekikn@mobile yetus]$ release-doc-maker/releasedocmaker.py --project test
> --version 0.1.0 --baseurl http://localhost:8080
> Traceback (most recent call last):
> File "release-doc-maker/releasedocmaker.py", line 698, in
> main()
> File "release-doc-maker/releasedocmaker.py", line 628, in main
> if len(jira.get_release_note()) > 0:
> File "release-doc-maker/releasedocmaker.py", line 216, in get_release_note
> field = self.parent.field_id_map['Release Note']
> KeyError: 'Release Note'
> {code}
> Maybe we can assume that the "Release Note" field is defined because it's
> vital for release-doc-making, but it'd be better that dependencies on other
> two custom fields are removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1192) Semaphore CI needs junit in full mode
[ https://issues.apache.org/jira/browse/YETUS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1192: Issue Type: Bug (was: New Feature) > Semaphore CI needs junit in full mode > - > > Key: YETUS-1192 > URL: https://issues.apache.org/jira/browse/YETUS-1192 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Semaphore CI needs junit in full format in order to process the test results. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1178) docker buildx cache clearing
[ https://issues.apache.org/jira/browse/YETUS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1178: Issue Type: New Feature (was: Improvement) > docker buildx cache clearing > > > Key: YETUS-1178 > URL: https://issues.apache.org/jira/browse/YETUS-1178 > Project: Yetus > Issue Type: New Feature > Components: Precommit >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > test-patch docker tools should also process the buildx cache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1189) audit temporary files and dirs to use mktemp
[ https://issues.apache.org/jira/browse/YETUS-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1189: Fix Version/s: (was: 0.15.0) > audit temporary files and dirs to use mktemp > > > Key: YETUS-1189 > URL: https://issues.apache.org/jira/browse/YETUS-1189 > Project: Yetus > Issue Type: Improvement > Components: build, Precommit >Reporter: Allen Wittenauer >Priority: Major > > See discussion in https://github.com/apache/yetus-homebrew/pull/6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1178) docker buildx cache clearing
[ https://issues.apache.org/jira/browse/YETUS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1178: Fix Version/s: 0.15.0 > docker buildx cache clearing > > > Key: YETUS-1178 > URL: https://issues.apache.org/jira/browse/YETUS-1178 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > test-patch docker tools should also process the buildx cache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-1178) docker buildx cache clearing
[ https://issues.apache.org/jira/browse/YETUS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-1178: --- Assignee: Allen Wittenauer > docker buildx cache clearing > > > Key: YETUS-1178 > URL: https://issues.apache.org/jira/browse/YETUS-1178 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > test-patch docker tools should also process the buildx cache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-1192) Semaphore CI needs junit in full mode
[ https://issues.apache.org/jira/browse/YETUS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-1192: --- Assignee: Allen Wittenauer > Semaphore CI needs junit in full mode > - > > Key: YETUS-1192 > URL: https://issues.apache.org/jira/browse/YETUS-1192 > Project: Yetus > Issue Type: New Feature > Components: Precommit >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > Semaphore CI needs junit in full format in order to process the test results. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1192) Semaphore CI needs junit in full mode
[ https://issues.apache.org/jira/browse/YETUS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1192: Summary: Semaphore CI needs junit in full mode (was: Add support for Semaphore CI artifacts) > Semaphore CI needs junit in full mode > - > > Key: YETUS-1192 > URL: https://issues.apache.org/jira/browse/YETUS-1192 > Project: Yetus > Issue Type: New Feature > Components: Precommit >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > Semaphore has added artifacts. Apache Yetus should support it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1192) Semaphore CI needs junit in full mode
[ https://issues.apache.org/jira/browse/YETUS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1192: Description: Semaphore CI needs junit in full format in order to process the test results. (was: Semaphore has added artifacts. Apache Yetus should support it.) > Semaphore CI needs junit in full mode > - > > Key: YETUS-1192 > URL: https://issues.apache.org/jira/browse/YETUS-1192 > Project: Yetus > Issue Type: New Feature > Components: Precommit >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > Semaphore CI needs junit in full format in order to process the test results. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1192) Add support for Semaphore CI artifacts
[ https://issues.apache.org/jira/browse/YETUS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1192: Fix Version/s: 0.15.0 > Add support for Semaphore CI artifacts > -- > > Key: YETUS-1192 > URL: https://issues.apache.org/jira/browse/YETUS-1192 > Project: Yetus > Issue Type: New Feature > Components: Precommit >Affects Versions: 0.15.0 >Reporter: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > Semaphore has added artifacts. Apache Yetus should support it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-250) docs on test-patch plugins doesn't explain how to include custom plugins
[
https://issues.apache.org/jira/browse/YETUS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-250:
---
Fix Version/s: (was: 0.15.0)
> docs on test-patch plugins doesn't explain how to include custom plugins
>
>
> Key: YETUS-250
> URL: https://issues.apache.org/jira/browse/YETUS-250
> Project: Yetus
> Issue Type: Bug
> Components: Precommit, website and documentation
>Affects Versions: 0.1.0
>Reporter: Sean Busbey
>Assignee: Allen Wittenauer
>Priority: Major
> Labels: beginner
>
> the docs section for test-patch plugins explains the load order and how to
> avoid the bundled plugins, but it never mentions how to actually load
> downstream plugins.
> (I believe it's just "point {{--user-plugins}} at a directory and they'll be
> loaded in shell collation order.")
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (YETUS-250) docs on test-patch plugins doesn't explain how to include custom plugins
[
https://issues.apache.org/jira/browse/YETUS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reassigned YETUS-250:
--
Assignee: (was: Allen Wittenauer)
> docs on test-patch plugins doesn't explain how to include custom plugins
>
>
> Key: YETUS-250
> URL: https://issues.apache.org/jira/browse/YETUS-250
> Project: Yetus
> Issue Type: Bug
> Components: Precommit, website and documentation
>Affects Versions: 0.1.0
>Reporter: Sean Busbey
>Priority: Major
> Labels: beginner
>
> the docs section for test-patch plugins explains the load order and how to
> avoid the bundled plugins, but it never mentions how to actually load
> downstream plugins.
> (I believe it's just "point {{--user-plugins}} at a directory and they'll be
> loaded in shell collation order.")
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1218) locate_patch falsely succeeds
[ https://issues.apache.org/jira/browse/YETUS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1218: Issue Type: Bug (was: Improvement) > locate_patch falsely succeeds > - > > Key: YETUS-1218 > URL: https://issues.apache.org/jira/browse/YETUS-1218 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > the return codes from some of the locate_patch functions are not correct. As > a result, test-patch thinks the PR code was downloaded when it was not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1218) locate_patch falsely succeeds
[ https://issues.apache.org/jira/browse/YETUS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1218: Fix Version/s: 0.15.0 > locate_patch falsely succeeds > - > > Key: YETUS-1218 > URL: https://issues.apache.org/jira/browse/YETUS-1218 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > the return codes from some of the locate_patch functions are not correct. As > a result, test-patch thinks the PR code was downloaded when it was not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1218) locate_patch falsely succeeds
[ https://issues.apache.org/jira/browse/YETUS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1218: Release Note: (was: With this fix, builds on MR/PR branches where the authorization to download from a bug system should work now. For example, prior to this change building a PR from a private GitHub on Circle CI would fail if no Github token was provided to `test-patch`. Now the build should work as expected, but will work the same as though building a regular branch.) > locate_patch falsely succeeds > - > > Key: YETUS-1218 > URL: https://issues.apache.org/jira/browse/YETUS-1218 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > the return codes from some of the locate_patch functions are not correct. As > a result, test-patch thinks the PR code was downloaded when it was not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1218) locate_patch falsely succeeds
[ https://issues.apache.org/jira/browse/YETUS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1218: Fix Version/s: (was: 0.15.0) > locate_patch falsely succeeds > - > > Key: YETUS-1218 > URL: https://issues.apache.org/jira/browse/YETUS-1218 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > the return codes from some of the locate_patch functions are not correct. As > a result, test-patch thinks the PR code was downloaded when it was not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-245) Quickstart with Jenkins
[ https://issues.apache.org/jira/browse/YETUS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-245: --- Fix Version/s: (was: 0.15.0) > Quickstart with Jenkins > --- > > Key: YETUS-245 > URL: https://issues.apache.org/jira/browse/YETUS-245 > Project: Yetus > Issue Type: Task > Components: website and documentation >Reporter: Sean Busbey >Priority: Major > > we need a quickstart guide for folks looking to set up a jenkins job to do > precommit testing with yetus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-368) Distinguish between "current" and "archival" releases
[ https://issues.apache.org/jira/browse/YETUS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-368: --- Fix Version/s: (was: 0.15.0) > Distinguish between "current" and "archival" releases > - > > Key: YETUS-368 > URL: https://issues.apache.org/jira/browse/YETUS-368 > Project: Yetus > Issue Type: Task > Components: build, website and documentation >Reporter: Sean Busbey >Priority: Major > > we currently have one list of releases. from that list we build our site docs > and point people to downloads on dist.apache. > We need to distinguish between releases that should be retrieved from > dist.apache and those that are just on archive.apache. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-245) Quickstart with Jenkins
[ https://issues.apache.org/jira/browse/YETUS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-245: -- Assignee: (was: Allen Wittenauer) > Quickstart with Jenkins > --- > > Key: YETUS-245 > URL: https://issues.apache.org/jira/browse/YETUS-245 > Project: Yetus > Issue Type: Task > Components: website and documentation >Reporter: Sean Busbey >Priority: Major > Fix For: 0.15.0 > > > we need a quickstart guide for folks looking to set up a jenkins job to do > precommit testing with yetus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-368) Distinguish between "current" and "archival" releases
[ https://issues.apache.org/jira/browse/YETUS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-368: -- Assignee: (was: Allen Wittenauer) > Distinguish between "current" and "archival" releases > - > > Key: YETUS-368 > URL: https://issues.apache.org/jira/browse/YETUS-368 > Project: Yetus > Issue Type: Task > Components: build, website and documentation >Reporter: Sean Busbey >Priority: Major > Fix For: 0.15.0 > > > we currently have one list of releases. from that list we build our site docs > and point people to downloads on dist.apache. > We need to distinguish between releases that should be retrieved from > dist.apache and those that are just on archive.apache. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-410) --basedir vs --patch-dir is annoying
[ https://issues.apache.org/jira/browse/YETUS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-410: -- Assignee: (was: Allen Wittenauer) > --basedir vs --patch-dir is annoying > > > Key: YETUS-410 > URL: https://issues.apache.org/jira/browse/YETUS-410 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Allen Wittenauer >Priority: Major > > We should use hyphenation consistently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-410) --basedir vs --patch-dir is annoying
[ https://issues.apache.org/jira/browse/YETUS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-410: --- Fix Version/s: (was: 0.15.0) > --basedir vs --patch-dir is annoying > > > Key: YETUS-410 > URL: https://issues.apache.org/jira/browse/YETUS-410 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > We should use hyphenation consistently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1231) codespell is trying to parse contents the of .git
[
https://issues.apache.org/jira/browse/YETUS-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762832#comment-17762832
]
Allen Wittenauer commented on YETUS-1231:
-
Take a look at the `.codespellrc` file in the Apache Yetus tree. We should
probably see if there is something we can do automatically though.
> codespell is trying to parse contents the of .git
> -
>
> Key: YETUS-1231
> URL: https://issues.apache.org/jira/browse/YETUS-1231
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Affects Versions: 0.15.0
>Reporter: Nick Dimiduk
>Priority: Major
>
> Using {{ghcr.io/apache/yetus:main}}, it seems the default {{codespell}}
> configuration is inspecting the contents of .git.
> {noformat}
>
>
> codespell plugin: full
>
>
> [Mon Jun 19 12:53:05 PM UTC 2023 DEBUG]: offset clock by 0
> WARNING: Cannot decode file using encoding "utf-8":
> ./.git/objects/68/2543a559782bec05d0d49067742babf19e34bd
> WARNING: Trying next encoding "iso-8859-1"
> WARNING: Cannot decode file using encoding "utf-8":
> ./.git/objects/74/65efc508cca072a4e103d8ce905d93f3a10010
> WARNING: Trying next encoding "iso-8859-1"
> WARNING: Cannot decode file using encoding "utf-8":
> ./.git/objects/f0/d57d38957178df8e9daae4eba779282ad62379
> WARNING: Trying next encoding "iso-8859-1"
> WARNING: Cannot decode file using encoding "utf-8":
> ./.git/objects/78/1615f230919cdcf42cc398cd1fc07a12ff2803
> WARNING: Trying next encoding "iso-8859-1"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (YETUS-1232) Periodically rebuild container images
[ https://issues.apache.org/jira/browse/YETUS-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-1232: --- Assignee: Allen Wittenauer > Periodically rebuild container images > - > > Key: YETUS-1232 > URL: https://issues.apache.org/jira/browse/YETUS-1232 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Nick Dimiduk >Assignee: Allen Wittenauer >Priority: Major > > I'm picking up Yetus for a new repo in HBase and while I sit here waiting on > my own image to build, I realised that Yetus images are stale. Starting from > `yetus-base:0.14.1`, I have loads of packages to update. Since we expect > users to be pulling these images directly, I think we should be explicitly > calling `apt-get update && apt-get upgrade` and rebuild on a timer. I propose > a weekly cadence, but almost anything will do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1232) Periodically rebuild container images
[ https://issues.apache.org/jira/browse/YETUS-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762828#comment-17762828 ] Allen Wittenauer commented on YETUS-1232: - Looks like we just need to implement https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule ? > Periodically rebuild container images > - > > Key: YETUS-1232 > URL: https://issues.apache.org/jira/browse/YETUS-1232 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Nick Dimiduk >Priority: Major > > I'm picking up Yetus for a new repo in HBase and while I sit here waiting on > my own image to build, I realised that Yetus images are stale. Starting from > `yetus-base:0.14.1`, I have loads of packages to update. Since we expect > users to be pulling these images directly, I think we should be explicitly > calling `apt-get update && apt-get upgrade` and rebuild on a timer. I propose > a weekly cadence, but almost anything will do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-574) --docker on branch labeled patch file ignores branch
[ https://issues.apache.org/jira/browse/YETUS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762826#comment-17762826 ] Allen Wittenauer commented on YETUS-574: I'm lowering the priority of this bug to minor because let's face it, no one uses the command line to do manual patches on a regular basis. > --docker on branch labeled patch file ignores branch > > > Key: YETUS-574 > URL: https://issues.apache.org/jira/browse/YETUS-574 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.6.0 >Reporter: Allen Wittenauer >Priority: Minor > > Given a patch file on the command line like "file.branch.patch", test-patch > will start on the given branch, then forget about it when it re-execs itself > under docker. Additionally, the --branch directive is ignored. (This > feature does work from JIRA, github, etc.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-574) --docker on branch labeled patch file ignores branch
[ https://issues.apache.org/jira/browse/YETUS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-574: --- Priority: Minor (was: Critical) > --docker on branch labeled patch file ignores branch > > > Key: YETUS-574 > URL: https://issues.apache.org/jira/browse/YETUS-574 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.6.0 >Reporter: Allen Wittenauer >Priority: Minor > > Given a patch file on the command line like "file.branch.patch", test-patch > will start on the given branch, then forget about it when it re-execs itself > under docker. Additionally, the --branch directive is ignored. (This > feature does work from JIRA, github, etc.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1226) patch command missing from container
[ https://issues.apache.org/jira/browse/YETUS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1226: Component/s: github-action > patch command missing from container > > > Key: YETUS-1226 > URL: https://issues.apache.org/jira/browse/YETUS-1226 > Project: Yetus > Issue Type: Bug > Components: build, github-action >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > patch command is missing from the container. it should not be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1228) Enable dependabot github actions scanning across all repos
[ https://issues.apache.org/jira/browse/YETUS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1228: Component/s: github-action homebrew > Enable dependabot github actions scanning across all repos > -- > > Key: YETUS-1228 > URL: https://issues.apache.org/jira/browse/YETUS-1228 > Project: Yetus > Issue Type: Task > Components: build, github-action, homebrew >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > We should enable dependabot's scanning of github actions to keep them > up-to-date.. For example, right now a few are still using checkout@v2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1226) patch command missing from container
[ https://issues.apache.org/jira/browse/YETUS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1226: Component/s: (was: github-action) > patch command missing from container > > > Key: YETUS-1226 > URL: https://issues.apache.org/jira/browse/YETUS-1226 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > patch command is missing from the container. it should not be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1224) 2023-05 Dependency Updates
[ https://issues.apache.org/jira/browse/YETUS-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1224: Release Note: * ansible (removed) * ansiblelint 6.8.7 -> 7.5.0 * bats 1.8.2 -> 1.9.0 * buf 1.9.0 -> 1.19.0 * bundler 2.3.26 -> 2.4.13 * codespell 2.2.2 -> 2.2.4 * golangci-lint 1.50.1 -> 1.52.2 * jsonlint 1.6.0 -> 1.6.3 * maven 3.8.6 -> 3.9.2 * markdownlint 0.32.2 -> 0.34 * node 14.x -> latest LTS at time of publishing (18.x currently) * pylint 2.15.6 -> 2.17.4 * rubocop 1.39 -> 1.51 * shellcheck 0.8.0 -> 0.9.0 * spotbugs 4.6.0 -> 4.7.3 * yamllint 1.28.0 -> 1.31.0 was: * ansible (removed) * ansiblelint 6.8.7 -> 7.5.0 * bats 1.8.2 -> 1.9.0 * buf 1.9.0 -> 1.19.0 * bundler 2.3.26 -> 2.4.13 * codespell 2.2.2 -> 2.2.4 * golangci-lint 1.50.1 -> 1.52.2 * jsonlint 1.6.0 -> 1.6.3 * maven 3.8.6 -> 3.9.2 * markdownlint 0.32.2 -> 0.34 * node 14.x -> latest LTS at time of publishing (18.x currently) * pylint 2.15.6 -> 2.17.4 * rubocop 1.39 -> 1.51 * shellcheck 0.8.0 -> 0.9.0 * spotbugs 4.6.0 -> 4.7.3 * yamllint 1.28.0 -> 1.31.0 > 2023-05 Dependency Updates > -- > > Key: YETUS-1224 > URL: https://issues.apache.org/jira/browse/YETUS-1224 > Project: Yetus > Issue Type: Task > Components: build, github-action, Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The usual dependency updates -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1228) Enable dependabot github actions scanning across all repos
[ https://issues.apache.org/jira/browse/YETUS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1228. - Fix Version/s: 0.15.0 Assignee: Allen Wittenauer Resolution: Fixed Thanks for the appoval [~ndimiduk]! > Enable dependabot github actions scanning across all repos > -- > > Key: YETUS-1228 > URL: https://issues.apache.org/jira/browse/YETUS-1228 > Project: Yetus > Issue Type: Task > Components: build >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > We should enable dependabot's scanning of github actions to keep them > up-to-date.. For example, right now a few are still using checkout@v2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
[ https://issues.apache.org/jira/browse/YETUS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1234: Fix Version/s: 0.15.0 > remove mac-10-15 from yetus-homebrew build > -- > > Key: YETUS-1234 > URL: https://issues.apache.org/jira/browse/YETUS-1234 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > github actions no longer supports that host so need to upgrade to macos 11 or > whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
[ https://issues.apache.org/jira/browse/YETUS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1234: Component/s: homebrew > remove mac-10-15 from yetus-homebrew build > -- > > Key: YETUS-1234 > URL: https://issues.apache.org/jira/browse/YETUS-1234 > Project: Yetus > Issue Type: Bug > Components: homebrew >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > > github actions no longer supports that host so need to upgrade to macos 11 or > whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1233) 2023-09 Dependency Updates
[ https://issues.apache.org/jira/browse/YETUS-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1233: Fix Version/s: 0.15.0 > 2023-09 Dependency Updates > -- > > Key: YETUS-1233 > URL: https://issues.apache.org/jira/browse/YETUS-1233 > Project: Yetus > Issue Type: Task > Components: build >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1233) 2023-09 Dependency Updates
[ https://issues.apache.org/jira/browse/YETUS-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1233. - Resolution: Fixed Thanks for the appoval [~ndimiduk]! > 2023-09 Dependency Updates > -- > > Key: YETUS-1233 > URL: https://issues.apache.org/jira/browse/YETUS-1233 > Project: Yetus > Issue Type: Task > Components: build >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
[ https://issues.apache.org/jira/browse/YETUS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762813#comment-17762813 ] Allen Wittenauer commented on YETUS-1234: - Yeah. I knew that Github removed 10.15 build nodes but I completely forgot we used them for this build. haha. > remove mac-10-15 from yetus-homebrew build > -- > > Key: YETUS-1234 > URL: https://issues.apache.org/jira/browse/YETUS-1234 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > github actions no longer supports that host so need to upgrade to macos 11 or > whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
[ https://issues.apache.org/jira/browse/YETUS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1234. - Resolution: Fixed Thanks for the appoval [~ndimiduk]! > remove mac-10-15 from yetus-homebrew build > -- > > Key: YETUS-1234 > URL: https://issues.apache.org/jira/browse/YETUS-1234 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > github actions no longer supports that host so need to upgrade to macos 11 or > whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (YETUS-1219) Yetus DOAP file has a parsing error
[
https://issues.apache.org/jira/browse/YETUS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reassigned YETUS-1219:
---
Assignee: Allen Wittenauer
> Yetus DOAP file has a parsing error
> ---
>
> Key: YETUS-1219
> URL: https://issues.apache.org/jira/browse/YETUS-1219
> Project: Yetus
> Issue Type: Bug
>Affects Versions: 0.14.1
>Reporter: Claude Warren
>Assignee: Allen Wittenauer
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 25, col: 6 ] \{E201} The attributes on this property element, are not
> permitted with any content; expecting end element tag.
> [1] http://yetus.apache.org/doap_yetus.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (YETUS-1219) Yetus DOAP file has a parsing error
[
https://issues.apache.org/jira/browse/YETUS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761958#comment-17761958
]
Allen Wittenauer commented on YETUS-1219:
-
Looks like the w3c validator passes if I just change the URLs to http instead
of https.
> Yetus DOAP file has a parsing error
> ---
>
> Key: YETUS-1219
> URL: https://issues.apache.org/jira/browse/YETUS-1219
> Project: Yetus
> Issue Type: Bug
>Affects Versions: 0.14.1
>Reporter: Claude Warren
>Assignee: Allen Wittenauer
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 25, col: 6 ] \{E201} The attributes on this property element, are not
> permitted with any content; expecting end element tag.
> [1] http://yetus.apache.org/doap_yetus.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (YETUS-1140) replace ansible-lint pip install w/apt-get
[ https://issues.apache.org/jira/browse/YETUS-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1140. - Resolution: Won't Fix ansible-lint has gotten to be much faster to install since it no longer pulls in all of ansible. > replace ansible-lint pip install w/apt-get > -- > > Key: YETUS-1140 > URL: https://issues.apache.org/jira/browse/YETUS-1140 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.14.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > Docker build takes _forever_ due to pip install of ansible-lint. Ubuntu > provides a (albeit older) version via apt so let's just use that to speed the > build up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1203) shelldocs and shellcheck should use similar/same code
[ https://issues.apache.org/jira/browse/YETUS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1203: Summary: shelldocs and shellcheck should use similar/same code (was: shelldocs and shellcheck should user similar/same code) > shelldocs and shellcheck should use similar/same code > - > > Key: YETUS-1203 > URL: https://issues.apache.org/jira/browse/YETUS-1203 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Allen Wittenauer >Priority: Minor > > shellcheck and shelldocs both work on shell code but use different algorithms > to determine what to actually run on. they should be nearly identical to > provide consistent results. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1212) upgrade github workflows checkout@v2 and upload-artifact@v2
[ https://issues.apache.org/jira/browse/YETUS-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1212. - Resolution: Duplicate > upgrade github workflows checkout@v2 and upload-artifact@v2 > --- > > Key: YETUS-1212 > URL: https://issues.apache.org/jira/browse/YETUS-1212 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Allen Wittenauer >Priority: Minor > Fix For: 0.15.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (YETUS-1212) upgrade github workflows checkout@v2 and upload-artifact@v2
[ https://issues.apache.org/jira/browse/YETUS-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reopened YETUS-1212: - > upgrade github workflows checkout@v2 and upload-artifact@v2 > --- > > Key: YETUS-1212 > URL: https://issues.apache.org/jira/browse/YETUS-1212 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Allen Wittenauer >Priority: Minor > Fix For: 0.15.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1212) upgrade github workflows checkout@v2 and upload-artifact@v2
[ https://issues.apache.org/jira/browse/YETUS-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1212. - Resolution: Fixed > upgrade github workflows checkout@v2 and upload-artifact@v2 > --- > > Key: YETUS-1212 > URL: https://issues.apache.org/jira/browse/YETUS-1212 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Allen Wittenauer >Priority: Minor > Fix For: 0.15.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1221) junit output no longer works on Circle CI
[ https://issues.apache.org/jira/browse/YETUS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1221. - Resolution: Won't Fix I don't think this one is/was our bug. CircleCI is still choking a bit on spotbugs junit but it _is_ processing ours. > junit output no longer works on Circle CI > - > > Key: YETUS-1221 > URL: https://issues.apache.org/jira/browse/YETUS-1221 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Minor > > I've seen an instance where spotbugs breaking also broke junit reporting in > at least circle ci. There is likely a subtle bug here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1233) 2023-09 Dependency Updates
[ https://issues.apache.org/jira/browse/YETUS-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1233: Release Note: External: * ansiblelint 6.16.1 -> 6.18.0 * bats 1.9.0 -> 1.10.0 * buf 1.19.0 -> 1.26.1 * bundler 2.4.13 -> 2.4.19 * codespell 2.2.4 -> 2.2.5 * golangci-lint 1.52.2 -> 1.54.2 * hadolint arm is now supported * maven 3.9.2 -> 3.9.4 * markdownlint 0.34.0 -> 0.36.0 * node: now comes from nodesource and hardcoded to 18.x * pylint 2.17.4 -> 2.17.5 * rubocop 1.51 -> 1.56.1 * spotbugs 4.6.0 -> 4.7.3 * yamllint 1.31.0 -> 1.32.0 Internal: * middleman went to 4.5.0 and a bunch of ruby deps updated in the process was: External: * ansiblelint 6.16.1 -> 6.18.0 * apache rat 0.14 -> 0.15 * bats 1.9.0 -> 1.10.0 * buf 1.19.0 -> 1.26.1 * bundler 2.4.13 -> 2.4.19 * codespell 2.2.4 -> 2.2.5 * golangci-lint 1.52.2 -> 1.54.2 * hadolint arm is now supported * maven 3.9.2 -> 3.9.4 * markdownlint 0.34.0 -> 0.36.0 * node: now comes from nodesource and hardcoded to 18.x * pylint 2.17.4 -> 2.17.5 * rubocop 1.51 -> 1.56.1 * spotbugs 4.6.0 -> 4.7.3 * yamllint 1.31.0 -> 1.32.0 Internal: * middleman went to 4.5.0 and a bunch of ruby deps updated in the process > 2023-09 Dependency Updates > -- > > Key: YETUS-1233 > URL: https://issues.apache.org/jira/browse/YETUS-1233 > Project: Yetus > Issue Type: Task > Components: build >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
[ https://issues.apache.org/jira/browse/YETUS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1234: Issue Type: Bug (was: Task) > remove mac-10-15 from yetus-homebrew build > -- > > Key: YETUS-1234 > URL: https://issues.apache.org/jira/browse/YETUS-1234 > Project: Yetus > Issue Type: Bug >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > github actions no longer supports that host so need to upgrade to macos 11 or > whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1235) figure out why apache rat 0.15 does not work
Allen Wittenauer created YETUS-1235: --- Summary: figure out why apache rat 0.15 does not work Key: YETUS-1235 URL: https://issues.apache.org/jira/browse/YETUS-1235 Project: Yetus Issue Type: Bug Components: Precommit Reporter: Allen Wittenauer The CLI version of Apache Rat 0.15 has issues with our XSL file that is generated by the asflicence plug-in. Need to spend some time to figure out why that is breaking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1234) remove mac-10-15 from yetus-homebrew build
Allen Wittenauer created YETUS-1234: --- Summary: remove mac-10-15 from yetus-homebrew build Key: YETUS-1234 URL: https://issues.apache.org/jira/browse/YETUS-1234 Project: Yetus Issue Type: Task Reporter: Allen Wittenauer Assignee: Allen Wittenauer github actions no longer supports that host so need to upgrade to macos 11 or whatever. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1230) hadolint is not executable on arm64
[
https://issues.apache.org/jira/browse/YETUS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761880#comment-17761880
]
Allen Wittenauer commented on YETUS-1230:
-
I've got a much simpler fix in YETUS-1233
> hadolint is not executable on arm64
> ---
>
> Key: YETUS-1230
> URL: https://issues.apache.org/jira/browse/YETUS-1230
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Affects Versions: 0.14.1
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Using the image published at ghcr.io/apache/yetus:0.14.1 to test a project
> locally, said project includes a Dockerfile, I see the following:
> {noformat}
> executable '/usr/bin/hadolint' for 'hadolint' is not executable.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (YETUS-1233) 2023-09 Dependency Updates
[ https://issues.apache.org/jira/browse/YETUS-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-1233: Release Note: External: * ansiblelint 6.16.1 -> 6.18.0 * apache rat 0.14 -> 0.15 * bats 1.9.0 -> 1.10.0 * buf 1.19.0 -> 1.26.1 * bundler 2.4.13 -> 2.4.19 * codespell 2.2.4 -> 2.2.5 * golangci-lint 1.52.2 -> 1.54.2 * hadolint arm is now supported * maven 3.9.2 -> 3.9.4 * markdownlint 0.34.0 -> 0.36.0 * node: now comes from nodesource and hardcoded to 18.x * pylint 2.17.4 -> 2.17.5 * rubocop 1.51 -> 1.56.1 * spotbugs 4.6.0 -> 4.7.3 * yamllint 1.31.0 -> 1.32.0 Internal: * middleman went to 4.5.0 and a bunch of ruby deps updated in the process > 2023-09 Dependency Updates > -- > > Key: YETUS-1233 > URL: https://issues.apache.org/jira/browse/YETUS-1233 > Project: Yetus > Issue Type: Task > Components: build >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1233) 2023-09 Dependency Updates
Allen Wittenauer created YETUS-1233: --- Summary: 2023-09 Dependency Updates Key: YETUS-1233 URL: https://issues.apache.org/jira/browse/YETUS-1233 Project: Yetus Issue Type: Task Components: build Reporter: Allen Wittenauer Assignee: Allen Wittenauer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1230) hadolint is not executable on arm64
[
https://issues.apache.org/jira/browse/YETUS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734889#comment-17734889
]
Allen Wittenauer commented on YETUS-1230:
-
At the time, binaries weren't available for arm and building Haskell code is
painful. Looks like hadolint has them now so we should revisit this one and
others that are not being installed on arm.
> hadolint is not executable on arm64
> ---
>
> Key: YETUS-1230
> URL: https://issues.apache.org/jira/browse/YETUS-1230
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Affects Versions: 0.14.1
>Reporter: Nick Dimiduk
>Priority: Major
>
> Using the image published at ghcr.io/apache/yetus:0.14.1 to test a project
> locally, said project includes a Dockerfile, I see the following:
> {noformat}
> executable '/usr/bin/hadolint' for 'hadolint' is not executable.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (YETUS-1226) patch command missing from container
[ https://issues.apache.org/jira/browse/YETUS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1226. - Resolution: Fixed > patch command missing from container > > > Key: YETUS-1226 > URL: https://issues.apache.org/jira/browse/YETUS-1226 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.14.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.15.0 > > Time Spent: 10m > Remaining Estimate: 0h > > patch command is missing from the container. it should not be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (YETUS-1211) Change Dockerfiles default repos to be ghcr.io
[ https://issues.apache.org/jira/browse/YETUS-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YETUS-1211. - Fix Version/s: 0.15.0 Resolution: Fixed > Change Dockerfiles default repos to be ghcr.io > -- > > Key: YETUS-1211 > URL: https://issues.apache.org/jira/browse/YETUS-1211 > Project: Yetus > Issue Type: Bug > Components: build, website and documentation >Affects Versions: 0.14.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Trivial > Fix For: 0.15.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1229) Yetus falsely reports on ASF licence after removing files from the PR
[ https://issues.apache.org/jira/browse/YETUS-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726274#comment-17726274 ] Allen Wittenauer commented on YETUS-1229: - Yup, that's what is happening here: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/artifact/out/apply-patch-git-apply.log > Yetus falsely reports on ASF licence after removing files from the PR > - > > Key: YETUS-1229 > URL: https://issues.apache.org/jira/browse/YETUS-1229 > Project: Yetus > Issue Type: Bug > Components: github-action >Reporter: Ferenc Erdelyi >Priority: Major > Attachments: Yetus_20Report.zip > > > For [PR-56638|[https://github.com/apache/hadoop/pull/5638]] I've added > text-based certificate files for testing, which did not have ASF license. > Later on, I removed these text-based certificates (as these were not used) > and kept the binary truststore and keystore files only. > The expected behavior was that the ASF license check should pass. > However, the check still alerted the already deleted files and Yetus failed > the check. > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/] > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/Yetus_20Report/] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (YETUS-1229) Yetus falsely reports on ASF licence after removing files from the PR
[ https://issues.apache.org/jira/browse/YETUS-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726270#comment-17726270 ] Allen Wittenauer edited comment on YETUS-1229 at 5/25/23 3:09 PM: -- In the vast majority of cases like this one, rebasing+squashing the commits is generally required because the patch being generated by github is leaving these files hanging around. was (Author: aw): In the vast majority of cases like this one, rebasing+squashing the commits is generally required because the patch being generated is leaving these files hanging around. > Yetus falsely reports on ASF licence after removing files from the PR > - > > Key: YETUS-1229 > URL: https://issues.apache.org/jira/browse/YETUS-1229 > Project: Yetus > Issue Type: Bug > Components: github-action >Reporter: Ferenc Erdelyi >Priority: Major > Attachments: Yetus_20Report.zip > > > For [PR-56638|[https://github.com/apache/hadoop/pull/5638]] I've added > text-based certificate files for testing, which did not have ASF license. > Later on, I removed these text-based certificates (as these were not used) > and kept the binary truststore and keystore files only. > The expected behavior was that the ASF license check should pass. > However, the check still alerted the already deleted files and Yetus failed > the check. > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/] > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/Yetus_20Report/] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (YETUS-1229) Yetus falsely reports on ASF licence after removing files from the PR
[ https://issues.apache.org/jira/browse/YETUS-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726270#comment-17726270 ] Allen Wittenauer commented on YETUS-1229: - In the vast majority of cases like this one, rebasing+squashing the commits is generally required because the patch being generated is leaving these files hanging around. > Yetus falsely reports on ASF licence after removing files from the PR > - > > Key: YETUS-1229 > URL: https://issues.apache.org/jira/browse/YETUS-1229 > Project: Yetus > Issue Type: Bug > Components: github-action >Reporter: Ferenc Erdelyi >Priority: Major > Attachments: Yetus_20Report.zip > > > For [PR-56638|[https://github.com/apache/hadoop/pull/5638]] I've added > text-based certificate files for testing, which did not have ASF license. > Later on, I removed these text-based certificates (as these were not used) > and kept the binary truststore and keystore files only. > The expected behavior was that the ASF license check should pass. > However, the check still alerted the already deleted files and Yetus failed > the check. > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/] > [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5638/22/Yetus_20Report/] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1228) Enable dependabot github actions scanning across all repos
Allen Wittenauer created YETUS-1228: --- Summary: Enable dependabot github actions scanning across all repos Key: YETUS-1228 URL: https://issues.apache.org/jira/browse/YETUS-1228 Project: Yetus Issue Type: Task Components: build Affects Versions: 0.14.1 Reporter: Allen Wittenauer We should enable dependabot's scanning of github actions to keep them up-to-date.. For example, right now a few are still using checkout@v2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (YETUS-1227) Use Github file comments
Allen Wittenauer created YETUS-1227: --- Summary: Use Github file comments Key: YETUS-1227 URL: https://issues.apache.org/jira/browse/YETUS-1227 Project: Yetus Issue Type: Improvement Components: Precommit Affects Versions: 0.14.1 Reporter: Allen Wittenauer Info: https://github.blog/changelog/2023-04-11-commenting-on-files-in-a-pull-request-is-now-generally-available There are times when precommit needs to comment on a file rather than a line. The code should use this functionality now that it is available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
