                   _______________  _______________
                 .'               .'               .|
               .'               .'               .' |
             .'_______________.'______________ .'   |
             | ___ _____ ___ || ___ _____ ___ |     |
             ||_=_|__=__|_=_||||_=_|__=__|_=_||     |
       ______||_____===_____||||_____===_____||     | __________
    .'       ||_____===_____||||_____===_____||    .'          .'|
  .'         ||_____===_____||||_____===_____||  .'          .'  |
.'___________|_______________||_______________|.'__________.'    |
|.----------.|.-----___-----.||.-----___-----.||    |_____.----------.
|]          |||_____________||||_____________|||  .'      [          |
||          ||.-----___-----.||.-----___-----.||.'        |          |
||          |||_____________||||_____________|||==========|          |
||          ||.-----___-----.||.-----___-----.||    |_____|          |
|]         o|||_____________||||_____________|||  .'      [        'o|
||          ||.-----___-----.||.-----___-----.||.'        |          |
||          |||             ||||_____________|||==========|          |
||          |||             |||.-----___-----.||    |_____|          |
|]          |||             ||||             |||  .'      [          |
||__________|||_____________||||_____________|||.'________|__________|
''----------'''------------------------------'''----------''
            (o)LGB                           (o)

The place to store functions that are used in pipelines for multiple repos.

Please add whatever is useful to you, but keep it tidy so its still useful to everyone else :)

Release Status: Alpha

TL;DR: Ready for use, but needs expansion.

The functions in this repo are tested and ready for use, but certain libsare pretty much place holders (eg logging). Those need further contributionsbefore they provide a comprehensive solution.

License: Apache 2.0

See the license file

Usage

Add bash-lib into your project in the way that best fits your workflow. The only requirement is that you pin the version ofbash-lib that you use. This is important so that changes to bash-lib do not have the power to break all projects that usebash-lib. Your project can then test updates to bash-lib and roll forward periodically.

Options:

Add a submodule: they are an easy way to integrate bash-lib and automatically use a single SHA until manually updated. Submodules add a pointer from a mount point in your repo to the external repo (bash-lib), and require workflow changes to ensure that pointer is derferenced during clone, checkout and some other opertaions.
Add a subtree: This repo uses subtrees to pull in test dependencies. Subtrees copy an external repo into a subdirectory of the host repo, no workflow changes are required. Subtrees naturally keep a single version of bash-lib until explicitly updated. Note that subtree merge commits do not rebase well ⚠️ , so best to keep subtree updates in separate PRs from normal commits.
Clone bash-lib in your deployment process, bash-lib doesn't have to be within your repo, just needs to be somewhere where your scripts can source init. This is where it's most important that you implement a mechanism to always use the same SHA, as a clone will track master by default, which is not an allowed use of bash-lib.

Once you have bash-lib cloned in your project, you source two things:

Source bash-lib/init. This ensures submodules are initalised and sets the BASH_LIB_DIR env var to the absolute path to the bash-lib dir. This makes it easy to source libraries from other scripts.
Source ${BASH_LIB_DIR}/lib-name/lib for any libraries you are interested in.

You are now ready to use bash-lib functions :)

Structure

The /init script sets up everything required to use the library, mostimportantly the BASH_LIB_DIR variable which gives the absolute path to the rootof the library and should be used for sourcing the modules.

The repo is organized into libraries, each library is a directory that has alib file. Sourcing the lib for a library should expose all the functionsthat library offers. The lib file may source or reference other supportingfiles within it's directory.

.
├── libname
│   ├── lib
│   └── supporting-file
├── init # init script, source this first
├── run-tests # top level test script, executes all tests
├── secrets.yml # secrets required for executing tests
├── test-utils
│   ├── bats # git subtree
│   ├── bats-assert-1 # git subtree
│   ├── bats-support # git subtree
│   ├── lib
│   └── tap2junit
└── tests-for-this-repo
    ├── filehandling.bats
    ├── fixtures #
    │   └── libname # Dir containing test fixtures for a library
    ├── tap2junit
    ├── libname.bats # contains tests for libname/lib
    ├── python-lint # supporting files for python lint
    ├── run-bats-tests # script to run bats tests
    ├── run-gitleaks # script to check for leaked secrets
    └── run-python-lint # script to run python lint

