If the $CI_PIPELINE_SOURCE variable isn't 'push', we exit 0.This is a bit confusing, so here it is line by line: What I would do is move this check to the script section so we can make it more complex for our benefit, and either immediately exit 0 so that the job doesn't run and it doesn't fail, or run the rest of the script.
![meshlab 2016 meshlab 2016](http://www.cgchannel.com/wp-content/uploads/2017/01/170103_MeshLab2016.jpg)
Or, if the pipeline is for a tag, it will hold the tag name.įor more information, read through the different Pipeline Sources (in the description of the CI_PIPELINE_SOURCE variable) and the other variables in the docs linked above.
#Meshlab 2016 full
If the commit isn't tied to a branch (ie, there was once a branch for that commit but now it's been deleted) it will hold the full commit SHA. For Push sources where the commit is tied to a branch, this variable will hold the branch name. One variable that will always be present regardless what triggered the pipeline is CI_COMMIT_REF_NAME. However if you create a Git Tag either in the GitLab UI or from a git push -tags command, it will create a Tag pipeline, and variables like CI_COMMIT_TAG will exist, but CI_COMMIT_BRANCH will not. For push pipelines, many of the Predefined Variables will not exist, such as CI_COMMIT_TAG, CI_MERGE_REQUEST_SOURCE_BRANCH_NAME, CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME, etc. Gitlab CI/CD has multiple 'pipeline sources', and some of the Predefined Variables only exist for certain sources.įor example, if you simply push a new commit to the remote, the value of CI_PIPELINE_SOURCE will be push. This is a case where creativity is not particularly rewarded if you want it to work and get meaningful help, my advice is to use the supported hardware architecture and operating system version. You might not even be able to tell when things aren't working as they should. Linux being what it is (flexible), lots of people have gotten the images to run on other flavors like Ubuntu with a bit of creativity, but only on x86 processors and even then the results are not guaranteed by Oracle: you won't be able to get support or practical advice when (and it's always when, not if in IT) things don't work as expected. The referenced My Oracle Support Doc ID goes on to say that the database binaries in their Docker image are built specifically for Oracle Linux hosts, and will also work on Red Hat. For more details please see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1) is supported for Oracle Linux 7 and Red Hat Enterprise Linux (RHEL) 7.