/rules-sdlc

Bazel respource for CFS projects

Primary LanguagePythonApache License 2.0Apache-2.0

Rules SDLCs 

                         ,,                                     ,,    ,,
`7MM"""Mq.             `7MM                                   `7MM  `7MM
  MM   `MM.              MM                                     MM    MM
  MM   ,M9 `7MM  `7MM    MM  .gP"Ya  ,pP"Ybd     ,pP"Ybd   ,M""bMM    MM  ,p6"bo
  MMmmdM9    MM    MM    MM ,M'   Yb 8I   `"     8I   `" ,AP    MM    MM 6M'  OO
  MM  YM.    MM    MM    MM 8M"""""" `YMMMa.     `YMMMa. 8MI    MM    MM 8M
  MM   `Mb.  MM    MM    MM YM.    , L.   I8     L.   I8 `Mb    MM    MM YM.    ,
.JMML. .JMM. `Mbod"YML..JMML.`Mbmmd' M9mmmP'     M9mmmP'  `Wbmd"MML..JMML.YMbmd'

Download Release Issues License

Distribution Chanel Description
‼️ Nightly Builds created out of the central repository every night, packaged up every night for bleeding-edge testers to install and test.These are not qualified by QA.
❗ Aurora Builds created out of the aurora repository, which is synced from central repository every weeks.There is a small amount of QA at the start of the 1 week period before the updates are offered.as such its status is roughly "experimental".
⁉️ Beta Builds created out of the master repository, qualified by QA as being of sufficient quality to release to beta users.
✔️ Release Builds created out of the release repository, qualified by QA as being of sufficient quality to release to hundreds of millions of people.

Bazel rules resources.

Table of Contents

  1. Introduction
  2. Reporting bugs and getting help
  3. Contributing
  4. Building
  5. Linux
  6. macOS
  7. Windows
  8. Usage
  9. Enviroment Variables
  10. Dependencies
  11. Compile-time options
  12. Automated testing
  13. Documentation
  14. Change log
  15. Distribution management
  16. Acknowledgments
  17. Known Limitations
  18. Contributors
  19. Inspiration & Ideas
  20. TODO
  21. License

Introduction

Multi-OS Systems Platform ...

Reporting bugs and getting help

Contributing to

Building

Gitlab CI Github Actions Circle CI Bitbucket CI Travis CI
Windows
MacOS
Linux
Android
iOS
Linux

Linux

macOS

Windows

Usage

Environment Variables

Dependencies

Compile-time options

Automated testing

Documentation

Bazel rules and resources used for all projects of the

  • cpp [proto|idl|grpc]
  • pyhton [proto|idl]
  • java [proto|idl|grpc]
  • sh
  • kotlin [proto]
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "com.github.doevelopper.rules-sdlc",
    urls = [
		"https://github.com/doevelopper/rules-sdlc/archive/TODO"],
    sha256 = "TODO",
)

Then, in your BUILD.bazel files, import and use the rules:

load("@com.github.doevelopper.rules-sdlc//<dir>/<dir>:<file>.bzl", "sdlc_cc_library")

sdlc_rule_repositories()
or ...

Change log

Branch Defects Commits Pull Request

A detailed list of all changes that have been made throughout the development of project is included in the file CHANGES, with the most recent changes listed first. Change notes include tags indicating the category of the change that was made; these categories are:

Category Description
[func] New feature
[bug] General bug fix
[security] Fix for a significant security flaw
[experimental] Used for new features when the syntax or other aspects of the design are still in flux and may change
[port] Portability enhancement
[maint] Updates to built-in data such as root server addresses and keys
[tuning] Changes to built-in configuration defaults and constants to improve performance
[performance] Other changes to improve server performance
[protocol] Updates to the DNS protocol such as new RR types
[test] Changes to the automatic tests, not affecting server functionality
[cleanup] Minor corrections and refactoring
[doc] Documentation
[contrib] Changes to the contributed tools and libraries in the 'contrib' subdirectory
[placeholder] Used in the main development branch to reserve change numbers for use in other branches, e.g., when fixing a bug that only exists in older releases

In general, [func] and [experimental] tags only appear in new-feature releases (i.e., those with version numbers ending in zero). Some new functionality may be backported to older releases on a case-by-case basis. All other change types may be applied to all currently supported releases.

Bug report identifiers

Most notes in the CHANGES file include a reference to a bug report or issue number.

📚 Acknowledgments

Known Limitations

🚀 Contributors

see Rules SDLC contributors

Thank you!

Inspiration & Ideas

TODO

Bazel rules sdlc is a work in progress, so any ideas and patches are appreciated.

  • use preview window for search results
  • Vim documentation
  • tests
  • improve error handling
  • allow specifying revision/version?
  • handle dependencies
  • make it rock!

📕 License

Licensed under Apache License, Version 2.0.

📫 Contact

Mail LinkedIn