Library	Description	Functions
filehandling	Functions relating to file and path handling	bl_abs_path: Ensure a path is absolute
git	Git helpers	bl_git_available: True if git binary or function is available bl_in_git_repo: True if current directory is a git working directory bl_github_owner_repo: returns $owner/$repo extracted from the url of the origin remote bl_repo_root: Find the root of the current git repo. bl_all_files_in_repo: List files tracked by git, excludes submodules. bl_remote_latest_tag: Returns the symbolic name of the latest tag from a remote. bl_remote_latest_tagged_commit: Returns the SHA of the most recently tagged commit in a remote repo (`tag^{}`). bl_remote_sha_for_ref: Returns the SHA for a given ref from a named remote. bl_remote_tag_for_sha: Returns the tag corresponding to a SHA from a named remote - if there is one. bl_tracked_files_excluding_subtrees: List files tracked by git, but excluding any files that are in paths listed in `.gittrees`. bl_gittrees_present: Succeeds if .gittrees is present in the root of the repo, otherwise fails. bl_cat_gittrees: Returns the contents of .gittrees from the top level of the repo, excluding any comments. Fails if .gittrees is not present.
github	Github Related Functions	bl_hub_available: True if hub binary or function is available bl_hub_creds_available: True if hub creds are available (file or env vars) bl_hub_check: Preflight check for hub, true if git installed, in git repo, hub installed and hub creds are available bl_hub_download_latest: Download latest hub binary from github and install to ~/bin or specified path bl_hub_issue_number_for_title: Find the issue number for an issue from its title, searches open issues in the current repo. (current repo = workding directory, repo is found by origin remote). If multiple issues match the supplied title string, only the first is returned. bl_hub_add_issue_comment: Add a comment to an issue bl_hub_comment_or_create_issue: Create issue if an issue matching the title doesn't exist. If a match is found, add a comment to it
helpers	Bash scripting helpers	bl_die: print message and exit 1 bl_fail: print message and return 1 bl_spushd/bl_spopd: Safe verisons of pushd & popd that call die if the push/pop fails, they also drop stdout. bl_is_num: Check if a value is a number via regex bl_retry: Retry a command until it succeeds up to a user specified maximum number of attempts. Escalating delay between attempts. bl_retry_constant: Retry a command until it succeeds with a constant delay between attempts
k8s	Utils for connecting to K8s	bl_build_gke_image: Build docker image for running kubectl commands against GKE. bl_delete_gke_image: Delete image from GKE. bl_run_docker_gke_command: Run command in gke-utils container, already authenticated to k8s cluster.
logging	Helpers related to logging.	bl_announce: Echo message in ascii banner to distinguish it from other log messages. bl_log: Log a message at the specified level. Default log level is info, change level by setting environment variable BASH_LIB_LOG_LEVEL bl_check_log_level: Check if a value is a valid bash lib log level bl_debug: Log a message at debug level bl_info: Log a message at info level bl_warning: Log a message at warning level bl_error: Log a message at error level bl_fatal: Log a message at fatal level
Ruby	Helpers related to ruby infrastructure	bl_gem_latest_version: Return the latest version of a gem from rubygems.org bl_jq_available: Check jq binary is available bl_curl_available: Check curl binary is available
test-utils	Helpers for executing tests	bl_shellcheck_script: Execute shellcheck against a script, uses docker. bl_find_scripts: Find git tracked files with extension. bl_tap2junit: Convert a subset of TAP to JUnit XML. Retains logs for errors. bl_validate_changelog: Check CHANGELOG.md (or a specified file) complies with keepachangelog.com format.

Contributing

For further information on contributing, style & testing, please see CONTRIBUTING.md

Maintainers

Hugh Saunders

使用案例

linux切换oracle用户报错-bash-4.1$ 解决办法

