Changes

Page history
Update Pipeline Notes authored by Slominski, Ryan's avatar Slominski, Ryan
Hide whitespace changes
Inline Side-by-side
Pipeline-Notes.md
View page @ 5ffbb420
...@@ -8,4 +8,6 @@ The `CI_API_TOKEN` CI Variable has the value set to the GROUP_API_TOKEN group to ...@@ -8,4 +8,6 @@ The `CI_API_TOKEN` CI Variable has the value set to the GROUP_API_TOKEN group to
The `CI_PUSH_KEY_VALUE` CI Variable has the value set to `GROUP_PUSH_TOKEN:<Value>` with `<Value>` being the actual value of the GROUP_PUSH_TOKEN. So, unlike the CI_API_TOKEN, the CI_PUSH_KEY_VALUE includes the name of Group Token. The `CI_PUSH_KEY_VALUE` CI Variable has the value set to `GROUP_PUSH_TOKEN:<Value>` with `<Value>` being the actual value of the GROUP_PUSH_TOKEN. So, unlike the CI_API_TOKEN, the CI_PUSH_KEY_VALUE includes the name of Group Token.
# Steps # Steps
Another experimental feature, [Steps](https://docs.gitlab.com/ci/steps/) may make our pipelines easier to understand and more performant. Currently each step is done as a separate job, which can be inefficient. We could potentially collapse many jobs that are really steps into a single job at the cost of a big complex script. Another experimental feature, [Steps](https://docs.gitlab.com/ci/steps/) may make our pipelines easier to understand and more performant. Steps don't appear to be supported on our code.jlab.org install at the moment. A no step_runner found error results when attempting to use.
\ No newline at end of file
So, currently each "step" is done as a separate job, which can be inefficient. We could potentially collapse many jobs that are really steps into a single job at the cost of a big complex script.
\ No newline at end of file