That’s also doable, but we should be “notarizing” our Mac binaries (same for Windows binaries, but I don’t know much about that system) using the Infra-provided code signing services. For Mac apps, this goes through the Apple Developer program which I’m not able to use as an employee there (we have a separate system for employees to do code signing which is for Apple products only).
For CI purposes, we can get a VM, though for code signing, it’s easiest to have someone with a Mac and a code signing certificate set up to run the codesign CLI tool (which I think is what Xcode uses). From my experience, it’s slightly easier to use and set up than GPG. On Wed, Jun 9, 2021 at 10:19 Ralph Goers <ralph.go...@dslextreme.com> wrote: > Another option. Perform the release build on your personal Mac. I’ve done > that for every Log4j release. > > Ralph > > > On Jun 9, 2021, at 7:40 AM, Matt Sicker <boa...@gmail.com> wrote: > > > > Another possibility is that PMCs can get a virtual machine allocated to > > them. Perhaps we could request a macOS EC2 instance for our VM? Or there > > may even be wider interest for a shared build agent. > > > > On Sun, Jun 6, 2021 at 19:15 Matt Sicker <boa...@gmail.com> wrote: > > > >> I don't see any Mac build agents for anything at ASF besides GitHub > >> Actions. We do have Windows build agents, so I wonder if getting Mac > >> agents is something possible. > >> > >> On Sun, 6 Jun 2021 at 18:43, Robert Middleton <rmiddle...@apache.org> > >> wrote: > >>> > >>> Thanks; I've been ignoring that while the release happens(there's > >>> probably an easier way to do it on my side). > >>> > >>> Somewhat related question: does the ASF Jenkins have any Mac builders? > >>> It would be nice to make sure that the DMG gets generated on builds(I > >>> suppose I could use github actions instead). > >>> > >>> -Robert Middleton > >>> > >>> On Sun, Jun 6, 2021 at 3:54 PM Matt Sicker <boa...@gmail.com> wrote: > >>>> > >>>> I've fixed this issue. The problem was that while the version in > master > >>>> doesn't have a -SNAPSHOT, it can't be deployed to the snapshots > >> repository > >>>> (duh). I've updated the pipeline to check the maven project version > for > >>>> this before attempting to run a deploy step to publish snapshot > >> builds. As > >>>> a bonus, the Chainsaw pipeline is now more "standard" (no need to > >> abstract > >>>> out a Windows build or toolchains.xml usage). > >>>> > >>>> On Sat, 5 Jun 2021 at 19:01, Mr. Jenkins < > jenk...@ci-builds.apache.org > >>> > >>>> wrote: > >>>> > >>>>> *BUILD FAILURE* > >>>>> Build URL > >>>>> https://ci-builds.apache.org/job/Logging/job/chainsaw/job/master/25/ > >>>>> Project: master > >>>>> Date of build: Sun, 06 Jun 2021 00:00:00 +0000 > >>>>> Build duration: 1 min 35 sec and counting > >>>>> * JUnit Tests * > >>>>> Name: org.apache.log4j.chainsaw Failed: 0 test(s), Passed: 1 test(s), > >>>>> Skipped: 0 test(s), Total: 1 test(s) > >>>>> Name: org.apache.log4j.chainsaw.receivers Failed: 0 test(s), Passed: > >> 1 > >>>>> test(s), Skipped: 0 test(s), Total: 1 test(s) > >>>>> Name: org.apache.log4j.db Failed: 0 test(s), Passed: 2 test(s), > >> Skipped: 0 > >>>>> test(s), Total: 2 test(s) > >>>>> Name: org.apache.log4j.helpers Failed: 0 test(s), Passed: 1 test(s), > >>>>> Skipped: 0 test(s), Total: 1 test(s) > >>>>> Name: org.apache.log4j.rewrite Failed: 0 test(s), Passed: 3 test(s), > >>>>> Skipped: 0 test(s), Total: 3 test(s) > >>>>> Name: org.apache.log4j.xml Failed: 0 test(s), Passed: 4 test(s), > >> Skipped: > >>>>> 0 test(s), Total: 4 test(s) > >>>>> * CONSOLE OUTPUT * > >>>>> [...truncated 1287 lines...] > >>>>> Progress (1): 295/858 kB > >>>>> Progress (1): 303/858 kB > >>>>> Progress (1): 311/858 kB > >>>>> Progress (1): 319/858 kB > >>>>> Progress (1): 328/858 kB > >>>>> Progress (1): 336/858 kB > >>>>> Progress (1): 344/858 kB > >>>>> Progress (1): 352/858 kB > >>>>> Progress (1): 360/858 kB > >>>>> Progress (1): 369/858 kB > >>>>> Progress (1): 377/858 kB > >>>>> Progress (1): 385/858 kB > >>>>> Progress (1): 393/858 kB > >>>>> Progress (1): 401/858 kB > >>>>> Progress (1): 410/858 kB > >>>>> Progress (1): 418/858 kB > >>>>> Progress (1): 426/858 kB > >>>>> Progress (1): 434/858 kB > >>>>> Progress (1): 442/858 kB > >>>>> Progress (1): 451/858 kB > >>>>> Progress (1): 459/858 kB > >>>>> Progress (1): 467/858 kB > >>>>> Progress (1): 475/858 kB > >>>>> Progress (1): 483/858 kB > >>>>> Progress (1): 492/858 kB > >>>>> Progress (1): 500/858 kB > >>>>> Progress (1): 508/858 kB > >>>>> Progress (1): 516/858 kB > >>>>> Progress (1): 524/858 kB > >>>>> Progress (1): 532/858 kB > >>>>> Progress (1): 541/858 kB > >>>>> Progress (1): 549/858 kB > >>>>> Progress (1): 557/858 kB > >>>>> Progress (1): 565/858 kB > >>>>> Progress (1): 573/858 kB > >>>>> Progress (1): 582/858 kB > >>>>> Progress (1): 590/858 kB > >>>>> Progress (1): 598/858 kB > >>>>> Progress (1): 606/858 kB > >>>>> Progress (1): 614/858 kB > >>>>> Progress (1): 623/858 kB > >>>>> Progress (1): 631/858 kB > >>>>> Progress (1): 639/858 kB > >>>>> Progress (1): 647/858 kB > >>>>> Progress (1): 655/858 kB > >>>>> Progress (1): 664/858 kB > >>>>> Progress (1): 672/858 kB > >>>>> Progress (1): 680/858 kB > >>>>> Progress (1): 688/858 kB > >>>>> Progress (1): 696/858 kB > >>>>> Progress (1): 705/858 kB > >>>>> Progress (1): 713/858 kB > >>>>> Progress (1): 721/858 kB > >>>>> Progress (1): 729/858 kB > >>>>> Progress (1): 737/858 kB > >>>>> Progress (1): 745/858 kB > >>>>> Progress (1): 754/858 kB > >>>>> Progress (1): 762/858 kB > >>>>> Progress (1): 770/858 kB > >>>>> Progress (1): 778/858 kB > >>>>> Progress (1): 786/858 kB > >>>>> Progress (1): 795/858 kB > >>>>> Progress (1): 803/858 kB > >>>>> Progress (1): 811/858 kB > >>>>> Progress (1): 819/858 kB > >>>>> Progress (1): 827/858 kB > >>>>> Progress (1): 836/858 kB > >>>>> Progress (1): 844/858 kB > >>>>> Progress (1): 852/858 kB > >>>>> Progress (1): 858 kB > >>>>> Uploading to apache.releases.https: > >>>>> > >> > https://repository.apache.org/service/local/staging/deploy/maven2/log4j/apache-chainsaw/2.1.0/apache-chainsaw-2.1.0.pom > >>>>> Progress (1): 4.1/21 kB > >>>>> Progress (1): 8.2/21 kB > >>>>> Progress (1): 12/21 kB > >>>>> Progress (1): 16/21 kB > >>>>> Progress (1): 20/21 kB > >>>>> Progress (1): 21 kB > >>>>> [INFO] > >>>>> > >> ------------------------------------------------------------------------ > >>>>> [INFO] BUILD FAILURE > >>>>> [INFO] > >>>>> > >> ------------------------------------------------------------------------ > >>>>> [INFO] Total time: 9.877 s > >>>>> [INFO] Finished at: 2021-06-06T00:01:34Z > >>>>> [INFO] > >>>>> > >> ------------------------------------------------------------------------ > >>>>> [ERROR] Failed to execute goal > >>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy > >> (default-deploy) > >>>>> on project apache-chainsaw: Failed to deploy artifacts: Could not > >> transfer > >>>>> artifact log4j:apache-chainsaw:jar:2.1.0 from/to > >> apache.releases.https ( > >>>>> https://repository.apache.org/service/local/staging/deploy/maven2): > >>>>> Transfer failed for > >>>>> > >> > https://repository.apache.org/service/local/staging/deploy/maven2/log4j/apache-chainsaw/2.1.0/apache-chainsaw-2.1.0.jar > >>>>> 401 Unauthorized -> [Help 1] > >>>>> [ERROR] > >>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with > >> the > >>>>> -e switch. > >>>>> [ERROR] Re-run Maven using the -X switch to enable full debug > >> logging. > >>>>> [ERROR] > >>>>> [ERROR] For more information about the errors and possible solutions, > >>>>> please read the following articles: > >>>>> [ERROR] [Help 1] > >>>>> > >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > >>>>> [Pipeline] } > >>>>> Deleting 1 temporary files > >>>>> [Pipeline] // configFileProvider > >>>>> [Pipeline] } > >>>>> [Pipeline] // withEnv > >>>>> Post stage > >>>>> [Pipeline] emailext > >>>>> > >> > > >