从root用户su -l oralce时不是正常的显示[oracle@soarServer ~]，而是显示成-bash-4.1$，并且使用sqlplus / as sysdba报说没有该命令，最后发现oracle下的 .bash_profile文件被删除，重新建该文件： -bash-4.1$ vi .bash_profile TMP=/tmp; export TMP TMPDIR=$TMP; ex
【mysql】切换到Mysql用户后显示：-bash-4.2$，不显示用户名路径

切换到Mysql用户后显示：-bash-4.2$，不显示用户名路径原因：因安装Mysql是用rpm包的方式安装，mysql用户是默认安装到了/var/lib/mysql目录 [root@mwm skel]# cat /etc/passwd |grep mysql mysql:x:987:982:MySQL server:/var/lib/mysql:/bin/bash 一般在linux下通过us
Ubuntu linux编译alsa-lib报错 automake-1.16: command not found 的解决方案

在编译alsa的时候报错，config完毕后，make错误如下： line 81: automake-1.16: command not found root@sw-desktop:/home/libalsa/src/alsa-lib-1.2.3.2/alsa-lib-1.2.3.2# make cd . && /bin/bash /home/libalsa/src/alsa-lib-1.2.3
总结：进普通用户出现-bash-4.1$的解决方法

1.每个用户都有的配置文件，只对单独的用户有效 .bash_profile：用户每次登录时执行 .bashrc：每次进入新的Bash环境时执行 .bash_logout：用户每次退出登录时执行 .bash_history 保存上次用户注销前使用的命令 [root@station6 tan]# ls -a . .bash_history .bash_profile er .mo
ORACLE 11g 切换到oracle账号显示bash 4.1的问题解决方案

Su – oracle切换过去的时候，发现没有显示oracle@hostname标识，而是显示了-bash-4.1$ ，如下所示： [root@hch_test_pd_121_217 ~]# su - oracle
-bash: /usr/lib/jvm/jdk1.8.0_221/bin/java: No such file or directory

这几天在着手将项目部署到实际的云服务器上本文针对的问题是配置云服务器环境的解决方法，仅供参考针对以上问题，解决方法：使用以下名令前提是：要以root权限执行，若你的身份不是root请看第2点 1.直接处理：命令行输入：apt-get install libc6-i386 2.不是root在线解释以下，租服务器并部署虚拟机，默认我们是有root账户的，但是没有设定密码，故进行如下操作 2.
AIX系统ksh到bash互切

以下切换ksh到bash在攀商行yypt(银银合作)平台测试： 1. #echo $SHELL /bin/ksh #which bash /usr/bin/bash #cd /usr/bin #bash // 执行后提示错误不能切换到bash，错误提示貌似是找不到libintl.so.8，查看/opt/freeware/lib/下有libintl.a，而没有libintl.so.8 2. 下
-bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory（误删 ...

【linux】-bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory linux操作移动了根目录下的/lib和/lib64之后系统使用除了cd之外的任何命令都提示 -bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF
- bash: /usr/bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

问题背景误删系统软链，此时只能使用cd、pwd，其他所有shell命令都不能执行， ssh也不行。注意：此时切勿退出终端！！问题现象 bash: /usr/bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory 问题解决 sln可能也是软链，所以有以下两种恢复方法方法一 /usr
-bash: /usr/bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

问题 [root@ecs-218164 src]# ls -bash: /usr/bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory [root@ecs-218164 src]# clear -bash: /usr/bin/clear: /lib64/ld-linux-x86-64.
bash: /usr/lib/command-not-found: /usr/bin/python3: 解释器错误: 没有那个文件或目录

sudo rm -rf /usr/bin/python3 sudo ln -s /usr/bin/python3m /usr/bin/python3 (python3m 是cd到/usr/bin下ls python* 找的)
-bash: /usr/lib/command-not-found: /usr/bin/python3: bad interpreter: No such fi

1、sudo apt-get install --reinstall python2.7-minimal 3.4 2.可能是一个破碎的系统链接sudo ln -s /usr/bin/python3.4 /usr/bin/python3或类似的位置找到你的python 3二进制文件并链接它。

bash-lib

bash-lib

Release Status: Alpha

License: Apache 2.0

Usage

Structure

Contents

Contributing

Maintainers

同类工具

相关阅读

相关文章

相关问答

相关文档