Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adoption of gha-scala-library-release-workflow across the Guardian #20

Open
rtyley opened this issue Jan 10, 2024 · 0 comments
Open

Adoption of gha-scala-library-release-workflow across the Guardian #20

rtyley opened this issue Jan 10, 2024 · 0 comments

Comments

@rtyley
Copy link
Member

rtyley commented Jan 10, 2024

There are something like ~48 Scala libraries at the Guardian, and ideally those projects will all be either using gha-scala-library-release-workflow, or archived - we don't want to confuse devs by leaving any other patterns to follow!

Already updated

  1. https://github.com/guardian/etag-caching
  2. Adopt GHA Scala Library Release Workflow play-secret-rotation#416
  3. Adopt GHA Scala Library Release Workflow play-googleauth#208
  4. Adopt GHA Scala Library Release Workflow facia-scala-client#299
  5. Adopt scala library release GHA workflow marley#102
  6. Adopt GHA Scala library release workflow redirect-resolver#3
  7. Support multiple Play json versions concurrently targeting-client#37
  8. Adopt GHA Scala Library Release Workflow mobile-apps-api-models#55
  9. Adopt GHA Scala Library Release Workflow pa-football-client#80
  10. use gha-scala-library-release-workflow to publish to maven identity-test-users#9
  11. Setup automated publishing to maven commercial-shared#57
  12. Adopt GHA Scala Library Release Workflow fezziwig#45
  13. Changes made for adding gh-scala release process. content-api-firehose-client#35
  14. Adopt GHA-Scala-Library-Release-Workflow cross-platform-navigation#70
  15. https://github.com/guardian/content-api-client-aws
  16. Adopt GHA Scala Library Release Workflow atom-maker#93 - needed fixing up to handle Java 17, see Fix tests under Java 17 (Upgrade to Play 2.9 & update Guice) atom-maker#94
  17. Implement gha-scala-library-release-workflow release process. content-api-scala-client#402
  18. Followed the steps to add gh-scala release scrooge-extras#30, fixed up with Fix release process scrooge-extras#33
  19. Implementing gha-scala-release-process in this library. thrift-serializer#27
  20. Adopt GHA-Scala-Library-Release-Workflow content-api-models#232 - Maven and NPM artifacts
  21. Adopt GHA Scala Library Release Workflow tags-thrift-schema#44
  22. Adopt gha-scala-rel-workflow in the project content-atom#166 - Maven and NPM artifacts
  23. Adopt GHA Scala Library Release Workflow flexible-octopus-model#15
  24. feat: adopt gha-scala-library-release-workflow guardian-configuration#29
  25. feat: add Scala release workflow simple-configuration#79
  26. https://github.com/guardian/flexible-model/pull/67
  27. Adopt gha-scala-library-release process content-entity#32 - Maven and NPM artifacts
  28. Follows the instructions to enable the scala lib release workflow janus-app#416 - library project is a sub-project alongside an app. This is OK so long as there's only 1 applicable version number for any library projects in the repo, it would get confusing if you were trying to release 2 different libraries with different version numbers in the same repo.
  29. Update build and include sbt publish GHA workflow anghammarad#193
  30. Automated releases using gha-scala-library-release-workflow pan-domain-authentication#135
  31. Adopt GHA Scala Library Release Workflow mobile-n10n#1223
  32. Change the release process mobile-logstash-encoder#27
  33. Adopt GHA Scala Library Release Workflow & use Sonatype token rather than password apps-rendering-api-models#90
  34. Adopt GHA Scala library release workflow fastly-api-client#47
  35. https://github.com/guardian/permissions/pull/224

Useful repos for adoption

These are repos that will either provide useful challenges we can learn from, or that will be good for introducing another group of devs to the workflow (eg where adoption is currently low):

Repos not yet converted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant